New test versions of FSUIPC and WideClient

[Patrick Smith]

No using old FS9 without the patch,have wideviewW and the new patch does not
seem to work with it all,so dont use it,it causes "frozen moments" for me
may be doing something wrong but dont have the time to fool around with
it,you know,as what works ,works!


Learn CPR

[Patrick Smith]

Well i dont know i thought i was replying to the New test versions FSUIPC and
WideClient,i placed the FSUIPC.dll on the Modules section,and when
starting FS9 it would not start,error report pointed to the FSUIPC Mod.dll





Learn CPR

[Peter Dowson]

On 11/21/2004 3:42:34 PM, Patrick Smith wrote:
>Well i dont know i thought i
>was replying to the New test
>versions FSUIPC and
>WideClient

Well, that is this thread. It was just your "Yes Pete" as if you'd said
something specific before to which I'd answered with a question. Is this not
so?

>i placed the FSUIPC.dll on the Modules
>section,and when starting FS9 it would not start,error
>report pointed to the FSUIPC Mod.dll

What sort of error report, please? How "not start"? There really isn't
anything that drastic changed in FSUIPC, just little additions and
improvements.

I can't really answer general reports, I do need specifics!

1. What EXACTLY is this message and when, exactly, does it occur?
2. What version of FSUIPC were you using before?
3. What version of FS? FS2002, FS2004, with/without update?

Regards,

Pete

[null null]

Just downloaded this version FSUIPC and WideClient, installed, and got the
following:
--------------
ERROR SIGNATURE:
AppName: fs9.exe AppVer: 9.0.0.30612 ModName: fsuipc.dll
ModVer: 3.4.2.2 Offset: 00020202
---------------
My OS is WIN XP PRO, Patch 1

Hope this helps.....

Matt O.


"Peter Dowson" wrote in message
news:271000.53815@wb.onvix.com...
> Hi folks,
>
> Here are my latest interim test versions of FSUIPC (3.422) and WideClient
> (6.412).
>
> The main work in FSUIPC has been in areas concerned with timestamps and
> corrections to a number of odd little things which have affected internal
DLLs
> and GAUges.
>
> In the more recent releases of WideFS, most of my attention has been on
> improving the efficiency of WideServer, as well as making to operate with
both
> TCP/IP and IPX/SPX at the same time. In the last couple of weeks I have
> concentrated instead on making WideClient run more smoothly. I think I've
> achieved this, now, by dividing up the tasks it does between different
threads
> in a different way, and re-ordering its priorities. Certainly it seems a
lot
> smoother here on all four of my Client PCs, and even works well on the PC
> which is running 3 copies of the Project Magenta PFD/ND/EICAS program.
>
> Please use them when you can, but don't delete your existing versions
just
> yet. I'd like to hear of any problems.
>
> Regards,
>
> Pete Dowson



----------------------------------------------------------------------------
----


>

[Peter Dowson]

>Just downloaded this version
>FSUIPC and WideClient,

I've uploaded a revised WideFS since then!

>installed, and got the
>following:
>--------------
>ERROR SIGNATURE:
>AppName: fs9.exe AppVer:
>9.0.0.30612 ModName:
>fsuipc.dll
>ModVer: 3.4.2.2 Offset:
>00020202
>---------------
>My OS is WIN XP PRO, Patch 1

Got this from where, doing what? There's no "signatures" in FSUIPC, so I have
no idea what this is about. What did you do and what reported that
message?

That offset "00020202" sounds very suspicious! Sounds like a bad download to
me. Try again. Version 3.422 is now in good use in several hundred Beta
tester's systems with no problems so far, and it will form the basis of the
next release within two weeks.

Regards,

Pete

[null null]

I should of mentioned, I do have the latest WideFS...

3.422 I installed is a second download and install, with the same anomaly
occurs, both times.

The "Microsoft Flight Simulator has encountered a problem and needs to
close. We are sorry for the inconvenience." message come up after starting
FS9.

Going to "See what data this error report contains" is where I found the
ERROR SIGNATURE information.

Only the FS9 system was running at the time of FS9 startup without any
other
programs running.

I reverted to the previous version, it's working fine. Any thing I can do
to
help resolve this, please let me know. BTW, I've never had any problems
with previous versions of FSUIPC.

I've decided to test FS9 with the 3.422 version on a separate system,
unfortunately I have the same anomaly occurring on that system. Peter, if
you don't mind, would you please send me ver 3.422 direct to my email....
matt@a340project.us

