Unterstützt der HPT370 Controller 300GB HDDs?
- Ersteller Fadl
- Erstellt am
DFmakaveli
Enthusiast
Hi habe den selben COntroller .
Ich habe ein älteres bios drauf als 2.xx.xx . Aber bei mir erkennt der Controller auch Festplatten mit 160 GB (unter WinXP) .
Kann leider kein bios apdate machen auf 2.xx.xx , weiss nicht woran das liegt ....
Vielleicht kann mir einer mal helfen .....
Ich habe ein älteres bios drauf als 2.xx.xx . Aber bei mir erkennt der Controller auch Festplatten mit 160 GB (unter WinXP) .
Kann leider kein bios apdate machen auf 2.xx.xx , weiss nicht woran das liegt ....
Vielleicht kann mir einer mal helfen .....
Snoopy69
Urgestein
- Mitglied seit
- 06.01.2005
- Beiträge
- 18.183
Noch einer mit dem gleichen Problem! Guck mal...
4. BIOS Update
===============
To update BIOS for onboard HPT3xx controller, please refer to your
mainboard manual or contact the hardware vendor for updating BIOS.
To update BIOS for HPT3xx adapter, you can use HighPoint BIOS loading
utility.
* Notes for BIOS update from v2.0.xxxx on adapters with auto-load enabled
If your HPT370/370A adapter has auto-load feature enabled, PCI configuration
header may change after you update BIOS. This will cause Windows 2000/XP
unable to boot from the controller. To avoid this problem, you must use load
utility v2.1.12.22 or later and specify the following parameters to update
BIOS:
load bios372.231 /e 408=1800003,42c=51103
5. Known Problems
==================
* Install OS to devices attached to HPT3xx controller
Before installing OS to devices attached to HPT3xx controller, you must
remove the drives connected to other controllers from your system temporarily.
After OS installation complete, you can put them back.
* Windows XP upgrade installation
When doing an upgrade installation of Windows XP (before Service Pack 1)
with HPT3xx controller, Windows XP will use HPT370 driver in its
driver package and prevent user to specify a new driver. To solve this
problem you can do the upgrade as below:
1. Run XP upgrade program in a running system.
2. When setup finished copying files and ask reboot, DO NOT reboot.
3. Open WinXP temporary installation folder ($WIN_NT$.~BT) and search for
txtsetup.sif file.
4. Open txtsetup.sif with Notepad, remove the line "hpt3xx=hpt3xx.sys,4"
under section [scsi.load] by adding a semicolon before that line.
5. Save the file and reboot.
6. Start XP setup as normal. When setup prompt "Press F6 to add SCSI driver",
press F6 and specify the new driver to be loaded.
7. During text-mode setup, Windows XP may still copy the built-in HPT370 driver
to the final Windows installation's System32\Drivers directory. To use the
new driver, you must replace the old one before you continue into graphic-mode
setup. This can be done by booting from a DOS floppy if you are using FAT
or FAT32 file system; if you use NTFS file system, you have to use some
other method to replace the built-in driver.
There are more information about this issue on Microsoft support site:
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q225125
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q220845
* Install HPT370/370A controller on an existing Windows XP system
When installing HPT370/370A controller on an existing Windows XP system,
Windows XP may try to install its HPT370 driver first; this may cause
system hang when you are using new features the driver don't support.
To avoid this problem, you shall update the driver first with no drives
attached to HPT370/370A controller, shutdown the system, attach the
drives, then start the system again.
* Compatibility issue with Adaptec SCSI adapter
If you encounter compatibility problems when you use HPT3xx controller
together with Adaptec SCSI adapter, please try to disable EBDA reallocation
in Adaptec SCSI BIOS, or enable "EBDA reallocation" in HPT3xx BIOS.
You can use BIOS loading utility v2.2.07.01 or later to enable this
feature (e.g. "load /c bios372.232").
* Moving disks to other IDE controllers
When you want to use disks previously attached to HPT370/370A/372 controller on
other IDE controllers, please first delete any array information on the
disks. Otherwise your data may be lost when you want to put it back later.
* Rescanning disks
There is a limitation for the refresh function in RAID Management Software.
If you remove a disk from the controller but the software does not notice this
event, it is also unable to notice the event when you plug another disk back
to that location. You must force a refresh action before changing the disk.
* Problem on two disks with same signature under Windows 98/ME
If you break a RAID 1 array into two single disks without destroying data and
use both of them under Windows 98/ME, Windows will behave abnormally since
there are two volumes with same Windows signature. To solve the problem, boot
into MS-DOS mode and run "fdisk /mbr".
4. BIOS Update
===============
To update BIOS for onboard HPT3xx controller, please refer to your
mainboard manual or contact the hardware vendor for updating BIOS.
To update BIOS for HPT3xx adapter, you can use HighPoint BIOS loading
utility.
* Notes for BIOS update from v2.0.xxxx on adapters with auto-load enabled
If your HPT370/370A adapter has auto-load feature enabled, PCI configuration
header may change after you update BIOS. This will cause Windows 2000/XP
unable to boot from the controller. To avoid this problem, you must use load
utility v2.1.12.22 or later and specify the following parameters to update
BIOS:
load bios372.231 /e 408=1800003,42c=51103
5. Known Problems
==================
* Install OS to devices attached to HPT3xx controller
Before installing OS to devices attached to HPT3xx controller, you must
remove the drives connected to other controllers from your system temporarily.
After OS installation complete, you can put them back.
* Windows XP upgrade installation
When doing an upgrade installation of Windows XP (before Service Pack 1)
with HPT3xx controller, Windows XP will use HPT370 driver in its
driver package and prevent user to specify a new driver. To solve this
problem you can do the upgrade as below:
1. Run XP upgrade program in a running system.
2. When setup finished copying files and ask reboot, DO NOT reboot.
3. Open WinXP temporary installation folder ($WIN_NT$.~BT) and search for
txtsetup.sif file.
4. Open txtsetup.sif with Notepad, remove the line "hpt3xx=hpt3xx.sys,4"
under section [scsi.load] by adding a semicolon before that line.
5. Save the file and reboot.
6. Start XP setup as normal. When setup prompt "Press F6 to add SCSI driver",
press F6 and specify the new driver to be loaded.
7. During text-mode setup, Windows XP may still copy the built-in HPT370 driver
to the final Windows installation's System32\Drivers directory. To use the
new driver, you must replace the old one before you continue into graphic-mode
setup. This can be done by booting from a DOS floppy if you are using FAT
or FAT32 file system; if you use NTFS file system, you have to use some
other method to replace the built-in driver.
There are more information about this issue on Microsoft support site:
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q225125
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q220845
* Install HPT370/370A controller on an existing Windows XP system
When installing HPT370/370A controller on an existing Windows XP system,
Windows XP may try to install its HPT370 driver first; this may cause
system hang when you are using new features the driver don't support.
To avoid this problem, you shall update the driver first with no drives
attached to HPT370/370A controller, shutdown the system, attach the
drives, then start the system again.
* Compatibility issue with Adaptec SCSI adapter
If you encounter compatibility problems when you use HPT3xx controller
together with Adaptec SCSI adapter, please try to disable EBDA reallocation
in Adaptec SCSI BIOS, or enable "EBDA reallocation" in HPT3xx BIOS.
You can use BIOS loading utility v2.2.07.01 or later to enable this
feature (e.g. "load /c bios372.232").
* Moving disks to other IDE controllers
When you want to use disks previously attached to HPT370/370A/372 controller on
other IDE controllers, please first delete any array information on the
disks. Otherwise your data may be lost when you want to put it back later.
* Rescanning disks
There is a limitation for the refresh function in RAID Management Software.
If you remove a disk from the controller but the software does not notice this
event, it is also unable to notice the event when you plug another disk back
to that location. You must force a refresh action before changing the disk.
* Problem on two disks with same signature under Windows 98/ME
If you break a RAID 1 array into two single disks without destroying data and
use both of them under Windows 98/ME, Windows will behave abnormally since
there are two volumes with same Windows signature. To solve the problem, boot
into MS-DOS mode and run "fdisk /mbr".
