xdaniel

Not in the near future, for various reasons. Maybe in some future version, but no guarantees about that.

Small changes to individual file mode as per petrie's suggestions: It now automatically selects the first stage/object set in the tree, the scene open dialog now has filters for *.zscene and *.*, and the room open dialog has filters for *.zmap/*.zroom and *.*. Also changed room vertex selection; right-clicking a polygon's vertex now shows a pop-up menu with options to change its color and display its properties. Need to write up another preliminary changelog for Beta 9, I think; got bunch of small changes and fixes, a few new features...

It's quite big in comparison - especially compared to, say, a modern barebone or even just a "normal" desktop -, but I feel like I'm used to them. My first PC was a big tower like this, the 486DX2-50, my trusty Athlon Thunderbird 1.4 @ 1.0 GHz (RIP) was one, so... yeah. Also, it's true that this machine's in really nice shape. I hadn't even cleaned it up much; it just had some spots of dirt on the outside, and there's still some dust on the inside, as you can see in the photos. And yeah, we do use 230V over here. In your case, I'm guessing that machine set to 230V simply didn't get enough power, so that it didn't even get the chance to damage anything. Don't quote me on that, tho, I'm not an electrician EDIT: In fact... have two ancient photos (pre-2006) I found when backing up my old LiveJournal blog a week or so ago. This was my old Athlon TB: ...and yes, that's the same Logitech keyboard I'm now using on the P100 Now, after a few days of working with this machine here, there are a few faults I've noticed despite its overall good condition: First, the CMOS battery doesn't seem to be holding up very well anymore. Problem with that being, it uses one of those old Dallas RTCs. I haven't looked at it closely yet, so I don't know the exact type of chip, nor if it's socketed or soldered on, nor if there's compatible replacements still being made. I know you can hack the original chip and add a new battery, but I'd prefer not to have to try that. Second, the CPU fan is very noisy and seems to get stuck sometimes. This is probably easier to replace than the RTC, I just need to get a new fan of the same diameter and especially height - because it's really close to the 3 1/2" drive cage - and solder it up to the original cable to the PSU. Finally, I've found another system information tool, this time for DOS and from... *drumroll*... the year 2010! The thing's called Navratil Software System Information, is freeware and... identified my mainboard perfectly fine as - wanna guess? - an Abit PK5! All my detective work was for naught! <.< ...okay, it wasn't really, because I found that diagram and jumper settings, and I could get 48 MB of RAM working on it because of that. Also, if you're curious, here's the output that program's report function produced for the P100. EDIT 2: Desktop!

Heh, I've actually heard of uxwbill, I think I friend of mine introduced me to his channel. I haven't seen very many of his videos yet, tho. I really like RetroJunkie's videos (channel RetroJunkie2020, I think), although they're more console- and more specifically Sega-centric - his repair/restoration videos on the Aiwa Mega CD (a boom box with integrated Mega Drive/Genesis and Mega/Sega CD) and the Sega Saturn Sophia (early Saturn development kit) in particular are really interesting. I haven't replaced bad caps before, but I do have some things that need new caps... My old GeForce 8500 GT, for example; that thing has seven caps on it, five of which are blown. I might also still have the old Super Socket 7 mainboard from my AMD K6-2+ (450? 500? I forgot) days, which also had bad caps the last time I saw it, some five or so years ago. That was a... Shuttle HOT-591P, I believe. Would be nice if I still had that board and could replace the caps on it, I'd love to get a K6-type machine up and running again. Back to the P100: Haven't made a video about it yet, but here's some photos of it and its innards: The whole mess as it is right now, haven't put the system back together yet; also in the picture, the backside of my Adaptec AHA-1542CF, and the other RAM. Also the kinda inappropriate for the timeframe Samsung SyncMaster 570B and Logitech Corded iTouch keyboard (Y-BC9), September 2000 and ca. 2001/2002(?) respectively: Side view of the opened tower: Close-up on the cards inside, from top to bottom: V7-Mirage video card, PCI IDE controller, RTL8029 LAN, ISA multi I/O and ESS 1868F sound card: Another close-up on the cards; as above, just from right to left: Area around RAM slots, above the top PCI slot. The two rightmost sticks are the 2x 16 MB, the other two are 8 MB each: Close-up on CPU, cache and chipset: The Tekram DC-290N PCI IDE controller in all its glory: Front panel of the tower; MHz display, HDD and turbo LEDs, turbo and reset switches, power switch and LED: The MHz display without flash, so that it's actually readable. Would be kinda cool if my desktop said "2x3450" The tower front's upper half: And the tower's rear, as well as the plastic cover that goes above the screws and exposed metal when closed up: Ports close-up, from top to bottom: VGA (video card), stereo audio out (on PCI IDE controller, intended for CD audio, apparently), LAN, serial ports (25-pin and 9-pin, on multi I/O), parallel port and gameport (multi I/O), gameport and audio jacks (sound card). The labels for LPT1, COM2 and COM1 were already incorrectly placed when I first got the system, btw, so I assume it had been upgraded at least once before: Went overboard with the descriptions maybe

