Windows 7 and CFS1 joystick problem; A FIX!!!

hubbabubba

hubbabubba

Charter Member
Many "workarounds" were offered, but I think that what aproblem_asolution (very apt name btw...) has found can only be described as a genuine fix;

Ok the problem is very simple!

Explanations:
-------------

In Windows 95 To XP, the game search for joystick name in regedit
at key "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\..."
but in Windows > XP (or 64 bits systems) (Example: Windows 7 - 64 bits) The key is not in "HKEY_LOCAL_MACHINE" but in "HKEY_CURRENT_USER"
"HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\..."

Then just patch the EXE file game to read in "HKEY_CURRENT_USER" and not in "HKEY_LOCAL_MACHINE"
The ASM instruction is "push 80000002" to request on "HKEY_LOCAL_MACHINE" (hexadecimal values=6802000080)
and "push 80000001" to request on "HKEY_CURRENT_USER" (hexadecimal values=6801000080)

Follow Simple Steps to patch properly (Change Only 2octets):
------------------------------------------------------------

01) Download Hexadecimal editor (example freeware: http://mh-nexus.de/en/downloads.php?product=HxD)
02) Optional: Backup the EXE Game file Default = "C:\Program Files (x86)\Microsoft Games\Combat Flight Simulator\COMBATFS.EXE"
03) Optional: Backup the Config game file (if exists) Default = "C:\Program Files (x86)\Microsoft Games\Combat Flight Simulator\COMBATFS.CFG"
04) Open the EXE Game file "COMBATFS.EXE" with the hexadecimal editor
05) Search for hexadecimal values an enter "6802000080" (CTRL+F -> Hexadecimal Values -> 6802000080, F3 To search next)
06) Normally you have 3 results (Me at offsets: 1141, C60F, C6BD) (Don't Select And Change The 1st result)
07) Select the 2nd result (Me at offset C60F) and replace "6802000080" by "6801000080" [Just replace 02 by 01]
08) Select the 3rd result (Me at offset C6BD) and replace "6802000080" by "6801000080" [Just replace 02 by 01]
09) Save the EXE game file "COMBATFS.EXE" (in hexadecimal editor)
10) Delete the config game file "COMBATFS.CFG" (if exists)
11) Start the Game...
12) Joystick And Configuration Menu Works Fine NOW

(If you have some problems just replace "COMBATFS.EXE" [steps 02] To restore original file)

Enjoy
Click to expand...

The original thread at FlightSim is HERE.

I took the liberty of re-posting here as I think that this fix is of general interest to anyone interested in flying CFS1. I tested the HEX editing procedure myself but, not having a Windows 7 machine, I would appreciate any feedback from people who do.
 
hubbabubba said:
Many "workarounds" were offered, but I think that what aproblem_asolution (very apt name btw...) has found can only be described as a genuine fix;



The original thread at FlightSim is HERE.

I took the liberty of re-posting here as I think that this fix is of general interest to anyone interested in flying CFS1. I tested the HEX editing procedure myself but, not having a Windows 7 machine, I would appreciate any feedback from people who do.
Click to expand...

Does this mean we won't get the funky message about the joy stick change, whenever we go to settings?

If I don't even know what octets are, should I be trying this?
 
mcbob said:
Does this mean we won't get the funky message about the joy stick change, whenever we go to settings?
Click to expand...

Yep!
Exactly what it means.

mcbob said:
If I don't even know what octets are, should I be trying this?
Click to expand...

Nope. I'm tempted to offer my own modified COMBATFS.EXE for those "technically challenged" like you. My only question is; will SOH let me? How about No Dice?

It would be a replacement for the ORIGINAL file, no more, no less.
 
hubbabubba said:
Yep!
Exactly what it means.



Nope. I'm tempted to offer my own modified COMBATFS.EXE for those "technically challenged" like you. My only question is; will SOH let me? How about No Dice?

It would be a replacement for the ORIGINAL file, no more, no less.
Click to expand...

great idea...i'll look into it.
 
hubbabubba said:
Yep!
Exactly what it means.



Nope. I'm tempted to offer my own modified COMBATFS.EXE for those "technically challenged" like you. My only question is; will SOH let me? How about No Dice?

It would be a replacement for the ORIGINAL file, no more, no less.
Click to expand...

I still might try it as it appears that it only changes the one exe file. I have change regedit before under email directions of a spyware expert.

Another question, should I reload CFS back to it's original location for win7? I had made a new folder directly under C as suggested by someone on the forum. That didn't seem to help anything for me. I know how to put my config and campaign files back to their present state.

mcbob
 
mcbob said:
(...)
Another question, should I reload CFS back to it's original location for win7? I had made a new folder directly under C as suggested by someone on the forum. That didn't seem to help anything for me. I know how to put my config and campaign files back to their present state.

mcbob
Click to expand...

I would re-install in its original location then, without running the game even once, replace the defective COMBATFS.EXE with the repaired one. This should permit to "skip" steps 3 and 10 altogether.

Keep us posted and. if you do it, tell us the results, if any. The worst that could happened is a hang-out game and a re-boot, maybe.
 
smilo said:
great idea...i'll look into it.
Click to expand...

Thanks smilo. Strictly speaking, it is a modification of the heart of the game (and probably against the EULA) but, also strictly speaking, M$ should have done it by themselves years ago. Your call guys!
 
done deal with positive results.
check your email for details.

i am most anxious to see if this will solve the issue in xp.
 
hubbabubba said:
I would re-install in its original location then, without running the game even once, replace the defective COMBATFS.EXE with the repaired one. This should permit to "skip" steps 3 and 10 altogether.

