DFY$VMSCD V1.9 (c) Doffy 2005 2005.02.08. Author: Istv‡n D—sa (Doffy) email: doffy@mailbox.hu First step: =========== Unzip the DFY$VMSCD_A.ZIP file (compressed on VMS with ZIP). UNZIP you can download from Digital (now HP) web pages. What is DFY$VMSCD: ================== This program build image file in FILES11B file format for VMS. Similar as "mkisofs" for UNIX systems. After writing image file to CD, you can use as other VMS CD-s, but it is your edition. If run program without parameteres, the displayed help: DFY$VMSCD v1.9 FILES-11B CD/DVD image file builder (c) Doffy 2005 (doffy@mailbox.hu) Command syntax: DFY$VMSCD "source path" "dest. file" "label" [boot:"boot file"] [VERBOSE] "source path" must be defined in full file format (with device name). For additional working information use "verbose" (or "v") option. If source path only used, then size test performed without file creating. Example: DFY$VMSCD $2$DKB0:[TOCD] $2$DKB100:[IMAGE]CD.ISO DOFFY_CD VERBOSE This example copying all files and directories from directory $2$DKB0:[TOCD] to $2$DKB100:[IMAGE]CD.ISO image file and set volume label of new CD/DVD to DOFFY_CD. Linked files (SET FILE/ENTER) supported. For Alpha boot disc use "boot file" option. "boot file" must be defined with directory name and file name only (example: BOOT:[TOCD.SYSEXE]APB.EXE). The specified source directory is used on CD as [000000]. If source path only defined, then size test performed for calculating the CD/DVD capacity and no output file created. In this case the program write out only number of files and calculated image size. System files in CD root directory created by DFY$VMSCD after reading needed information of source files. DFY$VMSCD copying all versions of files and directories to image file. Linked files (created by SET FILE/ENTER command) supported. CD label can maximum 12 charaters. If run DFY$VMSCD in source root and below directories you must have RWED privileges and for all files below you must have RE privileges (build image file recomended as SYSTEM user). If running DFY$VMSCD, then source files and directories don't modify! To use DFY$VMSCD you must - copy it to SYS$SYSTEM and use MC DFY$VMSCD or - create symbol DFY$VMSCD == "$ SYS$LOGIN:DFY$VMSCD.EXE" if DFY$VMSCD located in your login directory. Now one version of file exists: DFY$VMSCD_A.EXE - for Alpha systems (Itanium version planed in near future) DFY$VMSCD writed in MACRO-32 and compiled on VMS 7.3-1 (ALPHA). Tested hardware: Digital Personal WorkStation AlphaServer ES40 How to write CD: ================ CD write was tested with Nero 6 on Windows XP. Hardware: Athlon 2600+ processor 512Mb RAM HL-DT-ST CD-RW GCE-8160B and SONY DVD RW DW-U14A The created image file must be write to the media with MODE 1 and "disc at once" option. With NeroExpress select the "Disc Image or Saved Project", select All Files(*.*) and click on input file and burn it. How create image file directly on PC: ===================================== You can create image file directly on PC if on your system not enough space available. Create image file as describen in next steps: 1. start on PC Pathworks software with DECNET protocol. 2. change dir to working directory: CD \CDWORK 3. run FAL program from Pathworks clients share \PCAPP. 4. test connection on server: - if your PC have DECNET address 12.5 then type command on server: DIR 12.5:: it must list contents of working directory (CDWORK) 5. run DFY$VMSCD by next example: DFY$VMSCD $2$DKB0:[TOCD] 12.5::CD.ISO DOFFY_CD VERBOSE In this case image file (CD.ISO) created directly on PC (DECNET address 12.5), in working directory (\CDWORK). How testing before write to CD: =============================== If you have empty disk in system, then mount it as foreign disk and copy generated file to it. After copying dismount and mount as normal ODS-2 disk. Now you can compare original files and result. For example if empty disk is $1$DUA1: then next steps: 1. generate image file: MC DFY$VMSCD $2$DKB0:[TOCD] $2$DKB100:[IMAGE]CD.ISO DOFFY_CD VERBOSE 2. mount disk as foreign: MOUNT $1$DUA1: /FOREIGN 3. copy image file: COPY $2$DKB100:[IMAGE]CD.ISO $1$DUA1: Warning!!! All data loss on this disk! 4. dismount this disk: DISMOUNT $1$DUA1: 5. mount as ODS-2 disk MOUNT $1$DUA1: DOFFY_CD /OVERRIDE=SECURITY/NOWRITE 6. compare files: BACKUP/COMPARE $2$DKB0:[TOCD...] $1$DUA1:[000000...] If compare finished without errors then you can write CD! After testing the disk must be initialized for future use. DFY$VMSCD minimize size of INDEXF.SYS on CD, no empty file headers for create new files. Corrected Errors: ================= v1.9 - size limit removed (for DVDs and big CDs), so you must manualy check the correct image size. If you use previous versions of this software with VMS 7.3 or newer then the temporary directory not removed at end. Now this error corrected. The history: The temporary directory (DFY$TMP_DIR.DIR) created in source directory and it have the CD root directory information. All files in this directory created with SET FILE/ENTER command. Some things (today I don't know what) was changed in VMS 7.3 and the command SET FILE/REMOVE not working for root files. (The same problem exist when you use DCL commands, so it is a new "feature") The solution of this problem with old (pre 1.9) versions is the next: - change the default directory to the sorce directory - $ SET FILE DFY$TMP_DIR.DIR/NODIRECTORY - $ DELETE DFY$TMP_DIR.DIR;1 Small file system definitions related problems also corrected: - error message when mount on alfa - some analize/disk error messages ODS-5 file system and shadow disks currently not supported! This version is create a volume with summary size of files. So it is create the smallest image as possible. When run the analize/disk command then the next message can be displayed: %ANALDISK-I-SHORTBITMAP, storage bitmap on RVN 1 does not cover the entire device This is no error, because the image don't use the full disk. v1.8 - no errors, but "size test" mode included v1.7 - the created image file size allways multiple of 2048 (Gear software can write image file if size multiple of 2048 bytes) - some special files can damage datastream in image file and part of data can't reached correctly (file header like for QUORUM.DAT file) v1.6 - Alpha boot now supported (for VAX not supported) v1.5 - source path [000000] now supported - system disk archived with errors (QUORUM.DAT, SECURITY.SYS not will be copied) - use less I/O if counting files and building 000000.DIR (more quickly run) v1.3: - indexed files copied bad and at this point data stream not correct. - relative files copied bad and at this point data stream not correct. v1.2: - if size of any source file equal 0 and allocated size greater then 0, then in generated image file data stream calculated bad, can't read properly all next files on CD. - if in file header of source file "first free byte" field equal 0, then can allocate to many blocks for this file. - linked files allocated space two times. - if original of linked files not below "source path", then program exit. Thanks for help: ================ - my wife (2 mount patience) - Michael N. LeVine, Naval Air Weapons Station (FILES-11B info in JUICER) - Katherine Cochrane, CD Information Company (CD info and publication) - T—th L‡szl—, APEH (testing) - R‡kos Zolt‡n, APEH (testing) - Pink Floyd (accompaniment) - Tears for Fears (accompaniment) - Enya (accompaniment) - Led Zeppelin (accompaniment) - Yello (accompaniment) - Locomotiv GT (accompaniment)