Open Python-Exoproject opened 3 years ago
exoscoriae
commented
3 years ago it is impossible to do a save game transfer in a bootable image. So that is off the table with this method. The save game would have to be located and then inserted into the bootable image.
This one is going to take some time, as I'll have to create an entirely new VHD for it. Unless we don't use a full install.
exoscoriae
commented
3 years ago set up using the VHD you put together.
added notes listed above.
no idea how to test the midi is working as intended other than to say, there is music
Python-Exoproject
commented
3 years ago This game is driving me nuts. Two things, one minor and one major.
One last oversight in regards to res, I caught that this one needed fullresolution=0x0 which is done now but missed that it also needs windowresolution=640x480 not 800x600. My bad, sorry for that one.
When you run the game, add characters, and start new game its giving "Unable to open movie" error. As I know it was working when I uploaded it to the sync last year I tried reinstalling it again in case something weird happened. Uninstalled the game inside the VHD, reinstalled using a medium install, ran the game when it was done. Sweet, everything worked again and I could get all the way into the game with no issues. Quit the game and close Dosbox, restart it again for a test, "Unable to open movie". What the hell can cause that? My only thought is a full install so that it wont need to read movies from the CD but a) it worked that first time straight after install, and b) you said its not straight forward to get a VHD that big. Thoughts?
exoscoriae
commented
3 years ago Let me see what I can do....
exoscoriae
commented
3 years ago @Python-Exoproject Ok. I made an 850mb image. The deal is, dosbox can't handle more than 1024 cylinders for a hard drive. Anything larger than about 504mb goes beyond this. So... it's not incredibly hard to do, it just takes time. You have to make the larger drive, and then multiply the heads by the same factor you divide the cylinders. bximage can't do this naturelly, so it all has to be done in the original file mount when you first format the drive in dosbox.
The short of it is, I got it to work. It wasn't too hard once I sat down and just pushed through it. From there, you have a fresh image. So I installed DOS 6.22 to it, then windows, then sound, video, and cd drivers.
Anyways, after all that - take a wild guess at what happened when I started the game for the first time?
"Unable to open movie"
exoscoriae
commented
3 years ago Ok. I continued cranking on it. The version I am uploading, I started three separate times. And it worked all three times. I was able to start the game, add characters, start new game, watch intro movie.
I didn't go beyond that however
Python-Exoproject
commented
3 years ago Confirmed, all working now. What did you do to fix the movie error?
This is probably the best this turd of a windows version has ever run. Only thing now to consider for a future release is if\how to transfer savegames from an exodos copy of Wizardry V, especially now that its in a VHD.
exoscoriae
commented
3 years ago brain transplant surgery. I got the game installed on a non VHD copy, got it running there. then copied those files into the vhd. copied more files from the CD to the main drive, modified the games ini file, and then hired a small tibetan boy to pray the entire time.
VHD save game transfers are impossible as far as I'm concerned. There is a slight chance I could try copying them to a folder and mounting that folder as a floppy that then gets passed through the ide. however I don't hate my life enough yet to jump down that rabbit hole.
Python-Exoproject
commented
3 years ago No problem, Ill put it in the low priority hold pile due to the savegame thing, but I agree it will be a long time coming.
We established that the best way to avoid the Win32s error and general instability in this game is to install in a bootable image.