Re: Informix NT and SCSI Tape drive

Jon Freeland wrote: > On Tue, 1 Jul 1997, Walter S. Tyszka wrote: > > Jon, > > > > Is this an existing tape drive (one which the OS has been configured > > to use), or has this tape device just been added? > > An existing tape device that the OS has been configured to use. We're > running NT 4.0. When I check the properties for the device, it tells me > that the device name is "Tape0" and it shows up just fine. If I try to use > this label in the onconfig file, then do "ontape -s -L 0" it will say > "error opening device "Tape0" error no -1 and error -2" or something > similar. Our only other option is to set the tape device to > d:\\backup\\sysbackup, set an "at" job to delete this file if it exists, do > the ontape command, then use ntbackup to copy the "sysbackup" file to the > tape device. We'd just rather do it the normal way. :) > > Jon Freeland<*> > eclypse@cdc.net > Jon, In order to replicate your problem, I have added an Exabyte 8mm tape drive to a system running Windows NT 4.0. I configured the tape drive through the OS (Start -> Settings -> Control Panel -> Tape Devices) and allowed the the OS to autoselect and add the correct device driver for this tape drive. I then selected (Start -> Programs -> Informix Administration Tools -> ISM Setup) and selected \\\\.\\TAPE0 from the "Backup To:" pull down menu. After selecting OK, I took a look at my onconfig file and noticed that the Informix ISM Setup had replaced: TAPEDEV NUL with TAPEDEV \\\\.\\TAPE0 I then ran ontape via: Start -> Programs -> Informix Administration Tools -> Command Line Utilities "ontape -s -L 0" without any errors. Rather than editing the onconfig file, you might try the Informix "ISM Setup" utility to see if it is able to recognize the tape drive. Every time I have configured Informix OnLine on Windows NT to use a local tape drive, it has always used \\\\.\\TAPE0 rather than Tape0 to identify the tape device. Note: I am running Windows NTS 4.0 (build 1381 service pack 1) with Informix ODS 7.22.TC1. -- Regards, Walter S. Tyszka (wstyszka@ingr.com) * Standard disclaimers apply *