sherpya/vdk: VMware Virtual Disk Driver for Windows
Driver on

sherpya/vdk: VMware Virtual Disk Driver for Windows

 Digital Disk Driver for Home windows NT platform. Copyright (C) 2003-2005 Ken Kato ([email protected]) http://chitchat.at.infoseek.co.jp/vmware/vdk.html This program is free software program; you'll be able to redistribute it and/or modify it below the phrases of the GNU Normal Public License as printed by the Free Software program Basis; both model 2 of the License, or (at your choice) any later model. This program is distributed within the hope that it will likely be helpful, however WITHOUT ANY WARRANTY; with out even the implied guarantee of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Normal Public License for extra particulars. You need to have acquired a duplicate of the GNU Normal Public License together with this program; if not, write to the Free Software program Basis, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA The GNU Normal Public License can be obtainable from: http://www.gnu.org/copyleft/gpl.html This program owes an awesome deal to Bo Brantén's 'ntifs' venture and 'filedisk' program (http://www.acc.umu.se/~bosse/). This program merely couldn't occur with out his nice works. INTRODUCTION ============ This can be a Digital Disk Driver (VDK) Model Three for Home windows NT / 2000 / XP. I've acquired some reviews that it additionally works on Home windows 2000 Server. With VDK you'll be able to mount a VMware digital disk to your Home windows hosts and use them as one other disk drive connected to your system. VDK can open the next VMware digital disk varieties for each read-only and read-write entry: - VMware 2.x Plain Disks (*.pln). - VMware 2.x / 3.x Digital Disks (*.dsk, *.vmdk). - VMware 2.x / 3.x REDO log recordsdata based mostly on each Plain Disks and Digital Disks. - VMware 2.x / 3.x differential / nested Digital Disks (which truly are renamed REDO logs), based mostly on each Plain Disks and Digital Disks. There isn't a limitation on the nesting stage. - VMware 4.x Flat digital disks (each break up and monolithic). - VMware 4.x Sparse digital disks (each break up and monolithic). - VMware 4.x REDO log recordsdata (which truly are the identical factor as split-sparse digital disks) and differential / nested digital disks (ditto). VDK means that you can use all these digital disks with minor errors, similar to timestamp mismatch, sequence quantity mismatch, and so forth. (VDK merely ignores these errors, it doesn't repair them.) VDK can even open the next kinds of digital disks. - Uncooked sector picture which you'll create with common disk dump instruments similar to Linux dd command. - Non-partitioned disk picture, similar to floppy picture, detachable disk picture, and dd picture of 1 partition. (This isn't truly a sort of digital disk, however reasonably how the digital disk is formatted.) On this case, the entire picture is handled as a single partition. VDK can be able to creating REDO log recordsdata which VMware can use. Which means VDK can open digital disks in undoable mode, then you definitely can commit the adjustments utilizing VMware, or discard the adjustments by merely deleting created REDO log recordsdata. VDK can not use the next digital disks in the meanwhile, however I am planning to implement them: - Any disk varieties with critical errors. VDK can not use the next disk varieties, and I've no intention of implementing them: - Uncooked Disks for any model of VMware. - REDO log recordsdata for Uncooked Disks. On this textual content, the time period "Digital Disk" (with capitals) particularly means growable digital disk created with VMware 2.x / 3.x, whereas "digital disk" (in decrease case) is utilized in extra generic sense versus "bodily disk". I do know it is form of complicated, however I simply could not provide you with extra appropriate phrases. WARNING & LIMITATIONS ===================== The VMware digital disk format and construction on which VDK was developed is totally the results of my *private* investigation. Completely no official data is offered by VMware, Inc. or any different sources. Please word that there's ABSOLUTELY NO WARRANTY and you should definitely use it AT YOUR OWN RISK. It's essential to have administrative privileges to make use of the VDK. That is becuase Home windows doesn't enable non-administrative customers to govern onerous disk volumes. VDK is a *disk* driver, not a file system driver, due to this fact you'll be able to solely entry partitions which your Home windows host can acknowledge. For instance, you can not entry ext2 partitions on digital drives until you have got a third occasion ext2 file system driver put in in your Home windows system (See NOTES under for extra data). VDK doesn't talk with Home windows 2000/XP Mount Supervisor. Due to this fact: - Disk Administration Console (partition manipulation and mount level configuration) doesn't acknowledge the VDK digital drives. Most of third occasion utilities, similar to PartitionMagic, ought to work. - Disk Defragment utility doesn't acknowledge the VDK digital drives. Third occasion defrag utility, similar to Diskeeper, works file. - Graphical mode of Test Disk could not work. Generally it really works and generally it does not for me, although I could not determine the sample thus far. (command line chkdsk.exe works high-quality). VDK doesn't deal with GPT partitioned disk (I do not actually know what it is. All I do know is that it is a new sort of partition desk.) Additionally, I think that you simply can not use Home windows NT Fault Tolerant Volumes (mirror, stripe, quantity set, and so forth) or Home windows 2000/XP Dynamic Volumes on digital drives. I merely do not know as a result of I've by no means used them. TO DO ===== - Permit non-administrative customers to make use of this system. - Higher compatibility with Win2K/XP (PnP help, Mount Supervisor help, and so forth). - GUI entrance finish program. - Digital disk error correction. - Digital disk sort conversion. FILES ===== vdk.sys Digital Disk kernel-mode Driver. vdk.exe Digital Disk Driver management program (console). README.TXT Rationalization of the Digital Disk Driver (this file). COPYING.TXT GNU GENERAL PUBLIC LICENSE Model 2. INSTALL ======= Place VDK.SYS and VDK.EXE right into a listing on a neighborhood drive. Then use VDK.EXE to put in the motive force (VDK.SYS) onto the system. Learn the next sections for extra data. When you've got earlier model of VDK.SYS put in in your system, you do not normally must uninstall the earlier driver from the system. You possibly can simply cease the outdated driver, substitute the motive force file, and restart the motive force. !!! NOTE !!! Machine drivers can't be began from a community drive. Be sure that a minimum of the motive force file (VDK.SYS) is positioned on a neighborhood drive. UNINSTALL ========= Use VDK.EXE to take away the motive force entry from the system registry. Then delete VDK.SYS and VDK.EXE from the native drive. VDK.EXE REFERENCE ================= VDK.EXE is a command line entrance finish program to manage the Digital Disk Driver (VDK.SYS). SYNTAX: VDK.EXE command [command specific options...] COMMANDS: INSTALL Set up the Digital Disk Driver. REMOVE Uninstall the Digital Disk Driver. START Begin the Digital Disk Driver. STOP Cease the Digital Disk Driver. DRIVER Print Digital Disk Driver standing. DISK Set the preliminary variety of Digital Disk gadgets. CREATE Create a brand new Digital Disk gadget. DELETE Delete a Digital Disk gadget. VIEW Print disk picture recordsdata data. OPEN Open disk picture recordsdata as a digital drive. CLOSE Shut disk picture recordsdata. LINK Assign a drive letter to a partition. ULINK Take away a drive letter from a partition. IMAGE Print opened picture file data. HELP Print command assist. All instructions and choices are case insensitive. VDK INSTALL =========== Set up the Digital Disk Driver. SYNTAX: VDK.EXE INSTALL [driver] [/AUTO] OPTIONS: driver Specifies the trail to the Digital Disk Driver file (VDK.SYS). Default is VDK.SYS in the identical listing as VDK.EXE. (Be aware: *NOT* present working listing.) /AUTO Configures the motive force to start out on the system startup. (Be aware: this feature doesn't begin the motive force after set up is accomplished.) By default the motive force must be began manually. Machine drivers can't be began from community drives. Be sure that to position VDK.SYS on a neighborhood drive. VDK REMOVE ========== Uninstall the Digital Disk Driver. SYNTAX: VDK.EXE REMOVE OPTIONS: NONE This command removes the Digital Disk Driver entries from the system registry, however doesn't delete the motive force file from the drive. If the motive force is working, this command closes all picture recordsdata and stops the motive force earlier than eradicating it from the system. VDK START ========= Begin the Digital Disk Driver. SYNTAX: VDK.EXE START OPTIONS: NONE If the motive force shouldn't be already put in, this command makes an attempt to put in it with the default choices. VDK STOP ======== Cease the Digital Disk Driver. SYNTAX: VDK.EXE STOP OPTIONS: NONE This command closes all picture recordsdata earlier than stopping the motive force. The driving force can't be stopped if digital drives are utilized by some other packages. VDK DRIVER ========== Print Digital Disk Driver standing. SYNTAX: VDK.EXE DRIVER OPTIONS: NONE This instructions prints the next data: Driver file path Driver file model Driver begin sort (AUTO/MANUAL) Present working state Variety of disk gadgets VDK DISK ======== Set the preliminary variety of digital disks. SYNTAX: VDK.EXE DISK quantity OPTIONS: quantity Variety of digital disks between 1 and 22. The default worth is 4. This command units the variety of digital disk gadgets created when the driver is began. If the motive force is already working, this worth takes impact the subsequent time the motive force is began. VDK CREATE ========== Create a brand new digital disk gadget. SYNTAX: VDK.EXE CREATE OPTIONS: NONE This instructions creates a brand new digital disk gadget. The created disk has the best disk quantity. VDK DELETE ========== Delete a digital disk gadget. SYNTAX: VDK.EXE DELETE OPTIONS: NONE This command deletes a digital disk gadget with the best disk quantity. A disk can't be deleted if a picture is opened, or any course of is utilizing it. Disk #Zero can't be deleted (there should exist a minimum of one disk gadget). VDK VIEW ======== Print disk picture data. SYNTAX: VDK.EXE VIEW picture [/SEARCH:path] OPTIONS: picture Path to the picture to print the knowledge. /SEARCH:path Specifies a path to look the picture file (and associated recordsdata). The required path has the best precedence within the looking order, and searched even earlier than the specific paths within the command line, descriptor recordsdata and digital disk recordsdata. This command prints the next data for the desired picture: Digital disk capability (in 512 byte sectors) Variety of recordsdata composing the picture Sort, capability and path of every element file Dimension and sort of every partition within the picture VDK OPEN ======== Open a disk picture as a digital drive. SYNTAX: VDK.EXE OPEN disk# picture [/RW | /WB | /UNDO | /UNDO:path] [/SEARCH:path] [/P:part#] [/L:drive] OPTIONS: disk# Specifies the digital disk quantity. This have to be the primary parameter. '*' means the primary obtainable disk, and if all current disk is busy a brand new digital disk is created. picture Specifies the trail to the disk picture file. This have to be the second parameter. See IMAGE TYPES part under for extra data /RW Open the picture in Learn-Write mode. /WB Open the picture in Write-Block mode. /UNDO | /UNDO:path Creates a REDO log for the picture and open in Learn-Write mode. For those who specify a path, the REDO log is created within the specified listing. /P:half# Specifies a partition quantity to set a drive letter. Drive letters might be set/eliminated later with LINK/ULINK instructions. By default, drive letters are assigned to all mountable partitions. /L:drive Specifies drive letters to assign to partitions. By default, the primary obtainable drive letter is used. /SEARCH:path Specifies a path to look the picture file (and associated recordsdata). The required path has the best precedence within the looking order, and searched even earlier than the specific paths within the command line, descriptor recordsdata and digital disk recordsdata. Solely certainly one of /RW, /WB and /UNDO can be utilized at a time. When none of those is specified, the picture is opened in Learn-Solely mode. See ACCESS MODES part under for extra details about these choices. VDK CLOSE ========= Shut a disk picture. SYNTAX: VDK.EXE CLOSE disk# VDK.EXE CLOSE drive OPTIONS: disk# Specifies the goal digital disk quantity. '*' means all current digital disks. drive Specifies certainly one of drive letters of partitions on the goal disk. /Q Suppresses prompting and fails the operation when an error has occured. /F Suppresses prompting and forces the picture to shut even when an error has occured. Be sure that different packages are usually not utilizing any partitions on the drive earlier than closing the picture. Usually, the picture shouldn't be closed whereas the digital drive is utilized by any processes. Though you'll be able to drive to shut the picture by answering to take action when requested or by utilizing the /F choice, you ought to be conscious that to forcibly closing a picture could result in lack of information or sudden conduct of the working system. VDK LINK ======== Assign a drive letter to a partition. SYNTAX: VDK.EXE LINK disk# half# [drive] OPTIONS: disk# Specifies the goal digital disk quantity. half# Specifies the goal partition quantity. drive Specifies a drive letter to assign. By default, the primary obtainable drive letter is used. You can not assign a couple of drive letters to 1 partition. You can not assign a drive letter already used for an additional quantity. Use IMAGE command to see partition numbers and the present drive letter task. With regular (partitioned) digital disks, the primary partition on the disk is partition 1, the second is partition 2, and so forth. Not like Linux, partition numbers for major partitions and logical partitions are usually not distinguished -- logical partition quantity begins simply after the final major partition and might be any quantity from 1. Partition Zero represents the entire disk (like /dev/hda, /dev/hdb, /dev/sda, and so forth. in Linux) and you shouldn't assign a drive letter to it. You possibly can assign a drive letter, however file system drivers can not entry the partition, as a result of it isn't formatted in any file system. It's simply like you do not normally mount /dev/hda in Linux. Non-partitioned digital disks (similar to floppy picture and detachable disk picture) solely have partition 0, and a drive letter is to be assigned to this partition. Once more, it's like mounting /dev/fd0 in Linux. VDK ULINK ========= Take away a drive letter from a partition. SYNTAX: VDK.EXE ULINK disk# half# VDK.EXE ULINK drive OPTIONS: disk# Specifies the goal digital disk quantity. half# Specifies the goal partition quantity. drive Specifies the drive letter to take away. This command can take away drive letters of digital disk drives solely. Use IMAGE command to see partition numbers and the present drive letter task. Closing a digital disk robotically unlinks all drive letters assigned to partitions on the digital disk. VDK IMAGE ========= Print present digital disk picture data. SYNTAX: VDK.EXE IMAGE [disk#] VDK.EXE IMAGE [drive] OPTIONS: disk# Specifies the goal digital disk quantity. drive Specifies certainly one of drive letters of partitions on the goal disk. This command prints the next data for the goal disk: Digital disk entry mode Digital disk capability (in 512 byte sectors) Variety of recordsdata composing the digital disk Sort, capability and path of every element file Drive letter, measurement and sort of every partition on the digital disk When goal shouldn't be specified, data for all drives are printed. VDK HELP ======== Print VDK.EXE command assist. SYNTAX: VDK.EXE HELP [command] OPTIONS: command Specifies a VDK.EXE command to show assist. Following instructions might be specified: INSTALL REMOVE START STOP DRIVER DISK CREATE DELETE VIEW OPEN CLOSE LINK ULINK IMAGE HELP If not specified, the overall assistance is printed. IMAGE TYPES =========== You need to use digital disks on each native and community drives. VIEW and OPEN instructions settle for the next path expressions: relative paths [] absolute paths x: UNC paths  VIEW/OPEN instructions can deal with the next kinds of digital disks: - VMware 2.x Plain Disk Consists of 1 descriptor file (*.pln) and a number of uncooked information recordsdata (*.dat). Use the trail to the descriptor file for VIEW/OPEN instructions. - VMware 2.x Digital Disk / REDO log / differential disk (COWD model 1) Consists of just one digital disk file (*.dsk or *.REDO). Use this path for VIEW/OPEN instructions. - VMware 3.x Digital Disk / REDO log / differential disk (COWD model 3) Consists of a number of digital disk recordsdata (*.vmdk or *.REDO) Use any one of many composing recordsdata for VIEW/OPEN instructions. - VMware 4.x Monolithic Flat Digital Disk Consists of a descriptor file (*.vmdk) and a knowledge file (*-flat.vmdk). Use the trail to the descriptor file for VIEW/OPEN instructions. - VMware 4.x Cut up Flat Digital Disk Consists of 1 descriptor file (*.vmdk) and a number of uncooked information recordsdata (*-fxxx.vmdk). Use the trail to the descriptor file for VIEW/OPEN instructions. - VMware 4.x Monolithic Sparse Digital Disk (VMDK model 1) Consists of just one digital disk file (*.vmdk). Use this path for VIEW/OPEN instructions. - VMware 4.x Cut up Sparse Digital Disk / REDO log / differential disk (VMDK model 1) Consists of a descriptor file (*.vmdk or *.REDO_*) and a number of digital disk recordsdata (*-sxxx.vmdk or *-sxxx.REDO_*). Use the trail to the descriptor file for VIEW/OPEN instructions. - Single uncooked sector picture file Consists of just one uncooked sector picture file. The file measurement should be an integer a number of of 512. Use this path for VIEW/OPEN instructions. - A set of uncooked sector picture recordsdata Consists of a descriptor file and a number of uncooked sector picture recordsdata. Use the trail to the descriptor file for VIEW/OPEN instructions. The descriptor file on this case is a plain textual content file which merely lists composing picture recordsdata: e.g.1 picture01.dat picture02.dat picture03.dat ... e.g.2 c:datavolume.001 c:datavolume.002 c:datavolume.003 ... e.g.3 disk.img c:workpart2.dsk ..imagedata ACCESS MODES ============ When a picture is opened for read-only entry (with none entry mode choices) the digital drive is handled as a write protected quantity. Even with /RW or /UNDO choice, underlying recordsdata for REDO log, differential/nested Digital Disks are at all times opened for read-only entry. Use /RW choice with excessive care as a result of this feature causes VDK to modify the digital disk recordsdata. Once you use /WB (write-block) choice, it's best to keep away from utilizing the drive for a protracted time frame or writing great amount of information to the drive. The distinction between information on the drive, which is unmodified, and information within the OS's disk cache, which the OS believes to be written efficiently to the drive, could result in an unpredictable conduct. NOTES ===== Encrypted/compressed digital disk recordsdata NTFS has native help for encrypting/compressing recordsdata on the quantity. Nevertheless VDK doesn't enable to open encrypted or compressed digital disk recordsdata. It's because the Home windows cache supervisor could impasse if a digital disk file is encrypted/compressed. Resolving relative paths If relative paths are utilized in descriptor recordsdata or REDO log, differential/nested Digital Disks, VMware resolves them from the *.vmx file's location. Nevertheless VDK.EXE tries to resolve them from the present file's location, and VDK.EXE could not be capable to discover the goal recordsdata. In such circumstances, VDK.EXE will immediate you for the appropriate path. REDO logs created with /UNDO choice For those who use /UNDO choice for opening *.pln, *.dsk or *.vmdk recordsdata, VMware will acknowledge the REDO log created by VDK.EXE, and you'll commit or discard the REDO log utilizing VMware. Nevertheless VMware won't search for the REDO log for *.REDO recordsdata, so in case you use /UNDO choice for opening *.REDO recordsdata, it's a must to manually delete the created REDO log recordsdata afterward. Opening REDO logs VDK.EXE doesn't robotically open REDO log for the goal disk as VMware does (until /UNDO choice is specified). If you wish to open a REDO log, it's a must to explicitly specify the trail to the REDO log file as proven within the examples under: VDK.EXE OPEN VDISK.VMDK Opens VDISK.VMDK, even when VDISK.VMDK.REDO exists. VDISK.VMDK.REDO shouldn't be used in any respect. VDK.EXE OPEN VDISK.VMDK.REDO Opens VDISK.VMDK.REDO, which should exist. Additionally makes use of VDISK.VMDK for read-only entry. VDK.EXE OPEN VDISK.VMDK /UNDO Creates VDISK.VMDK.REDO, which should NOT exist, then opens it for read-write entry. Additionally makes use of VDISK.VMDK for read-only entry. VMware can use VDISK.VMDK.REDO and can robotically acknowledge it once you use VDISK.VMDK as a digital disk. VDK.EXE OPEN VDISK.VMDK.REDO /UNDO Creates VDISK.VMDK.REDO.REDO, which should NOT exist, then opens it for read-write entry. Additionally makes use of VDISK.VMDK.REDO and VDISK.VMDK for read-only entry. VMware can use VDISK.VMDK.REDO.REDO however won't robotically acknowledge it once you use VDISK.VMDK or VDISK.VMDK.REDO. It's essential to explicitly specify VDISK.VMDK.REDO.REDO for VMware to use it. Utilizing REDO logs, differential/nested Digital Disks When adjustments are made to Digital Disks, VDK doesn't replace timestamp or sequence quantity within the Digital Disk header as VMware does. For those who made any adjustments to father or mother/underlying disks of REDO log or differential/nested Digital Disks, VMware would not know that they are consequently invalidated. Be sure that to not make any adjustments to father or mother/underlying disks. Don't use /RW choice to open them, and use /UNDO or /WB choice as a substitute in case you want read-write entry to the digital drive. Partition varieties on digital disks After efficiently opened the digital disk, VDK.EXE assigns drive letters to partitions of the next varieties on the digital drive: - FAT16, NTFS partitions on Home windows NT - FAT16, FAT32, NTFS partitions on Home windows 2000/XP When you've got third occasion file system drivers put in in your system and need to entry these partitions, it's a must to manually assign drive letters with VDK.EXE LINK command. The next file system driver works on VDK with none identified issues: - FAT32 for Home windows NT FAT32 file system driver for Home windows NT 4.0 obtainable from Sysinternals. http://www.sysinternals.com/ - Paragon Ext2FS Anyplace Demo model ext2/ext3 file system driver for Home windows 95/98/ME/NT/2000/XP (free trial model with restricted options) obtainable from Paragon Software program Group http://www.paragon-gmbh.com/ Because of Dave Parsons for mentioning this product to me. I suppose that the product model additionally works, however I can not verify it as a result of I can not afford it in the meanwhile ;-) The next file system drivers work on VDK with some points: - Ext2Fsd ext2 file system driver for Home windows 2000/XP written by Matt Wu. http://sys.xiloo.com/ * This driver solely partially helps dismounting of the volumes. After getting mounted an ext2 partition, this driver retains maintain of the partition object and prevents the VDK driver from unloading (signifies that you can not cease the VDK driver with out rebooting your system). - Ext2 File System Driver for Home windows NT 4.0 ext2 file system driver for Home windows NT 4.0 written by Manoj Paul Joseph http://freesourcecodes.tripod.com/ext2.htm * This driver doesn't help dismounting of the volumes. As a consequence, after you have mounted an ext2 partition, this driver retains maintain of the partition object and prevents the VDK driver from unloading. - EXT2IFS ext2 file system driver for Home windows NT/2000/XP written by John Newbigin http://uranus.it.swin.edu.au/~jn/linux/ext2ifs.htm * This driver doesn't help dismounting of the volumes. As a consequence, after you have mounted an ext2 partition, this driver retains maintain of the partition object and prevents the VDK driver from unloading. ** The GUI entrance finish program included in EXT2IFS assumes that every one ext2 partitions exist solely on mounted disks (very affordable assumption, I have to say), so its drive letter task methodology doesn't work effectively with VDK. Nevertheless in case you assign drive letters to ext2 partitions on the digital drive with VDK.EXE, the EXT2IFS driver acknowledges the partition and you'll entry it. You can too use different utitity packages to entry such partitions: - explore2fs A program to entry ext2 quantity from Home windows. http://uranus.it.swin.edu.au/~jn/linux/explore2fs.htm Because of João Alves for mentioning this program to me. Learn-only digital drives and Home windows By default VDK.EXE opens digital disks read-only for some security. Nevertheless silly Home windows doesn't appear to manage effectively with the thought of read-only onerous disk drives: - Home windows NT and Home windows 2000 merely can not entry NTFS partitions on read-only volumes. (See the subsequent part) - Home windows could sometimes complain that it can not write to the disk and warn you about lack of information. You possibly can safely ignore it. How will you lose information on read-only volumes anyway? When VDK opens a digital disk for read-only entry, it correctly units a flag to declare the drive as read-only, solutions that the quantity is write protected every time requested by the system, and declines each write request with well mannered "no, you'll be able to't write to this quantity as a result of it is write protected" standing code. Nonetheless, Home windows tries to put in writing. If Home windows doesn't consider what the drivers say and attempt to write anyway, why does it trouble to ask within the first place? - Home windows NT Disk Administrator causes the entire system to freeze in case you are utilizing a read-only digital drive. - and, I think, many extra... Utilizing NTFS partitions on digital drives Home windows NT and Home windows 2000 can not mount NTFS partitions if the quantity is read-only, so it's a must to open digital disks in writable mode if you wish to use NTFS partitions on it. (Home windows XP can mount read-only NTFS partitions). Nevertheless you have to be very cautious once you use NTFS partitions created with Home windows NT from Home windows 2000/XP. Home windows NT and Home windows 2000/XP truly use completely different variations of NTFS (Home windows NT makes use of NTFS 4, Home windows 2000/XP makes use of NTFS 5). When Home windows 2000/XP finds NTFS Four partitions it robotically upgrades the file system to NTFS 5 WITHOUT EVER ASKING IF THE USER WANTS IT. Truly Home windows 2000/XP can not mount NTFS Four partitions with out changing it to NTFS 5. Alternatively, Home windows NT can not entry NTFS 5 partition in any respect with out the Service Pack Four or later utilized to the system, and even with correct Service Packs some disk administration packages can not work on NTFS 5 partition (chkdsk, sure defragment utility, and so forth). And it's inconceivable to revert the upgrading course of. Outrageous, is not it? Once you need to entry NTFS Four partitions from Home windows 2000/XP, do not EVER use /RW choice. Use /UNDO or /WB choice as a substitute. HISTORY ======= 06-04-2005 Model 3.2 (VDK.SYS 3.1, VDK.EXE 3.2) - Settle for digital disks created with VMware 5.x - Settle for digital disks with "lsilogic" digital controller. - Added /SEARCH choice to VIEW and OPEN instructions. - Added /UNDO:path choice to OPEN command. 10-11-2003 Model 3.1 (VDK.SYS 3.1, VDK.EXE 3.1) - Mounted a bug that the motive force might trigger the system to stall through the system shutdown. - Mounted a bug that vdk.exe couldn't learn prolonged partition tables saved past 4GB from the start of the disk. - Added /Q (quiet) and /F (drive) choices to CLOSE command. - Corrected description of required privileges within the assist and the doc. 04-11-2003 Model 3.Zero Launch (VDK.SYS 3.0, VDK.EXE 3.0) Added help for a number of digital drives, write-block mode, sector picture file set, view data command. 30-07-2003 Model 2.Zero Launch (VDK.SYS 2.0, VDK.EXE 2.0) Added help for VMware 4.Zero digital disks, easy sector picture recordsdata, non-partitioned disk picture recordsdata. 27-05-2003 VDK.SYS 1.01 Mounted a significant bug the place it could not deal with digital disks bigger than 4GB correctly. 20-05-2003 Preliminary Launch (VDK.SYS 1.0, VDK.EXE 1.0) 

Leave a Reply

Your email address will not be published. Required fields are marked *