CompuServe Thread

I recently bought a new 386 BB. When I first installed it in my A3000 I couldn't get the BB to recognize either of my internal floppies. It turned out my floppy controller was bad. I replaced the BB with a new one and it seemed to work ok. Since my small 52 meg hard drive is full, I decided to boot the BB from my df0: shared floppy (at least until I get a bigger or another hard drive). Since I was lucky enough to find an A3000 with a high density floppy drive, I decided to boot from a high density workbench disk. While the BB booted ok (and read high density MS-DOS disks ok) from an 880k workbench disk, when trying to boot from a high density workbench disk a requestor would pop up and ask for the workbench disk (which was, of course, in the drive) or report read errors on the disk. This made the floppy do a LOT of thrashing. Next thing I know, the drive began reporting read errors on ALL of my disks, standard or high density. The BB seems to have damaged my high density floppy drive! Is that possible? I seem to remember reading here that this happened to someone else. When I asked my dealer if he could get a replacement high density drive he said no. I then called Gold Service and since 3000's don't officially ship with high density drives, they refuse to recognize I had a high density drive and would only replace it with an 880k drive. T make a long story short, after a few calls to West Chester and a couple of weeks, I was able to get a replacement. I still can't boot from my new high density drive. I've been able to determine the problems begin when my startup-sequence reaches the "binddrivers" line. Could this be a bug in the binddrivers command or the janus.library? Or do I have another bad BB? Is anyone out there booting the 386 BB successfully from a high density floppy? Any help greatly appreciated. Steve