Bjossi on 14/11/2006 at 22:38
Or he can go the much easier way that I mentioned, I can't see the problem when this will probably be the only executable he'll ever put into system32. I personally find it useful for many old games that dislike dualcores.
SultanofSmash on 16/11/2006 at 08:18
I placed imagecfg.exe into system32 and system32/dllcache and ran the proper command into the command line and still no effect. The same thing happens, black screen, back to desktop, error message saying it needs to close.
The Brain on 16/11/2006 at 08:41
Did you apply imagecfg command to shock2.icd-file, too? And did you use -u command line switch with it before you did use -a 0x1 switch?
THRESHIN on 16/11/2006 at 13:54
Quote Posted by SultanofSmash
Intel P4
Windows XP home edition with service pack 2(I think.. i might be confused about that)
3.00ghz
ATI X800 xt All In Wonder with the latest Radeon catalyst(i think its called the 6.10 catalyst, its on ati.com)
1 gig of ram
Every time i open the game, i get a black screen(looks like its loading up), then it just goes back to the desktop with an error saying the program needs to be closed. I've tried tried the fixed .exe file, i've tried a file called shock2_xp_2000_fix, ive tried creating a shortcut so i can manipulate it using xcpu. Ive done the -lghtingforce thing(i know thats not how its spelt, but ive tried that) as well. And while doing those, i switch to every compatibility mode each time which has had no result either.
I'm looking quite forward to playing this game, but im starting to lose hope. As a side note, while looking at solutions, i saw something on the hyperthreading problem, and while i know this is going on(when i can manage, i do the task manager thing and turn it off) but considering my game closes right away, changing that has little effect on anything since the error erases anything i do to it.
i've just solved the SAME problem myself. turns out its a combination of dual core and video issues. its actually the texture memory error but for some reason it doesn't always report it. go figure. at least that was my problem and thats why it was hard to identify. simple add the 'safe texture manager' line to the proper config file (can't remember exact details, here somewhere). once you get to the main menu alt+tab out and bring up the task manager (ctrl+alt+del) and then set affinity for shock2.exe to either cpu 0 or 1. for some reason, i find that i have to set to cpu 1 or i can get crashes. make sure you do this BEFORE you start the game/load a saved game or it will not work.
and hey if this doesn't work, at least its worth a shot. it does sound exactly what i was getting though.
SultanofSmash on 17/11/2006 at 05:59
Sorry threshin, that is not my problem. Unfortunetly, I cannot even GET to the main menu. As I've said, the game starts loading up(black screen) then closes RIGHT AWAY, and comes up with an error. And yes, I have the safe texture manager typed in.
The Brain:
I'm unsure of what you mean... Here is what I did. I unzipped imagecfg.zip, and out came imagecfg.exe(obviously). I placed that file in system32 and system32/dllcache. I opened the command line, and typed in what Bjossi told me to type. There was no effect.
Did I do something wrong, or was that not the solution to the problem?
Bjossi on 17/11/2006 at 12:50
You should see the cmd print some info below the line that you typed that tells you that the affinity header of shock2.exe has been modified. Did you type the location correctly? People do install games in all sorts of locations, I just gave you the default one.
The Brain on 17/11/2006 at 14:54
Quote Posted by SultanofSmash
Sorry threshin, that is not my problem. Unfortunetly, I cannot even GET to the main menu. As I've said, the game starts loading up(black screen) then closes RIGHT AWAY, and comes up with an error. And yes, I have the safe texture manager typed in.
That's odd. Have you tried (
http://www.strangebedfellows.de/index.php?topic=36.0) Bobruck's fixed shock2.exe-file? Before you extract that file in your shock directory, rename your orginal shock2.exe to different name so it wont get overwritten.
Quote Posted by SultanofSmash
The Brain:
I'm unsure of what you mean... Here is what I did. I unzipped imagecfg.zip, and out came imagecfg.exe(obviously). I placed that file in system32 and system32/dllcache. I opened the command line, and typed in what Bjossi told me to type. There was no effect.
Did I do something wrong, or was that not the solution to the problem?
What I meant in my previuos post that did you follow instructions properly at here (
http://www16.brinkster.com/salvage/thief/darkengine.htm) http://www16.brinkster.com/salvage/thief/darkengine.htm? There is two files (shock2.exe and shock2.icd) at your shock directory that need to have affinity header applied on them.
In some rare occasions Windows XP still assigns shock2.exe and/or shock2.icd processes to CPU1, even if you have applied CPU0 - affinity mask on both files. You should check their masks in Task Manager by right clicking on their names and selecting Set affinity-menu item. If their affinity mask is different than CPU0, then you need apply imagecfg command to file named clokspl.exe in your shock2 directory.
SultanofSmash on 18/11/2006 at 01:40
to Bjossi:
Yes, I typed it in correct. The location is correct too since i too have my system shock installed to that exact location.
to The Brain:
I have tried the fixed exe which left me with no success. However, unless I'm reading this wrong, the link you gave me(which i have seen) seems to require me to type different things then what Bjossi told me.
I'm slightly confused as to what I'm doing if your both telling me to do different things, however, since what Bjossi told me to type did not work I will try the link and tell you what happens.
Bjossi on 18/11/2006 at 12:25
Imagecfg is just a system commend, it has many options to go, like -a, -u, etc.
-a 0x1 should be the one to use to modify the affinity header, it did for me and everyone else I've recommended it to.
The Brain on 18/11/2006 at 20:47
Bjossi: Erm, it's not a system command. It's just a separate program which is not included in default Windows installation. You need download and install/extract it first before you can run it. A system command (or program) is already in OS either in a form of internal or external function. For example there is no dir.exe-file or dir.com-file for dir command in DOS/Windows operating systems, so it's internal command.
SultanofSmash:That link in my previous post points to real instructions how to use imagecfg to apply affinity header to System Shock 2. Or in any other games, which have difficulties to run at multicore systems.
