...
To start the utility open "cmd.exe" in the Start menu and switch to the CHARON x86 utilities executables directory (typically "C:\Program Files (x86)\CHARON\Utilities_X.X.XXXXXBuild_XXX\x86" or "C:\Program Files\CHARON\Utilities_X.X.XXXXX\x86
").
...
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.
...
It is also possible to create custom disk images using the "-blcount" (blocks count) and "-blsize" (blocks size) switches.
Div | ||
---|---|---|
| ||
| ||
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).
...
Div | ||||
---|---|---|---|---|
| ||||
Transferring disk images
The "MkDskCmd" utility is able to transfer (copy) disk images of one type to a disk image of another type.
...
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. |
...