VIA V-RAID Software Package Release Note
Microsoft Windows 98SE, Windows Millennium
Microsoft Windows NT4 plus Service packs 6
Microsoft Windows 2000, Windows XP, Windows Server2003, Windows Vista, Windows Server2008
Microsoft Windows XP-x64, Windows Server 2003-x64, Windows Vista-x64, Windows Server 2008-x64
Microsoft Windows Home Server
Microsoft Windows 7
VT8237S, VT8237A, VT8251, CX700/VX700, VX800(UT)/VX820(UT) and VT6421
Only support RAID5 on VT8251, and the controller’s subclass code must be RAID mode (Subclass Code = 04) to enable RAID5
Begin from Version 5.20b, VIA Combo-RAID Driver was renamed to VIA V-RAID Driver
Begin from Version 5.50a, VT8251 SATA Controller will be supported by Microsoft default AHCI driver when it works in AHCI mode on Microsoft Windows Vista
For VT8237/R/R Plus, and VT6410 controllers, the V5.50b is the final stable package for them. So, VIA stops to support them from V5.60.
Driver/Tools version description inside this package
|
Item |
Version |
|
98SE/Me driver |
V2.0.950.573 |
|
NT4.0 driver |
V4.0.1381.573 |
|
2K/XP/Server2003/Home Server driver |
V5.1.6000.581 |
|
XP-x64/Server 2003-x64 driver |
V5.2.6000.581 |
|
VISTA/VISTA-x64 driver |
V6.0.6000.6173 |
|
RAID Utility |
V5.85 |
|
Driver Disk Preparation Utility |
V1.1 |
Installation Guide
Pre-OS Installation Notice:
We provide a driver disk preparation utility since package version 5.50a. You can use this utility to create pre-OS installation driver disk for separate operations systems. For more information, please see the related README file in \VRAIDDrv folder.
If you want create driver disk manual, please just copy all files under \VRAIDDrv\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.
Installation steps on Windows Vista and Windows Server 2008:
1. Text setup
(1) Switch to the floppy disk(driver disk), and enter .\VISTA\x86 directory, then copy all files to the floppy disk's root.
Following are dos commands to complete the actions.
>a:
>cd \VISTA\x86
>copy *.* a:
(2) When Windows Vista setup program prompt dialog box including "load driver" button, please insert the floppy disk, click the button ”load driver”, set “drive A” as target directory, then the VIA V-RAID driver can be installed.
2. Install driver in Device Manager after Windows Vista was 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 .\VISTA\x86 directory, then VIA RAID can be installed.
Installation steps on Windows Vista-x64 and Windows Server 2008-x64:
1. Text setup
(1) Switch to the floppy disk(driver disk), and enter .\VISTA\x64 directory, then copy all files to the floppy disk's root.
Following are dos commands to complete the actions:
>a:
>cd \VISTA\x64
>copy *.* a:
(2) When Windows Vista-x64 setup program prompt dialog box including "load driver" button, please insert the floppy disk, click the button ”load driver”, set “drive A” as target directory, then the VIA V-RAID driver can be installed.
Note: This method can be used only when the logo for this driver binary is ready.
2. Install driver in Device Manager after Windows Vista-x64 was 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 .\VISTA\x64 directory, then VIA RAID can be installed.
Silent Installation for satisfying Customer setup spec Notice:
An external file, Setup.iss, was opened to provide another “auto reboot” option for silent installation.
While the parameter of silent install auto-reboot, /z”reboot” is not present:
Ø While the BOOTOPTION value is 0, it means the silent installation will not reboot system automatically after executing.
Ø Once the BOOTOPTION value is 3, it means the silent installation will reboot system automatically after executing.
While the parameter of silent install auto-reboot, /z”reboot” is present
Ø Regardless the value of BOOTOPTION to be 0 or 3, U-setup will reboot system automatically after executing.
V-RAID Tool Installation Notice for Event Log Purpose:
VIA provides Event Log function through V-RAID tool to record any RAID operation events at self-defined Log File located at the same directory of RAID tool location. After V5.70b, the tool can also record these events at Application Event catalog of Windows Event Log. So, if you want to use this Event Log function, the V-RAID tool should be run at minimum mode, in other word, you should execute it in the background and minimum it at Windows task area, liked as Windows Clock application.
For some customers, they want to automatically run this V-RAID tool when each Windows boot-up time for event log purpose, but some customers want to leave this auto-start decision by end-users at installation time through dialog box popping behavior, or only let end-users manually run this tool at run time. VIA seriously takes these customers feedback, so V-RAID tool installation program behavior can be configured through two control flag bits, which are inside component initialization file (component.cif) located at RAID tool directory of package, to satisfy different customers marketing demand. One control flag bit, named as “Auto-start Dialog box Control”, is provided for customers to decide whether the dialog box is popped at installation time or not in order to get end-users’ decision, and the other control flag bit, named as “Force-running Mode”, is provided for customers to decide whether RAID tool can be forced to run automatically at each Windows start up time. For these detail control flag bits location and related information, please refer the description inside component initialization file (component.cif).
For these flags setting value and behavior, we describe them as following:
Ø The Auto-start Dialog Box control flag bit can be set as enabled to allow end-user to decide whether RAID tool can be automatically run at each Windows start-up time. It is inactive if VIA installation program is executed at Silence Mode.
Ø The Force-running Mode control flag bit can be set as disabled in order to let RAID tool not to be run automatically at each Windows start-up time. It is inactive if Auto-start Dialog Box control flag bit is enabled.
Ø For silence installation mode, only the Force-running mode control flag bit is major behavior decision flag bit.
(Note: About the flags default setting value, VIA V-RAID SW general published package are set as disabled. VIA customers can change these default value based on marketing need.)
Based on POS system user behavior and VIA V-RAID SW architecture characteristic, VIA also provides the VIA Log Service to log hot plug and broken status during system log-off period for meet POS market requirement.
(Note: U-Setup will copy the log-translation file (VRAIDlog.dll) for Windows Event Log into \WINDOWS\system\ of current operating system when install the RAID tool, and remove it when uninstall it.)
V-RAID Tool Installation Notice for Microsoft OEM Ready Test:
To meet the Microsoft OEM Ready Test’s requirement, from V5.80d on, V-RAID tool uses manifest with “asInvoker” level. In this case, the customers choose to run V-RAID tool automatically will meet a running privilege issue on VISTA, in other word, once V-RAID tool runs without choosing “Run as administrator”, error message will popup. So from V5.80d on VIA U-Setup program will promote the privilege of V-RAID tool for the account who installs the package and V-RAID tool will start to run automatically normally. For other accounts, to avoid the error message popup, manual setting is necessary. The setting steps are described below:
Ø Find the V-RAID tool binary at the system installation volume: for example, for VISTA x86, it is installed at “C:\Program Files\VIA\RAID\”; for VISTA X64, it would be “C:\Program Files (x86)\VIA\RAID\”
Ø Launch the “Properties” by right clicking raid_tool.exe, then choose the page of “Compatibility” and check the “Run this program as an administrator” in “Privilege Level” setting.
After save the settings above, V-RAID tool will run normally without necessary to choose “Run as administrator” and this account won’t meet the error message.
Limitations
RAID Tool limitations on Windows 98SE/ME and Windows NT4:
1. On Win98SE/Me and NT4, don’t support “Advanced” Smart command in “Check All Disks”
2. On Win98SE/Me and NT4, don’t support “Verify” (verify physical hard-disks) in “Check All Disks”
3. On Win98SE/Me and NT4, don’t support “VIA Log Service”
4. On Win98SE/Me and NT4, don’t support logging event into Windows Event Log
RAID Tool limitations
1. The hot-plugged in/out information won’t be recorded into “VIA View Event Log” by real time while “VIA View Event Log” window is opening.
Driver limitations on Windows 98SE/ME and Windows NT4:
1. On Win98SE/Me and NT4, don’t support “Create/Delete/Repair RAIDs without reboot”
2. On Win98SE/Me, RAID5 function is not supported.
3. On Win98SE/Me, RAID0 migration action is not supported.
4. On Win98SE/Me and NT4, doesn’t support “notify OS when hot-plug happens”
5. On Win98SE/Me and NT4, don’t support VIA SATA controller work at IDE mode (subclass code = 01)
Driver limitations Windows 2000 and above:
1. On Windows Server 2003 and VIA VT8251 platform, hard disks which OS was installed can not execute “turn off hard disk” command. The root cause is no spin-down command been sent to VIA RAID driver by OS, it’s an OS limitation.
2. On Microsoft Windows XP and VIA CX700/VX700 platform, the system will restart while switching mode between RAID mode and IDE mode because the operation system doesn’t support this feature. Please refer to http://support.microsoft.com/kb/314082/ to solve this issue.
3. On Microsoft Windows VISTA and Windows VISTAx64 system, the system will be requested to reboot when the migration or synchronization is completed. After the system is rebooted, the RAID controller will be rescanned. It is an OS limitation.
4. After removing V-RAID driver V5.80A from Device Manager on VT8251 platform under Vista+SP1 x64 system and then rebooting system, the system will show “Windows cannot verify the digital signature for this file” error message.
Other Limitations:
1. Unsupported ATA device: Pioneer DVD-123A PATA DVD-ROM, BENQ EW162U SATA DVD ROM.
2. On Microsoft Windows VISTA、Windows Server 2008、Windows VISTAx64 and Windows Server 2008x64, RAID Utility must run with the method of Right-Clicking the Application and select “Run as Administrator”.
3. P4M800 NB+VT8251 SB platform, the S3 resume time will exceed 5 seconds.
OS Limitations:
1. After deleting RAID1 array, on which current OS is running, by V-RAID Tool under Microsoft Windows VISTA SP1, it will cause that system can’t enter into OS successfully with the mirror disk. (Microsoft Windows XP and previous OSs have no this issue)
2. After installing V-RAID driver V5.80A from Device Manager under Windows 2K+SP4, the V-RAID driver information will be shown “Unknown or Not available” some times.
3. On Microsoft Windows VISTA X86 OS, raid tool will be blocked by OS temporarily till user allows it to be run if raid tool is installed as auto-start mode. This issue will be under checking with Microsoft for OEM Ready Test Program.
4. Driver disk is required during whole installation process, and couldn’t be removed from floppy, otherwise, the system will pop-up an error message “Could not initialize UI subsystem” while installing the Windows Home Server on RAID controller.
5. Microsoft Windows XP (x86) does not support hard disk with capacity larger than 2T, although VIA V-RAID solution can report a RAID disk capacity above 2T to OS and operated for the space over 2T. For correct disk capacity displayed at OS disk manager and operation for the disk operation above 2T, User should use Windows XP (x64) and above version, including Windows XP x64，Windows Server 2003 X64/x86，Windows VISTA x86/x64 and Windows Server 2008 x86/x64 with GPT format for disk partition, not MBR format. MBR formal is only used for the disk capacity lower than 2T and included. For MS OS installation for the disk capacity above 2T, the correct BIOS/OSes, supporting GPT format, should be used. Based on current information, only EFI BIOS and OSes which can support EFI BIOS can do it. The current MS OSes which support EFI BIOS includes Window Server 2008 (x64) and Window VISTA (X64). For any detail and correct information, please contact Microsoft.
Known Issues:
1. The buttons on the caption of Mirror’s synchronization windows will be re-drawn abnormally by OS once when you click on the title bar at the first time, during the process of synchronization.
2. The HDD is disappeared randomly or reboot rarely when we install Microsoft Win7 into a RAID Disk , which is compounded by some different brand special HDDs, inside VX800(UT)/VX820(UT) platform based on Win7 in-box V-RAID Driver. It is still under investigation inside VIA RD.
3. While installing V-RAID driver V5.80 under Windows SRV03 x64 with 8GB DRAM, it will cause the disk which is on VT6421A SATA RAID controller can’t be formatted successful. [To check with 6GB DRAM or install Vista x64 driver will work well]. This issue root-cause is found and fixed and the solution is under-verification.
.
VT8237A support starts from v4.31
VT8237S support starts from v5.40
VX800(UT)/VX820(UT) support starts from v5.60
Release History
|
Version |
Release Date |
Comment |
|
2009/11/12 |
1． Support V-RAID Utility installation for Microsoft Windows 7 to work with in-box V-RAID Driver. |
|
|
2009/03/19 |
1． Fix bug in Driver Disk Preparation Utility |
|
|
2009/02/20 |
1． Fix 5.80d bugs 2． Fix bugs for OEM Ready Test |
|
|
2009/01/20 |
1． Update U-Setup kernel program files 2． Change manifest level of V-RAID tool binary in 5.80c from “requireAdministrator” to “asInvoker” and update U-Setup library for utility |
|
|
2008/09/25 |
1． Fix 5.80a bugs 2． Add tips for different icons in taskbar 3． Change the color of icons in taskbar 4． Add minimize button into the window of synchronization of Mirror 5． Change to log the “Disk Degrading” event as ID #1790 |
|
|
2008/07/23 |
1. Record all events into the Windows Application Event Log. 2. Add control method at installation program to decide whether RAID tool can be run automatically at each Windows start-up time or not 3. Add “Set Recover Method” and related functions 4. Add VIA Log service to log the hot plug event and broken status when log off. 5. Fix 5.70a bugs |
|
|
2008/03/07 |
1. Support New Windows operation systems 2. Support full scan function 3. Record the hot plug event in the log file 4. Fix 5.60a bugs MS WHQL Logo Certified Drivers |
|
|
2007/08/02 |
1. Support VIA new chipset CX8x0 2. Fix the issue that package doesn’t support hard disk or RAID array whose capacity is larger than 2TB 3. Enable automatic RAID creating method again on VT8251 platform when RAID Utility works on Windows Vista 4. Fix 5.50b bugs MS WHQL Logo Certified Drivers |
|
|
2007/04/16 |
Fix 5.50a Software Installation Program Bugs MS WHQL Logo Certified Drivers |
|
|
2007/04/12 |
1. Fix 5.40a bugs 2. Support new SW architecture driver for Microsoft Windows Vista 3. Provide a new Utility to make Pre-OS installation driver disk 4. Fix controller disappear issue at V-RAID utility at Windows Server 2003 and Vista even though the end-users don’t attach devices at this controller MS WHQL Logo Certified Drivers |
|
|
2006/12/27 |
1. support VIA new chipset VT8237S; 2. support Multiple Language in RAID Utility; 3. new GUI for RAID Utility; 4. fix 5.30c bugs; Vista WHQL Logo Certified Drivers |
|
|
2006/06/06 |
Correct wrong version string showed at setup program. WHQL Logo Certified Drivers |
|
|
2006/05/26 |
Fix 5.30a RAID Tool and Setup bugs WHQL Logo Certified Drivers |
|
|
2006/05/12 |
1. support VIA new chipset CX700/VX700; 2. support hard disk spin-down on VT8251 platform; 3. support new device IDs; 4. display broken RAID0/5 status; 5. use Microsoft new technology, DIFX, for setup program 6. WHQL Logo Certified. |
|
|
5.20c |
2006/01/20 |
fix 98/Me Copy&Compare issue |
|
5.20b |
2005/12/29 |
fix Raid5 functions and Raid0 migration on Microsoft Windows NT4 fix Microsoft Windows 98/Me Copy&Compare issue |
|
5.20 formal release |
2005/11/3 |
fix RAID5 rebuild issue fix the RAID TOOL display issue |
|
5.20 Pre |
2005/10/25 |
fix the HCT issue fix the RAID5 rebuild issue fix the install Microsoft Windows NT4 by SATA ATAPI fail issue fix the RAID TOOL version mismatch issue |
|
5.10a |
2005/8/12 |
1. support VT8251 on Microsoft Windows 98/ME/NT4 2. Fix Microsoft Windows X64 OS, 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 Microsoft Windows XP X32/X64, Windows Server 2003 X32/X64 WHQL Logo Drivers. |
|
4.40 |
2005/7/6 |
Modify the version number to 4.40 |
|
4.30G |
2005/6/24 |
Fixing Raidtool can’t be updated under Microsoft Windows NT4 |
|
4.30F |
2005/06/20 |
Fix setup problem Fix authorization problem |
|
2005/05/20 |
Extend supporting to include VT8237A Update RaidTool to be 5.21 |
|
|
2005/05/20 |
Update RaidTool to be 5.21 |
|
|
4.30D |
2005/05/11 |
Update RaidTool to be 5.20 |
|
4.30C |
2005/04/25 |
Suppoort silent install |
|
2005/04/21 |
Add Microsoft Windows XP x64 Logo |
|
|
2005/04/15 |
Microsoft Windows XP/2000 Logo package |
|
|
4.30 |
2005/04/08 |
|
|
4.20P5 |
2005/03/01 |
Include Microsoft Windows x64 driver |
|
4.20A |
2005/02/24 |
Microsoft Windows XP/ SRV2003 i386 Logo’d |
|
4.20P4 |
|
Microsoft Windows XP/ SRV2003 Driver HCT Passed |
|
Issue: No V-RAID Utility can be workable with Microsoft Windows 7 in-box V-RAID Driver. Fix result: fixed Fix method: Modify VIA U-Setup program to allow V-RAID Utility V5.85 can be installed into Microsoft Windows 7 in order to let V-RAID utility can be workable with in-box V-RAID Driver checked in by VIA. |
Version 5.80f
|
Issue: While install OS - Windows XP (x86) using the driver disk made by Driver Disk Preparation Utility (only selects “Windows XP/ Server 2003 (x86)”), OS will inform users “Software Installation has not passed Windows Logo Testing to verify its compatibility with Windows XP”. Fix result: fixed. Fix method: Fix the code error. |
|
Issue: While installing V-RAID driver package V5.80A by “Silent” under Vista+SP1 x64 and then rebooting system, the system will pop-up the “VIA RAIDTool MFC has stopped working” error message. Fix result: fixed. Fix method: Fix the code error. |
|
Issue: The word “syncing” should be written “synchronizing”. Fix result: fixed. Fix method: Fix the code error. |
|
Issue: OEM Ready Program test will fail at “Verify that the application creates uninstall entries in the Register” item due to the information of “U-Setup Install Location” is blank. Fix result: fixed. Fix method: Fix the code error. |
|
Issue: OEM Ready Program test will fail at “Verify that the application passed specific AppVerifer check” item due to the V-RAID Tool will abnormal break into the debugger. Fix result: fixed. Fix method: Fix the code error. |
|
Issue: After removing V-RAID driver by U-Setup under 64Bit OS ( Vista、XP、Server2003 ) on VT8237 or VT8251 platform, the system will pop-up the “Platform Error” and “Feature transfer error” error message. Fix result: fixed Fix method: fix a coding bug |
|
Issue: Microsoft OEM Ready Test and popup error message in VISTA if choose “Yes” in the query box “… to run V-RAID Tool at minimal mode automatically…” for the account who installs package. Fix result: fixed Fix method: Change manifest level in V-RAID tool in 5.80c from “requireAdministrator” to “asInvoker”. Update installation program to promote the V-RAID tool’s privilege for the account. |
Version 5.80c
1. Fixed issues and related changes:
|
Issue: Popup query box to repair broken array, although there are no available disks to be used for repair. Fix result: fixed Fix method: fix a coding bug |
|
Issue: Popup error message in VISTA if choose “Yes” in the query box “… to run V-RAID Tool at minimal mode automatically…” Fix result: fixed. Fix method: Add manifest into V-RAID tool. |
2. Add tips for different icons in taskbar
Add tips for different icons in taskbar to illustrate the current status.
3. Change the color of icons in taskbar
Change the color of icons in taskbar to make it clearer to see.
4. Add minimize button into the window of synchronization of Mirror
Set the window of Mirror’s synchronization as minimized mode by default.
5. Change to log the “Disk Degrading” event as ID #1790
Log the “Disk Degrading” event returned by S.M.A.R.T command as ID #1790, which indicates the disk’s performance is degrading and it has the possibility of data loss.
1. Record all events into the Windows Application Event Log.
From this package, all events recorded in the log file of V-RAID utility will be recorded in the Windows Application Event Log in the same time. And the event of broken array and the result of repair broken array are recorded.
2. Add control method at installation program to decide whether RAID tool can be run automatically at each Windows start-up time or not
Please refer the description of “V-RAID tool Installation Notice for Event Log Purpose” section listed at above.
3. Add “Set Recover Method” and related functions
Provide two recover methods - “Manual” and “Auto”.
In “Manual” mode, when RAID tool detects an array with “Need Synchronization” status, it will request users to confirm to begin the synchronization or not; otherwise, tool will begin synchronization automatically. And “Auto” is the default setting.
4. Add VIA Log service to log the hot plug event and broken status when log off.
Add VIA Log service to log the hot plug event and broken status when operating system is in logged off status.
Note: this function is not supported on Microsoft Windows 98/ME and Windows NT4.
5. Fixed issues and related changes:
|
Issue: The system will pop-up the “VIA RAID Tool MFC has stopped working” error message under Windows Vista x64+SP1 while choosing “To run V-RAID Tool at minimal mode” and then rebooting the system. Fix result: fixed Fix method: fix a coding bug |
|
Issue: After removing V-RAID driver V5.70A by U-Setup under Windows Vista x64 on VT8251 platform, the system will pop-up the “Platform Error” and “Feature transfer error” error message. Fix result: fixed Fix method: fix a coding bug |
|
Issue: When OS booting from Mirror disk of RAID1 Array, after finish sync data from Mirror disk to Source disk, BSOD will occur if you plug out the Mirror disk. In this case, it’s recommended to reboot the system when the synchronization finished. Fix result: fixed Fix method: fix a coding bug |
Version 5.70a
1. Support new Windows operation systems:
From this package, Microsoft Windows Home Server, Microsoft Windows Server 2008 and Microsoft Windows Server 2008-x64 are supported. The driver for Windows Home Server is the same as that for Windows Server 2003. The driver for Windows Server 2008 is the same as that for Windows Vista. The driver for Windows Server 2008-x64 is the same as that for Windows Vista-x64.
2. Support full scan function:
From this package, the full scan function for hard drive is supported. This function is supported on Microsoft Windows 2000 and later, and it is not supported on Microsoft Windows 98/ME and Microsoft Windows NT4.0.
3. Record the hot plug event in the log file:
When hot plug event happens, the associated device’s information will be recorded in the log file.
4. Fixed issues and related changes:
|
Issue: After unplugging SATAPI device during transferring data under Microsoft Windows Vista, the device will be removed from Device Manager after about 5 minutes Fix result: fixed Fix method: fix a coding bug |
|
Issue: VIA V-RAID software package doesn’t support CX8x0 RAID controller work on Microsoft Windows 2000 Fix result: fixed Fix method: fix a coding bug |
|
Issue: While executing Benchmark tool of “HD Tune V2.51” on RAID JBOD array under Microsoft Windows Vista, the system will pop-up an error message “Read Error” Fix result: fixed Fix method: fix a coding bug |
|
Issue: While using IDE 40 pin cable to install Windows XP/SRV03/Vista OS on RAID controller of VT3324, the system will be BSOD Fix result: fixed Fix method: Add the IDE 40 pin support in the driver |
|
Issue: When issuing ioctl command to driver to get SMART information, the informations for all drive are the same Fix result: fixed Fix method: Update the ioctl command supports. |
|
Issue: While excuting ACPI S3 Burn-in test on VT8237S RAID platform under Vista, the test can’t over 1000 times. Fix result: fixed Fix method: Fix a coding bug |
5. Vista WHQL Logo Certified Drivers
Version 5.60a
1. Support the following new Device IDs:
|
|
|
IDE (Subclass Code 01) |
RAID (Subclass Code 04) |
AHCI (Subclass Code 06) |
|
CX8x0 |
Device ID |
0x5324 |
0x0581 |
N/A |
|
Supporting OS |
N/A |
Microsoft Windows 98/Me/NT4/XP/SRV2003/ Vista |
N/A |
2. Fix the issue that package doesn’t support hard disk or RAID array whose capacity is larger 2TB:
Hard disk or RAID array, whose capacity is larger than 2TB, is supported from this package.
3. Enable automatic RAID creating method again on VT8251 platform when RAID Utility works on Windows Vista
4. Fixed issues and related changes:
|
Issue: While installing Windows XP (x86 or x64) on VT8237S RAID controller with V-RAID driver v5.50b and then executing ACPI S1, the resume time will take around 10 seconds Fix result: fixed Fix method: fix a coding bug |
|
Issue: When unplugging SATAPI device from VT8237S RAID platform under Windows XPSP2/Vista/XPSP1 x64/Vista x64, the system will hang Fix result: fixed Fix method: fix a coding bug |
5. Vista WHQL Logo Certified Drivers
Version 5.50b
Fixed issues and related changes:
|
Issue: During Software Installation, the wrong information should be corrected, including version number..etc. Fix result: fixed. Fix method: Update the Installation program file. |
Version 5.50a
1. Fixed issues and related changes:
|
Issue: For VIA CX700/VX700 RAID Controller, the system will hang or no responding after executing the “Turn off hard disk” on RAID array under Microsoft Windows NT5 Fix result: fixed. Fix method: patch for the CX700/VX700 platform |
|
Issue: For VIA V-RAID Driver V5.40A: While playing audio file (such as MP3) with Microsoft Windows Vista Media Player 11 on VIA RAID disk, there will be noise. Fix result: fixed. Fix method: fix a source code error |
|
Issue: The 'Business Disk' performance of Win Bench V2.0 will drop 40~45% with V-RAID driver V5.40A under Window XPSP2 x86. (Compare with V5.30C) Fix result: fixed. Fix method: fix the source code error |
2. Support new SW architecture driver for Microsoft Windows Vista.
Provide new SW Architecture driver, which is enhanced from VIA checked-in Driver Code Base and passed WHQL DTM test, for Microsoft Windows Vista.
3. Provide a new Utility to make Pre-OS installation driver disk.
Provide a new utility DriverDiskPrep.exe which can make driver disk based on the user’s selection. This Utility is located on \VRAIDDrv and please run this program in this full directory. For more information, please refer the related README file in \VRAIDDrv folder.
4. Fix controller disappear issue at V-RAID utility on Microsoft Windows Server 2003 and Windows Vista even though the end-users don’t attach devices at this controller.
5. Added WHQL Logo Certified files into package, including Microsoft Windows 2000, Windows XP X32/X64, Windows Server 2003 X32/X64 and Windows Vista X32/X64
Version 5.40a
1. Support the following new Device IDs:
|
|
|
IDE (Subclass Code 01) |
RAID (Subclass Code 04) |
AHCI (Subclass Code 06) |
|
VT8237S |
Device ID |
0x5372 |
0x7372 |
NA |
|
Supporting OS |
NA |
Microsoft Windows 98/Me/NT4/2000/XP/SRV2003/ Vista |
NA |
2. Support Multiple Languages in RAID Utility, including English, German, French, Dutch and Simplified Chinese.
If the executed Windows OS is in an un-supported language OS to the RAID Utility, the user interface of the RAID Utility will be represented in English.
3. New GUI for RAID Utility:
More beautiful graphical user interface;
Easier operation flow;
Add a new function: “Rescan Array Status”.
4. Fixed issues and related changes:
|
Issue: After installing V-RAID driver V5.30c and creating the RAID array onCX700/VX700 RAID controller, the Disk drives name will show 'VIA CX70 0' in Device manager.[Should be spelt CX700 not CX70 0]
Fix result: fixed
Fix method: fix a coding bug
|
|
Issue: If inserting the VT6421 PCI RAID card on VT8237R/VT8237A/VT8251/ICH7R platform and then installing Microsoft Windows 2K/XP/SRV03/x64 OS on VT6421 by txtsetup, the RAID controller's name will be something wrong in the 'Nero Info Tool' hardware monitor utility. (It also happens if you insert and install VT6421 PCI RAID card on VT8237R/VT8237A/VT8251/ICH7Rplatform with Windows OS already installed.) A. For VT8237R/VT8237A/ICH7R platform: There will be two VIA VT6421 RAID Controllers. B. For VT8251 platform: There will be two VIA VT8251 AHCI RAID Controllers.
Fix result: It is not a driver bug, but an Nero Info Tool’s bug
|
|
Issue: Microsoft Windows OS should not Boot from broken RAID1 array which have the invalid data.
Fix result: fixed(need update OPROM to cooperate with this package)
Fix method: Add codes to RAID Utility
|
5. Vista WHQL Logo Certified Drivers
|
Issue: The V-RAID driver version is description error in the U-Setup program of V-RAID driver V5.30B. [Should be V5.30B not V5.30A]
Fix result: the version numbers is corrected.
Fix method: 1. Change SCF version number string from V5.30B to V5.30c. 2. Change CIF version number string from V5.30a to V5.30. (In other word, we only show driver version, not package version.) |
Fixed issues and related changes:
|
Issue: While VIA SATA controller is set to be IDE mode, VIA RAID Tools still can be installed successfully by U-Setup of V-RAID driver V5.30beta4 for VT8237 serious chips (not including VT8237A).
Fix result: it is HW Limitation for VT8237 serious chips (not including VT8237A).
Fix method: User need to choice the correct driver package according the selection of BIOS Setup items
|
|
Issue: While removing V-RAID driver V5.30a from VT6421 RAID controller, there are some issues as following: A. Error-1: V-RAID driver can not be removed under Microsoft Windows 2000 SP4 while installing the driver by U-Setup and then removing by U-Setup. [Fixed failed] B. Error-2: V-RAID driver can not be removed under Microsoft Windows ME while installing the driver from Device Manager and then removing by U-Setup. [Fixed failed] C. Error-3: RAID controller will show yellow mark under Device Manager of Microsoft Windows XPSP2 and Windows Server2003+SP1 x86 while installing the driver from Device Manager and then removing by U-Setup. [Windows XP+SP2 is still failed]
Fix result: Fixed.
Fix method: update U-Setup source code
|
|
Issue: While installing V-RAID driver package V5.30A under German Microsoft Windows 2K+SP4, VIA RAID Tools V5.30 can not be executed successful.
Fix result: U-Setup coding error issue, fixed
Fix method: Fix this coding error.
|
|
Issue: The driver string is not uniformity in the txtsetup file of V-RAID driver package V5.30A
Fix Result: Correct this string. (Remove “s” character.) |
1. WHQL Logo Certified Package.
2. Support the following new device IDs:
|
|
|
IDE (Subclass Code 01) |
RAID (Subclass Code 04) |
AHCI (Subclass Code 06) |
|
VT8251 |
Device ID |
0x5287 |
0x3349 |
0x6287 |
|
Supporting OS |
NA |
Microfost Windows 98/Me/ NT4/2000/ XP/ SRV2003/ Vista |
Microfost Windows 98/Me/ NT4/2000/ XP/ SRV2003/ Vista |
|
|
VT8237A |
Device ID |
0x5337 |
0x0591 |
NA |
|
Supporting OS |
NA |
Microfost Windows 98/Me/ NT4/2000/ XP/ SRV2003/ Vista |
NA |
|
|
CX700/VX700 |
Device ID |
0x5324 |
0x0581 |
NA |
|
Supporting OS |
NA |
Microfost Windows 98/Me/ NT4/2000/ XP/ SRV2003/ Vista |
NA |
3. Fixed issues and related changes:
|
Issue: When running ACPI S1, the hard disk can not spin down
Fix result: fixed
Fix method: fix a coding bug |
|
Issue: name in driver disk is too long, and will be truncated in txtsetup screen display
Fix result: fixed
Fix method: unify the display name in driver disk to “VIA V-RAID Controller Series”
|
|
Issue: RAID 0/JBOD/5 array is disappearance from VIA RAID Tools after unplugging one disk by static and enter Windows system.
Fix result: fixed
Fix method: add this feature
|
|
Issue: V-RAID driver V5.30 can not be removed successfully by U-setup while OS is installed on PATA IDE of 0571. (Only occurs while ATAPI device is connected to RAID controller and ATA device is connected to PATA IDE of 0571
Fix result: Known issue and it maybe OS Limitation at current stage.
Note: 1. It can repro by some special configuration. Not all platforms. 2. After we checked the U-setup log; the log recorded DifxAPI had removed the device successfully, but it was not to be removed successfully, we still trying to find the root cause and report it to MS. It maybe MS DiFX API issues.
|
|
Issue: While hot plugging and re-plugging in the SATA hard disk from SATA RAID controller of VT8237A/VT8237R/VT8251/CX700/VX700, the file or the folder will be lost from FAT16/FAT32 partition.
Fix: known issue.
Note: RAID driver hotplug is used for replacing failed disk in a fault tolerance RAID array without reboot OS, and it has no notification mechanism for user to let OS and driver flush data in disk write cache, when the plug-out event occurs on FAT/FAT32 file system, it possiblely loses data
|
|
Issue: If inserting the VT6421 PCI RAID card on VT8237A/VT8237R/VT8251/VT3287/ICH7R platform and then installing Microsoft Windows 2K/XP/SRV03/x64 OS on VT6421 by txtsetup, the RAID controller's name will be something wrong in the 'NeroInfo' hardware monitor utility. A. For VT8237A/VT8237R/ICH7R platform: There will be two VIA VT6421 RAID Controllers.B. For VT8251 platform: There will be two VIA VT8251 AHCI RAID Controllers.
Fix: not a driver bug.
Note: It is not a driver bug, but a neroinfo bug.in neroinfo, it uses a name of all for controllers supported by same driver. If change driver name and install it to VT6421, it displays correctly. |
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 Microsoft Windows 98SE/ME. [Update RAID driver to be 5.20a will PASS]
Fix result: fixed
Fix method: fix a coding bug
|
|
Issue: Microsoft Windows 98/Me Copy&Compare issue.
Fix result: fixed
Fix method: fix a coding bug
|
|
Issue: After installing the Combo RAID driver V5.10A under Microsoft Windows 98SE/ME, the SATAPI devices are still not recognized in the My Computer and Device Manger.
Fix result: fixed
Fix method: fix a coding bug |
fix issues and changes
|
Issue: Not Support Raid5 functions and Raid0 migration on Microsoft Windows NT4
Fix result: fixed
Fix method: open these functions in raid tool |
|
Issue: In Microsoft Windows 98/Me on VT8251, Can not Copy&Compare
Fix result: fixed
Fix method: fix coding bug in RAID driver |
Version 5.20 formal release
fix issues and changes
|
Issue: when dynamic repair a broken RAID5, RAID TOOL show the newly plugged free disk as OS disk, and reboot fail after repair.
Fix result: fixed
Fix method: fix coding bug in RAID Utility
|
|
Issue: The word “Hardware” is spelt “Hareware”. When plug/Un-Plug SATA/SATAPI device, the RAID tool will pop-up the dialog “Hareware Hotplug”
Fix result: fixed
Fix method: fix coding bug in RAID Utility |
Version 5.20 Pre
fix issues and changes
|
Issue: Storage Data Verification Filter test item is failed at HCT12.101
Fix result: fixed
Fix method: fix coding bug in RAID Driver
|
|
Issue: Enable RAID5 migration function on Microsoft Windows 2000/XP or later OS
Fix result: add new feature
|
|
Issue: install Microsoft Windows NT4 through SATA ATAPI Cdrom on VT8237A fail
Fix result: fixed
Fix method: fix coding bug in RAID Driver
|
|
Issue: RAID TOOL show different version info in About Dialog Box
Fix result: fixed
Fix method: fix coding bug in RAID Utility
|
|
Issue: Microsoft Windows 98/ME, Windows NT4 can’t work on 3349
Fix result: fixed
Fix method: Add this feature |
Version 5.10a
fixed issues
|
Issue: For VT8237/VT6410/VT6421 RAID Chip: When the Windows OS is installed by txtsetup, the ACPI S4 can not be implemented.
Fix result: fixed
Fix method: fix coding bug in RAID Driver
|
|
|
Issue: The VT6410/VT6421 RAID chips are not supported the RAID 5 function, but it can be created by VIA RAID Tool.
Fix result: fixed
Fix method: fix coding bug in RAID Utility
|
|
|
Issue: Microsoft Windows x64 system, txtsetup, create partition, and RAID0 migration fail
Fix result: fixed
Fix Method: fix coding bug in RAID Driver
|
|
|
Issue: When the Microsoft 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.
Fix result: A known issue
|
|
|
Issue: Remove un-stable RAID 5 Migrate Function Button from RAID Utility.
Result: Add a new feature
|
|
|
Issue: Release Microsoft Windows 2000, Windows XP X32/X64, Windows Server 2003 X32/X64 WHQL Logo Drivers
Result: WHQL Logo certified driver package |
|
Version 4.40
fixed issues
|
Issue: Modify the version number, change inf to RAID sub class code (04)
Result: update sub class code |
Version 4.30 G
Fix setup problem
|
Issue: 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 Microsoft Windows NT4.0+SP6.
Fix result: fixed
Fix method: fix coding bug in RAID Utility
|
|
Issue: When removing the Combo RAID driver V4.31P1 by U-Setup/Control Panel/Silent, the system will hang at the driver removed dialog under Microsoft Windows XP+SP1 X64 and Windows SRV03+SP1 X64.
Fix result: fixed
Fix method: update U-Setup source code |
Version 4.30 F
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. |
Version 4.31 P1
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. |
Version 4.31
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 (317A2+227A9) and VT8288B1 (275A4+227A9). [Check VIA RAID Tool v4.06 à PASS] |
User authorization problem on Microsoft Windows 2000, Windows Server2003
Version 4.30 D
Update RaidTool to be 5.20
RaidTool 5.20 fixes
User authorization problem on Windows XP
Add sound effect
Version 4.30 C
Update U-Setup kernel to be 5.2.1.12
Version 4.30 B
Add Windows XP-x64 Logo
Fix:
Windows 2000 txtsetup BSOD problem
Windows XP/2000 Logo version
Version 4.30 P1
Fixed issues:
|
VIA VT6410 RAID chipset name is written VT6210 in the txtsetup.oem file. |
|
Readme file update with correct file name and driver disk operation |
Version 4.30
Fixed issues:
All OS, RAID 0 migration hang at 99%
AMD64 install pop up console window.
Serv2003 SP1 can not install.