#a4008 oddities.
5 messages in this thread
Is this a bug or a feature?
When I have my Syquest and my Texel DM-5024 (Rom Ver 1.10) hooked to my
brand new A4008 Controller, they _will_not_ finish their "run up" and go
ready until the A4000(or the A4008) initializes. On the Syquest, the heads
_WILL_NOT_LOAD until a few seconds _after_ the A4000 is powered on.
While this is not a bad thing for the syquest, the Texel doesn't seem to
like this too much. In order to get my CD-ROM to be visible, I must
warmstart the machine as soon as workbench pops up.
If I don't do this, I don't see the CD-ROM. (and, yes, there _is_ a disk
in it).
Any ideas?
Brian
Brian — Cruising on AutoPilot…..
Brian;
I don't have an A4000 🙁 but maybe doing a diskchange might work. If so,
then you could probably make it conditional upon the device being present
(ie: assign devices).
-bill
Actually, a diskchange will probably not work. On the other hand, we provide a
program called GVPSCSICTRL which is used to rescan the bus for `latecomers'
such as the syquest. The argument for re-scan is GVPSCSICTRL -R. You may copy
the command to your favorite flavor of directory.
GW
Guys,
How about telling me what error #33 is.
To recap:
Before A4000 power-on: no SCSI devices on ths bus will come on-line.
Is the 4008 designed to hold the SCSI reset line down
when it's not powered up?
On coldboot: I can't see my CD-ROM, until I warmboot. I get "Error 33"
messages here.
On Warmboot: Everything's fine.
Thanks in advance.
One more thing, why did you shut down phone support for the holidays? It
_does_ make it difficult for people who get GVP Products for Xmas
presents….
Brian
Brian — Cruising on AutoPilot…..
I don't remember the message that your last refers to but if I was saying
that diskchange can be used to mount a cartridge with a different
structure than a currently mounted one then you are quite right, it won't
work… well, it does work but the results are less than satisfactory.
-bill