I never posted another photo of that painting of Log Horizon's Akatsuki like I said I would... ...here it is, now hanging in my living room! Well, since ca. two weeks ago actually, which is when the photo was taken.

Implementing Nini was really easy: Copypasta'd and modified/simplified an example class from Stack Overflow, manually added all the properties previously managed by Properties.Settings, then did a mass replace in the project from "Properties.Settings.Default" to "Configuration". The resulting Configuration class as of right now: using System; using System.Collections.Generic; using System.Linq; using System.Text; using System.IO; using Nini.Config; namespace SceneNavi { /* Based on http://stackoverflow.com/a/15869868 */ static class Configuration { static readonly string ConfigName = "Main"; static string configPath; static string configFilename; static IConfigSource source; public static string FullConfigFilename { get { return (Path.Combine(configPath, configFilename)); } } public static bool RenderRoomActors { get { return (source.Configs[ConfigName].GetBoolean("RenderRoomActors", true)); } set { source.Configs[ConfigName].Set("RenderRoomActors", value); } } public static bool RenderSpawnPoints { get { return (source.Configs[ConfigName].GetBoolean("RenderSpawnPoints", true)); } set { source.Configs[ConfigName].Set("RenderSpawnPoints", value); } } public static bool RenderTransitions { get { return (source.Configs[ConfigName].GetBoolean("RenderTransitions", true)); } set { source.Configs[ConfigName].Set("RenderTransitions", value); } } public static string LastROM { get { return (source.Configs[ConfigName].GetString("LastROM", string.Empty)); } set { source.Configs[ConfigName].Set("LastROM", value); } } public static bool RenderPathWaypoints { get { return (source.Configs[ConfigName].GetBoolean("RenderPathWaypoints", false)); } set { source.Configs[ConfigName].Set("RenderPathWaypoints", value); } } public static bool LinkAllWPinPath { get { return (source.Configs[ConfigName].GetBoolean("LinkAllWPinPath", true)); } set { source.Configs[ConfigName].Set("LinkAllWPinPath", value); } } public static bool RenderTextures { get { return (source.Configs[ConfigName].GetBoolean("RenderTextures", true)); } set { source.Configs[ConfigName].Set("RenderTextures", value); } } public static bool RenderCollision { get { return (source.Configs[ConfigName].GetBoolean("RenderCollision", false)); } set { source.Configs[ConfigName].Set("RenderCollision", value); } } public static bool RenderCollisionAsWhite { get { return (source.Configs[ConfigName].GetBoolean("RenderCollisionAsWhite", false)); } set { source.Configs[ConfigName].Set("RenderCollisionAsWhite", value); } } public static bool OGLVSync { get { return (source.Configs[ConfigName].GetBoolean("OGLVSync", true)); } set { source.Configs[ConfigName].Set("OGLVSync", value); } } public static SceneNavi.ToolModes LastToolMode { get { return ((SceneNavi.ToolModes)Enum.Parse(typeof(SceneNavi.ToolModes), (source.Configs[ConfigName].GetString("LastToolMode", "Camera")))); } set { source.Configs[ConfigName].Set("LastToolMode", value); } } public static string LastSceneFile { get { return (source.Configs[ConfigName].GetString("LastSceneFile", string.Empty)); } set { source.Configs[ConfigName].Set("LastSceneFile", value); } } public static string LastRoomFile { get { return (source.Configs[ConfigName].GetString("LastRoomFile", string.Empty)); } set { source.Configs[ConfigName].Set("LastRoomFile", value); } } public static SceneNavi.CombinerTypes CombinerType { get { return ((SceneNavi.CombinerTypes)Enum.Parse(typeof(SceneNavi.CombinerTypes), (source.Configs[ConfigName].GetString("CombinerType", "None")))); } set { source.Configs[ConfigName].Set("CombinerType", value); } } public static bool ShownExtensionWarning { get { return (source.Configs[ConfigName].GetBoolean("ShownExtensionWarning", false)); } set { source.Configs[ConfigName].Set("ShownExtensionWarning", value); } } public static bool ShownIntelWarning { get { return (source.Configs[ConfigName].GetBoolean("ShownIntelWarning", false)); } set { source.Configs[ConfigName].Set("ShownIntelWarning", value); } } public static bool RenderWaterboxes { get { return (source.Configs[ConfigName].GetBoolean("RenderWaterboxes", true)); } set { source.Configs[ConfigName].Set("RenderWaterboxes", value); } } public static bool ShowWaterboxesPerRoom { get { return (source.Configs[ConfigName].GetBoolean("ShowWaterboxesPerRoom", true)); } set { source.Configs[ConfigName].Set("ShowWaterboxesPerRoom", value); } } public static bool IsRestarting { get { return (source.Configs[ConfigName].GetBoolean("IsRestarting", false)); } set { source.Configs[ConfigName].Set("IsRestarting", value); } } public static int AntiAliasingSamples { get { return (source.Configs[ConfigName].GetInt("AntiAliasingSamples", 0)); } set { source.Configs[ConfigName].Set("AntiAliasingSamples", value); } } public static bool EnableAntiAliasing { get { return (source.Configs[ConfigName].GetBoolean("EnableAntiAliasing", false)); } set { source.Configs[ConfigName].Set("EnableAntiAliasing", value); } } public static bool EnableMipmaps { get { return (source.Configs[ConfigName].GetBoolean("EnableMipmaps", false)); } set { source.Configs[ConfigName].Set("EnableMipmaps", value); } } static Configuration() { PrepareConfig(); source = new XmlConfigSource(FullConfigFilename); source.AutoSave = true; CreateConfigSections(); } static void CreateConfigSections() { if (source.Configs[ConfigName] == null) source.AddConfig(ConfigName); } static void PrepareConfig() { configPath = Path.Combine(Environment.GetFolderPath(Environment.SpecialFolder.ApplicationData), System.Windows.Forms.Application.ProductName); configFilename = String.Format("{0}.xml", ConfigName); Directory.CreateDirectory(configPath); if (!File.Exists(FullConfigFilename)) File.WriteAllText(FullConfigFilename, "<Nini>\n</Nini>\n"); } } }

