ToxicFrog on 29/9/2005 at 04:01
...wow. I'll look into this.
I take it that it's the original you're using, not Mok's...I wasn't able to test that on mine, because it doesn't run in the first place on 2k. Most likely answer is that I made a mistake in the signature for that and it's trashing something it shouldn't be.
[Edit]
I can't reproduce this - the game starts up fine and even plays the intro. It errors out when I try to start or load a game with "not enough memory to create email cursor", but that's normal for the DOS version on 2k.
I also tried it in DOSBOX, and in that I was able to actually get into the game, running the pure DOS version at 800x600 and 1024x768. Unplayably slow, of course, but stable.
Do the v1 highres binaries ((
http://www.funkyhorror.net/toxicfrog/projects/ss1hr/CDSD800.exe) 800x600 (
http://www.funkyhorror.net/toxicfrog/projects/ss1hr/CDSD1024.exe) 1024x768) work?
It would be nice if we could get it working in 98 again -- what's the error it gives you?
NHJ BV on 29/9/2005 at 09:00
I have a GeForce 6600GT, by the way, and it runs fine (except a COM port error on startup which can be ignored. This is not high-res related, however). It would seem that this issue (like many others) is related to the Geforce 4 MX series.
Shadowcat on 29/9/2005 at 11:39
Quote Posted by ToxicFrog
I take it that it's the original you're using, not Mok's
Yes indeed. The original always worked fine for me. All I ever needed to do before was install it, update the memory properties for cdshock.bat and that was it. It always ran fine. I've been using these video drivers long enough that I thought I'd have played it since first installing them, but I also think it's been an uncharacteristically long time since I last played System Shock, so maybe they're the problem. I can't think what else might have changed in the meantime.
Quote:
I also tried it in DOSBOX, and in that I was able to actually get into the game, running the pure DOS version at 800x600 and 1024x768. Unplayably slow, of course, but stable.
I can also run the game through DOSBox, and the first mapping of 640x400 to 800x600 works, but the 640x480 to 1024x768 mapping seems to set the resolution back to 320x200. Odd.
Quote:
Do the v1 highres binaries work?
hmmm... I'll give 'em a whirl. Have to reboot to DOS, of course...
Quote:
It would be nice if we could get it working in 98 again -- what's the error it gives you?
I didn't note it down, sorry. It locks my machine up, so I'll check it later :) I have just had a thought, though... the (
http://exuberant.ms11.net/98sesp.html) unofficial Win98 service pack might be new since I last played (or certainly the version I've currently got installed, in any case). That might be what's responsible. I can restore an old ghost image of my boot partition to test that, but it might be a while before I'm keen to sit through all that...
Enchantermon on 29/9/2005 at 11:48
Quote Posted by NHJ BV
I have a GeForce 6600GT, by the way, and it runs fine (except a COM port error on startup which can be ignored.
You get that too? I get one for COM1 and one for COM2 and ignoring both makes the game run just fine. Do you know what causes this?
Enchantermon
Shadowcat on 29/9/2005 at 12:21
I'm now a bit confused, as the patch version didn't crash in the same way from DOS this time around, however I think the autoexec.bat and config.sys entries are different this time, which could be a factor. More testing required there, but not tonight.
I think the following just happened (all in DOS)
* original game plays fine
* cdsd800.exe plays fine!
* cdsd1024.exe I had big problems with, as it would lock up in the pre-game menus after a few seconds (no idea whether the timing was consistent), but not necessarily at the exact same place (one time in the first menu, another in the 'new game' menu). On the third reboot, I skipped through the titles as quickly as I could to see whether I could reach the game itself if I was fast enough, and I did, and it actually played fine from then on. Very strange.
I then tried the patched executable (still configured for 800x600 and 1024x768), and as I mentioned up top it didn't crash the way it had before (however it did lock up in the menu like cdsd1024.exe had done, and I'm afraid I didn't try rebooting and skipping quickly to the game this time).
So. I will definitely play with it some more, and try to get some consistent results and test out the things I didn't try, but right now it's late and I'm tired, so I'm off to get some sleep...
At the very least, I got your original hacked executable running consistently in 800x600 under DOS with a GeForce4! :)
TheNightTerror on 29/9/2005 at 13:02
Quote Posted by Enchantermon
You get that too? I get one for COM1 and one for COM2 and ignoring both makes the game run just fine. Do you know what causes this?
Enchantermon
I almost wonder if it's a minor quirk/bug of the hacked .exe file. I get those 2 errors on my laptop, and curiously enough, only the COM2 error on the computer that's almost identical to yours. Kind of odd, but I always considered that error normal, and if I didn't get it, that meant the game would soon be telling a salt addict to salt the fries. :p
NoOne on 29/9/2005 at 15:05
Quote Posted by TheNightTerror
I almost wonder if it's a minor quirk/bug of the hacked .exe file. I get those 2 errors on my laptop, and curiously enough, only the COM2 error on the computer that's almost identical to yours. Kind of odd, but I always considered that error normal, and if I didn't get it, that meant the game would soon be telling a salt addict to salt the fries. :p
nope, original .exe files ask the same thing. it has something to do with how 2k/xp handle ports.
TheNightTerror on 29/9/2005 at 15:54
Are you sure? I remember when I was first getting SS1 running, that error was something new to me when it cropped up. It wasn't something that had been there all along.
NHJ BV on 29/9/2005 at 16:19
Quote Posted by Enchantermon
You get that too? I get one for COM1 and one for COM2 and ignoring both makes the game run just fine. Do you know what causes this?
Enchantermon
Haven't the foggiest. It didn't happen back on another computer with XP SP1 though, so I assume it's SP2-related. Or some part of this computer that's significantly different from the old one.
Enchantermon on 29/9/2005 at 18:02
Quote Posted by TheNightTerror
I get those 2 errors on my laptop, and curiously enough, only the COM2 error on the computer that's almost identical to yours.
Really? Huh. For a while, I only got the COM1 error, and then recently (earlier this year, around May or so I think) I started getting COM2 as well. :erg:
Quote Posted by NHJ BV
Haven't the foggiest. It didn't happen back on another computer with XP SP1 though, so I assume it's SP2-related. Or some part of this computer that's significantly different from the old one.
Now that I think about it, I don't think it started giving me either error until after we installed SP2.....
Enchantermon
