[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: BUG: HardPressed in 'infinite loop'?
In article <1993Jul1.111503.1@gallua.gallaudet.edu> 11hlayton@gallua.gallaudet.edu (Aviator Margalis Tast'annin) writes:
>up, so I ran AWGS. HP turned the border pink, indicating that it was busy
>uncompressing AWGS, then a text error screen came up:
>------------------HardPressed----------------------------
>|"Received an unexpected error from GS/OS (disk is full)|
>|while trying to expand the file: [#0506] |
>|:CyberDisk2:Apps:AWGS:AppleWorksGS continue<- |
>---------------------------------------------------------
>
>When I pressed return to 'continue', my GS went back to the pink bordered screen
>just like it was before the error...a few moments later, the same error message
>comes up. Everything I try to do won't abort this 'infinite loop'. Seems like
>HP keeps trying to expand AWGS even though it posts an error message.
Probably not HP's fault. Odds are it returned the error message, but the
caller ignored it. The system loader reads things in (I think) 16K chunks,
so it was probably busily trying to read the next chunk. Strange though;
the system is usually pretty good about catching errors. Maybe it just
didn't expect a "disk full" during a read. :-)
>The reason for my confusion is, that my system has PLENTY of room...here's my
>system setup:
Where's your temp folder located? Sounds like that managed to fill up, or
GS/OS got confused.
>Gee, I know this is pretty detailed, but since I couldn't find anything in the
>manual regarding this, and since I have plenty of room on my system to expand
>AWGS, I can't figure out why HP acted like it did.
If you've got 16MB of free space, I find it hard to believe. However, HP
isn't making these errors up; it tried to write some stuff and GS/OS told it
that the disk was full (error $48). #0506 comes from the low-level expansion
disk I/O routines.
Since you hit reset, you'll probably have a left-over file in the temp
folder. It'll get overwritten eventually, but you might want to take a look
at it and see how big it is (and remove it to free up space).
In the mean time, if you've got a disk checking program like ProSel, Universe
Master, or whatever that Vitesse product is (Salvation?), set HP to inactive
and run it on the disk. (And no, HP can't screw up your disks... it's file
oriented, not disk oriented.) Sometimes GS/OS spits out a "disk full" error
when it gets confused and can't allocate any space. It might be something
funny with your disk. Most likely it was caused by something stomping on part
of GS/OS and causing it to get all confused, so rebooting would've cleared
it up.
At any rate, if it works now, you're probably fine.
--
fadden@uts.amdahl.com (Andy McFadden)
[ Above opinions are mine, Amdahl has nothing to do with them, etc, etc. ]