Tweet
Depending on the location where I am testing, the disk that I am testing on varies. Is there a way, through the scripting language or in any other way, to programmatically select the disk that I would like to test on?
I have come across the SETDISK command, yet its behavior is not what I had expected. My config file initially has no disks selected, and if I try a command like 'SETDISK DISK d:', this drive is not selected. However, if I manually select this disk, then use the same command with more parameters, like MODE or FILE, those parameters are altered accordingly. Is this the expected behaviour? If so, how can I programmatically select a disk for testing?
Furthermore, the disks that I am dealing with are physical disks, unformatted. I have tried to use the commands above, such as 'SETDISK DISK 5:', but it errors out, saying it is unable to execute the script command.
This seems like fairly straight-forward question, and I apologize if the solution can be easily found. If so, I have not found it after much searching. Any help would be greatly appreciated.
I have come across the SETDISK command, yet its behavior is not what I had expected. My config file initially has no disks selected, and if I try a command like 'SETDISK DISK d:', this drive is not selected. However, if I manually select this disk, then use the same command with more parameters, like MODE or FILE, those parameters are altered accordingly. Is this the expected behaviour? If so, how can I programmatically select a disk for testing?
Furthermore, the disks that I am dealing with are physical disks, unformatted. I have tried to use the commands above, such as 'SETDISK DISK 5:', but it errors out, saying it is unable to execute the script command.
This seems like fairly straight-forward question, and I apologize if the solution can be easily found. If so, I have not found it after much searching. Any help would be greatly appreciated.
Comment