2framesbelowzero
TPF Noob!
- Joined
- Mar 24, 2006
- Messages
- 300
- Reaction score
- 1
I'm trying to help a friend with a PC problem.
The system is running win98 and, although it has over 2.5 GB of free
space on the C: drive, there is continuosly the Win o/s dialogue box appearing stating 'Youve run out of free space on drive C' (Disk Cleanup).
This happens erratically but constantly while trying to open Photoshop,
copy files from a cd onto the C: print out emails etc etc. Mysteriously,
it then ceases for a few minutes and the application is usable..then it starts again.
Needless to say, this is driving everybody nuts. Anyone had this problem or know a fix ? I looked on the net and found an HP url discussing something quite similar re: scanning & printing but the recomended Virtual Memory tweak is not something i want to take responsibility for as it carries a warning about unpredictabile effects if i switch to manually-set parameters.
There is a firewall running with also additional application-protection. I disabled these and it seemed to be the fix...then it started with the error again so i guess not.
The system is running win98 and, although it has over 2.5 GB of free
space on the C: drive, there is continuosly the Win o/s dialogue box appearing stating 'Youve run out of free space on drive C' (Disk Cleanup).
This happens erratically but constantly while trying to open Photoshop,
copy files from a cd onto the C: print out emails etc etc. Mysteriously,
it then ceases for a few minutes and the application is usable..then it starts again.
Needless to say, this is driving everybody nuts. Anyone had this problem or know a fix ? I looked on the net and found an HP url discussing something quite similar re: scanning & printing but the recomended Virtual Memory tweak is not something i want to take responsibility for as it carries a warning about unpredictabile effects if i switch to manually-set parameters.
There is a firewall running with also additional application-protection. I disabled these and it seemed to be the fix...then it started with the error again so i guess not.