Info: Windows 7 *GUARANTEED* fix

[Render]

Don - That thought had crossed my mind. Hence the new separate breaker panel and outlets.

But both of those rigs had seen hard usage and were well beyond their service life expectancy. The older XP rig spent most of its time in a hot dusty environment and hung on like a bitter old clydesdale horse (or an old DOS game we all love). The second rig had been a dedicated COD4/WAW server for a fairly large gaming community and was running 24/7 non-stop for a couple of years before I got it (my bad for taking the cheap route).

All of the rigs (and late 1970's stereo equipment) that are in my office are run through a late 1990's 2,500watt rackmount UPS.

===

To give an idea of what I do for work, I wrote the below article.

http://www.longwarjournal.org/threat...vered_from.php

I'm the in-house weapons guy for the Long War Journal. Most of what I write is for private consumption, although sometimes I post articles on my own little bloglet. It's only just recently that I've been asked to step up to the LWJ front line. Making it a particularly bad time to have to build a new system and format my drives...

ENJOYING
THE DAY
OFF,
R

[DRG]

I need a few people who are running the game using Win7 in fullscreen mode to act as beta testers for us

The attachment contains a new GameOptions.exe and a .cmd file that will emulate what NCrawler did with his fix but will allow players to start the game from GameOptions.

I would ask that anyone who takes the time to DL this please take the time to report back on how it worked for you.

You will need to do the following

1/ Ensure you have SHOW INTRODUCTION already set to NO with your existing GameOptions. That's the first line on the first page when it loads.


2/ Go to wherever you have your game installed and rename your existing GameOptions.EXE to XXGameOptions.EXE to ensure if this does not work you still have a copy of GameOptions that works.


3/ Extract the attached ZIP file to where ever you have the game installed. It needs to be extracted to the main winSPMBT folder that your existing GameOptions.exe is already in.


4/ Start up GameOptions then press PLAY WINSPMBT. If you are running the game fullscreen and the NCrawler fix solved your palette issues with fullscreen mode this should work as well. If not, let us know



Thanks

Don

[2ndLt_Fjun]

Downloaded the zip..

1. Changed my exisiting file to not show introduction.
2. Renamed the exisiting to something else, extracted the new one into the folder
3. Started the game intro
4. Changed parameters to 'full screen mode'
5. Clicked "play WinSPMBT"

Got the following error:
SAL error: IpDD-->SetDisplayMode() failed, code 80004001
DirectDraw could not be initialized! Error code 80004001
Then the game crashed.

[Mobhack]

Originally Posted by DRG

I need a few people who are running the game using Win7 in fullscreen mode to act as beta testers for us

The attachment contains a new GameOptions.exe and a .cmd file that will emulate what NCrawler did with his fix but will allow players to start the game from GameOptions.

I would ask that anyone who takes the time to DL this please take the time to report back on how it worked for you.

You will need to do the following

1/ Ensure you have SHOW INTRODUCTION already set to NO with your existing GameOptions. That's the first line on the first page when it loads.


2/ Go to wherever you have your game installed and rename your existing GameOptions.EXE to XXGameOptions.EXE to ensure if this does not work you still have a copy of GameOptions that works.


3/ Extract the attached ZIP file to where ever you have the game installed. It needs to be extracted to the main winSPMBT folder that your existing GameOptions.exe is already in.


4/ Start up GameOptions then press PLAY WINSPMBT. If you are running the game fullscreen and the NCrawler fix solved your palette issues with fullscreen mode this should work as well. If not, let us know



Thanks

Don

Unfortunately, now that I have a Windows 7 development machine, this fix does not work due to some quirks in Windows batch file handling.

To cut a long story short

the line:

start explorer.exe

Works completely differently if a CMD file is called from the desktop level (ie double clicking on it in Windows Explorer) and when it is called from a program via the Shellexecute command (as done with the modified GameOptions beta included in the quoted post).

-If called from the desktop level, it restores explorer.exe and your desktop.

-If called from inside a programme (via the shellexecute command), it merely opens a Windows Explorer window on your desktop. It does not restore the desktop!.



Cheers
Andy

NB - if you get left on a bare Windows 7 desktop:
CTRL+ALT+ESC launches Windows Task Mananger
On the Applications tab select "new Task" button
Type in explorer.exe to the dialogue and accept
Job done, close Windows Task Mananger

[Mobhack]

Originally Posted by Mobhack

Unfortunately, now that I have a Windows 7 development machine, this fix does not work due to some quirks in Windows batch file handling.

To cut a long story short

OK - A final rewrite of the CMD batch file seems to solve the problem when run from an external programme. (GameOptions in our case)

- If your Windows 7 or Vista machine is not English then you may well have to edit the line
cd c:\windows to whatever your national language calls the Windows directory, if it differs.

I stumbled on this purely by accident just now - explorer.exe does have entirely differing behaviour if started in the windows directory - an entirely undocumented feature...

Cheers
Andy