Problem with MyFSTools

[pierrot1951]

Hello

I used unregistered version of FSUIPC 3.6.5, with MyFSTools 1.4 without any problem on 2 computers with FS9.1.

> On one computer, I installed the 3.7.1 update (overwrite) and it still works.

> On second, I kept 3.6.5, and installed MyFSTools 1.5 update (MyFSTools.dll in module folder), and FSPilot.

On launching FS9 I get the following message:

****************************************

*MyFSTools *

*[init Fs2] Error opening FSUIPC connection: 2 *

*(OK button) *

****************************************

The MyFSTools items are available (map, locator), but with FSUIPC not connected, so with default Lat=0 and Long=0 coordinates.

With all other apps, FSUIPC still works properly (Excbuilder, Afcad link, ...)

I tried to reinstall the older MyFSTools.dll without success.

do MyFSTools need a registration key?

Thanks for help so I can use those tools again;

Pierrot - FMEP

[Pete Dowson]

Hello

I used unregistered version of FSUIPC 3.6.5, with MyFSTools 1.4 without any problem on 2 computers with FS9.1.

Not heard of "MyFSTools". Sounds interesting.

On second, I kept 3.6.5, and installed MyFSTools 1.5 update (MyFSTools.dll in module folder), and FSPilot.

Is there any reason you didn't update to 3.71?

On launching FS9 I get the following message:

****************************************

*MyFSTools *

*[init Fs2] Error opening FSUIPC connection: 2 *

*(OK button) *

****************************************

And what does that mean? Do you have any "MyFSTools" documentation to explain it? Have you asked them?

I tried to reinstall the older MyFSTools.dll without success.

do MyFSTools need a registration key?

I've no idea, since I've never heard of it. Sorry. If it doesn't work and it needs FSUIPC and you haven't registered it as a user, then that is probably the reason, but you need to ask the suppliers of MyFSTools.

Pete

[pierrot1951]

Thanks for answer

So far, the unregistered FSUIPC worked; the problem seems to come from ver 1.5 replacing 1.4. The only way to know would be to install MyFSTools 1.5 instead of 1.4 on the still working installation to be sure it will not any more! But I need to have one still working!

In the setup doc:

=======================================

MyFsTools requires FSUIPC by Peter Dowson (vr. 3.4 or later), available at http://www.schiratti.com/dowson.html.

MyFsTools runs fine with a registered version of FSUIPC, but also has a built-in freeware key to make it work with an unregistered version of FSUIPC. Registered users of WideFS can also start it on a separate PC (see later below for details).

=======================================

I give you the site:

http://www.elbiah.de/flusi/

About history of program and FSUIPC (if it may help you)

=======================================

Changes

Vr. 1.5

New "Online Map" window

Hotkeys to open windows (see About-Setup to enable them)

Added database "db-nav.geo" containing NAV aids (VOR and NDB) of FS2004

NAV aids can now be selected on "Map" window (see "Database files")

Added checkboxes to select location types to be listed in "Locator" window

By clicking on "Runway:" label in "Guide" window, NAV1 and OBS can be set in FS.

Vr. 1.4

Bug fixed: The built-in freeware key for FSUIPC was not working any more.

Vr. 1.3

WideFS support (see Setup page for details).

Flight log book (see About page for details).

Some fixes for drawing graphics.

Vr. 1.2

Due to too many problems, communication between Flight Simulator and MyFsTools has been changed to use FSUIPC by Peter Dowson now.

Vr. 1.1

Some bug fixes related with inaccurate runway headings shon in Guide window (inaccurate data files, wrong magnetic variation, rounding issues).

Guide window additionally shows wind direction and speed now.

Default font size in Map window was increased, it can also be changed in MyFsTools.ini now.

Double-click airport in Guide window to open Locator window.

Airports with ILS are marked with "Apt-ILS" now, so you can filter on "ILS" in Locator window.

Some minor fixes.

Vr. 1.0

First public release.

=======================================

Thanks; Pierrot - FMEP

[Pete Dowson]

So far, the unregistered FSUIPC worked; the problem seems to come from ver 1.5 replacing 1.4.

Seems as though they meessed things up then. I have a record or an "MyFsTools.dll" being issued with an access key on 2nd April 2005. That will apply to all version 3.xxx of FSUIPC -- except 3.71 for which no access keys are required in any case.

I fail to understand why you insist on keeping to FSUIPC 3.65 on the PC on which you have this problem. If you don't want to update it, you don't get support from me in any case, and you need to talk to MyFsTools folks.

