WideFS and ActiveSky6

[RichardL]

Hi Pete,

While I wait for an answer from ActiveSky, I thought I'd you a question.

I do not know if you use the AV6 program so you may not be able to answer this question. Could WideFS in any way keep AV6 from accessing network files?

Since I upgraded to AV6, I cannot get AV6 to recognize my FS9 pc over the network. I have been emailing AS over the past few days and through testing have determined that something (not AV6) is keeping the AS software from seeing the correct files on the FS9 pc.

I have no antivirus software other than what may be in BIOS. I added an exception to WinXP firewall for AV6. Still the problem persists.

WideFS may have nothing to do with the problem but I thought I'd better ask.

Regards,

Richard

[Pete Dowson]

I do not know if you use the AV6 program

I installed it yesterday. It looks a lot like ASVE and ASV before it, which I've been using since they appeared.

Could WideFS in any way keep AV6 from accessing network files?

No, of course not. File access is a Windows thing. WideFS has no such powers over Windows. Why should it, even if it could?

Since I upgraded to AV6, I cannot get AV6 to recognize my FS9 pc over the network.

Did you edit its INI files as the install notes mention? It seems easy enough to get the weather part working, but I had more problems with the grahics part which wanted to backup my cloud textures. Seems you also have to enter the correct network path for the Graphics thing -- I edited its INI file too, but it still needed me to change it in its dialogue. Seems okay now. It's a bit of hassle during installation and first start up, I agree. It wasn't helped in my case by my having remnants of an FS installation on the same client as AS6.

I have been emailing AS over the past few days and through testing have determined that something (not AV6) is keeping the AS software from seeing the correct files on the FS9 pc.

Can you see them, in Windows explorer? If the Explorer can, then anything else should (unless possibly you have firewalls excluding specific programs -- but I don't think they operate on simply file access, do they?).

To make paths easier I always share my FS9 path explicitly on the FS PC, with a short share name. So, for instance, the path to my FS9 looks like

\\fspc\fs9

This make it much easier to enter (and check) than using the horrible default FS install path.

Regards

Pete

[RichardL]

Hi Pete,

I'll take a look at the AV6 ini again. Maybe the problem is there.

Yes, through Explorer on the AV6 pc I can see all the FS9 files. I disabled the WinXP firewall on both pc's but that did not help.

You may be on to something with the FS9 name. A month or so ago we were discussing a RunReady problem that I believe was related to folder names and length.

Thanks for the help,

Richard

[Pete Dowson]

I'll take a look at the AV6 ini again. Maybe the problem is there.

There's also an ini which needs the path in the graphics folder.

Pete

[Pete Dowson]

I don't know whether it will help or not, but I've just been informed that there's a Service Update for ASv6 available now. See the sales.hifisim.com site.

Pete

[RichardL]

Pete,

I'll check the AV6 update but Damian has been emailing me new .exe files to try to fix this problem.

One other question. Is it necessary to include the drive letter in the ini file.

My FS9 is on E drive. In the AV6 ini, the FS path is identified as:

FSPath=\\SIMSERVER\FS9\

Any idea if it matters whether FS9 is on C, D, E, etc drive in the path name?

Richard

[Pete Dowson]

Is it necessary to include the drive letter in the ini file.

My FS9 is on E drive. In the AV6 ini, the FS path is identified as:

FSPath=\\SIMSERVER\FS9\

Any idea if it matters whether FS9 is on C, D, E, etc drive in the path name?

The name after the \\\ part is the SHARE name you gave it in Windows explorer when you told Windows you wanted to share it. By default, for Drives, Windows offers the drive letter (sometimes the drive name), but not for folders. Either way, you should know its name as you chose it. It should be unique on that PC -- I doubt that windows would allow anything not unique.

Be sure you also gave permission to all to both read AND write files on that share.

I noticed in the update (SU1), which I just installed and tried, that it wanted my Application Data folder sharing too -- which I've done as "AppData". Maybe it wanted that last time, but the mess with my partial FS installation (now all cleaned up) on the Client got it diverted.

Regards,

Pete

[RichardL]

Pete,

One clarification and I will quit taking up your valuable time.

When you say "Be sure you also gave permission to all to both read AND write files on that share". Where is that done?

I can see two psssible places. When I right click on the folder and select Sharing and Security, there is a box to check to "Allow network users to change my files". Is that the correct place?

The other area I see is right click on the folder and under Properties there is a check box that says "Attributies Read-Only". Do I remove the check in that box to allow read and right?

Richard

[Pete Dowson]

When you say "Be sure you also gave permission to all to both read AND write files on that share". Where is that done?

I can see two psssible places. When I right click on the folder and select Sharing and Security, there is a box to check to "Allow network users to change my files". Is that the correct place?

That's where I mean, yes.

The other area I see is right click on the folder and under Properties there is a check box that says "Attributies Read-Only". Do I remove the check in that box to allow read and right?

Ouch! Is that checkmark BLACK or GREY?

If the check mark is GREY I think it simply means that probably at least one file in the folder or its subfolders is or may be read-only, or something like that. It may even mean "leave this attribute to individual cases", whereas no check means all read/write and a solid black check means all read-only.

If it is BLACK, then Yes!!! That would stop everything writing to that folder! It isn't anything to do with sharing -- it would stop things writing there on the same PC too!

Regards

Pete

[RichardL]

They were BLACK "Read Only". I unchecked them. Seems like I saw in one or maybe two of the folders, the Read Only box was filled in with Green. Anyway, all those that have anything to do with FS and ASv6 are unchecked now.

Thanks for the help,

Richard

[RichardL]

Pete,

I uninstalled ASv6 and the network. Reintalled and re-established the sharing files with "full read'write". ASv6 is now working correctly.

Many thanks for the help,

Richard