Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!uwm.edu!bionet!agate!ucbvax!dog.ee.lbl.gov!nosc!humu!pilikia!art
From: art@pilikia.pegasus.com (Art Neilson)
Newsgroups: comp.sys.ncr
Subject: Pcdsk on SCSI flex
Keywords: pcdsk SCSI
Message-ID: <1991Mar19.005953.15726@pilikia.pegasus.com>
Date: 19 Mar 91 00:59:53 GMT
Sender: art@pilikia.pegasus.com (Art Neilson)
Organization: Bank of Hawaii Tech Support
Lines: 45

We have a problem writing to our SCSI 5.25 flex via pcdsk(1).  I realize
pcdsk is an unsupported utility, this means we are SOL if NCR doesn't
know of an answer offhand.  Pcdsk works just fine on MSC based flex drives,
however it does not work for SMSC and HPMSC (SCSI) based flex drives.  On
our Tower 32/650 in the /etc/RELDEF directory, the following text can be
found in the file 3.00.00.rd:

      The pcdsk(1) command does not  operate  on  the  SCSI
      floppy  disks.  This  is  due  to the pcnodes(1) command not
      creating the correct nodes. The following  are  the  correct
      nodes for the SCSI floppy disk:

      /dev/pcdsk/h1s8  major no. 12, minor no. 232
      /dev/pcdsk/h1s9  major no. 12, minor no. 236
      /dev/pcdsk/h2s8  major no. 12, minor no. 200
      /dev/pcdsk/h2s9  major no. 12, minor no. 204
      /dev/pcdsk/t80h1s8  major no. 12, minor no. 224
      /dev/pcdsk/t80h1s9  major no. 12, minor no. 228
      /dev/pcdsk/t80h2s8  major no. 12, minor no. 192
      /dev/pcdsk/t80h2s9  major no. 12, minor no. 196

      It only works on the MSC  floppy.  This  is  an  unsupported
      command.


Hmmmm. the nodes mentioned here yeild no joy when created with mknod(1),
pcdsk complains that it can't open /dev/pcdsk/h2s9.  I do know of some
nodes that work, they are as follows:

      /dev/pcdsk/h2s8  major no. 64, minor no. 200
      /dev/pcdsk/h2s9  major no. 64, minor no. 204

These seem to work, we can get a directory of the flex via pcdsk,
and can transfer files from MSDOS to UNIX via the pcdsk mtu command.
However, when we attempt writing to the flex via the pcdsk utm command
the flex drive light goes on and pcdsk appears to be copying the file
to the flex.  After the copy completes, the pcdsk dir command reveals the
file was never really copied to the disk.  Is this a problem with the
pcdsk utility itself, or does it lie at the driver level ?  If it is in
pcdsk, I can take a stab at porting the PD mtools package over to the 
Tower or something.  If the problem is elsewhere, I'm SOL.  Is anyone
else aware of this problem or a solution to it ??
-- 
Arthur W. Neilson III		| INET: art@pilikia.pegasus.com
Bank of Hawaii Tech Support	| UUCP: uunet!ucsd!nosc!pilikia!art