jim@jagubox.gsfc.nasa.gov (Jim Jagielski) (12/12/90)
I am one of the lucky ones that actually HAS a MicroNet tape drive (MT-155).
Anyway, I think that there are two versions of Tony's driver available: one
specifically for teac drives (driver "teac") and one for streaming tape
drives (driver "st"). I have/had st. Whenever one tries to access the tape
device file, you get the "this driver has expired" message and get booted.
The expire date is hardwired into the code (as far as I can tell) so trying
to re-finstall it don't work. The driver I have is Version 1.00 beta.
The other driver, "teac" also supposedly has an expire date, but if you re-
install the driver, then it'll unexpire itself. I also have a copy of this
driver, Version 1.01 beta TEST.
teac comes with a replacement for /bin/mt. It's compatible with the Apple 40SC
and teac drives. st comes with a new tape-handler, /bin/tape, that's just for
the st driver.
Does anyone know if the teac-specific portion of st is the same (or older
or newer) than the teac driver itself? Without a doubt, the distribution of
st is more "finished".
--
=======================================================================
#include <std/disclaimer.h>
=:^)
Jim Jagielski NASA/GSFC, Code 711.1
jim@jagubox.gsfc.nasa.gov Greenbelt, MD 20771
"Kilimanjaro is a pretty tricky climb. Most of it's up, until you reach
the very, very top, and then it tends to slope away rather sharply."rmtodd@servalan.uucp (Richard Todd) (12/13/90)
jim@jagubox.gsfc.nasa.gov (Jim Jagielski) writes: >The other driver, "teac" also supposedly has an expire date, but if you re- >install the driver, then it'll unexpire itself. I also have a copy of this >driver, Version 1.01 beta TEST. That's the one I have. I'm not sure it actually has an expire date in it. The reason I say this, is that 1. strings on /etc/boot.d/teac shows no sign of any such message (but, of course the msg could be encrypted) and 2. doing an nm on the same file shows that the teac driver nowhere references as external variables the kernel's time variable, or indeed seem to reference anything it shouldn't be looking at in the kernel. Has anyone actually seen this version (1.01) expire? -- Richard Todd rmtodd@uokmax.ecn.uoknor.edu rmtodd@chinet.chi.il.us rmtodd@servalan.uucp Motorola Skates On Intel's Head!