| Anchor | TopUtilPage | TopUtilPage | |
|---|---|---|---|
| Include Page | |||
|
Table of Contents
| Table of Contents | ||
|---|---|---|
|
General Description
The "MkDskCmd" utility:
- Creates empty disk images of a given standard or custom disk type or a customand disk size
- Transfers existing disk images of one type to disk images of another type.
To start the utility open "cmd.exe" in the Start menu and switch to the CHARON executables directory ("C:\Program Files\CHARON\Build_XXX\x86").
Creating disk images
The first step is to obtain the disk type of the disk that needs to be created:
...> mkdskcmd -list |
This command results in a list of all the supported disk types.
Choose the desired disk type (for example "RZ22"), then use the "mkdskcmd" command to create the virtual disk image as shown below:
|
A disk container "rz22.vdisk" will be created in the current directory.
| Info |
|---|
A file "rz22.avdisk" will also be created. This file helps CHARON to accurately recognize a specific disk image type. It is recommended to put the ".avdisk" file in the same directory as the created disk image. |
It is also possible to create custom disk images using the "-blcount" (blocks count) and "-blsize" (blocks size) switches.
...
| class | pagebreak |
|---|
For a list of all available parameters use the "–help"switch:
|
The "-avtable" parameter is used to work with an alternative disk specification database (or to point to the standard database ("mkdsk.vtable") if it is in a location other than the current directory).
The "-blcount" (blocks count) and "-blsize" (blocks size) switches are used to create custom disk images.
...
| class | pagebreak |
|---|
Transferring disk images
The "MkDskCmd" utility is able to transfer (copy) disk images of one type to a disk image of another type.
This operation is needed, for example, to obtain more free space on a disk image that already contains data.
Note: it is not possible to add more free space dynamically. CHARON-VAX/PDP11 must be stopped before performing this operation.
| Info |
|---|
If a source disk image is larger than the target disk image, the extra data is lost. If the source disk image is smaller, it will be extended and padded with null bytes ('\0'). |
An example of the syntax follows:
...> mkdskcmd -transfer <source disk file name> <source disk parameters> [-shrink] [-k] |
where:
<source disk file name> - the file name of the disk image to be transferred
<source disk parameters> - the name of the disk from the list of available on "mkdskcmd --list" request or the disk geometry specification (see below).
- -shrink or -k - used in the case when the target disk is transferred to a smaller disk.
Example:
...> mkdskcmd -transfer "C:\My Disks\rz22.vdisk" rz25 |
It is also possible to specify the disk parameters manually with "-blcount / -c" (blocks count) and "-blsize / -z" (blocks size) switches:
...> mkdskcmd -transfer <source disk file name> -blsize <number> -blcount <number> |
Example:
...> mkdskcmd -t "C:\My Disks\custom.vdisk" -z 512 -c 262134 |
| Warning |
|---|
There is a certain delay between the moment when the utility reports that a disk image has been transferred and its actual availability to CHARON. This delay can reach up to several minutes in the case of very large disk transfers. This is because the host operating systemsneeds time for the actual allocation of the enlarged file on HDD. |
...
|