Pete

[pierrot1951]

Thanks

Sorry if I didn't explain in a clear way.

I guess the apparent problem is MyFSTools, but the cause would be FSPilot; I'll test as soon as possible.

Thanks; Pierrot - FMEP

[pierrot1951]

**** Latest test ****

I made test on the still working configuration (untill test!)

I had installed the same day FSTools15 and FSPilot; as FSPilot worked, and FSTools no, I thought that it was a problem with FSTools. So, I tested the same installation on the still working computer.

All was OK with FSUIPC 371 (MyFSTools); then I installed FSPilot as on other computer

MyFSTools can't connect any longer to FSUIPC; same message:

*MyFSTools *

*[init Fs2] Error opening FSUIPC connection: 2 *

*(OK button) *

But it's sure now that MyFSTools is not the origin of conclict.

The conflict seems to come from FSPilot; I found a solution: if I simply delete the FSPilot.dll in modules, all is ok as previous installation.

But I have no more FSPilot. I'll have to choose FSPilot or MyFSTools by moving the dll before launching FS9!

Thanks; Pierrot - FMEP

[Pete Dowson]

All was OK with FSUIPC 371 (MyFSTools); then I installed FSPilot as on other computer

MyFSTools can't connect any longer to FSUIPC; same message:

*MyFSTools *

*[init Fs2] Error opening FSUIPC connection: 2 *

*(OK button) *

Are you now using FSUIPC 3.71 on both computers? If not why not?

But it's sure now that MyFSTools is not the origin of conclict.

The conflict seems to come from FSPilot

Nevertheless the problem is in MyFSTools, and you need to contact the supplier/author to find out what the above message means. It makes no sense to me -- it presumably means something to the author!

If the "2" is the error number returned by FSUIPC_Open, then this means "Cannot link to FSUIPC or WideClient", which is simply a failure to get the SendMessageTimeout through to FS for FSUIPC to see. It probably simply means that Windows is so busy swapping processes or threads between FS and FSPilot that the messages from MyFSTools are timing out.

Most programs try many times before giving up. Maybe MyFSTools has no or few retries built in, and FSPilot is very greedy in its dealings with FS.

I'm afraid your recourse still lies with the author(s).

Regards

Pete

[pierrot1951]

Thanks for reply

Sorry not to be clear: I use FSUIPC 371 on both.

Excuse me, but I didn't understand exactly (french speaking!):

I'm afraid your recourse still lies with the author(s).

My English is not very fluent, and maybe I didn't use the right words to explain my problems; I only try to understand what happens and how to solve it, there is no problem about programs and authors. I just want to make those programs work together.

I contacted the FSPilot forum; their answer tells it may be a memory allocation error, or a memory problem as you think (I have 1Go, including 256 shared video).

They asked me to send them my memory before starting FS9, after starting FS9, after adding FSTools, or after switching to FSPilot.

I didn't succeed in contact with MyFSTools so far, to know their answer to problem.

In the meantime, I use FS9 with choice of FSPilot or MyFSTools.

Thanks for your programs and answers; Pierrot - FMEP

[pierrot1951]

Hello

I tried a latest test by buying the key for registered FSUIPC.

It didn't solve problem; My FSTools seems to have noticed FSUIPC was changed since,now, after se firts message, I get a new message when clicking MyFSTools items:

"FS2004 not running or FSUIPC.dll not installed"

It seems to be desperate!

Pierrot - FMEP

[Pete Dowson]

I tried a latest test by buying the key for registered FSUIPC.

It didn't solve problem; My FSTools seems to have noticed FSUIPC was changed since,now, after se firts message, I get a new message when clicking MyFSTools items:

"FS2004 not running or FSUIPC.dll not installed"

Hmmmthat is rather strange. Can you enable IPC read and IPC write Logging (see the Logging options), then close FS, restart so as to run that test again, then Close FS (very important), ZIP up the FSUIPC.Log file and send it to me at petedowson@btconnect.com (or show it here if it is short enough).

Regards

Pete

[pierrot1951]

ok!

I mail you the log files.

I send you the log file for 2 tests:

- with MyFSTools.dll + FSPilot.dll (problem)

- with MYFSTools.dll , no FSPilot.dll (all ok)

Thanks for help; Pierrot

[Pete Dowson]

I mail you the log files.

I send you the log file for 2 tests:

