Path: utzoo!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!sdd.hp.com!spool.mu.edu!snorkelwacker.mit.edu!stanford.edu!leland.Stanford.EDU!jessica.stanford.edu!aaron
From: aaron@jessica.stanford.edu (Aaron Wallace)
Newsgroups: comp.windows.ms
Subject: Re: Extended Memory blues
Message-ID: <1991Mar7.202637.18984@leland.Stanford.EDU>
Date: 7 Mar 91 20:26:37 GMT
References: <1991Mar7.173724.20416@murdoch.acc.Virginia.EDU>
Sender: Aaron Wallace
Distribution: usa
Organization: Academic Information Resources
Lines: 45

In article <1991Mar7.173724.20416@murdoch.acc.Virginia.EDU> ak7g@maxwell.acc.Virginia.EDU (Ashish Kapur) writes:
>
>I am sorry if this question has already been addressed.
>
>I am having problems with my windows 3.0a program after
>I installed 1M extended memory.
>
>I am running in standard mode.
>
>I have a total of 2M of memory now.
>Details of my system:
>
>386-25MHZ clone.
>ST157n-1 Seagate SCSI 48MB hard drive.
>Windows version 3.00a
>
>
>The config.sys file reads as:
>
>CONFIG.SYS
>--------------------------------------------------------
>FILES=30
>BUFFERS=30
>device=c:\himem.sys
>device=c:\windows\smartdrv.sys 768
                                     ^^^^--- note lack of 2nd number!!!
>
>---------------------------------------------------------
>
>Now when I boot up my system the windows startup logo is displayed but
>after that the system hangs up
>

I had a very similar problem: a 286 w/2 meg.  Sometimes it would load Windows
fine, other times it hung at the logo.  Thing is it seemed to be random; I'd
run it, it'd work fine, then exit and try again and kaboom.

The fix, as I hinted at, *seems* to be that a minimum cache value needs to
be specified.  I don't know if it's in TFM, but this jiggle fixed things
for me.  Maybe startdrive has a bug when Windows tells it to release every-
thing, which may happen on a 2 meg system.  

Anyway, hope this helps everyone...  Only took about 6 hours to find this fix!

Aaron Wallace