ToxicFrog on 30/9/2005 at 21:53
Check it against the md5sums I posted?
Enchantermon on 1/10/2005 at 16:08
Quote Posted by ToxicFrog
Check it against the md5sums I posted?
No need.....(I wouldn't know how, anyway :p)
Okay, this is really weird. I tried to load my game in SS1, and the monitor switched off, just like it does when I try to go to the higher resolutions. :weird: Odd. So, I ran ss1hr.exe and remapped 640x480 to 640x400. I didn't think to check what is was currently mapped to, becuase it
should have been mapped to 640x480. I go back to the game, everything's fine. Even the boundaries on all four sides of the screen (remember, I had the boundaries set to the 640x400 setting). Then, I exited, and ran ss1hr.exe again. That's when I realized that the 640x400 button had somehow
mapped itself to 800x600! I
know I didn't do it. I can only assume that 640x480 had also been mysteriously mapped to either 800x600 or 1024x768. But, I re-mapped it to 640x480, set the MOUSE2KV variable to 640x480, and everything worked perfectly! The boundaries are all correct, the mouse isn't going off of the bottom of the screen in-game, and I have nice, 640x480 graphics. I have no idea what happened, but apparently the problem fixed itself. :weird:
Enchantermon
FiveFingerDiscount on 1/10/2005 at 21:00
The 1280 DOS-version doesn't seem to work properly... selecting 640x480 in-game makes it actually run at 640x480, while selecting 640x400 in-game makes it run at 1024x768.
ToxicFrog on 2/10/2005 at 00:51
Quote Posted by FiveFingerDiscount
The 1280 DOS-version doesn't seem to work properly... selecting 640x480 in-game makes it actually run at 640x480,
This behaviour is intended. None of the DOS versions override 640x480.
Quote:
while selecting 640x400 in-game makes it run at 1024x768.
Oops. 154, not 144. Fixed, re-download for 1280x1024 goodness.
FiveFingerDiscount on 2/10/2005 at 17:52
Um, now the 1280 crashes when I select 640x400 (ie: 1280x1024), with a Salt the Fries error, followed by "Page fault", then a load of registers I *really* hope you don't need me to copy out... That's if I change resolution after starting a new game. If I change resolution after loading a saved game, it gives those errors, plus: "DOS/4GW Professional error (2001): exception 05h (bounds) at 180:00000008 TSF32: prev_tsf 6B18". I've reproduced the error several times.
Help? :confused:
ToxicFrog on 2/10/2005 at 18:03
Could you give me the value of the EIP register?
Bear in mind, I may not be able to do anything - I can't test the DOS version, I can't even run it except in DOSBox, which behaves oddly in SVGA even with the unmodified version. It's possible that 1280x1024 simply doesn't work in the DOS version.
FiveFingerDiscount on 2/10/2005 at 19:59
EIP: 00531fbc
Shadowcat on 3/10/2005 at 04:58
A tip to avoid copying and pasting error messages:
Edit cdshock.bat to read:
"[...]\cdrom\cdshock.exe >errlog.txt"
then when the game crashes, it will output the error message into the file "errlog.txt" instead of to the screen.
ToxicFrog on 3/10/2005 at 11:51
Quote Posted by FiveFingerDiscount
EIP: 00531fbc
FOAM IN MY BRAIN
That is to say, I have no idea what's going on there. :weird: Nor do I know how to fix it.
descenterace on 3/10/2005 at 13:09
Quote Posted by ToxicFrog
Now I'm wondering why SS1 is talking to the serial ports at all. I mean, did they build a serial mouse driver into the game?
That'll be the DOS/4GW extender. The DPMI interface is a Protected Mode app's only contact with the hardware (unless it uses the Real Mode call gates supplied by the extender) and it basically grabs all the hardware when it's activated. I think it does an inventory of what's available as the app loads.