Keep us posted and. if you do it, tell us the results, if any. The worst that could happened is a hang-out game and a re-boot, maybe.
Click to expand...

I did reload the whole program to the default location and then made the two changes as suggested. My only problem was figuring out that I had to go in and allow myself to overwrite that file. When I started CFS1 the joystick worked just like it should with no changes at all. I didn't even have to pick it or turn it on. It was just there and working just like it should. I will of course, have to go in and reassign some of the buttons to my liking. I didn't see that funky message after I checked to see that it showed my joystick and verify that all the functions were active.

I did notice that when I flew the free flight that the mountains were 3d. Before, only the buildings were 3d. I wasn't getting that before after I used the config fix. Also the movie plays when you start the program. Are all the flights supposed to have 3d terrain?

I still have to figure out my video settings.

I never had any problems with XP, but I don't remember anything but the buildings being 3d.

Thanks for all the help so far. I'm sure I'll have more questions.

mcbob
 
I'm happy to see that it is working, mcbob.:jump: As for 2D/3D issue; I can't even imagine what a mountain would look like in 2D. You can skip the intro movie by modifying your CFG file this way;

[MAIN]
ShowLogo=0

I have send a "patch" to smilo who will give it a shake on his machines. Once he declare it safe, and working, I will upload here and to your site, No Dice. Quite frankly, I think that the more places offer this fix, the better.
 
as hubba said, i am running a few tests on several machines.
understand that all of my machines run xp,
so, basically, i'm just trying to find out
if the "your joystick has changed from blah blah to blah blah..."
message has gone away.
with any luck and few interruptions,
i will finish this evening and will report to hubba.
if anyone wants to test this on a vista or w7 machine,
i would suggest talking to hubba.
 
smilo said:
as hubba said, i am running a few tests on several machines.
understand that all of my machines run xp,
so, basically, i'm just trying to find out
if the "your joystick has changed from blah blah to blah blah..."
message has gone away.
with any luck and few interruptions,
i will finish this evening and will report to hubba.
if anyone wants to test this on a vista or w7 machine,
i would suggest talking to hubba.
Click to expand...

Vista and up should try it. As for XP, some machines do get the problem, some don't. Why? :banghead:
 
No Dice said:
I have gone thru a few XP's and never had the problem ??

Dave
Click to expand...

LUCKY, you.

all of my xp machines get the %$#^&* joystick message.
with the exception of my main machine
which stopped getting it after i dropped in the patch.
problem is, i tried it on 3 other xp machines and it doesn't work.
i have tried for hours and can't figure it out.

i thought, maybe, my main was 64 bit, but no.

i have no doubt that this was caused by a bogus ms automatic security update,
but have no idea what it was or when it was installed.
i guess i could reinstall xp without service packs on a reformatted machine
and then manually install all of those updates, but really?
i think i have better things to do with my time.

...or do i? i am curious.

edit; read on to see that the commentator does not know what he is talking about.
the issue was caused by a corrupt combatfs.exe NOT a bogus ms automatic security update.
my apologies for falsely pointing fingers.
 
Last edited:
Well now I am really confused, or missing something...maybe my brain.

I thought the problem was with Vista and win7, I really never had a problem with XP.

Was there an XP pro or something ? I only ask because the win7 problem does not happen on Win7 pro version.

Let me take a look, maybe I have XP pro or something?

Edit: I do not allow updates and do not use Norton ect. protection, they don't really do much, in my opinion.

Dave
 
It's the have-not talking to the have-plenty here but I think that M$ released a 64 bits version of XP in limine.

Maybe they did the same with the Registry hierarchy and switch controls location as well. I know I have installed CFS1 (and FS95 and 98 as well) on the "going to the curb" (an XP) machine without problem whatsoever.

As I was saying in a e-mail I just send to smilo, maybe COMBATFS.EXE installed differently, but this makes no sense unless a third-party (you) modified that file.

I really would like some Vista-7-8 guinea pigs!!!:icon_eek:
 
No Dice said:
Well now I am really confused, or missing something...maybe my brain.

I thought the problem was with Vista and win7, I really never had a problem with XP.

Was there an XP pro or something ? I only ask because the win7 problem does not happen on Win7 pro version.

Let me take a look, maybe I have XP pro or something?

Edit: I do not allow updates and do not use Norton ect. protection, they don't really do much, in my opinion.

Dave
Click to expand...
yup, there was/is a 64 bit xp version.

this will explain and tell what you have;
http://support.microsoft.com/kb/827218


it would appear that this is yet another instance of smilo hijacking a thread.
my apologies hubba.
i was hoping this patch would also fix the joystick message issue in xp.
 
smilo said:
yup, there was/is a 64 bit xp version.

this will explain and tell what you have;
http://support.microsoft.com/kb/827218


it would appear that this is yet another instance of smilo hijacking a thread.
my apologies hubba.
i was hoping this patch would also fix the joystick message issue in xp.
Click to expand...

The patch only works on OS that have their controls-joysticks under HKEY_CURRENT_USER instead of HKEY_LOCAL_MACHINE. I just tried my wife 32 bits Vista machine and this is the case. So, just to be clear, 32 or 64 bits has no effect on the giberish message. Register is the deciding factor.

If you receive that message under XP machines, smilo, one of two things is happening; 1-you have a Register that has controls-joysticks under HKEY_CURRENT_USER or; 2- your COMBATFS.CFG is corrupted.

And this is not highjacking...:icon_lol:
 
You must log in or register to reply here.
Back
Top