Page 1 of 1
Win 2000 Server Shares
Posted: Tue Mar 26, 2002 11:47 am
by Peter Clouston
I wondered if anyone had come across this.
When accessing text files on a Windows 2000 Server Share, textpad 4.5 stops and hangs. It has to be terminated using the task list.
This only occurs when using a Windows 2000 Professional machine - not a 95 or 98 machine to the same share/file combination. The other fact is that they are running Novell's 32 Bit Client (evaluation of Windows 2000 Server).
Would be grateful for any advice.
Peter Clouston
Re: Win 2000 Server Shares
Posted: Wed Apr 03, 2002 8:03 pm
by Susumu Harada
I have been encountering a similar problem, where TextPad would hang when I try to open certain files from certain drives on my Windows 2000 Advanced Server machine.
I have three drives setup (C: D: and E:), and TextPad seems to hang when I try to open any files from the D: drive or C: drive, and certain files from the E: drive. There was one time when I let TextPad sit for few hours in this state, and it actually came back, and I was able to continue to work on the file without any problems.
I would be interested in hearing if you have come across a solution or an explanation for this behavior.
Susumu Harada
Re: Win 2000 Server Shares
Posted: Sat Apr 06, 2002 6:49 am
by Raheem Rhemtulla
I am noticing this too, but I also have noticed that this only happens for certain file types, regardless of the drive that they reside on. Text-pad doesnt hang if I open a "*.ini" file, but if I use it for a "*.txt" file, it needs to be stopped using Task Mgr.
I am running Win 2000 Server with IE 6, and I thought that this might be because of the comctl32.dll that gets distributed with IE (this is listed by the Textpad site), but I have tried changing this to a newer one to no avail.
So if you guys have found a response, please let me know. Textpad is one heck of a critical app, but this is frustrating!
Thanks RR
Re: Win 2000 Server Shares
Posted: Tue Apr 09, 2002 12:52 pm
by Richard Gordon
Under the preferences / file if I set the "When files modified by another program" to "Ignore" this seems to solve the problem.
For us the problem only occurs when accessing files from a Windows 2000/XP client machine and the file is on a Windows 2000 server machine (running mcafee !!). Windows 98 client seems fine as do windows NT servers.