[Paid the fee, Got the Reg., Dwnlde: Everything working OK!!]

Really you should keep your INI files. If you replace them every time you update your copy of WideFS (or FSUIPC or anything) you risk losing anything you've set up to get it working well on your system. Most folks use things like the Run options in the INI files to load up ancillary programs, expecially on the clients. Are you re-entering such things on every update? It doesn't make sense.

Maybe I should simply remove the sample INI files from the ZIP and force everyone to either use their existing ones or make them from scratch?

:(

Pete

Naa Pete,

see my other post to the same issue - I think a note saying that the UseTCPIP=No MUST be in the ini-file if somebody is using good old IPX is probably sufficient - at least as far as I can see. I was not complaining - problem was solved quickly and my post was just a heads-up.

I did not overwrite my existing ini-files, just copied the dll and the exe (in fact I never do) for the reasons you describe.

[Paid the fee, Got the Reg., Dwnlde: Everything working OK!!]

yep right.... but up to now it worked without deleting the ini every time. And I did not want to destroy my settings.

No big issue - its solved now :)

[Paid the fee, Got the Reg., Dwnlde: Everything working OK!!]

Well.... WideFs and Wideclient just gave me a scare :)

I have been running with IPX and W2K for ages with no worries. Now when I just installed the new version WideFs stopped and Wideclient gave me a message about needing a Servername when running under TCP/IP.

The problem was solved quickly by adding UseTCPIP=No into the ini-files. Pete, you might add a note to the manual that this MUST now be in the ini's :)

Otherwise, everything seems to be fine - up to now ...