ISMBLD.LIT 2.1(140) no longer stores the data file device in the IDX unless it is specified explicitly on the command line (e.g. ISMBLD DSK2:MYFILE) or to the "Data file device:" prompt. This partially rolls back a change introduced in 2.1(139) which made the data device explicit in all cases.
The explicit data device specification was causing a problem for non-AMOS-conforming devices like ARCH27: or VSK: because of limitations in the historic binary format of the IDX. It was also inviting confusion when an IDX/IDA pair was copied to another location for testing. If the data device specification was not updated using the ISMBLD /D switch, the new IDX would continue to reference the old IDA device, possibly leading to inadvertent updating of the wrong file.
Comments
| • | ISMDMP displays the data file device (only if it is non-blank). |
| • | ISMDMP <file>/D can be used to change it. |
| • | If using an explicit data file device, make sure it follows the form of three alphabetic characters followed by a number 0-66635, e.g. DSK1: or XYZ999: |
