Original Message:
> I have several hundred rewritable optical disks in DOS format and 20-30 more
> coming every month. My users need to read these files on a DU 3000/400. Does
> anybody know of an utility for DU which can read these? I have the same type
> of optical drive on a DU 3.2C system as was used to write the files in the DOS
> world.
>
> Any help would be greatly appreciated!
>
> Thanks
> Stuart
> ssides_at_goblin.wr.usgs.gov
Sorry my summary took so long, but I wanted to test it first. The most popular
answer was to get a copy of mtool. I found this at gatekeeper.dec.com and
several other places. There were two versions 2.0.7 and 3.0. 3.0 had several
compilation errors, so I went back to 2.0.7. The first change was to modify the
devices.c file to include an entry for the alpha. This is the what I added.
#ifdef DUNIX
struct device devices[] = {
{'A', "/dev/rrz14c", 0L, 16, 0, (int (*) ()) 0, 0, 0, 0},
{'B', "/dev/rrz14g", 0L, 16, 0, (int (*) ()) 0, 0, 0, 0},
{'\0', (char *) NULL, 0L, 0, 0, (int (*) ()) 0, 0, 0, 0}
};
#endif /* DUNIX */
I added two devices because some of our opticals have data on both the a and g
partitions (why, I don't know). I also had to change the line in msdos.h to read
as follows:
#define MAX_CLUSTER 16384 /* largest cluster size */
This may need to be even higher for larger opticals. This works for a 1.2GB 512
byte/sector disk.
Next I commented out the following line in fat_read.c. There is probably a
better way, but this worked.
/*#define CHK_FAT*/
Then I did a make.
Last but not least the Makefile was using a form of the install command which I
think assumed mtool had been installed previously, so I copied the executables
over to the usr/local/bin area by hand.
After these small problems everything seems to work.
There was one other suggestion:
Look into a product call Transfer Pro from a company called Digital
Instrumentation Technology.
Thanks for all your answers.
Stuart
ssides_at_goblin.wr.usgs.gov
Received on Thu Jun 20 1996 - 20:46:20 NZST