🚀 go-pugleaf

In article <hatton.727755291@cgl.ucsf.edu> hatton@socrates.ucsf.edu (Tom Hatton) writes:
>From: hatton@socrates.ucsf.edu (Tom Hatton)
>Subject: Re: Is OS/2 a dead end?
>Keywords: So quoth Bill Gates
>Date: 23 Jan 93 02:14:51 GMT
>djg2@crux3.cit.cornell.edu (David J. Greenberger) writes:
>>tcscs!zeta@src.honeywell.com (Gregory Youngblood) writes:
>>>or so.  With OS/2, when it reboots, particularly after a crash or unexpected
>>>shutdown, it takes upwards of 5 to 30 minutes depending on your hard drive
>>>size and configuration.  One time of that happening and your average computer
>>>user is going to be disoriented.
>
>>Upwards of 5 to 30 minutes?!  How much RAM do you have?  I have 16 MB on a
>>486/33, and it *never* takes more than one or two minutes for OS/2 to boot up.
>
>It takes little time for an ordinary boot, but if you read his post, you'll
>note he's talking about "after a crash or unexpected shutdown" and he's
>absolutely right: if you have a crash, requiring a reset or cold boot, then
>the system will see that on boot, and examine the disk with chkdsk (don't
>remember what level, but I'll assume f3). 
> 
No, not level f3. It dowsn't take that long. 

>If you have a BFD (big disk) then the chkdsk is going to take a long time
>to go thoroughly through the partition(s). 
> 
Well, I have 2x200Meg, and it takes a whole lot less that 5 minutes, 
even after a _total_ crash. You will need about a zillion megs to 
get 30 minutes (at least).

>I disagree that it would "disorient" someone; alarm, potentially, and
>annoy, certainly. But it does tell you what it's up to while it goes at it,
>so I don't see anyone getting too confused. And it's nice to know that the
>file system is intact before getting the system going. Just painful waiting
>for that assurance.

The last UHPFS.DLL fix helps alot.

>-- 
>Tom Hatton
>hatton@cgl.ucsf.edu
>(415)-476-8693