Ziemanskye on 19/6/2006 at 15:28
0.3, and still with trying to change the resolution (even with twiddled CDShock.bat) it just blacks out or kills my monitor.
Blacks out on the 640x480 button, turns the monitor off on the 640x400.
Is there anyway to force this so it plays in a window rather than full screen?
(Might at least make successful/not resolution changes more obvious)
Spitter on 19/6/2006 at 15:37
Got it working in 640x480 by using the ss1hr.exe and defaulting the 1024 res back to 640 one. Videos play back now, too.
Kolya on 19/6/2006 at 15:56
Could you please try a newly extracted version 0.3 + the (
http://www.strangebedfellows.schwarzsilber.de/index.php?topic=211) MonitorKillPatch.zip I just uploaded to SBF? Unzip this into the game dir.
It contains MOK's unchanged cdshock.exe and a corresponding cdshock.bat.
It should let you play at 640x480.
I know you got that working already Spitter, but please confirm if it works for you too. Thanks.
Ziemanskye on 19/6/2006 at 17:00
Monitor kill patch thing works fine at 640x480, should I test to see if I can force higher on it?
Kolya on 19/6/2006 at 17:12
My guess is that brings you back to your monitor problems.
ZylonBane on 20/6/2006 at 00:14
Considering how problematic the high-res hacks of SS1 are, isn't it a bad idea to include them in this?
Kolya on 20/6/2006 at 00:24
I didn't expect this to end all SS1 problems but it's doing pretty well and I assume people want to play at high resolutions when they are possible in SS1.
And with the MonitorKillPatch.zip it's easy to return to the game's original resolution.
ZylonBane on 20/6/2006 at 00:33
Just tried it under XP. Double-clicking the PIF yielded a variety of odd results. Running CDSHOCK.BAT directly seemed to work fine. Wish videos played fullscreen.
Nameless_Voice on 20/6/2006 at 07:38
There should be two PIFs, CDShock.pif and !System Shock.pif. The first is needed to set the memory settings for the game, but you shouldn't actually run it. The second, !System Shock.pif, should just run CDShock.bat, though it also sets a few other options such as allowing the game to receive the Print Screen key.
To be honest, I'm surprised the pifs work at all without correcting their paths.
Kolya on 20/6/2006 at 09:31
There is only one PIF in the archive, that is "System Shock.pif" (I omitted the '!'). I also omitted CDSHOCK.pif because I couldn't see where it actually gets used, and it ran fine without it.
System Shock.pif sets the RAM parameters and calls CDSHOCK.bat via command line parameter (empty program path).
CDSHOCK.bat starts dosdrv.exe and cdshock.exe (with MOUSE2KV.EXE and dos32a.exe).
Where does cdshock.pif come in?
Edit: Upon further investigation cdshock.pif seems to save RAM parameters for it's exe-file. That is if I set the RAM parameters on the cdshock.exe a corresponding PIF gets created with these parameters.
Still wonder if cdshock.pif is really necessary. Will the RAM parameters not get handed down from "System Shock.pif"?
I can't really test this because the game seems to run for me whatever RAM settings I use.
And yeah, just starting CDSHOCK.bat works for me too. So I might as well omit any PIFs.
The question is what works best for all.
EDIT2: Even more investigation reveals that "System Shock.pif" is what gets us arround using VDDLoader.DLL
ZB and me didn't notice because we both have VDMSound installed (right ZB?).
Anyway, "System Shock.pif" is needed for everyone without VDMSound.