General: I'm not sure if SceneNavi's structure would allow for undo/redo functionality. I'll need to take a closer look at this. First your select a triangle in "static object mode", then you can click on one of its vertices. However, that currently only allows changing its color and doesn't ex. show the vertex's coordinate, which is what you'd need, I assume. I hadn't thought about that this might be needed before, so I'll have to implement that for the next version. Individual scenes: Yeah, I didn't think of individual scenes when adding the room drop-down a while ago. Will need to look into this... Will do that for individual file mode, makes sense there, yeah. .zscene and .zmap I'm a bit torn about. One on hand, they're the de facto standard, on the other, .zmap should be .zroom for accuracy's sake and some extractors don't adhere to this convention (i.e. OZMAV2 doesn't assign extensions). What's everyone's opinion on this? As for localization, I've dabbled in that before but haven't really worked in that direction seriously. Will need to look into that more, as well as Transifex, etc. As for that seam in the Spirit Temple boss screenshot, it's visible in-game too, just like a few in other places (ex. Deku Tree): In other news, Nini-based configuration storage will be in Beta 9. It's still using XML files for storage, now stored at (on ex. Windows 7) "C:\Users\<username>\AppData\Roaming\SceneNavi\". Well, technically "[Environment.SpecialFolder.ApplicationData]\[system.Windows.Forms.Application.ProductName]\" and thus not hard-coded, so as long as Mono has those implemented properly, the configuration path stuff should work fine. And as long as Nini itself works right in Mono, configuration storage in general should finally work right under Linux. Example:

