(I don't know if this is a TextPad problem or something else.) When I try to load a large number of files (in this case about 2700 HTML files totalling about 12mb) the system runs out of resources. MS Resource Meter shows both user and system resources running low. I have 512mb of RAM, Duron 950. When I check system resources with Flexy (a shareware utilitly) it shows most of system RAM still available (often over 400mb). When I use similar resources in some other app, say loading a bunch of images in Paint Shop Pro, I don't have a problem. I'm running TextPad 4.5. On my old PC (64mb of RAM) running an earlier version, I did not have this problem.
TIA,
John
All system resources used
Moderators: AmigoJack, bbadmin, helios, Bob Hansen, MudGuard
Re: All system resources used
Well, I already am part way to an answer on this. I just found some info. on the web (not in the MS KB) which says that in Win 9x, system resources are not related to the amount of RAM, but to things like the number of windows being drawn. So perhaps I'm out of luck on this one, although I'm pretty sure I did not have this problem before. (Probably wrong on that!)
John
John
Re: All system resources used
Check the location where the swap file is being written (i.e., what drive). Check to see how much disk space is available on that drive. (Swap file control is under "Performance" in the 'System' thingy in Start->Settings... at least it is on NT and W2K).
If the amount of disk space on the drive where the swap file is being maintained varies greatly you might want to give the swap file a fixed size so that it will always occupy a given amount of disk space. This will result in more meaningful error messages when disk space runs out.
Or just direct Windows to put the swap file on a drive that has lots of free disk space (or both).
evan
If the amount of disk space on the drive where the swap file is being maintained varies greatly you might want to give the swap file a fixed size so that it will always occupy a given amount of disk space. This will result in more meaningful error messages when disk space runs out.
Or just direct Windows to put the swap file on a drive that has lots of free disk space (or both).
evan