5 Feb
2003
5 Feb
'03
7:15 a.m.
You wrote...
Everything, in our specific situation. I mean, since you said 2000Access
is
the only one we have machine readable source code for, then, to tweak the
O/S (rewrite the disk I/O handlers) to support other hard drives that are
easier to find and more reliable, like the really small HP-IB units, we have
to have source, and the only source you mentioned we had was Access, which
requires the IOP firmware.
Jay West
It gives separate part numbers for IOP firmware for
the 2100, M-series,
and E-series. For the M-series, it only gave the number of the complete
firmware accessory board assembly, but for the 2100 and E-series, it
gave the part numbers of the actual PROMs.
I'm sure that's because on the M
series, you didn't ever get "proms" for
IOP. You got a board with the proms soldered in permanently. On the 2100 and
E, you don't get a board, you get chips that plug into the existing firmware
sockets already in the machine (FAB/FEM).
Which brings
us back to needing the IOP firmware, in order to tweak the
code to support other more common drives. *sigh*
I'm not sure I understand. What does IOP firmware have to do with
drives?