🚀 go-pugleaf

Shucks,  I thought I posted this query on friday but now I cannot find my
orginal query or any follow-ups.

Previously I had a 80MB RLL Micropolis as the boot drive coexisting with a
330MB Maxtor SCSI.  Everything was fine except I was out of disk space.

In early december I installed a 660MB HP SCSI to replace the 80MB RLL.  While I
could boot from the new SCSI, I could not make a number of products run when
restored from tape back-up.  I could not make them run when reinstalled. 

I have concluded that since these products would install successfully on a
ramdrive that the problem was not with the distribution floppies and must be
with the hew HP SCSI.

I finally ran the pattern tester in PCTOOLS.  I then lowlevel formatted the
disk, installed windows, (worked the first time), installed borland C++, and
performed the restore from tape of everything else.

It now appears to work fine.  I am also convinced that I was exeriencing a
hardware or media problem with the HP drive.  I speculate I had some bad blocks
that were, for some reason, not in the factory revector table and were not, for
some reason, immediately revectored when I repeatedly tried to restore or
reinstall borland C++ v3.1, Powerpoint and windows 3.1.
                                                                       
A local retailer and friend of mine said it sounded like a mother-board
compatibility problem, but I don't see how this could be since the disk is
connected to the mother board via a controller (IN-2000) that had been working
just fine with another SCSI drive for over a year.

This behavour is nevertheless strange and I am wondering if these kind of
problems could come back to haunt me in the future.  Anybody have any ideas?

Should I send the drive back ?  It is still under warenty.

			Thanks,
					Sieg