Re: Adding HD to 1000A

On Sun, 15 Jul 2007 06:55:48 -0600, Mark Whitlock wrote:

Try the low level format utility, then if you get the bios screen,
you will
know that the interface (cables,IDE pins, & ROMS) are all working. If
this
works (probably 1/2 hour, to 2 hours) then try the regular format &
install.
The low level also sets up a parameter block (I think on the last
track) to
hold the info you input in case it has to virtualize. If the low level
does not
work then we know there is a communication error. The hang could be
caused by the controller getting bad information from the block or
even
by it attempting to boot using a non tandy OS. The fact it tries is a
good
sign.
Please let us know how it is going.,


All good suggestions, gentlemen, but I'm not getting so far as to even attempt a low-level format, in general. As I mentioned in my original post, I'm trying to boot from my floppy, and it is during the initial boot sequence that the machine will generally hang. If I do get lucky and get a boot prompt (after booting from my floppy), on the very first access to the drive, the system will hang with the HD selected.

And, yes, everyone who mentioned the low-level formatting particulars are correct. The DEBUG command 'G=C800:0005' is correct. It kicks off the WD BIOS formatting process. As mentioned in my first post, though, I have confirmed that this drive/controller combination work just fine in a Leading Edge Model D. The drive is formatted, and DOS 3.3 is installed, ready to go. It will boot my LE Model D without any difficulties at all. So I know the drive and controller are working (at IRQ 5, at least) and that the HD is bootable.

Now, back to the Tandy 1000A...

I'm starting to believe that it is *indeed* a DMA problem. Turns out that during one particular sequence when I *was* able to successfully boot from the floppy, I did successfully get to the HD BIOS with DEBUG, exectued the C800:5 format routines and all went fine. No DMA events are used for that, and the PC is just waiting for a functional return from the WD BIOS. Once I complete the format, and return to DOS, on my next attempt to *read* anything from the drive (i.e., FDISK, DIR, etc.) then the system will hang with the HD LED lit up. I'm starting to think that the Tandy BIOS is not really fixed. The most recent comment from Willard suggests that there actually were HD controller BIOSes specific for the T1000(A?). Perhaps that's at the root of this.

Anyone have such a WD controller BIOS that they could dump? I'd like to burn it to a ROM and give it a try...

Many thanks,

Jared
.

Relevant Pages

  • RE: Can FreeBSD safely use a (un-booted from) drive that is invisible to the BIOS?
    ... ata controler but have HD on wrong ribbon nipple to match master ... ad0 is the boot drive. ... It is recognized by the BIOS, obviously, ... ad2 is the only device on the second controller and it is definitely ...
    (freebsd-questions)
  • Re: Install Problem at GUI Startup
    ... confirmed earlier in this thread that you had the latest bios and drivers. ... In essence, DO boot on the cd, and wait for the Setup is Starting Windows, ... I am using the non promise controller exactly as you suggest. ... Enter to install ...
    (microsoft.public.windows.server.sbs)
  • Re: Why this configuration not working?
    ... C:boot.ini implies you have "C" HDas first boot device on computer BIOS. ... > Disk 3 is my CF Card Reader, ... >>Your DVD/CD has to be on MB Secondary controller. ...
    (microsoft.public.windowsxp.perform_maintain)
  • Re: "NTLDR is Missing" after adding Promise ATA66
    ... > HDD limit on the BIOS I think). ... Does the BIOS have a boot order selection in it somewhere? ... You can't just move a drive with 2000 on it to another port or controller. ...
    (microsoft.public.win2000.setup)
  • Re: BIOS - Format
    ... This old puter only has a CD drive and no floppy. ... Compaq then boot from the CD and format. ... even work I can't get into the Compaq's BIOS. ...
    (alt.os.windows-xp)
Loading