Zip drive on Proliant 3000?
 

I have a Proliant 3000 450MHz. I have an old 100 MB SCSI internal Zip
drive that I have installed in the bay on the top right. The Proliant
had been used with an HP DDS drive, so I just moved the cable. The Zip
drive is connected to internal SCSI controller 1 (controller 2 is used
by the hard disks).
It will not boot when the drive is connected. Smart Start v5.5 does
not see the Zip drive. It doesn't show up in the POST, either. I have
played with the SCSI settings in Smart Start (SCSI-1, SCSI-2,
Auto-detect and Asynchronous).
Have I missed something obvious?

Zip drive on Proliant 3000?
 

M J Dowden wrote:
I have a Proliant 3000 450MHz. I have an old 100 MB SCSI internal Zip
drive that I have installed in the bay on the top right. The Proliant
had been used with an HP DDS drive, so I just moved the cable. The Zip
drive is connected to internal SCSI controller 1 (controller 2 is used
by the hard disks).
It will not boot when the drive is connected. Smart Start v5.5 does
not see the Zip drive. It doesn't show up in the POST, either. I have
played with the SCSI settings in Smart Start (SCSI-1, SCSI-2,
Auto-detect and Asynchronous).
Have I missed something obvious?

Have you made sure that the SCSI port is terminated? The DDS drives are
(for the most part) self terminating...but your Zip drive is not. You
need a SCSI cable with an active terminator on the end.

Jeff

Zip drive on Proliant 3000?
 

Jeffrey Alsip wrote:

Have you made sure that the SCSI port is terminated? The DDS drives are
(for the most part) self terminating...but your Zip drive is not. You
need a SCSI cable with an active terminator on the end.


The Zip drive has a jumper for termination. I have tried it with the
jumper on and with the jumper off. No luck either way.

Zip drive on Proliant 3000?
 

M J Dowden wrote:
Jeffrey Alsip wrote:

Have you made sure that the SCSI port is terminated? The DDS drives are
(for the most part) self terminating...but your Zip drive is not. You
need a SCSI cable with an active terminator on the end.


The Zip drive has a jumper for termination. I have tried it with the
jumper on and with the jumper off. No luck either way.

Try a terminated cable. It's possible that one is still tucked inside
of your 3000. Pull out the drive tray and look against the inside back
wall...the machine comes with one tucked away for future use.

I have never specifically tried to put a Zip drive in my 3000's, but I
have installed several SCSI CD Drives (using the terminated cable)
without any problems.

Jeff

Zip drive on Proliant 3000?
 

Possible the addition on that scsi port allowed itself to modify the
controller boot order.
Press f-10 on boot and make sure boot order is correct.
A thought ....
Phil


"Jeffrey Alsip" wrote in message
s.com...

M J Dowden wrote:
Jeffrey Alsip wrote:

Have you made sure that the SCSI port is terminated? The DDS drives
are
(for the most part) self terminating...but your Zip drive is not. You
need a SCSI cable with an active terminator on the end.


The Zip drive has a jumper for termination. I have tried it with the
jumper on and with the jumper off. No luck either way.

Try a terminated cable. It's possible that one is still tucked inside
of your 3000. Pull out the drive tray and look against the inside back
wall...the machine comes with one tucked away for future use.

I have never specifically tried to put a Zip drive in my 3000's, but I
have installed several SCSI CD Drives (using the terminated cable)
without any problems.

Jeff

Zip drive on Proliant 3000?
 

"Phil" wrote in message
...
Possible the addition on that scsi port allowed itself to modify the
controller boot order.
Press f-10 on boot and make sure boot order is correct.
A thought ....
Phil


I would think if that was the case, that the device would still be
enumerated on the SCSI bus. Perhaps the onboard controller was disabled in
the SCU ?

- LC

Zip drive on Proliant 3000?
 

Lc,
Possible, but the Compaq bios won't know what that zip device is !
Sounded like he was grasping at straws. Terminator, or lack of, I doubt
would cause that, though it could cause unreliable data.

I have seen the addition of/or something introduced to the unused scsi chain
change boot order.
Nothing carved in stone, again, just a thought as to something to check.

Phil

"NuTCrAcKeR" wrote in message
t...

