🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.os.msdos.misc
Article #3426

How do I prove that it is a hardware problem?

#3426
From: Sergio L Aponte
Date: Tue, 18 Jun 1991 23:59
40 lines
2274 bytes
	System : 386/33 64K cache 4Mb RAM Megatrends BIOS
		 200Mb hard drive, 5.25 HD (A:) and 3.5 HD (B:)

	Problem: System came with DOS 4.01 on the hard drive. WHen I tried to
	add emm386.sys to the config.sys, I lost access to the flopy drives.
	Ventura loved it, but no flopy drives was a problem. If I take the
	emm386.sys OFF the config.sys, I can leave himem.sys and the mouse
	driver in there and all works ok, other than ventura (and some other
	software) complains of shortage of memory.

	Thinking it might be a DOS 4.0 BUG, I upgraded to 5.0 right away. The
	5.0 did NOT put emm386.exe in my config.sys, but added "DOS=HIGH" to it,
	and I lost my flopy drives again. I took the "DOS=HIGH" out, all works
	ok. I added "DEVICE=C:\DOS\EMM386.EXE RAM" and lost my flopies again.
	So I am back to HIMEM and the mouse...

	"LOST the flopy drives?" That means that when I do a "dir a:" or "b:",
	I get
		1) locked up (reboot)
		2) my screen printed (!)
		3) a partial list of files and then garbage

	Other "info" : The system has a shadow ram, some 64K @ ffffff (I
	might be missing an "F"). I disabled this, no change. Do I have to
	specify this area to emm386 not to be used? How?

	What else can I check?

	I called my "clone" vemdor, they said it was "DOS"es fault, to
	get querterdecks QEMM. How do I know if this is true???

	Thanks for any/all help
						Sergio

--
===============================================================   _|||_
Sergio L. Aponte, MTS @ ASK Computer, Ingres Product Division     <*,*>
Internet : sergio@coqui.ingres.com                                [`-']  Keko
UUCP     : {sun,mtxinu,pyramid,pacbell}!ingres!coqui!sergio       _"_"_  Jones
Technical Details
Message-ID: <1991Jun18.235933.18532@ingres.Ingres.COM>
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!think.com!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!ucbvax!mtxinu!rtech!ingres!sergio

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!think.com!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!ucbvax!mtxinu!rtech!ingres!sergio
From: sergio@ingres.com (Sergio L Aponte)
Newsgroups: comp.os.msdos.misc
Subject: How do I prove that it is a hardware problem?
Message-ID: <1991Jun18.235933.18532@ingres.Ingres.COM>
Date: 18 Jun 91 23:59:33 GMT
Reply-To: sergio@Ingres.COM (Sergio L Aponte)
Organization: Ask Computer Systems Inc., Ingres Division, Alameda CA 94501
Lines: 40