rbabel@babylon.rmt.sub.org (Ralph Babel) (05/31/91)
In article <drbit.0120@phobos.UUCP>, drbit@phobos.UUCP (Jorgen Kjaersgaard) writes: > I have even tried to write an assembly program which > attempts to open the device. DOS loads the device all > right but the device returns -1 on an OpenDevice call. -1 is returned by the exec.library (*NOT* the driver) if it cannot find the device. There is no DOS-loadable version of the gvpat.device, only a ROM and a BindDrivers version. > Gvpat.device is version 2.3. BindDrivers driver 2.3 doesn't support the '030 rev 7. Looks like you received an old installation disk. > So, what does the device check in order to determine > whether to open or not? jumpers? something in the drive > itself? It's not the device driver. -1 is Exec. > boot EPROM (I don't have a boot EPROM yet). You already said so in <drbit.0042@phobos.UUCP>; I replied in <08029.AA08029@babylon.rmt.sub.org>. You still haven't told us why you don't have a boot ROM. They're standard on all rev 7 (and later) boards. > Does my version of gvpat.device _require_ a boot EPROM? You're confused. The boot ROM _is_ gvpat.device. Ralph