I had forgotten about the WARNINGS about Mozilla first downloading to TEMP then copying to the destination.
Was using Mozilla to do an 80 MB download. Unfortunately, my TEMP directory was defined as existing on disk C: What happened was that Mozilla filled my C: disk completely, then went into a 100% CPU-using loop. And the procedures I use to try to avoid system reboot did not seem to be working. As I tried to kill Mozilla, I eventually got a pop-up about OS/2 being unable to save os2.ini. The system appeared unresponsive -- I was forced to do a reboot. [And *during* that (C: still full) reboot, I got messages about OS/2 unable to access certain extended attributes! I cleared out the space chkdsk found was left unclosed by Mozilla, and rebooted again.] I intensely __DISLIKE__ it when an application can during its "normal" operation bring down OS/2. From now on, I will make sure that TEMP is not on the OS/2 system disk. But it would sure be nice if Mozilla could handle an "out of temp disk space" condition more gracefully. mikus