- with MyFSTools.dll + FSPilot.dll (problem)

- with MYFSTools.dll , no FSPilot.dll (all ok)

Okay. The log files show several things.

First, whilst MyFSTools does use FSUIPC, FSPilot does not. It is not a conflict within, or even to do with FSUIPC at all.

Second, then FSPilot is running is is actually preventing MyFSTools getting access to FSUIPC altogether -- in the log where both are installed there is no sign whatsoever of MyFSTools.

I have no idea why this might be -- it looks like FSPilot is doing something rather unfriendly, but I have no idea what that might be. I cannot possibly diagnose it because FSUIPC never sees any sign of MyFSTools.

Maybe you could try getting it loaded earlier. I see at present that you have two other FS DLLs loading, both of which also use FSUIPC and neither of which are affected by FSPilot: SB3GAUGEBRIDGE.DLL and PMDGOPTIONS.DLL. I'm not sure what controls the order of DLL loading by FS, but you could try renaming MyFSTools.DLL as "AMyFSTools.DLL" to see if having it earlier in the alphabet helps.

The problem might be due to the method used by MyFSTools for connecting to FSUIPC. With version 3.71 I cannot tell what method it uses, as I removed the access checking, but if you have a previous version you could try it with the same logging, so I can see the access method. If MyFSTools uses the EXTERNAL method for connecting to FSUIPC (which has been wrong for many years!), then it would explain more easily how this problem could be caused by FSPilot, and if that is the case it would need a change by the authors of MyFSTools.

If you don't have an FSUIPC version 3.709 or earlier let me know and I'll email one, just for this test.

Regards

Pete

[pierrot1951]

Thanks for quick answer.

In fact, I was troubled with the 2 other dll you say; the PMDG comes from B737PMDG, the other SB3GAUGEBRIDGE.DLL , I don't know its origin or use! I'll try to move those two.

I have a hope since I mailed my question on FSPilot forum; a user mailed me he had no trouble with registered DFSUIPC + FSPilot; he tested to add MyFSTools and it works for him., with an equivalent config as mine. I think it would be useful I ask him the content of its module folder.

Concerning the renaming, it could be a good pist: this method was a solution for a recent AI traffic problem; I used a commercial AI traffic add-on that occupied all places on airports, and my personnal handmade traffic blg were never considered; by renaming with an "A" at beginning, they get priority on loading!

I'll contact you as soon as I test.

Pierrot

[pierrot1951]

I've just got a short free time for test.

Yes, the "A" renaming works! That's the second time this technic saves my FS!

Concerning the test you asked with an older FSUIPC, I still have a 3.6.0.0; how do I proceed? I just overwrite the 3.7.1 by older? After, when reinstalling 3.7.1 will registration still be ok?

Great thanks; Pierrot - FMEP

[pierrot1951]

Hello

This new post should cancel the previous one: I was wrong about A-renaming!

In fact, as it seemed to work, I tested on second computer, and it failed.

Then, I was ready to make the "log" files with 3.6 you asked; on first computer I renamed back AMyMSTool.dll to MyFSTools.dll, and I was surprised all was ok!

I analysed the differences with 2 installations: same FSUIPC, same MyFSTools, but a noticeable difference concerning FSPilot.

It is the evaluation version, that gives you 30 "runs" with full fonctionnalities; then, if not registered, AP works, but some extra features (screens captures, music playing) don't work any more.

>>> In fact, on first computer, during last test, the 30th FSPilot had expired.

I immediately tried on second computer on which 25 runs were left; I launched/stopped 25 times until expiration; then all starts ok, with "normal" name "MyFSTools.dll".

Strange? Maybe a conflict with the evaluation countdown check system???

Finally, problem seems to be really solved, I hope.

Thanks; Pierrot

[Pete Dowson]

I've just got a short free time for test.

Yes, the "A" renaming works! That's the second time this technic saves my FS!

Right. So it it gets its connection into FSUIPC done before FSpilot starts up it is okay. That FSpilot mst be doing something rather odd.

Concerning the test you asked with an older FSUIPC, I still have a 3.6.0.0; how do I proceed? I just overwrite the 3.7.1 by older? After, when reinstalling 3.7.1 will registration still be ok?

Yes. Just move your 3.71 FSUIPC.DLL file someplace safe, then put the 3.60 FSUIPC.DLL in its place, in the Modules folder. Don't change anything else. Run the test then put the 3.71 back.

Regards

Pete