The vmunix.tape kernel is for testing to see if your tape drive
 --which is not supported-- is compatable with one of the supported types.

Why would you do this? If you don't have the manual on the tape drive it might
be worth it to do this instead of recompiling the kernel each time.
THIS is only temporary until we can patch the kernel to automagically
recognize your particular tape drive type! 

This kernel is based on the vmunix #720 kernel with two view patches
from chris hopps, a reboot patch, and some patches from mike hitch
so that all supported controller cards and tape drives would use
sd and st, rz and rt are no longer supported.

This kernel is built with INET and has been tested with X11R5 for the ECS
chip set. However this kernel is only for boot strapping your tape
drives.
------------------------------------------------------------------------
A patchable char variable called st_pretend_tobe_mt is used into
fooling you kernel into thinking you have one of the following
supported tape drives.


#define MT_ISEXABYTE    0x0c            /* Exabyte */
#define MT_ISVIPER1     0x0e            /* Archive Viper-150 */
#define MT_ISPYTHON     0x0f            /* Archive Python (DAT) */
#define MT_ISHPDAT      0x10            /* HP 35450A DAT drive */
#define MT_ISWANGTEK    0x11            /* WANGTEK 5150ES */
#define MT_ISCALIPER    0x12            /* Caliper CP150 */
#define MT_ISWTEK5099   0x13            /* WANGTEK 5099ES */
#define MT_ISVIPER2525  0x14            /* Archive Viper 2525 */


To pretend your tape drive is a MT_ISCALIPER do:

binpatch -b -s _st_pretend_tobe_mt -r 0x12 vmunix.tape

The default value for the _st_pretend_tobe_mt is 0, and the
tape driver will behave normally.

Once you are running NetBSD in single user mode,
copy the raw vender string printed by the kernel
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Raw vendor string ->This is the string<-
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
on a sheet of paper. Try using your tape drive, 
by doing a tape operation such as creating a archive
               tar -cvf /dev/rst0 /etc
If this works and ....
               tar -tvf /dev/rst0
works, your pretty much in business.

An error message of 'Bad file descriptor' tells you to try another patch
value.

If this patch value doesn't work reboot.
Patch the kernel to a new drive type and try again. 

Unfortunately this kernel won't reboot for me via /dev/reload so you'll
have to binpatch the vmunix.tape kernel under amiga dos.

IF THE PATCH WORKED

Since my E-mail address will be changing shortly and I may even loose my
internet access for a while, and I'll be moving... all in march
the best way to contact me is by posting a message to the mailing list
with the Subject: st_pretend is MT_.... for "Raw Vendor string"

So say you discovered that your Rander tape drive behaved like a MT_VIPER1
send the message to the Netbsd-amiga or comp.unix.amiga mailing list

To:Netbsd-amiga@....
Subject: st_pretend is MT_VIPER1 for "Rander Snake 5320-46"

With this information patches can easily be made to automagically
recognize your tape drive.

This is the best I can do.

-Rob