The best resolution is to update the BIOS to have 48bit LBA capability. This avoids any reliance on measures installed on the drive itself that depend on the drive being booted from in order to work. ie you can expect other things like imaging or recovery utilities that boot from CD to be able to see the full drive. The board manufacturer must have an updated BIOS available, and there's a small risk of a BIOS update going wrong.
An IDE controller card is very viable. Such a card has its own 48bit LBA capable BIOS. Possible limitations include bus congestion if it's a PCI card & you're also using the PCI bus for sound etc, & ensuring compatability if using an older OS such as Win98.
A DDO (Dynamic Drive Overlay) obtained from the drive manufacturer loads a BIOS patch for 48bit LBA each time the system boots. Loss of 48bit LBA access and consequent possible drive corruption are potential problems if the DDO gets damaged or the system is booted without the DDO e.g. floppy or CD boot.
Driver level support relies on the I/O chipset provider developing 48bit LBA drivers, Intel has their Application Accelerator for several chipsets, AMD also released drivers for some motherboard chipsets. The same restriction applies in that 48bit LBA access is not available unless Windows loads from the drive.
In any of these cases, unless and until 48bit LBA is implemented by some means, it is not possible to access beyond the 28bit LBA limit to create multiple partitions. This is another reason to prefer BIOS update or 48bit IDE controller, as only these two options allow both full drive access for creating partitions during Windows installation, and when not booting from the drive. For example, if you intend to install the Intel Application Accelerator, Windows will have been installed onto a partition of at most 137GB. After the Accelerator install, further partitions will then be able to be created beyond that, or third-party software can be used to expand the existing partition out into unallocated space. If at any time the Accelerator software fails to load when Windows boots up, subsequently created partitions would become unavailable, or a partition that was expanded beyond the 137GB size could become corrupted. As already mentioned, there are sound reasons (including this one) to create more than one partition, rather than having one partition filling the entire drive.
Edited by Platypus, 13 October 2007 - 07:35 AM.