Oh man, Windows XP at anything less than 512 MB RAM is a pain to use. At one point years ago, my mom's PC's memory died (or was faulty from the start, I don't remember), so I had to lend her one of my two 256 MB sticks. We were both running XP back then, and both of our machines struggled visibly with that little memory. As for the P100 here now, I haven't done anything with it today - was all over the city in the afternoon, had to pick a package up at customs, etc... -, besides digging up another longer LAN cable and putting a small 5-port switch between my main desktop and the LAN cable. That way, I can get onto the network from there instead of having to kinda lay a cable right across the room to reach the router. I'll take more pictures of the machine and the insides once I get the chance. I actually wanted to document this "restoration" project on video and upload it to YT, but once I started working on it, I kinda got carried away... *cough*

I assume that's actually for actor 0x0169 and not 0x015F (considering the type attribute), but regardless, that definition is working fine for me in Beta 8 and Beta 9 WIP:

Incoming PSP goodness: Have yet to try LocoRoco, but those copies of Digimon World Re:Digitize and K-ON! Houkago Live!! (the latter I mentioned before) are replacing my ISO images of those. ...or, well, K-ON! does but Re:Digitize's UMD cannot read the saved data I created using the ISO...

Been looking around trying to identify my mainboard for good. While I couldn't find Everest, formerly AIDA32, for Windows 3.11 - it appears to be some 10 years too young for that - I remembered Dr. Hardware, another hardware information tool that was around during the late 90s. A lot of searching and crawling the Internet Archive later, I found a 32-bit version of it that does run (mostly) under Win 3.11 via the Win32s extension. That confirmed that the board is indeed an ABit/Silicon Star International, but couldn't tell me much else. Then I ended up searching for more information about the Abit PK5 I assumed it is, or is closely related to, based on that BIOS string. That way, I found this site here, with diagrams and jumper settings for a lot of boards. Comparing those diagrams with the jumpers I can see on my physical board, it appears to be very close to the "PK5 (REV. 1.1)" listed there... but the chipset doesn't match; mine has an SiS 501-503, that one has an OPTI of some kind. That said, there's a set of DRAM configuration jumpers listed on the site, where you have to select the correct configuration depending on where there's single-sided and/or double-sided RAM sticks in your system. That's something else that I vaguely recalled while looking this up, that single-sided and double-sided SIMMs can make a difference. So, I ended up switching the jumpers around, and put those other two 16 MB sticks in... didn't work. Well. Tried the next smaller sticks, the two 8 MB sticks... and success! 48 MB of RAM, or 49152 KB! I also noticed the section about the CPU speed configuration jumpers and tried to mess around with those a bit, and while I couldn't overclock this particular CPU to 120 or 133 MHz - it just stayed at 100, apparently -, I could underclock it to 90 MHz. I guess if I'd come across a 120 or 133 MHz Socket 5 Pentium somewhere, I could use it in this machine as long as I set the jumpers correctly. Heh, I had almost about having to set CPU speeds manually on the board... we're really lucky nowadays with the CPU speed being configurable from the BIOS and such. Finally, after even more searching and Internet Archive browsing, I even did find what appears to be a BIOS update for the PK5... although which PK5, I do not know. The "2A5IAA11" part of the version string matches, it's about half a year younger than the BIOS I've got installed (06/20/95 vs 12/30/94 on mine), but beyond that... I'm really not sure. Neither am I sure if I should even try to update the BIOS at this point, seeing how I did get at least those two 8 MB RAM sticks working.

Gigantic Stalchilds sound familiar: http://z64.spinout182.com/index.php/topic,33.0.html

Hehe, this is my first time dealing with a whole secondary IDE controller, too. I only ever had one of those ISA multi I/O cards per machine before, or everything on-board later on... That said, I'm not very sad about Windows 95 not working right - I haven't really used Windows 3.x since... my last PC that came with Windows 3.x? Which IIRC was a Pentium 75 of some kind, I don't think I had that one very long. So I'm fine with getting back into 3.11 here. Windows 3.11 here, and this machine in general, remind me of my first PC too: forgetting some details here, but it was a 486DX2 with 50 MHz, 24 MB RAM, some sort of SVGA video card (that I never bothered to get Windows drivers for), and an Adaptec AHA-1542B SCSI controller with two huge 800 MB IBM hard disks! "Huge" in two respects even, the capacity and the size - one was as high as two regular 5 1/2" drives, so stack four CD-ROM drives on top of each other and you get the idea XD As far as I can remember, we were told it was some sort of server system before, which explains the SCSI card and HDDs. Think I got it in... 1997 or thereabouts? Didn't even come with a CD-ROM drive, btw, but I later got a TEAC CD-532S (IIRC) for my birthday or somesuch - one of the best drives I've ever had, too, as it had some great error correction. Read pretty much every CD I fed it, no matter how scratched up it was. The mouse problem is a curious one. I know the mouse works because I used it on said ThinkPad before, I don't know if the adapter works... Hm, let me see if my "disk fabricator" (aka my old Dell Latitude C640 laptop I've been using for writing the floppy disks) recognizes the mouse via the adapter on its serial port... ... ...nope, no dice. Rebooted and specifically set the laptop's BIOS to serial mouse - disables PS/2 and integrated touchpad -, but Windows (XP SP2) didn't recognize nor respond to it. Changed that setting back, put mouse into PS/2 port, and bam, it works fine. Doesn't work via serial in PS/2 and touchpad mode, either... The BIOS I'm not sure if I can update, because I'm not even 100% sure about the board's model nor manufacturer. Again, the version string shown on startup points to it being an ABit PK5 - chipset given and "2A5IAA11" match this description, but there's no marking or anything on the board that would confirm this. It's actually an Award BIOS, too, not Phoenix or AMI... And btw, I noticed earlier that it has the infamous Y2K bug! Or a sort of variation thereof anyway, because if I enter 2014 as the year in the BIOS, it ends up as 2094 after saving and restarting. And the RAM would've been a little extra something for the machine - just think, a Pentium 100 with 64 MB RAM! Whoa!! I had that in my Cyrix MII 333 MHz back in 1999/2000 or so, if I remember correctly! - but it's no problem that it isn't working. Now that you mention it, I do remember there being differences between EDO- and I guess FPM-type RAM, so that might be the issue... I did remember to put them in in pairs, at least. But yeah, it's pretty fun to work with those old systems, and especially old PCs (i.e. less than, I dunno, 500 MHz) I haven't done much with recently. I mean, I have my Amiga 500 that I want to upgrade some more, but that's a whole different beast... plus a pretty expensive one, if you want ex. an accelerator board, or even an IDE or SCSI controller. Also have that ThinkPad I mentioned - Pentium MMX 166 MHz, 80 or so MB RAM, Windows 98 SE, etc. - but I'd consider that comparatively modern, compared to a Socket 5 Pentium running DOS and Windows 3.x

About Windows 95's errors during setup, it could imagine that it's unable to cope with the PCI IDE controller somehow... The system has two IDE controllers: one on the typical ISA multi I/O card you'd have in many pre-Socket 7 systems (very similar to this one, almost the same chipset in fact), the other is a dedicated PCI E-IDE controller, the Tekram from the first post, which also has a small daughterboard that plugs into the end of a 16-bit ISA slot. There's no on-board I/O, outside of the AT keyboard connector and obviously the PCI and ISA slots. The main IRQ-related thing I had to change in the BIOS, was for where the PCI IDE interrupt should be mapped to. If I left this on "PCI-AUTO" or any other "PCI-" setting, the BIOS would never proceed beyond the memory test, so I had to change it to "ISA" - presumably so that the interrupt could reach that daughterboard, and in turn the PCI IDE controller. Also, even though that was the original hardware configuration when I got the machine, I couldn't get the CD-ROM drive to be recognized if it was left on the ISA IDE controller, which is why I switched that over to the other IDE, too. Also, further adventures to report: I actually did have a PS/2 mouse all along - in fact, I used it with my Pentium MMX ThinkPad before! The problem is, tho... it doesn't get recognized at all. Neither Microsoft's DOS driver, nor the CuteMouse DOS driver, nor any of Windows 3.11's drivers work. In fact, CuteMouse's COMTEST.COM (which lists all COM ports and things attached to them) doesn't see anything attached to either port when the mouse is plugged in. The ports appear to be configured correctly and get recognized in the BIOS, by COMTEST.COM and by good old MSD/Microsoft Diagnostics. I also happened to have another 9-pin COM port to attach to the I/O card, which didn't change a thing. So... I'm guessing the PS/2-to-serial adapter might be busted? Oh well... no Warcraft 2 tonight! (And I realize I could just play Warcraft 2 in DOSBox or somesuch, but... where's the fun in that?) Next up, networking, again. Functionality is still pretty limited, but at least I seem to be able to bring up the network reliably now. Previously, I'd have intermittent problems ex. connecting to the network in the first place. Now... I've switched the LAN cable - and even the "broken" port on my router is working again. So, yeah, I think it's pretty likely that the other cable is bad. Oh also, while looking for the mouse, I also happened to come across some ancient EDO RAM sticks, wrapped in tape, with handwritten labels stating their sizes! I don't even remember when I packed them up, it must've been around 2000 or thereabouts... However, problem: only the two 4 MB sticks would work on the Pentium's board. The two 8 MB and two 16 MB sticks either don't work at all, only come up with less total memory than they should, and/or don't work together with the existing 32 MB RAM. Maybe some of them are bad, maybe they aren't compatible with the board, I'm not sure. Regardless, I've at least got the two 4 MB sticks in, bringing the memory up to 4 sticks in 4 slots, totalling 40 MB.

Long story, WALL OF TEXT actually, but maybe interesting if you're interested in old PCs. So, there's this PC I was given for free on Saturday. Like so many old electronics these days, it was supposed to be trashed, because it wasn't of use to its owner anymore. That said, for this particular PC, I can understand that mindset - it's just under 20 years old: Intel Pentium 100 MHz, Socket 5 ABit PK5 Socket 5 mainboard or similar (presumably; no markings on board, just BIOS strings to go by) 32 MB EDO-RAM (2x 16 MB) SPEA/V7 Mirage P-64 video card, S3 Trio64 chipset, 2 MB RAM 16-bit ISA I/O controller (floppy, IDE, serial, parallel, gameport) Tekram DC-290N PCI E-IDE controller 1.2 GB IDE hard disk Quad-speed IDE CD-ROM 3.5" floppy AT Big Tower case w/ 200W PSU ...while I ended up adding: Realtek RTL8029-based PCI LAN card ESS AudioDrive 1868F 16-bit ISA sound card First things first, I had to wipe the hard drive. That was more or less a requirement, because the machine belonged to an acquaintance (or somesuch) of a good friend, and there was still old but personal data on it. I also looked up drivers, manuals, etc. online for as many of the components I could find. So, HDD wiped, machine cleaned, additional cards installed... and then I had to fight with the BIOS to work properly with the PCI IDE controller, the ISA one, and respectively the HDD and CD-ROM drive. Turns out I had to change one IRQ-related setting, so that the PCI card correctly receives certain IRQs. And to prevent even more potential IDE-related headaches, I ended up hooking up HDD and CD-ROM to the same controller, the PCI one, leaving the one on the I/O controller unused. Next up, I went and installed Windows 95... or, well, at least I tried to. It couldn't get very far in the setup process, dying with floating-point unit errors or just giving up altogether without any messages at all... so I decided on MS-DOS 6.22 and Windows 3.11. Fabricated the three DOS setup disks, using some of the only working floppy disks I still have around - and those are over 10 years old, too! - and got a barebones copy of DOS installed. Afterwards, I borrowed the good old Oak Technology CD-ROM driver from a Windows 98 boot disk, put that onto the HDD, started getting re-accustomed to CONFIG.SYS, AUTOEXEC.BAT and co., and a reboot later, I had a working CD-ROM drive. And that drive is how I installed Windows 3.11 - and now I hear you scream, or those who're familar with Windows 3.x and such - "But was that ever on CD-ROM?" ...actually, I don't know for sure, but I don't think it came on CD from Microsoft. However, I do have an original setup CD from some manufacturer's PC, which has DOS, Windows 3.11 and Works 2.0 on it. The DOS is useless tho, as that requires setup from floppy disks... or that's what the setup told me, anyway. As Windows was installing, I tried copying the LAN card's drivers onto another floppy disk, for Windows Setup to, uh, install during, well, setup. But that didn't seem to work - all I ever got were read errors, even though ex. WinImage could write (and verify!) a disk image onto the disk... I left networking aside for the moment, to get Windows going. In the meantime, I put together a collection of drivers, DOS and Windows tools, as well as Windows 3.1 and 3.11 itself, to burn onto a CD and use to set this machine up. Once Windows was done installing, I first tried to get the proper video drivers set up. First set of drivers detected the card fine, installed properly, then I went to increase the resolution... and was met with a "frequency out of range" from the monitor I'm using (Samsung SyncMaster 15" TFT). Had to shutdown, then edit SYSTEM.INI manually to replace the driver with the default VGA one, then restart Windows once more - back to 640x480 VGA we went. More fiddling around with the driver didn't give much better results... or well, I did get 800x600 going, but nothing higher. And there's been an even more severe problem, too: any DOS application would cause the monitor to go "VGA cable not connected"! Including the freaking DOS Command Prompt! ...out that driver went. In went the second one I had found... which turned out to be a few versions newer - like 1.x versus 2.4 or something, in fact. And this one even worked perfectly first try - resolution up to 1024x768 at 16-bit color and 60 Hz, no problems with DOS applications, etc., etc. The sound card was next, and as equally painless as the second video driver was. There might've been one mishap or two, again with regards to IRQs, but overall I got sound working quite quickly. Now, networking... this was a real pain in the ass to get to work. Installing the drivers, installing the TCP/IP stack (that was separate back then!), configuring everything, trying to connect to my router... then finding that apparently one of the LAN ports on said router is broken... then trying to set file sharing up to transfer data, etc... In the end, it's basically working. Using a static IP - because DHCP doesn't seem to work - I can ping across the network, have my normal desktop move files into a shared folder on the Pentium, can access my Thin-Client-turned-server's FTP, pretty much all I want to do, really. I think all that was left to do at this point, was installing all the tools and such that I wanted... or well, I actually haven't installed very many of them yet, just a few essentials like the Norton Commander for DOS. I've also copied over and/or installed a few games, namely Doom, SimCity 2000 and Warcraft 2, even though... I don't have a mouse yet. Yeah, I've installed and used Windows 3.11 with just the keyboard. I have a PS/2-to-serial adapter but not actually a PS/2 mouse I could use here - at least I don't think so, but I guess I'll need to go through my spare parts in the basement. Well, uh, it's getting late (1:08 am late, which means getting up in... less than 5 hours), this is getting long, so to round this out, here's a few pictures of the beast!

As usual, I'm jumping between projects, and right now I'm working on SceneNavi more. This here isn't forgotten, this isn't abandoned, I said it'll be January for a first release, and it's going to be that. When exactly in January I cannot say, but probably this week for a preliminary "not that user-friendly but working" release. And just wondering, is there really not a single other thing you can do in your hack right now, besides fixing Unicat?

Oh man, so many posts... I might be misremembering here, but you don't mean that header setting or whatever it was you said was responsible for the errors, right...? Because that wasn't it. Mind pointing me to your solution again, now that I actually am working on a converter again? The location of your Besitu file(s) changed. SceneNavi reads in the DMA table, the filename table, then, when it's reading the scene table, for each entry there it tries to find an entry in the DMA table with the same scene start address, and if it finds one, it uses the filename from that as the scene name. The scene table entry for your Besitu points to a different address than the original Besitu entry in the DMA table, so there's no matching DMA table entry anymore, so it can't fetch a filename from there. My picking code kinda sucks, so there's definitely the chance for bugs to be in there. I'll look at my code again, double-check if it's sane, then try to hunt around for potentially related Mono bugs... Hmm, might be an idea to do both, calculate the shift count using your function by default, but allow an optional attribute in the definition to override it? Just to be safe, I guess. Uh, hope I didn't forget anyone/anything I wanted to comment on right now...

Airikita: Because the filename table maps one-to-one to the DMA table, I have to use the latter to determine filenames, so if you've not modified that, you won't get the proper name displayed for your file. Also, any particular reason why you're still using Beta 2? That's extremely out of date... I really shouldn't even take bug reports for builds this old (even though this particular behavior hasn't changed since) mzxrules: Is automatically detecting the shift count reliable under all circumstances (i.e. any potential mask value, etc)? If so, I could do it this way, instead of adding a MaskShift attribute or somesuch. Btw, you've seen my previous post, ex. about the Usage attribute? I'll get to more feedback to your, uh, feedback about the system later.

Very quick initial thoughts about the actor definitions and mzxrules' comments, more over the weekend. The Usage attribute is optional as in, it defaults to "Generic" if the attribute is not found in the definition. If it is defined, it has to be set to one of the values SceneNavi understands because the known Usages are an enum, otherwise it'll throw the exception as Enum.Parse fails. I should probably make that Enum.TryParse and have it disregard the attribute if its value is unknown/invalid, and have it fall back to "Generic" in that case. Known Usages are: Yes, the situation with masks and bitshifts is a bit of a problem... and I'd prefer to add another attribute, "MaskShift" or somesuch, that stores how many bits the mask is shifted instead of trying to calculate it on-the-fly. Feels less error-prone as long as the definition is correct. The attribute would just be an integer and would be optional; if it's missing, the shift count defaults to 0. Anything else, as mentioned, I'll look over and try to comment on during the weekend.