I encounter an odd problem when I double click a file to open it with textpad (5.1, I will upgrade to 5.2 in a few minutes). When I double click on any file of an associated type on my hard disk TEXTPAD opens it correctly and everything works.
When I do the same on any file located on any network drive I get the traditional (I have scanned the forums extensively)message "Ok to create" + the filename of the file in question. Whether you then select yes or no is irrelevant, it does not work.
The network has not changed from before and I did not have this problem as long as I had an XP machine, it is now there on my VISTA machine although I have set up the system to run Textpad as an XP service pack 2 application with administrator rights.
I suspect that the obviously much slower network access imposed by VISTA is causing the problem. By the time TEXTPAD expects the file to be accessible VISTA is still chewing on it and TEXTPAD then thinks the file does not exist.
Any suggestions on how this could be solved would be much appreciated
Tried it but unfortunately: no success. In the mean time I have noticed something else though about VISTA and the described behaviour:
- When you open explorer to locate a file it often shows the network drives as being inaccessible.
That is not through because as soon as you click it to get access you get it instantly.
- If you then double click a file associated with textpad, textpad will come up with the "OK to create" message. then click "no"
- If you then use the "open" facility in TEXTPAD, edit the file etc.. everything works.
- oddly enough though from that moment on you can double click any files associated with TEXTPAD on that same network drive and everything works fine.
I Gues it must have something to do with VISTA initially telling TEXTPAD something wrong about the file that was double clicked or the network drive it is on.
If anybody can think of something to solve it it would be much appreciated
In reply To "Mudguard's" question: no it does not.
Secondly: did some further detailed checking and I can now be more precise when it goes wrong. The exact procedure is:
- Open explorer and go to a particular file.
- Double click it => you get the "create" message.
- Click "no" and use "open" from the textpad software => you get a sort of explorer like file selection utility.
- Main difference with the actual "explorer" display: the network drives are all crossed out "red" as if they are not available.
- Simply clicking them gets you access and you can select the file + open it effortlessly.
- Having done this you can then double click any other file on the same network drive using the standard explorer and evrything works.
just found a workaround: instead of selecting a file to double click through "computer", selecting a network drive and then double clicking the file use a different method.
- Use the general windows network symbol instead of "computer"
- select the server containing the "network drives"
- select the "folder" corresponding to the "network drive" where the file is located.
- Then double click the file => everything works perfectly
is causing the problem. By the time TEXTPAD expects the file to be accessible VISTA is still chewing on it and TEXTPAD then thinks the file does not exist.
