TextPad works very good on Windows XP, except that it is slow too save....
Can take sometimes 3 to 5 seconds for a small text file of 10 lines!
Please Help.
Slow to Save
Moderators: AmigoJack, bbadmin, helios, Bob Hansen, MudGuard
-
Maxime Laplante
Re: Slow to Save
sorry, i forgot to said, it's only when I save to a network drive........
And the same file in notepad save in less than a second !
And the same file in notepad save in less than a second !
-
Brian
Re: Slow to Save
I too have been experiencing this problem. I don't understand from where it manifested, because I have been using TextPad for years, saving to the network mapped drive with no problems.
The issue seems to be isolated to one particular server, running Windows 2000 Server . We also have two other servers, one running 2000 and one running NT4. These other two servers save their file with no delay. Opening or reading files from any of the three servers happens with no delay.
I have not been able to ascertain the difference between these two example 2000 servers. Maybe one is running Active Directory. Maybe Textpad is using a Windows built-in function that is handled differently between implementations of CIFS, or SMB? I am using TextPad version 4.5.0.
When the situation occurs, the program appears to go unresponsive for 10 - 30 seconds. Then it returns to life and allows user interaction. The data is saved successfully.
I would bet that the problem is the Windows 2000 server. We have problems with the local network that nobody wants to step in and fix. Nevertheless, we can manipulate files upon the network share using other software as described by the previous posts in this thread.
Thanks for any ideas or suggestions,
The issue seems to be isolated to one particular server, running Windows 2000 Server . We also have two other servers, one running 2000 and one running NT4. These other two servers save their file with no delay. Opening or reading files from any of the three servers happens with no delay.
I have not been able to ascertain the difference between these two example 2000 servers. Maybe one is running Active Directory. Maybe Textpad is using a Windows built-in function that is handled differently between implementations of CIFS, or SMB? I am using TextPad version 4.5.0.
When the situation occurs, the program appears to go unresponsive for 10 - 30 seconds. Then it returns to life and allows user interaction. The data is saved successfully.
I would bet that the problem is the Windows 2000 server. We have problems with the local network that nobody wants to step in and fix. Nevertheless, we can manipulate files upon the network share using other software as described by the previous posts in this thread.
Thanks for any ideas or suggestions,