davewt@NCoast.ORG (David Wright) (10/09/90)
I have been having a problem attaching an external hard drive to my 3000. The drive is mounted in it's own case, with it's own power supply, and is fully up to speed when I turn the 3000 on. No matter what I do I can't get the drive recognized by AmigaDOS. The HDToolBox will detect the drive, and even let me low-level format and partition the drive, but it won't show up to AmigaDOS at all. The drive does NOT support the "verify" option of HDToolBox. Do you need to be able to use the "verify" option to have HDToolBox write some critical data to the drive? Would creating a mountlist entry work to let me format the drive? Is it also possible that it isn't showing up for the same reason that the 1.3 partition doesn't show up when the 2.0 is in use? Dave
jesup@cbmvax.commodore.com (Randell Jesup) (10/10/90)
In article <1990Oct9.022719.29879@NCoast.ORG> davewt@NCoast.ORG (David Wright) writes: > > I have been having a problem attaching an external hard drive to my >3000. The drive is mounted in it's own case, with it's own power supply, and >is fully up to speed when I turn the 3000 on. What type? this sort of message is useless without that sort of info. Kind of like "my printer doesn't work, what's wrong with it?" > No matter what I do I can't get the drive recognized by AmigaDOS. >The HDToolBox will detect the drive, and even let me low-level format and >partition the drive, but it won't show up to AmigaDOS at all. > > The drive does NOT support the "verify" option of HDToolBox. Do you >need to be able to use the "verify" option to have HDToolBox write some >critical data to the drive? Would creating a mountlist entry work to let >me format the drive? Does Save Changes work? If you reboot, does hdtoolbox find the information when you run it? A drive not supporting Verify is very close to being non-SCSI-I compatible, and is certainly not CAM (Common Access Method, the minimum standard for disk devices) compatible. Still, that alone shouldn't stop it from working, but that may be the tip of the iceberg. A mountlist may work, no guarantees. > Is it also possible that it isn't showing up for the same reason that >the 1.3 partition doesn't show up when the 2.0 is in use? No, not unless you named it WB_2.x: or WB_1.3:. -- Randell Jesup, Keeper of AmigaDos, Commodore Engineering. {uunet|rutgers}!cbmvax!jesup, jesup@cbmvax.cbm.commodore.com BIX: rjesup Common phrase heard at Amiga Devcon '89: "It's in there!"
gwalborn@unix.cis.pitt.edu (Gary D Walborn) (10/11/90)
Help!!!!
I am having a serious problem with booting my Amiga 3000. I have a stock
Amiga 3000/25-50 with 3 external SCSI drives as follows:
ID# Device
1 Maxtor 2190 230Meg Drive with Adaptec 4070 controller
2 3M 40 Meg SCSI tape
3 Data Technology Take 10 , 10 Meg Removable
The internal 50 Meg drive was factory configured to be ID #6.
The problem:
When I attempt to boot with all drives running, the system searches
the drives and displays 'LOADING KICKSTART 2.0'. At this point, the MAXTOR
light comes on and stays on for about 3 seconds. Then the system goes into
an endless loop of starting to boot, led flashing, and rebooting. If I boot
without the external drives connected, the system boots normally. I can then
plug the external drives back in (with the CPU 'on') and perform a
CNTL-AMIGA-AMIGA. The system reboots OK and mounts the external drives
just fine.
Not only is this procedure painfully slow, but I believe it is not wise
to plug and unplug drives with the power on. Can someone please tell me
how to keep my Maxtor drive from interfering with the boot process?
Gary Walborn (gwalborn@unix.cis.pitt.edu)
Phone: (216) 758-8323 or (216) 726-8450
US Mail: 7551 Sugartree Drive
Youngstown, OH 44512martin@IRO.UMontreal.CA (Daniel Martin) (10/11/90)
In article <47261@unix.cis.pitt.edu> gwalborn@unix.cis.pitt.edu (Gary D Walborn) writes: (description of problem) >..light comes on and stays on for about 3 seconds. Then the system goes into >an endless loop of starting to boot, led flashing, and rebooting. If I boot >without the external drives connected, the system boots normally. I can then >plug the external drives back in (with the CPU 'on') and perform a >CNTL-AMIGA-AMIGA. The system reboots OK and mounts the external drives >just fine. This is also what I get by connecting a SCSI CD-ROM drive (Apple CD-SC). If the drive is on before powering the A3000, the HD goes into an infinite load loop (light access stays on). If you boot, then power up the CD-ROM, everythings fine. Q&A: Terminator: Only the last device on the daisy chain should be terminated. Is it also the case for the first one? Internal vs External SCSI: The standard internal drive is connected to the internal scsi. If you daisy chain one internal HD, and one external HD, who's get the terminator? Are the internal and external connector two different chain? Driver: For CD-ROM supporting ISO 9660 (High Sierra) and CD-DA.. Where can I get source/bin ? -- // Daniel Martin Universite de Montreal \\ // MediaLab, ca vous regarde! C.P. 6128, Succursale A, \\ \\// Mail: martin@IRO.UMontreal.CA Montreal (Quebec), CANADA, \\// \/ Tel.: (514) 343-6111 poste 3494 H3C 3J7 \/