Code: Select all
subst R: /D
subst R: d:\r
subst P: /D
subst P: d:\r
subst H: /D
subst H: d:\h
subst Z: /D
subst Z: d:\zx
subst X: /D
subst X: z:\x
Code: Select all
Media removed : R:\
Media added: R:\ - 1234-5678- Data_Bck
Media added: P:\ - 1234-5678- Data_Bck
Media added: H:\ - 1234-5678- Data_Bck
Media added: Z:\ - 1234-5678- Data_Bck
Media added: X:\ - 1234-5678- Data_Bck
Evidently, RomCenter plays tricks with volume labels, but they are shared between the SUBST'ed volumes and the underlying actual volume.
Is it done on purpose, for people with big ROM collections on removable disks that are mounted with random drive letters? In this case, the program should detect that there are multiple volumes with the same label and
- give precedence to the unit letter the user actually specified for the rom path;
- ignore all drive letters, within the set of overlapping units with the same label, that don't have the specified path, rather than giving a frightening "Volume data_bck not available" dialog box;
- never alter permanently the rom paths in the database, and maybe ask the user confirmation for temporary "smart" replacements drive letters.