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

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

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

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

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

Thanks for reply Sorry not to be clear: I use FSUIPC 371 on both. Excuse me, but I didn't understand exactly (french speaking!): 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

**** 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

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

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

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