16 Nov
2019
16 Nov
'19
8:05 p.m.
On 11/16/2019 3:40 AM, Mark Pizzolato wrote:
I will send this. This looks to me like it isn't showing what we want to
see. Meanwhile I will download the latest commit and try again. And a
new license copy and not rename it.
Bill
On Friday, November 15, 2019 at 11:06 AM, Bill
Cunningham wrote:
[...]
Nothing was typed after vmst. The
C style comment was a note.
sim> att tq -f ansi-vms vmst /* the license
file */
Can't open: //mst - no such file or directory.
Can't open tape image.
If you look at the very explicit instructions I
originally outlined, you really didn't follow them.
The HELP TQ ATTACH provides several examples of situations that would work.
Meanwhile you typed:
sim> att tq -f ansi-vms vmst /* the license
file */
In this command EVERYTHING beyond the ansi-vms token is considered a list
of space or comma delimited file names, or wildcard file names.
In this example, this list would be:
vmst
Everything in the / directory
the
license
file
Everything in the current directory
The / directory file itself.
The auto tape assembly process that is implemented by this command might treat directory
files as binary data, I'm not sure, but trying to pass the / directory and any
directories in it as files on a tape is likely a meaningless operation.
Possibly only one of these would be valid (vmst). Of course
there might be something I am forgetting and not doing here.
I also type at the prompt in all caps, same result. For example,
ATT -F ANSI-VMS? VMST
You are working on a Linux system which has case sensitive
file names, so there is a distinct difference between vmst and VMST. This command is
missing the device name TQ as well...
The simh commands and many of their arguments (ansi-vms and -f) are case insensitive, but
filenames are whatever the host system supports.
In the latest commit, I've enriched the error messages issued when unrecognized
arguments/files are presented to a tape attach.
- Mark