Hi Bob
I Think This Project Is GREAT, Most Probarbly The Best I Have Seen Since The Modchip Was Introduced.
I Been Doing Some Research And This Is What I Have Found, I Hope Theese Link Are Of Some Use M8.
Also i think this maybe a hardware problem as it says here a source from maxtor
http://www.maxtor.co...ive_enabler.htmMaxtor's Big Drive Enabler is a one step executable that enables support for drives larger than 137 Gigabytes in Windows 2000 Service Pack 3 and XP Service Pack 1. This utility takes the guess work out of editing the Windows registry. The Big Drive Enabler fixes an operating system limitation.
This utility is needed anytime a Hard Disk Drive larger than 137 GB is connected to the motherboard's ATA bus, regardless of any system BIOS that supports 48-bit LBA."
Note: Failure to install the required service packs and install the Enable Big LBA patch can result in data loss when accessing the hard disk beyond 137 Gigabytes. For more information regarding Windows limitations and the 137 Gigabyte barrier please read Maxtor Knowledge Base Answer ID 960 and MS Knowledge Base Article 303013.
Linux SiS IDE ressource page
http://gyver.homeip.net/sis5513/And Finally Some More Information Here
http://maxtor.custhe...ated=1016214655I Have A Maxtor Plus 9, 120GB Hard Drive, So This Is Why I Have Chosen Maxtor Research.
The operating system only recognizes 128 GB or 137 GB of my large capacity drive.
Description: I have a drive that is larger than 137 GB but the operating system only recognizes 128 GB or 137 GB. How can I fix this?
Answer: Problem
The full capacity of ATA drives larger than 137GB is not recognized by the operating system.
Solution
Currently, there are three options to remedy the 137 Gigabyte barrier. Failure to implement one of the following installation options will result in data loss when trying to access the hard disk beyond 137 Gigabytes.
Installation Option 1.
Upgrade the operating system to either Windows 2000 with Service Pack 3 (or newer) or Windows XP with Service Pack 1 (or newer) and download the Maxtor Big Drive Enabler software patch. The Maxtor Big Drive Enabler, once executed, will update the Windows registry for large drive support.
Installation Option 2.
Download and install the Intel Application accelerator. The Intel Application Accelerator provides 48-Bit LBA compliant ATA/ATAPI controller drivers (IntelATA.mpd) and replaces the Windows 98/Me, 2000 and XP ATA controller drivers (ESDI_506.PDR). Intel is the only chipset manufacturer that we are aware of that offers a compatible controller driver for Windows .
http://www.intel.com...t/chipsets/iaa/The Intel Application Accelerator only supports the following chipsets: 810, 810E, 810E2, 810L, 815, 815EP, 815G, 815EG, 815P, 820, 820E, 840, 845, 845E, 845G, 845GE, 845GL, 845GV, 845PE, 850, 850E, 860. The Intel Application Accelerator can be obtained at
http://www.intel.com...t/chipsets/iaa/. If you have an unsupported chipset or do not want to upgrade the operating system then try the next solution.
Installation Option 3:
Attach the large hard drive to an add-in Ultra ATA PCI adapter card with a 48-Bit LBA compliant BIOS and controller driver. The adapter card bypasses the system BIOS and operating systems controller driver and uses its own BIOS and controller driver.
Using an IDE ATA/ATAPI controller that has a 48-Bit LBA compatible controller driver will allow safe use of large drives beyond the previous limits of 137 GB capacity. Additional controllers that do not have 48-Bit compliant drivers cannot safely access drives larger than 137 GB. A compatible card such as the Maxtor Ultra ATA/133 PCI for Windows and Sonnet Tempo ATA/133 PCI Card for MACs can be purchased at
http://www.maxstore.com (U.S. only) or at a local retailer.
http://www.maxstore....asp?sku=1856734http://www.maxstore....asp?sku=2190259Here Is A Guide To All Of The Above In An Adobe Acrobat .PDF Format
http://service.maxto...B_Solutions.pdfLast But Not Least, Here Is Some Information From MS.
http://support.MS.co...kb;en-us;303013MS Knowledge Base Article - 303013
SUMMARY: This article describes the Windows XP Service Pack 1 (SP1) 48-bit Logical Block Addressing (LBA) support for ATA Packet Interface (ATAPI) disk drives that can enable the capacity of your hard disk to exceed the current 137 gigabyte (GB) limit.
Note 48-bit LBA support is not enabled and therefore supported without Windows XP SP1. Windows XP Media Center Edition and Windows XP Tablet PC Edition already include SP1.
For additional information about the latest service pack for Windows XP, click the article number below to view the article in the MS Knowledge Base:
To determine if you have the latest ATAPI driver, verify that the version of Atapi.sys in your %systemroot%system32drivers folder is version 5.1.2600.1135 (or version 5.1.2600.1152 for Windows XP 64-Bit Edition) or later. To do this, follow these steps:
Click Start, and then click Search (or point to Search and then click For Files and Folders).
Type Atapi.sys, and then click Search.
If the Atapi.sys file in your %systemroot%system32drivers folder is not found, change your preferences for the Search Companion to search system and hidden folders and then repeat step 2. For additional information about how to search for hidden and system folders, click the following article number to view the article in the MS Knowledge Base:
302347 HOW TO: Search For Hidden Or System Files In Windows XP
In your %systemroot%System32Drivers folder, Right-click Atapi.sys, and then click Properties.
On the Version tab, note the file version.
If Atapi.sys is not version 5.1.2600.1135 (or version 5.1.2600.1152 for Windows XP 64-Bit Edition), obtain and install the hotfix described in MS Knowledge Base article 331958. For additional information about this hotfix, click the following article number to view the article in the MS Knowledge Base:
331958 Hard Disk May Become Corrupted When Entering Standby or Hibernation or When Writing a Memory Dump
By default, the original release of Windows XP Home Edition and Windows XP Professional do not have 48-bit LBA support enabled.
You must meet the following requirements to use 48-bit LBA ATAPI support:
You must have a 48-bit LBA compatible BIOS.
You must have a hard disk that has a capacity that is greater than 137 GB.
You must have Windows XP SP1 installed.
For the original release of Windows XP Home Edition or Windows XP Professional, 48-bit LBA could be enabled for testing purposes by setting a registry value, named EnableBigLba, to 1 in the following registry key:
HKEY_LOCAL_MACHINESystemCurrentControlSetServicesAtapiParameters
Warning Data corruption can occur you use this registry value to enable 48-bit LBA support in the original release of Windows XP Home Edition or Windows XP Professional, or if previous versions of Windows that do not support 48-bit LBA out of the box (for example, Windows 2000 or earlier) are installed on a disk partition that was previously created by a 48-bit aware operating system such as Windows XP SP1 that is larger or spans the current addressable limit of 137 GB.
Note: The preceding registry setting is ignored in Windows XP SP1 and later. If you attempt to enable the 48-bit LBA ATAPI support in the original release of Windows XP Home Edition or Windows XP Professional by editing the preceding registry setting and you did not meet the minimum requirements, you may observe the following behavior:
The registry value EnableBigLba is disabled. If you have a 48-bit compatible BIOS that can support a hard disk that has a capacity that is greater than 137 GB, only the first 137 GB of the hard disk are addressable. The rest of the hard disk is not used.
The registry value EnableBigLba is enabled, but you do not have a 48-bit LBA compatible BIOS and the capacity of the hard disk does not exceed 137 GB:
If you enable the 48-bit LBA ATAPI support by editing the registry setting, but you lack both a 48-bit LBA compatible BIOS and a hard disk that has a capacity that is greater than 137 GB, you have not changed the system. The hard disk continues to function as a standard hard disk.
The registry value EnableBigLba is enabled without a 48-bit LBA compatible BIOS, but you have a hard disk with a capacity that is larger than 137 GB.
If you enable 48-bit ATAPI support in the registry and you have a hard disk that has a capacity that is greater than 137 GB, but you do not have a 48-bit LBA compatible BIOS, only the first 137 GB of the hard disk are addressable. The remainder of the hard disk is not used.
To enable 48-bit LBA support by means of an unattended installation with the MS System Preparation (Sysprep) tool:
Copy the following text into MS Windows Notepad and save the text as the 48bitLba.inf file:[version]
signature="$CHICAGO$"
SetupClass=BASE
[DefaultInstall]
AddReg=48bitlba.Add.Reg
[48bitlba.Add.Reg]
HKLM,"SystemCurrentControlSetServicesAtapiParameters","EnableBigLba",0x10001,1
Create a file named Cmdlines.txt, which includes the following lines:
[Commands]
"rundll32 setupapi,InstallHinfSection DefaultInstall 128 .48BITLBA.INF"
Locate the SysprepI386 folder in the Sysprep image, and then create a $OEM$ subfolder in this folder.
Copy the 48bitlba.inf and Cmdlines.txt files into the SysprepI386$OEM$ folder.
In your Sysprep.inf file, add a key named InstallFilesPath to the [Unattended] section. This key must have the following value: InstallFilesPath = "C:sysprepi386"
To add the preceding settings to the Images folder, which had been created with the Riprep.exe program:
On the remote installation server that contains the Riprep image, create a SysprepI386$OEM$ folder in the following folder:
RemoteInstallSetupLanguageImagesRiprep_dir_nameI386Mirror1UserData
Note The word "Language" in the preceding path reads "English" for the English language, and "Riprep_dir_name" is the unique name that you selected for the Riprep image.
Copy the 48bitlba.inf and Cmdlines.txt files into the $OEM$ folder.
Modify the Riprep.sif file in the RemoteInstallSetupLanguageImagesRiprep_dir_nameI386TemplatesRiprep.sif folder (and any other template files for this Riprep image that you may have created), and then add the OemPreinstall and InstallFilesPath values so that they are set up as:
[Unattended]
OemPreinstall = "Yes"
InstallFilesPath = "C:sysprepi386"
Close, and then save the file.
OEMs have the ability to turn this support on by means of the MS Windows OEM Preinstallation Kit.
For more information, refer to the OEM Preinstallation Kit or the following MS Web site:
http://www.MS.com/oemLast Reviewed: 5/16/2003
Keywords: kbAppCompatibility kbenv kbhowto kbWinXPsp1fix KB303013
Hope This Helps
Best Regards
Adam
Vast Gsm Team
