> The critical reason that everything works seems to be a
> rather fortunate use of the mutually exclusive areas by the
> RT-11 file structure and the standard ISO file structure.
I'm pretty certain that at least one VMS engineer participated
in the standards process for ISO9660. I've also heard that, as
a result, this ability to have ISO9660 and A.N.Other file
structure not tread on each other is NOT an accident! Of
course, said engineer was almost certainly thinking of ODS
rather than the RT-11 file structure (does that have a name?).
If you look at
http://support.tditx.com/~odsiso/index.html
you'll find a toolset that allows you to do something
similar with ODS-2 and ISO9660 i.e. have 600MB+ of data
accessible in native for both via an ISO9660 directory
structure and via an ODS-2 structure. It works (IIRC) by
building the ISO9660 image using mkfsiso and then analysing
mkfsiso's log file to find where the files are and creating
the mapping info that ODS-2 needs (or it may be the other
way around - it's been a while since I used it).
So you *may* be able to automate (or semi-automate) your
existing process.
It does look like ODS-2 and RT-11 FS cannot co-exist, however,
since they both want to use the 64 blocks at the start of
the image, unless it's possible that the unnecessary fields in
each of those two formats can be persuaded to step out
of each others way. Do you have any details about exactly
what RT-11 requires in that area? Maybe a disk that boots
on PDP-11, VAX (VMS), Alpha (VMS) and PC is possible
after all :-)
Antonio
--
---------------
Antonio Carlini arcarlini_at_iee.org
Received on Tue Mar 04 2003 - 16:57:00 GMT