Community

Hi,

I am using TextPad 4.5 under Windows XP. Whenever I attempt to open a text file that is on the LAN, the program locks up.

I love Textpad and have used it for years, but I often have to edit files on the LAN, and this problem is causing me to consider looking elsewhere for a text editor.

--Bruce

I have no trouble opening files with UNC names of the form //server/share/path/name.ext (e.g. File/Open/My Network Places / etc.) under Windows 2000.

Is that what you're doing?

- Rich

I have had similar problems with XP, although they are not consistent. There are certain files that when pulled from a UNC path lock up the machine. I use Textpad mainly for editing kix based logon scripts, and since this problem, I have had to look to other editors for completing this task. Let me know if there is a solution, or even an explanation.

I am double-clicking on a text file in Windows Explorer, or right-clicking and selecting Open or TextPad.

Today I had one open okay, but after I made a bunch of changes and saved it, you guessed it, it locked up.

Never have a problem with local files, always files on the LAN,

I am having a similar problem in Windows 2Kpro.

We decided to copy some (ASCII) files to another server. I can't edit any of the files that were copied. I know I have the proper security, because I can create new files, edit & save files with Notepad, but TP locks up.

I love TextPad, but this bites!

I've had this problem running Textpad 4.5 on a Win XP machine. If you have an anti-virus program that has real-time scanning enabled and if it scans network drives as well that could be why this problem occurs. Try disabling real-time network drive scanning and test it out.

I to have the same problem. Only on XP pro though, not win2k. I have yet to find a solution. It dosen't matter if I double-click to open a .txt file or do the right click method. Sometimes it'll open up, sometimes it'll lock.

This exact problem has been driving me nuts for the past few weeks ever since I installed SP1 on my XP client. I use TextPad to edit ASP and HTML files on my web server, to which I am connected using a mapped network drive. The web server is running W2k Server SP3.

For me, it isn't that TextPad completely locks up. Rather, if I give the program about 20-30 seconds it will eventually open the file, but often the file is not listed in the file list in the left panel. If I enter Task Manager during this slowness, I see that System is sucking up 99% of the CPU. Furthermore, after closing the file and TextPad, the file is left open on the server (looking at Open Files under Computer Management). The only way to close these files is either manually or log off the XP client. This behavior is not experienced when working on local files and.

I rely on TextPad for web development and truly love the speed and ease of use. I guess I will use another text editor until an upgrade is released (hint, hint).

Dan

Found a fix listed on this site in another forum. it's a kludge, and a little dangerous, but it works. BTW, both "autoload" and "Ignore" work.

-Michael

Author: Jacob Carpenter (216.57.209.---)
Date: 04-08-02 18:13

Jennifer--

Its funny you should mention this. I am encountering the same problem, today. In my case, it seems that here on our network the FindFirstChangeNotification API is constantly (and erroneously) signaling a change notification handle... or something like that. I've talked to our network guy about this, and he's currently stumped.

It seems that one workaround is changing the Configure->Preferences...->File option "When files are modified by another process:" to Ignore.

I know that's lame, because its such a cool feature, but it seems to get the job done.

Jacob.

After some testing, I found that the problem (in my case at least) is SP1 for XP Pro. After reinstalling XP and all patches except SP1 the problem has disappeared.