Support is available only via email; typical response time is within one business day. The registered users have priority in technical support. If the problem is not addressed in the FAQ, please send an email to support@xtralogic.com. Please provide detailed description of the problem.
Please check your spam filter folder for the missing message. If that doesn't help, please contact us at support@xtralogic.com
Please send a request to support@xtralogic.com. To allow us identify you as a registered user, write the name and email address you have used during the registration. We'll send the registration key only to the email address that was used during the registration.
Go to Control Panel and open VHD utility applet
Click Register.
Enter your first, last name and the registration key you have received.
The status will change to "registered".
The hard disk capacity reported by Windows Explorer is actually size of a file system partition. While the storage capacity of the VHD was increased, the file system partition size remained unchanged. You can see that in Windows Disk Management. The file system partition needs to be extended to occupy the new space. VHD Utility does not manipulate file system partitions. You will find recommendations on how to extend a file system partition here.
While VHD size can be up to 2 TB, the maximum VHD size supported by Microsoft Virtual PC's IDE controller is only 127 GB. The VHDs, bigger than 127 GB, have to be attached to a SCSI controller in Microsoft Virtual Server.
This can happen when disk capacity crosses one the following boundaries - 528Mb, 1Gb, 2Gb, 4Gb, which causes the disk geometry reported by BIOS to change.
The Windows MBR code and NTFS boot sector initial program loader (NTFS IPL) are using CHS addressing on disks with capacity less than 8 Gb.
CHS addressing relies on the disk geometry. The disk geometry is essentially comprised of two parameters: number of heads and number of sectors per track.
In order to be able to access all the disk space using number of cylinders less than 1024, BIOS performs translation of physical disk geometry.
The translated disk geometry reported by BIOS, namely its number of heads parameter, changes depending on the capacity of the disk.
For example for a disk with a size between 1Gb and 2Gb number of heads reported by BIOS will be 64, between 2Gb and 4Gb it'll be 128,
and over 4Gb it'll be 255 (even for the disk with capacity more than 8Gb). This will affect any CHS address with non-zero cylinder component.
Normally the boot partition offset in MBR is in the cylinder 0, so it's not affected by this.
But, at the time the partition created by NTFS, the disk geometry is stored in the BIOS parameter block (BPB) of the NTFS boot sector.
After the disk geometry changes, the offsets of the of the $Boot metadata file, calculated by NTFS IPL code become invalid due to
the mismatch in the current number of heads reported by BIOS and the number of heads stored in the BPB.
NTFS IPL is not able to read the $Boot metadata file and reports the 'disk read error'.
This problem can be fixed by rebuilding the NTFS boot sector, and, if necessary replacing the MBR,
with the one which does not use the disk geometry for disk operations.
All of these can be done using the Testdisk utility.
Step-by-step guide on rebuilding NTFS boot sector using Testdisk.
