Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!bloom-beacon!oberon!uscacsc!carl
From: carl@uscacsc.usc.edu (Carl Braganza)
Newsgroups: comp.sys.ibm.pc.rt
Subject: Re: 3363 Optical Disk on 6152 Academic System
Summary: Man page for 3363 under 6152
Keywords: 3363 Optical Disk Drive, 6152 Academic System, HELP !
Message-ID: <610@uscacsc.usc.edu>
Date: 22 Mar 89 20:36:24 GMT
References: <7553@batcomputer.tn.cornell.edu> <601@uscacsc.usc.edu>
Reply-To: carl@uscacsc.UUCP (Carl Braganza)
Organization: USC ACSC, Los Angeles
Lines: 123

Enclosed is a man page I received from Palo Alto for the 3363 under AOS
4.3. Note, the device is still unsupported!

.\" $Header: op.4_ca,v 1.2 88/07/13 15:41:38 achan Exp $ 
.\" $Source: /ibm/acis/usr/man/man4/RCS/op.4_ca,v $ 
.\"
.\" P_R_P_Q_# (C) COPYRIGHT IBM CORPORATION 1986,1987,1988
.\" LICENSED MATERIALS - PROPERTY OF IBM
.\" REFER TO COPYRIGHT INSTRUCTIONS FORM NUMBER G120-2083
.\"
.\"$Header: op.4_ca,v 1.2 88/07/13 15:41:38 achan Exp $
.\"$Source: /ibm/acis/usr/man/man4/RCS/op.4_ca,v $
.\" This file uses -man macros.
.TH OP 4 "Sept 1988" "Space overwritten by .AC macro" " "
.AC 1 0
.SH NAME
op \- optical disk interface
.SH SYNOPSIS
.PP
For the IBM 6152 Academic System:
.br
.B "controller opc0 at iocc0 csr 0xffffffff priority 2"
.br
.B "device op0 at opc0 drive 0"
.br
.B "device op1 at opc0 drive 1"
.br
.B ...
.SH DESCRIPTION
.PP
On the IBM 6152 Academic System, the
.I op
device provides access to an System/2 IBM 3363 optical disk drive.
The disk drive uses removable 200 megabyte cartridges with
write-once (WORM) media.
.PP
Access to the cartridge is thru DOS, which provides an mechanism that
makes the write-once media appear to be normal read-write media.
.PP
Each \fIUnix\fP device uses a file on the DOS device (e.g. \fBUNIXFILE.\fP\fIddd\fP
where \fIddd\fP is the minor device number). The first time a optical disk file
is opened for writing the corresponding DOS file is created.
.PP
Raw I/O requests must start on a sector boundary, involve an integral
number of complete sectors, and not go off the end of the disk.
.SH NOTES
In most cases it is best to not treat an optical disk device as a normal read-write
device. In particular, it is not recommended that one use \fInewfs\fP(1) and then 
mount and copy files onto an optical disk as this will involve rewriting the same
sectors a number of times, and result in needless wasting of space.
In general, when putting a large filesystem on optical disk that will then
be mounted later, it is better to create the filesystem on a hard disk (locally
or remotely) and then use \fIdd\fP(1) to copy the resulting filesystem onto
the optical disk. The filesystem can then be mounted read-only and accessed
normally.
.PP
One can also use other utilities that such as \fIdump\fP(8), and \fItar\fP(1),
which are better suited to a write-once media for backup to optical disk.
.PP
One must use the appropriate DOS 3363 utilities to initialize an optical
disk cartridge for the first time before it can be used from \fIUnixfP.
.PP
The various 3363 driver and utility files should be installed as described
in the 3363 documentation. If the system is configured to automatically boot
\fIunix\fP out of \fBautoexec.bat\fP, there is a problem in that both \fIunix\fP
and \fIibm3363\fP need to be the last command executed out of \fBautoexec.bat\fP.
One solution for this is to put the \fIunix\fP command into a .bat file of its
own, and then put the appropriate \fIibm3363\fP command as the last entry in
autoexec.bat, such as ``ibm3363 xx=1000 cmd=rununix''
where \fBrununix.bat\fP contains the command that would have normally appeared
last in autoexec.bat to start \fIunix\fP.
.SH ERRORS
The following errors may be returned by the driver:
.TP 12
[ENXIO]
Nonexistent drive (on open); 
offset is too large or not on a sector boundary or
byte count is not a multiple of the sector size (on read or write);
bad (undefined) ioctl code.
Drive not ready; usually because no disk is in the drive or
the drive door is open.
.TP
[EIO]
A physical error other than ``not ready'', probably bad media or 
unknown format.
.SH FILES
/dev/op[01]
.br
/dev/rop[01]
.SH SEE ALSO
tar(1), dd(1)
mkfs(8), newfs(8)   
.SH DIAGNOSTICS
.BR "op%d: hard error" ,
.BR "BIOS error=0x%b" ,
.BR trk=%d ,
.BR Sec=%d ,
.BR Head=%d ,
.BR state=%s .
An unrecoverable error was encountered.  The System/2
BIOS error code, track, sector, head and state are displayed.
.PP
.BR "op%d: state %d (reset)" .
The driver entered an invalid state.
.PP
.BR "op%d: timeout" .
Lost interrupt.
.PP
.BR "op%d: write protected" .
The driver detected a drive containing a write-protected disk.  (On open
only.)
.PP
.BR "op%d: door open or hardware fault" .
Autodensity failed due to an unrecoverable error. (On open only.)
.PP
.BR "op%d: pc timeout" .
The device driver timed out waiting for the PC to accept a command.
.SH BUGS
.PP
In order to access large files (e.g. more than 32mb), the option
.BR XX=1000
should be specified on the \fIibm3363\fP command. Otherwise it is likely that
a large file will not be usable, and result in considerable waste space.