[comp.sys.ibm.pc.misc] ** Heeellp!!! System crash due to 3.5" floppy installation?

bell@cod.NOSC.MIL (Thomas T. Bell) (05/29/91)

I recently purchased a TEAC 1.44 Meg drive for my clone '386 with an
AMI BIOS.  The drive worked fine except that it would not send a signal
to the computer that a new disk had been inserted into the drive.  
Consequently, the dir command would always give the same directory
listing of drive B: (where the 3.5" drive is located) even if a new
disk was inserted into the drive.  So, I called Datel Computers and
they told me that it might be a problem with the drive itself and
that they would be glad to exchange it.  So I go exchange the drive and
install the new one exactly like the previous one.  When I booted up
the computer I noticed that the autoexec.bat took a long time to run.
Also, the autoexec.bat hung on my Logitech mouse TSR for about two
minutes before it finally finished running. I put a formatted 3.5" disk
in the B: drive and typed the dir command and got a Drive not ready 
error.  Also, when the computer was initially booting up the drives made
a strange churning sound.  I turned the computer off and removed the
3.5 drive and then turned on the computer again.  However, the problem
with the slow boot up was still there and the mouse TSR hung again.
I tried running my communications program but the modem initialization
failed and when I tried to log on to some of my favorite BBSs I just
received garbage on the screen.  I then ran Norton Utilities system
information program.  The program gave me erroneous results for the
system performance relative to an XT.  I got system performance numbers
ranging from 33 to 956 and some times it would not even calculate
the performance but would just tell me that the clock is inactive.
So, now I booted the system from a 5.25 floppy with DOS and the AMI 
diagnostics program on it.  When I ran the diagnostics I got the 
following errors:

	1. BIOS ROM test - failed
	2. Programmable Interval Timer test - failed
	   Timer is counting at faster rate.
	3. Real Time Clock test - failed
	   Real Time Clock is running at slower rate.

I thought that the battery had died but it is just fine and the clock has
not lost any time yet.  When I tried to run the video test with the AMI
diagnostics the program initiated the tests and ran fine until it got to
the colored graphics tests then the system hung.  Also when I tried to 
print out the error report it took about 20 minutes just to print out
about 5 lines.

The 3.5" drive is a TEAC-235HF with the following jumper settings:

	J2 is jumpered.
	G3-G4 jumpered.
	E3-E4 jumpered.
	B4-C4 jumpered.
	B1-C1 jumpered.

I would greatly appreciate ANY helpful comments or suggestions since I
need to get the computer running soon!

Thanks in advance,

Tom Bell
bell@nosc.mil

v087mxgb@ubvmsa.cc.buffalo.edu (Shawn E Thompson) (05/29/91)

In article <3095@cod.NOSC.MIL>, bell@cod.NOSC.MIL (Thomas T. Bell) writes...
> 
>Consequently, the dir command would always give the same directory
>listing of drive B: (where the 3.5" drive is located) even if a new
>disk was inserted into the drive.  So, I called Datel Computers and

There is a jumper on the back of the drive that gets shipped in the
XT position .....change it to the AT position......I had the same
problem TWICE........(after the first time I forgot...hehe...whoops)


This is why it gives the same dir over again.....XT controllers
have an on-board buffer, AT 's use a buffer in the drive itself
so if it thinks you have an XT it wont clear the buffer ......



(I might have the explanation backwards, but you get the basic
idea......)



regards 


ST