VIA VT8237R/VT8237A/VT8251
V-RAID Driver External Release Note
Windows 9x, Windows
Millennium
Windows NT4 plus Service
packs 6
Windows 2000, Windows XP
and Windows Server2003
Windows XP-x64, Windows
Server 2003 –x64
note: only support RAID5 on
VT8251, and the controller’s subclass code must be RAID (04) to enable RAID5
note: begin from Version 5.20b,
VIA Combo-RAID Driver was renamed to VIA V-RAID Driver
Item |
Version |
98/Me driver |
v5.20 |
NT4.0 driver |
v5.20 |
2K/XP/Server2003 driver |
v5.20 |
XP-x64/Server 2003-x64 driver |
v5.20 |
RAID Utility |
v5.27 |
After 4.20P5, the package had included x64
drivers and supported txtsetup installation in the meantime. By following the
new feature on Server2003SP1 for “F
Please just copy all files under \Drvdisk
to make up the floppy disk for pre-OS installation instead of copying specific
platform files. Otherwise, the text mode installer can’t find the driver files
with opposite folder structure.
1. Text setup
(1) Switch to the floppy disk(driver disk), and enter .\i386\NT5 direcotry, then copy all files to the floppy disk's root.
following
are dos commands to complete the actions.
>a:
>cd \i386\NT5
>copy *.* a:
(2) When Windows Vista setup program prompt "load driver", insert the floppy disk, then the VIA raid can be installed.
2. Install driver in Device Manager after Windows Vista installed
(1) Open the "Device manager", and select the VIA RAID Controller, then update its driver.
(2) Insert the driver disk, select the inf file in the .\i386\NT5
directory, then VIA raid can be installed.
1. On Win98/Me and NT4, don’t support
“Create/Delete/Repair RAIDs without reboot”
2. On Win98/Me, RAID5 not supported
3. On Win98/Me, RAID0 migration not supported.
4. On
Win98/Me and NT4, don’t support “notify OS when hot-plug happens”
Version |
Release Date |
Comment |
5.20c |
|
fix 98/Me Copy&Compare
issue |
5.20b |
|
fix Raid5 functions and Raid0
migration on NT4 fix 98/Me Copy&Compare issue |
5.20 formal release |
|
fix RAID5 rebuild issue fix the
RAID TOOL display issue |
5.20 Pre |
|
fix the HCT issue fix the
RAID5 rebuild issue fix the install NT4 by SATA ATAPI fail issue fix the
RAID TOOL version mismatch issue |
5.20 beta2 |
|
fix 5.20beta1 bugs,
enable RAID5 migration function on 2k/xp or later OS Known
issue: when migrate win2k/xp/svr2003 system from single HD to a RAID0, RAID5
or JBOD, if the RAID capacity less than |
5.20 beta1 |
|
fix server 2003
HCT12.1 syscache bug, support 3349 on win9x and nt4; RAID Utility does
not display RAID5 block size info any more. |
|
|
1. support 3349 on win9x and nt4 2. Fix X64, S4, and
RAID 5 display bugs. 3. Add RAID5 help
info into RAID Utility. 4. Remove unstable
RAID 5 Migrate function button from RAID Utility. 6. Release Win2K,
WinXP X32/X64, WinServer 2003 X32/X64 WHQL Logoed Drivers. |
4.40 |
|
Modify the version number to 4.40 |
|
|
Fixing Raidtool can’t be
updated under winNT4 |
|
|
Fix setup problem Fix authorization
problem |
|
Extend supporting to
include 0591 Update RaidTool to be
5.21 |
|
|
Update RaidTool to be
5.21 |
|
4.30D |
|
Update RaidTool to be
5.20 |
|
|
Suppoort silent install |
|
Add Windows XP x64 Logo |
|
|
Windows XP/2000 Logo
package |
|
4.30 |
|
|
4.20P5 |
|
Include x64 driver |
|
|
XP, SRV2003 i386 Logo’d |
4.20P4 |
|
XP, SRV2003 Driver HCT Passed |
fix issues and changes
|
Issue:After installing V-RAID driver V5.20B by U-Setup on VT8251
platform, SATA/SATAPI device can not be recognized by VIA RAID Tools under Windows
98SE/ME. [Update RAID driver to be Fix result: fixed Fix method: fix a coding bug |
|
Issue:win98se/winMe Copy&Compare
issue. Fix result: fixed Fix method: fix a coding bug |
|
Issue: After installing the Combo RAID driver V Fix result: fixed Fix method: fix a coding bug |
fix issues and changes
|
Issue: Not Support Raid5
functions and Raid0 migration on NT4 Fix result: fixed Fix method: open these functions in raid tool |
|
Issue: In 98/Me on VT3349, Can not Copy&Compare Fix result: fixed Fix method: fix coding bug in RAID driver |
fix issues and changes
when dynamic repair a
broken RAID5, RAID TOOL show the newly plugged free disk as OS disk, and
reboot fail after repair. |
The word “Hardware” is
spelt “Hareware”. When plug/Un-Plug SATA/SATAPI device, the RAID tool will
pop-up the dialog “Hareware Hotplug” |
fix issues and changes
Issue: Storage Data Verification Filter
test item is failed at HCT12.101 |
after dynamic rebuild
RAID5, OS reboot fail |
install
nt4 through SATA ATAPI Cdrom on 0591 fail |
RAID TOOL show different version info
in About Dialog Box |
fix issues and changes
Enable RAID5 migration function on 2k/xp or later OS Known issue: when migrate
win2k/xp/svr2003 system from single HD to a RAID0, RAID5 or JBOD, if RAID
capacity less than |
When installing Windows 2K/XP/SRV03/AMD64 OS on RAID 5 array and running
the ACPI S4, the system is BSOD |
win9x/me, when installing OS to IDE
controller and installing RAID driver V5.20Beta1, the RAID 5 rebuild function
can not be implemented |
fix issues and changes
HCT SysCache test
abnormal end of task at FAT32 and software RAID 5 partition for Windows
Server 2003 |
win9x can’t work on
3349 |
winnt4 can’t work no 3349 |
RAID Utility does not display RAID5
block size info any more. |
fixed issues
win9x can’t work on
3349 |
|
winnt4 can’t work no 3349 |
|
For VT8237/VT6410/VT6421 RAID Chip: When
the Windows OS is installed by txtsetup, the ACPI S4 can not be implemented. |
|
The VT6410/VT6421
RAID chips are not supported the RAID 5 function, but it can be created by
VIA RAID Tool. |
|
x64 system, txtsetup, create partition, and RAID0 migration fail |
|
When the Windows XPSP2 OS is installed by txtsetup and then running ACPI
S3 by Microsoft Bootvis on VT8251 platform, the RAID driver delay time is
greater than 5 sec. |
|
Remove un-stable RAID 5 Migrate Function Button from RAID Utility. |
|
Release Win2K, WinXP X32/X64, WinServer 2003 X32/X64 WHQL Logoed Drivers |
|
fixed issues
Modify the version number, change inf to RAID sub
class code (04) |
Fix setup problem
After
updating the VIA RAID Tools from V4.06 to V5.20, the system will pop up an
error message “raid_tool.exe – Entry Point Not Found” under Windows
NT4.0+SP6. |
When
removing the Combo RAID driver V4.31P1 by U-Setup/Control Panel/Silent, the system
will hang at the driver removed dialog under Windows XP+SP1 X64 and SRV03+SP1
X64. |
fixed issues
While
the setup program is executing, a console box windows is popped up for a long
time under Windows AMD64 system. |
When
execute the silent uninstall from MS-DOS, all of VIA drivers and tools can
not be removed under Windows XP 64bit and Server 2003 64bit. |
fixed issues
While
the setup program is executing, a console box windows is popped up for a long
time under Windows AMD64 system. |
When
execute the silent uninstall from MS-DOS, all of VIA drivers and tools can
not be removed under Windows XP 64bit and Server 2003 64bit. |
After installing the RAID driver 4.31, the system will show the error message "Windows Protection Error" under Windows 98SE/ME. [Check RAID driver installation from Device Manager à FAIL too] |
RAID
driver v4.31 can not be installed by U-Setup under Windows 2K+SP4. |
Provide down-mode algorithm for worst motherboard quality issue with VT3210
fixed issues:
After installing the RAID Tool v5.20 and
restart the system, the RAID Tool will pop up an error message “Error
Starting Program” under Windows 98SE/ME. [Check VIA
RAID Tool v4.06 à PASS] |
The
authorization problem of RaidTool is only fixed with WinXP, Win2000 and
SRV2003. |
While executing the RAID 0 Migration and RAID 1 Synchronization,
the completed status will hang at 100% on the demo board VT8369B2 ( |
User authorization problem on Windows 2000, Server2003
Update RaidTool to be 5.20
RaidTool 5.20 fixes
User authorization problem on Windows XP
Add sound effect
Update U-Setup kernel to be
Add Windows XP-x64 Logo
Fix:
Windows 2000 txtsetup BSOD problem
Windows XP/2000 Logo version
Fixed issues:
VIA VT6410 RAID chipset name is written VT |
Readme file update with correct file name and driver disk operation |
Fixed issues:
All OS, RAID 0 migration hang at 99%
AMD64 install pop up console window.
Serv2003 SP1 can not install.