View Issue Details

IDProjectCategoryView StatusLast Update
0001147FSSCP---------public2008-10-14 04:28
ReporterFUBAR-BDHR Assigned To 
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionunable to reproduce 
Product Version3.6.9 
Summary0001147: Launcher has caused an error in Kernel32.dll on Win ME
DescriptionNew launcher in 3.6.9 RC7.9U causes an error in Kernel32.dll on my Win ME machine. Works fine on both XP machines. Closing the error allows the program to continue to load and I am able to use launcher to run FS2 just fine.
Additional InformationOnly other noticable differece between ME and XP is with the crash when launching a standalone. Launching standalone works on XP but in ME I get the error. Standalone still doesn't work on either but that was expected. I'll attach a screenshot of the error.
TagsNo tags attached.

Activities

2006-11-16 00:12

 

image5LR.JPG (649,734 bytes)

taylor

2006-11-16 00:33

administrator   ~0007141

This isn't actually a Launcher problem, but a build exe problem. It will probably just be build specific though (some optimization/build problem), rather than some code bug.

What kind/speed of CPU do you have on the ME machine?

FUBAR-BDHR

2006-11-16 03:06

developer   ~0007143

The Win ME machine is a P3 866 with 768Meg of ram. I actually built that machine just to play FS2 back in the day.

FUBAR-BDHR

2006-12-27 21:40

developer   ~0007333

Still getting the same thing with the RC8 build. Doesn't seem to cause a problem as hitting the close box still allows the launcher to load.

taylor

2007-02-27 17:14

administrator   ~0007747

* BUMP *

I assume that this was only happening with Launcher 5.5? If so, does it work properly with Launcher 5.5a?

FUBAR-BDHR

2007-02-28 02:47

developer   ~0007757

Actually it was happening with both 5.5 and 5.5a. I just double checked and it did it with the 5.5a launcher out of the 3.6.9 final rar. Date on the launcher is 12/25/06.

taylor

2007-03-01 13:23

administrator   ~0007771

I installed ME on a VM to try and replicate this bug, No luck so far, it all works fine for me. I did find one code error, which will be fixed in an updated version of 5.5b, but I'm not sure that would actually cause your crash.

Anyway, just in case that was the problem, give this a try:
http://icculus.org/~taylor/fso/willrobinson/Launcher.rar

FUBAR-BDHR

2007-03-02 05:37

developer   ~0007778

Well still no luck. That launcher did the exact same thing. It doesn't cause a crash I just get the window with the error message and as soon as I close it everything works fine.

Could it have something to do with multiple IP addresses on ME? They aren't really supported but work just fine if you manually add them to the registry. Other than that it is a pretty standard setup.

taylor

2007-03-02 07:07

administrator   ~0007779

Try these two things, maybe it will narrow down the problem a bit more:

1) Put just the Launcher exe and one of the game exes in a directory by themselves. Try and the Launcher and see if it messes up, if not then select the game exe and see if it's still ok, if so then go to each tab to make sure that they all work. If it's still ok then press "Ok" to exit the Launcher, then repeat the process. If at no point does it mess up during this process, skip 0000002 and let me know.

2) Make sure that you are out of the game/FRED/launcher, then go into regedit and rename the "HKLM/Software/Volition/FreeSpace2" key to something else (like "HKLM/Software/Volition/FreeSpace2save"). Try 0000001 again, see if it messes up. If so then be sure to go back and restore the original reg entry, and let me know. If not then restore and export the original reg entry to file and attach it to this bug for me to examine.

FUBAR-BDHR

2007-03-02 09:18

developer   ~0007780

Last edited: 2007-03-02 09:30

OK created a test directory and put the 5.5b launcher and 3.6.9 final exe in it. Launcher loaded fine but as soon as I browsed and selected the exe in the launcher I got the problem.

Should have read the rest the first time but following the rest of it and renaming the registry key resulted in the exact same thing.

I uploaded the registry key just in case. I also had another key but it's probably from the demo but I uploaded it too.

2007-03-02 09:29

 

FUBAR.reg (1,438 bytes)

2007-03-02 09:29

 

FUBAR2.reg (189 bytes)

taylor

2008-07-17 16:26

administrator   ~0009456

Not going to work on this.

FUBAR-BDHR

2008-10-14 01:56

developer   ~0009963

Since no one else seems to have had this problem and I have no way to test it anymore (updated the PC to XP ages ago) might as well file this one as unable to reproduce.

chief1983

2008-10-14 04:28

administrator   ~0009966

You're probably one of the few who ever tried to run it on ME. Besides, cross platform launcher will eliminate this anyway, eventually.

Issue History

Date Modified Username Field Change
2006-11-16 00:12 FUBAR-BDHR New Issue
2006-11-16 00:12 FUBAR-BDHR Status new => assigned
2006-11-16 00:12 FUBAR-BDHR Assigned To => phreak
2006-11-16 00:12 FUBAR-BDHR File Added: image5LR.JPG
2006-11-16 00:33 taylor Note Added: 0007141
2006-11-16 00:33 taylor Assigned To phreak => taylor
2006-11-16 00:33 taylor Category launcher => ---------
2006-11-16 03:06 FUBAR-BDHR Note Added: 0007143
2006-12-27 21:40 FUBAR-BDHR Note Added: 0007333
2007-02-27 17:14 taylor Note Added: 0007747
2007-02-28 02:47 FUBAR-BDHR Note Added: 0007757
2007-03-01 13:23 taylor Note Added: 0007771
2007-03-02 05:37 FUBAR-BDHR Note Added: 0007778
2007-03-02 07:07 taylor Note Added: 0007779
2007-03-02 09:18 FUBAR-BDHR Note Added: 0007780
2007-03-02 09:26 FUBAR-BDHR Note Edited: 0007780
2007-03-02 09:29 FUBAR-BDHR File Added: FUBAR.reg
2007-03-02 09:29 FUBAR-BDHR File Added: FUBAR2.reg
2007-03-02 09:30 FUBAR-BDHR Note Edited: 0007780
2008-07-17 16:26 taylor Note Added: 0009456
2008-07-17 16:26 taylor Assigned To taylor =>
2008-07-17 16:26 taylor Status assigned => new
2008-10-14 01:56 FUBAR-BDHR Note Added: 0009963
2008-10-14 04:28 chief1983 Note Added: 0009966
2008-10-14 04:28 chief1983 Status new => closed
2008-10-14 04:28 chief1983 Resolution open => unable to reproduce