Matt O.

"Peter Dowson" wrote in message
news:271988.53815@wb.onvix.com...
> >Just downloaded this version
> >FSUIPC and WideClient,
>
> I've uploaded a revised WideFS since then!
>
> >installed, and got the
> >following:
> >--------------
> >ERROR SIGNATURE:
> >AppName: fs9.exe AppVer:
> >9.0.0.30612 ModName:
> >fsuipc.dll
> >ModVer: 3.4.2.2 Offset:
> >00020202
> >---------------
> >My OS is WIN XP PRO, Patch 1
>
> Got this from where, doing what? There's no "signatures" in FSUIPC, so I
have
> no idea what this is about. What did you do and what reported that
> message?
>
> That offset "00020202" sounds very suspicious! Sounds like a bad download
to
> me. Try again. Version 3.422 is now in good use in several hundred Beta
> tester's systems with no problems so far, and it will form the basis of
the
> next release within two weeks.
>
> Regards,
>
> Pete
>

[null null]

Hi Peter. Sorry to say this but I too am getting an error with this ver of
FSUIPC. Same as Matts....
I am using XP Home SP2 installed All that I was tying to run was FS.

Bob Reed
"Peter Dowson" wrote in message
news:271000.53815@wb.onvix.com...
> Hi folks,
>
> Here are my latest interim test versions of FSUIPC (3.422) and WideClient
> (6.412).
>
> The main work in FSUIPC has been in areas concerned with timestamps and
> corrections to a number of odd little things which have affected internal

> DLLs
> and GAUges.
>
> In the more recent releases of WideFS, most of my attention has been on
> improving the efficiency of WideServer, as well as making to operate with

> both
> TCP/IP and IPX/SPX at the same time. In the last couple of weeks I have
> concentrated instead on making WideClient run more smoothly. I think I've
> achieved this, now, by dividing up the tasks it does between different
> threads
> in a different way, and re-ordering its priorities. Certainly it seems a
> lot
> smoother here on all four of my Client PCs, and even works well on the PC
> which is running 3 copies of the Project Magenta PFD/ND/EICAS program.
>
> Please use them when you can, but don't delete your existing versions
just
> yet. I'd like to hear of any problems.
>
> Regards,
>
> Pete Dowson



--------------------------------------------------------------------------------


>

[Peter Dowson]

>Hi Peter. Sorry to say this
>but I too am getting an error
>with this ver of
>FSUIPC.

And you aren't going to show me the FSUIPC LOOG file either? I cannot work in
a vacuum, sorry.

Luckily Matt has just emailed me his Log. It looks like he is still using
FS9.0. I am wondering if you are too? I will have to uninstall FS9.1 to try
and test this ... currently all my systems are on 9.1. I was really on the
verge of withdrawing support for 9.0, there's so many problems in it solved
by 9.1. If you are still on 9.0, can you tell me why, please?

It's now 01:45 am here. I'll start on this tomorrow. If I cannot reproduce
it, or you are on 9.1 after all, then I'll probably need to start adding more
diagnostics.

Regards,

Pete

[Peter Dowson]

On 11/23/2004 8:22:12 PM, Bob Reed wrote:
>Hi Peter. Sorry to say this
>but I too am getting an error
>with this ver of
>FSUIPC.

Okay, I have assumed you are on 9.0. In this case please discard the interim
version you have and use 3.424 just supplied in a separate thread.

Regards,

Pete

[null null]

Yes Peter I am still using FS 9.0. If you would like my log file I can send

it. I was in a hurry when I posted this there was someplace I had to be.

Bob Reed
"Peter Dowson" wrote in message
news:272107.53815@wb.onvix.com...
> >Hi Peter. Sorry to say this
>>but I too am getting an error
>>with this ver of
>>FSUIPC.
>
> And you aren't going to show me the FSUIPC LOOG file either? I cannot work

> in
> a vacuum, sorry.
>
> Luckily Matt has just emailed me his Log. It looks like he is still using
> FS9.0. I am wondering if you are too? I will have to uninstall FS9.1 to
> try
> and test this ... currently all my systems are on 9.1. I was really on
the
> verge of withdrawing support for 9.0, there's so many problems in it
> solved
> by 9.1. If you are still on 9.0, can you tell me why, please?
>
> It's now 01:45 am here. I'll start on this tomorrow. If I cannot
reproduce
> it, or you are on 9.1 after all, then I'll probably need to start adding
> more
> diagnostics.
>
> Regards,
>
> Pete
>