🚀 go-pugleaf

xu@rintintin.Colorado.EDU (XU  JIEFENG) wrote:

>I ran into a problem running MS window 3.1 on my computer and ask for
your
>expert's help. The window 3.1 was pre-loaded on my 486-DX33 machine and 
>had been working fine for one and half years until yesterday when I typed

>"win", it showed the Microsoft banner and then returned back to MS DOS. 
>Then I reinstalled the Windows using the six original windows disk. The
setup 
>was successful and I can saw the Program Manager Graphics at the end of 
>installation. However, after installation, whenever I type "win", it
rebooted
>the machine after showing the Microsoft banner. Finally I found that I
can
>run windows using the standard mode (type "win /s"), but not the enhanced
>386 mode (when I typed "win" or "win /3", it rebooted machine). Since I
don't 
>have such problems before (I think I ran in enhanced 386 mode before), I
am 
>wondering if there is any software/hardware problem in my machine. I
would 
>appreciate any pointers on this.
>Cheers,

>Jiefeng Xu
?Graduate School of Business
>University of Colorado at Boulder

Sounds like some of your memory developed Alzheimers!  Windows will not
run in enhanced mode if you experience memory problems--I have seen this
in numerous systems.  

You could have experienced a power surge, static charge, etc.  Your chips
may have just gone bad--it happens somewhat frequently and often for no
detectable reason .

Unfortunately, it is not particulary cost effective to test each
individual memory chip--replacing all the RAM is fastest.   Feel free to
call me if you need help with this.

Diana Baranauskas
PC Obedience
DBaran@aol.net
voice:  494-0775

XU,

Did you delete the windows directory before you reinstalled Windows? If I 
had to take a SWAG, I'd say that you probably have one or more corrupted 
dll files. If you don't wipe out the windows directory, you can't be sure 
that the corrupted dll gets replaced. Of course, zapping the windows 
directory means that you'll have to reinstall all of your windows 
applications, but hey, they aren't doing you much good now.

Other things you try are to run ScanDisk from the DOS prompt to get rid 
of lost clusters (assuming you have DOS 6.0 or later; if not, run chkdisk 
/f or something like that).

If this doesn't work or it screws something up, I am not responsible (so 
go sue somebody else).

Good luck,

Bob Thomas

XU JIEFENG wrote:
> 
> Dear netter,
> 
> I ran into a problem running MS window 3.1 on my computer and ask for 
your
> expert's help. The window 3.1 was pre-loaded on my 486-DX33 machine and
> had been working fine for one and half years until yesterday when I 
typed
> "win", it showed the Microsoft banner and then returned back to MS DOS.
> Then I reinstalled the Windows using the six original windows disk. The 
setup
> was successful and I can saw the Program Manager Graphics at the end of
> installation. However, after installation, whenever I type "win", it 
rebooted
> the machine after showing the Microsoft banner. Finally I found that I 
can
> run windows using the standard mode (type "win /s"), but not the 
enhanced
> 386 mode (when I typed "win" or "win /3", it rebooted machine). Since I 
don't
> have such problems before (I think I ran in enhanced 386 mode before), 
I am
> wondering if there is any software/hardware problem in my machine. I 
would
> appreciate any pointers on this.
> 
> Cheers,
> 
> Jiefeng Xu
> Graduate School of Business
> University of Colorado at Boulder

This is exaclty correct.  Check the temp directory and delete all your 
temp files, run scandisk and defrag, try re-starting windows.  If it still 
fails, boot as described and re-install windows.

KErry

DBaran wrote:

> Unfortunately, it is not particulary cost effective to test each
> individual memory chip--replacing all the RAM is fastest.   Feel 
> free to call me if you need help with this.


You've got to be kidding?  Replace ALL the RAM just because Windows 
won't start up?  This is ridiculous.  If this guy has 6MB of RAM, 
you expect him to trade in 6MB of possibly faulty RAM for 6MB of new 
RAM at a cost of what?  $500?  That's just nuts.

What needs to be done is a system backup. Rename the CONFIG.SYS and 
AUTOEXEC.BAT files to something else.  Make a new CONFIG.SYS with 
only the line DEVICE=C:\DOS\HIMEM.SYS  or whatever drive and 
directory contains HIMEM.SYS.

Then reboot the machine, then reinstall Windows 3.1.  It should work 
just fine,and if not, THEN you have some kind of hardware problem.  
More than likely, you have a problem with various drivers or TSR's 
in the CONFIG.SYS and AUTOEXEC.BAT files.  MEMMAKER.EXE can also 
assign memory locations to drivers and programs incorrectly, causing 
such a problem.

Why would anyone leap out and just replace RAM haphzardly?  That not 
very realistic unless you are loaded and really don't know what 
you're doing.


Chris Murphy
Rapid Remedies