Apologies if I'm asking a question that's been answered elsewhere.

I've installed Kate on my Win7 machine.

I've added a Win7 desktop shortcut to a remotely mounted UNIX filesystem.

When I launch Kate, I can navigate within the remote UNIX filesystem fine, but when I try to open a file on the remote filesystem, I see an error message like:

The file /<remoteide>.org/xxx/yyy/filename could not be loaded, as it was not possible to read from it.
Check if you have read access to this file.

I have no problems opening this same remotely-mounted UNIX file from other (Windows-based) editors on my PC.

Does anyone have any suggestions on what I could try to resolve this?

Regards,
Gavin Bowlby

Is Kate able to access other files, stored locally on the system, without problems?

Thanks for the response! Yes, Kate can access files stored locally on my WIn7 PC. If I copy the file over from the remote site to my local PC, Kate can access the file just fine.

How is the remote file system mounted? Is it through the regular Windows Map Drive mechanism, or something else?
Based on the path you've shown, I suspect the appropriate drive letter prefix isn't being included for some reason - preventing the file from being opened.

It's not mounted via a drive letter.

The remote filesystem is accessed via something like:

\\x.org\<UNIX access point>\..\..

where x.org is my company's filesystem access point, with a UNIX filesystem under the umbrella filesystem access point.

I'm accessing my company's data via a VPN connection. I think the domain name: \\x.org has been added to a list of trusted WIndows domains, because I can access other parts of my company's filesystems from a Web browser when I'm connected to the VPN.

thanks so much!
Gavin

I see. I suspect the problem is that KDE on Windows applications don't support UNC paths. Can you try mounting it via a drive letter to see if that allows you to open the file in Kate?

Bingo! After mapping the network address to a drive, I can open the file after navigating via the drive.

Thanks so much for your help!

Gavin

How did you do that?
Thank you.

Here's how I did this:

1) right click on "My Computer" or whatever the name of your computer is on the Windows desktop icon for your computer

2) select "Map network drive..." to pull up the "Map Network Drive" dialog box

3) select the drive letter you'd like to use

4) provide the network path to get to the remote filesystem you'd like to access. Example:
\\<remote server>\<directory you'd like to access>

5) check the box to reconnect at login if you want this done

6) check the box that says to connect with different credentials if needed. This isn't required, you can always specify a domain-specific userid.

That should be it. The drive may not be there at login if you have to VPN into the remote network, but it should be accessible after this step has been done. There can be delays in accessing the remote data if the connection "ages out". The "aging out" window seems to be pretty quick, about a minute or less. I've found that the fastest thing to do is to cache the files I want on my local PC, and then use a script to upload the changed files to the remote site. In this usage model, I never change files on the remote site with an editor, I always change them on my PC and then upload the new copies to the remote site.

HTH,
Gavin