🚀 go-pugleaf

In article <92351.29836.J056600@LMSC5.IS.LMSC.LOCKHEED.COM> J056600@LMSC5.IS.LMSC.LOCKHEED.COM writes:
>
>Aye, 'tis true that the "three-fingered salute" in the middle of an app will
>giving you the "Updating allocation map..." message.  I've also encountered
>a "volume damaged" (aka "you should have backed up your hard drive, dummy)
>error on doing so--twice.  After the second time I scrapped Stacker and
>have had no more bad sectors arise (version 2.0).

I have the "Updating FAT" messages when I reboot during an app as well, but
with v1.x, I have never encountered the "volume damaged".  It looks like
all of the complaints I have seen about Stacker have been regarding v2.0
Yet another reason for me to keep using v1.x like I have been for over two
years....

>What happens when a program hangs up, though?  You can't exit normally and
>gracefully.  You have no choice but to reset the machine.  I always tried to
>avoid needing to turn the machine off while programs were actively running,
>but it wasn't possible 100% of the time.

I have programs hang all the time on me...and I am constantly rebooting 
while on a Stacker volume.  As long as the app in question wasn't in the middle
of a read/write exercise, you are okay.  Otherwise, on reboot, Stacker will
have to update the FAT the best it can.  Then you should run SCHECK and
CHKDSK to fix any lost sector groups, etc...


-- 
John Mechalas                                          "I'm not an actor, but
mechalas@gn.ecn.purdue.edu                                 I play one on TV."
Aero Engineering, Purdue University                     #include disclaimer.h