CompuServe Thread

Jerry, I used to work in a graphics lab and the technique is similar to one used in some tape back software I wrote. I would expect that it's a common thing to do in the cdrom business too. Depending upon how the application works you'll need shell level commands or a library to manage the mounting and unmounting of cdroms in response to user needs. Basically you organize the "files" on a normal file system as if they were real files but all they contain is a pointer to the appropriate disk/file combination which may or may not be on-line. You'll have to manage this interface because no common version of Unix provides any kind of "file migration" capability – which isn't really what you need anyway. Before the cdroms are written it would be a stellar idea to have some information as likelihood of access on a per file basis so you can write the cdroms to minimize disk changes. Are you custom develop for a client or something? I lost your original message. Chris