"Phil" wrote in message
...
Possible the addition on that scsi port allowed itself to modify the
controller boot order.
Press f-10 on boot and make sure boot order is correct.
A thought ....
Phil


I would think if that was the case, that the device would still be
enumerated on the SCSI bus. Perhaps the onboard controller was disabled in
the SCU ?

- LC

Zip drive on Proliant 3000?
 

LC,
Also when people ask these questions sometimes they are not totally accurate
in the presentation of the question or related facts.
It's not like we can see with our own eyeballs, so to speak. Often a minor
mistake in their statement or an assumption on their part would yield an
altogether different answer. Who knows, he could have failed to plug in the
power to the device. That was the basis for what I said.

Phil

"Phil" wrote in message
...
Lc,
Possible, but the Compaq bios won't know what that zip device is !
Sounded like he was grasping at straws. Terminator, or lack of, I doubt
would cause that, though it could cause unreliable data.

I have seen the addition of/or something introduced to the unused scsi
chain
change boot order.
Nothing carved in stone, again, just a thought as to something to check.

Phil

"NuTCrAcKeR" wrote in message
t...

"Phil" wrote in message
...
Possible the addition on that scsi port allowed itself to modify the
controller boot order.
Press f-10 on boot and make sure boot order is correct.
A thought ....
Phil


I would think if that was the case, that the device would still be
enumerated on the SCSI bus. Perhaps the onboard controller was disabled
in
the SCU ?

- LC

Zip drive on Proliant 3000?
 

In article ,
"Phil" wrote:

Also when people ask these questions sometimes they are not totally accurate
in the presentation of the question or related facts.
It's not like we can see with our own eyeballs, so to speak. Often a minor
mistake in their statement or an assumption on their part would yield an
altogether different answer. Who knows, he could have failed to plug in the
power to the device. That was the basis for what I said.


Thanks for the suggestions, but I feel pretty comfortable with the
accuracy of the description of the problem. The unit is definitely
powered, as the light blinks at power-on. I simply moved the SCSI cable
from the HP tape drive to the Iomega Zip drive. The tape drive wasn't
terminated, but worked fine, and now the Zip drive isn't either (I tried
both jumper settings). I'm inclined to agree that the Compaq BIOS
doesn't know what a Zip is and that that is probably the entire problem.
The oddest part is that Smart Start doesn't list it as an attached SCSI
device.

Thanks again.

Zip drive on Proliant 3000?
 

M J Dowden wrote:
Thanks for the suggestions, but I feel pretty comfortable with the
accuracy of the description of the problem. The unit is definitely
powered, as the light blinks at power-on. I simply moved the SCSI cable
from the HP tape drive to the Iomega Zip drive. The tape drive wasn't
terminated, but worked fine, and now the Zip drive isn't either (I tried
both jumper settings). I'm inclined to agree that the Compaq BIOS
doesn't know what a Zip is and that that is probably the entire problem.
The oddest part is that Smart Start doesn't list it as an attached SCSI
device.

Thanks again.

I am, also, starting to think that the Compaq bios just doesn't
understand what a Zip drive is. I wish that I had one...I would try it
in one of my machines. I have had some "weird" things happen with IDE
Zip drives. For instance, if one is installed on the IDE bus (as a
slave for instance) it will not show up in My Computer UNLESS a disk is
inserted prior to power up. However, if the Zip Tools disk is inserted
at power-up and then run (after the boot), the drive wil, in the
future, appear whetehr a disk is inserted or not! I consider that kind
of "weird" as I can't imagine Zip Tools affecting the bios...it must
simply add a driver that was otherwise missing.

On your particular problem, I can only think of one other thing that we
havn't checked. That would be SCSI ID. Assuming that you CAN change the
ID number (probably one or two jumpers), and assuming that the Zip
drive is the ONLY device on this bus, the ID should be set to "0".
Correct me if I am wrong, LC, but I believe that the controller will
grab ID "7" for itself. If the Zip is accidentally set as ID "7" then a
conflict will occur that could very easily result in the drive not
appearing.

That's my final idea. If it doesn't help, I think we may have to
soberly admit that we have found ANOTHER shortcoming in COmpaq Bios.

Jeff