I know this must be something i'm doing wrong here, and i've looked at Ray's fix for 'Big Al', but i just can't get RCv4.3 to install on my client PC. Even though i point RC to my FS install, i keep getting an error about RC can't find the FS registry entry.Now, i know all my shareing protocols are correct, as i can happily use WideFS to run FSCommander with FS9 & FSX and, if i'm not completely off the mark, FSC must access the same files as RC?I know it DOES work, 'cos i've done before.Any ideas please?

there is an updated section on widefs in the the 4.3 documentationwww.jdtllc.com/v4/rcv43.pdfjd

Hi thereJust downloaded that. There's nothing on page 134 (wideFS) relating to my issue.

Hi Phil,Is WideFS connecting across your network? Do you see "Connected" in the WideFS and FS title bars? If you do then carry on reading. If you see "Not Connected" then WideFS isn't setup correctly and you need to concentrate on that. RC should still install either way but until you get WideFS working RC won't actually communicate with FS.Assuming WideFS is okay then do you have the drive on which FS is installed mapped (F:FS9 for example) or do you use the full URL (myfsmachinefs9 for example)? Either way pointing RC to the folder should work.I'm pretty sure RC doesn't look in the Registry on the FS machine for the location of FS9.EXE but just uses the folder you point it to.Cheers,

If you use a mapped drive, try pointing it to that..should be mapped to "y" or "z". If not, try pointing it to the actual folder...under your "network places" folder though...!!! Also, make sure you have run the mkrwys.exe first in the main FSX root folder on your server pc.You can also try running the FSX registry fix which is widely available.

I have to take a pause from this just now, as i'm swapping over various PCs around the house. I'll be able then to utilise a better PC as my FS client PC.Ray, all your questions are actually answered in my 1st post.... Yes WideFS reports connected. If it didn't, i wouldn't be able to use FSCommander.Running the FSX registry fix makes no difference at all.I wonder where i'm going wrong - i've had this setup before.

Sorry Phil, I spotted that WideFS was okay after posting. Then it's just a case of pointing RC to FSX.Once you've sorted out your computers hopefully the problem will resolve itself. The WideFS install routine has been tested so should be robust.

Hi Guys, Just an update....PCs now swapped and new network setup. Still got those same error messages! "Unable to find FS registry enrty...."I have managed to install RC though. If i hit cancel when asked for correct path, install routine gets 'stuck' in circle. However, if done quickly, before the 'fail' box appears, it goes ok. Bizarre or wot!!??It also snagged up again when looking for the FSX entry, but the same applied.I now just need to reactivate them AGAIN! - Sorry John, hope you got my email about my activations?

Remember that FSCommander uses a slightly differnet method by using the virtual (mapped) drives. I think RC needs to be directed to the actual folder.Ensure you can write to and read from the main FSX folder using your client pc.If you can, and WideFS is connected there should not be a problem.Networks always need "waking up"...ensure you can read to and from all your shared folders from all your PCs before attempting to install RC.Also, if you are un-installing RC ensure you clear out all temp files and do a registry clean.It may also be worth "unsharing" and then "sharing" (again) the relevant folders just to reinitialise everything.The only other thing that may be upsetting the apple-cart, is a firewall...ensure your windows firewall for the shared folders is OFF. Also check that you have switched-off Zonealarm etc...and any antivirus programs.If you have Norton - get rid - it sux big time for networking !