Anybody else out there??

[N47330]

Hey Pete! (or anyone else out there),

I have just downloaded your FSUIPC V.3, and though it is an EXCELLENT program, it will not work with my system setup (maybe it is FS2002 :?: :?: ) but even though i've enabled old modules in the FS2002.cfg file, it still won't boot FSUIPC. But regardless, i was wondering where (and when) i can get a copy of V.2.96, since it seemed to work fine. Thanks for your help! By the way i am running a P4 3.06GHz with a Nvidia GeForce4 Ti4600 and an off-the-shelf intel motherboard with onboard RAID. I don't think that my hard drive or sound system would cause any problems, so there ya have it! Yes i do know that i owe you the last 2 minutes of your life back, but its all i can do. :wink: Thanks again..

[Pete Dowson]

I have just downloaded your FSUIPC V.3, and though it is an EXCELLENT program, it will not work with my system setup (maybe it is FS2002 :?: :?: ) but even though i've enabled old modules in the FS2002.cfg file, it still won't boot FSUIPC.

You don't need OldModules set for FSUIPC. It never has needed it.

When you say "it will not work" can you be more explicit please? What does it say or do? What is "not working" about it?

Pete

[N47330]

I'm sorry. It just dawned on me that I must register FSUIPC before it will allow other programs to run off of it. So anyway, is there another place where I can get the previous version? I would love to purchase it, but I've just spent quite a small fortune on my computer, and am quite low on cash right now. Thanks for your time and I hope I didn't cause too much trouble!

[Pete Dowson]

It just dawned on me that I must register FSUIPC before it will allow other programs to run off of it.

It will allow all accredited programs to run with it. That is programs which have access keys, either because the commercial developers paid for this, or because they are freeware and the developers get the access key from me free of charge.

So anyway, is there another place where I can get the previous version?

Not officially, no. It will probably still be on earlier magazine cover CDRoms, and maybe on some websites someplace, but it won't be officially supplied. I expect you could get someone to email you a copy. It won't be supported and won't work on FS2004, that's all.

Regards,

Pete

[N47330]

Okay well that answers most of my questions. I guess i must have a program created before V.3 was released. Thanks for your time! btw, if anybody out there reads this and has FSUIPC V.2.96 please post a reply, and i will give you my e-mail address, as i would appreciate it greatly!

[Jakob Tischler]

Pete, I just downloaded the newest version of FSUIPC, put the dll in the modules folder (FS2004) and started FS. Everything went fine, but when starting a flight, it loads, and then there's just a black screen, and about 30 seconds later there's a message saying FS just crashed, and if I wanted to restart it. How do I fix that?

[Pete Dowson]

Pete, I just downloaded the newest version of FSUIPC, put the dll in the modules folder (FS2004) and started FS. Everything went fine, but when starting a flight, it loads, and then there's just a black screen, and about 30 seconds later there's a message saying FS just crashed, and if I wanted to restart it. How do I fix that?

Sorry, I don't know. That is certainly nothing to do with FSUIPC. If it won't fix by updating video drivers, then report it to MS.

Regards,

Pete

[Jakob Tischler]

Well, the second I added the dll to the modules folder, the problem appeared, the moment I deleted the dll, FS worked fine again. :roll:

[Pete Dowson]

Well, the second I added the dll to the modules folder, the problem appeared, the moment I deleted the dll, FS worked fine again. :roll:

Sorry, that only means there's something else wrong which doesn't show up until the loading of FSUIPC changes the memory layout, or possibly some other action. The only other possibility is that your copy of FSUIPC is corrupted, so you could try getting another copy.

Maybe it's some other application which interferes with applications like FS. Known culprits are RoboForm and WindowBlinds, but there are probably others. I've not known them to actually crash FS, but it is certainly possible. Try closing down every other process or add-on before running FS. None of them do its performance any good in any way. I recommend "EndItAll", a little freeware program which helps get rid of things.

