the .exe names have to be rcv3.exe, regardless of whether it is 3.00 or 3.01jd

I'm not sure what you're saying here. rcv3.exe is the 3.01 binary.

have you installed 3.0, and upgraded to 3.01 on your widefs machine?i guess i'm not following which machine is getting the error.jd

Sorry about that. The WideFS Server has no RC installed. That PC has a WinXP Bare bone system on it with just FS2002 installed. The Client WideFS has RC 3.0 installed on it with the config stated in the first post. When I rename rcv3.exe to rcv3.exe.bak (Which is the 3.00 version) and copy the new rcv3.exe (Which is the 3.01 downloaded from your site) to the install directory I get the error stated in my first post. If I reverse the naming and start rcv3.exe (Which is now 3.00) it works fine. I even flew a flight last night with the 3.00 version using WideFS. I hope this helps. -Matt

maybe you have bad bits. try downloading it again, and extracting the .zip file

RC 3.00 works. I installed, sent key request. Ran 3.00, updated the key, backed up the .exe, copied 3.01 to the install directory.If I start the backup exe RC 3.00 runs fine. However, if I start the 3.01 exe I get an Application error:The instruction at "0x77ea918" referenced memory at "0x00229000". The memory could not be "read".The instruction and reference doesn't change whenever I try and run 3.01.Here's my setup:Dual Intel Celeron 500Mhz512 megs RAMWindows XP ProMS Office XPMS Office XP DeveloperVS.NET 2003VS 6.0 EntSQL Server 2K (Not Running)IIS 5.1.NET Framework 1.1Inoculan 4.53ZoneAlarm 3.xI'm using WideFS. So this is just a client.What's odd is that 3.00 works with no problem.Any ideas?-Matt

Ok,I've uninstalled and reinstalled, downloaded a new binary off your website and I'm still gettting the same error. What could have changed from the 3.0 and 3.01 compile to cause this?Any idea?

the problem is something strange on your machine. hundreds/thousands of people have done what you have done, without problems.open a dos window, change directory to your rc directory. type the command dir *.* > dir.txtcopy and paste the contents of the dir.txt file here, or send it to me.also open the rcv3.dat file, and copy and paste the contents here, or send it to mejd

I agree. There's something diffrent about my machine. Here's the info that you requested. Volume in drive C is DRIVEC Volume Serial Number is D0F3-BF29 Directory of C:FSUtilitiesrcv3004/23/2003 12:52 PM

add the following line to the rcv3.dat file, and see if that helps 1800 , 1800 , 1800

I didn't put that in the .dat file, however this is what happened to fix the problem.You can see that the directory is C:FSUtilitesrcv3. Just off a whim I moved the root files to another directory above "FSUtilities" and the 3.01 binary worked just fine. So I copied the entire install onto the root of the C: drive and everything works fine now. This is a strange one for sure. All the premissions seem the same. One for the books.Thanks for you quick responses to all this. -Matt