There are thousands of users with FSUIPC installed already, and never once in the 4 year history of FSUIPC has there been one single error which has the effect you describe. What else can I say? The module doesn't even do anything if you've not registered it and haven't got any applications or other add-ins which use it. If it is crashing so early, with nothing going on, then it probably can't even add its Menu entry, which could certainly point to something like WindowBlinds.

Regards,

Pete

[Jakob Tischler]

The only other possibility is that your copy of FSUIPC is corrupted, so you could try getting another copy.

I downloaded it from your website (http://www.schiratti.com/files/dowson/FSUIPC.zip)

If it is crashing so early, with nothing going on, then it probably can't even add its Menu entry, which could certainly point to something like WindowBlinds.

I'm not running anything like that, but I'll try EndItAll and tell you the results.

Regards, Jakob

[Pete Dowson]

I downloaded it from your website (http://www.schiratti.com/files/dowson/FSUIPC.zip)

It isn't my website, as is made clear there, it is Enrico Schiratti's. Anyway, I was not sayting it was corrupted on the site, only that possibly your copy might be corrupted somehow and you should try again.

Regards,

Pete

[Jakob Tischler]

:( I still encounter the same problem. Do I have to put anything else in the modules folder than "fsuipc.dll"?

[Pete Dowson]

:( I still encounter the same problem. Do I have to put anything else in the modules folder than "fsuipc.dll"?

No. That's it. As I say, until it is registered it does almost nothing. It certainly doesn't do anything for a while anyway. Does it get as far as making an FSUIPC.INI and FSUIPC.LOG file at all? If so, can I see them please?

Pete

[Jakob Tischler]

Yes, they are created:

FSUIPC.ini:

[General]

History=SJAILUO1LVLGQD4XL0SCL

TCASid=Flight

TCASrange=40

TrafficScanPerFrame=10

AxisCalibration=No

CentredDialogue=Yes

ClearWeatherDynamics=Yes

MainMenu=&Modules

SubMenu=&FSUIPC ...

FSUIPC.log:

********* FSUIPC, Version 3.04 by Pete Dowson *********

User Name=""

User Addr=""

FSUIPC not user registered

WIDEFS not user registered, or expired

Module base=01B60000

ClassOptions: UIPCMAIN=FF7F, FS98MAIN=FF7F, FS2KMAIN=FF5E

WeatherOptions(Orig)=0000B027[0000B027]

InitDelay: 3 seconds

4476 System time = 15:07:31

Internal Debug Code 0

4476 E:\Microsoft Games\Flight Simulator 2004\

17505 FLIGHTS\OTHER\FLTSIM.flt

17635 AIRCRAFT\c172\Cessna172SP.air

26838 System time = 15:07:53, FS2004 time = 15:07:46 (22:07Z)

27159 Advanced Weather Interface Enabled

30974 F:\Flight Simulator Files\UI generated flight.flt

31355 Clear All Weather requested: external weather discarded

[Pete Dowson]

Yes, they are created

Okay, that's a relief then. I'm wondering if there's some sort of odd timing conflict going on during loading. Do you run FS with the initial selection menu coming up first, or have you set the "Show opening screen" parameter to 0 in your FS9 CFG file? If you haven't, would you like to try that for me?

The FS9.CFG file is in

C:\Documents and Settings\\Application Data\Microsoft\FS9

You can edit it with Notepad or any editor. In the [sTARTUP] section, find

SHOW_OPENING_SCREEN=1

and change it to 0.

See if that helps. Let me know.

Another thing you can do is to change the delay in FSUIPC's start-up. Add a line:

InitDelay= 10

to the [General] section of FSUIPC.INI, before running FS. The default is 3 seconds, 10 would be 10 seconds. You can delay its startup by up to 30 seconds, so experiment with that.

Finally, when you do get the window coming up saying FS has crashed, can you click wherever it says to look at more details. The module name and address might be useful. It isn't actually crashing in FSUIPC, otherwise this would be trapped and recorded in the FSUIPC LOG file -- this is a precaution I've been taking for a while now.

Regards,

Pete