|If you need a Windows WDM or WDF device driver I can develop it for you. Please
me for further details.
||SIV Unicode Release Kit for Windows XP and later systems. You should use
SIV64X.exe on 64-bit Windows x64 and
SIV32X.exe on 32-bit Windows x86.|
||32-bit SIV ASCII add-on that is needed for the legacy Windows 2000, NT4 and 9X systems.
||for Intel Enterprise Servers. Using SIV32X do Menu->File->Download->SIV64I add-on
to get the native SIV64I.exe.|
||for DEC Servers/Workstations. Using SIV32X do Menu->File->Download->SIV32A add-on
to get the native SIV32A.exe.|
||Doing Menu->File->Download->SIV Beta will download the latest SIV Beta.
The SIV Beta should not be mirrored as it changes frequently.||
|Note that siv.zip is always needed
as it contains the device description files, SIV kernel drivers and the SIV resource DLL.
The add-ons should be placed in the same folder as the files from siv.zip.||
|If you find SIV useful, please consider making a donation towards its development.
SIV is free for home use but if you wish to use it commercially then
for further information.|
|Version 5.06 released on 14-Dec-2015||
|Added support for UASPStor controlled USB Disks.|
|Added support for the ASUS Crossblade Ranger + P5B-E + X99-PRO and Gigabyte X99M motherboards.|
|Resolved [Link Fans] reporting issue of Fixed PWM for AXi + HXi + RMi PSUs. Change maximum fan speed to 9999.|
|Added reporting of REG_BINARY to [Link Devices]. Improved Corsair AirFlow reporting.|
|Corsair Link hardware reporting is available only when the Corsair Link program is not active as CorsairLink.exe does not use the
mutex to interlock access to the
Corsair Link hardware.
Corsair Link should have always have used a global mutex to interlock Corsair Link hardware access and as I have recently
signed an NDA with Corsair I am hoping this restriction can be removed from SIV.|
|If does not list your Corsair Link devices then check that they are
, listed on the [USB Bus] panel,
have no I/O errors, they are reported by Devices and Printers, are in the Device Manager HID (Human Interface Device) or USB (Universal Serial Bus)
sections and there are no errors (yellow triangles). Does a device come and go on unplug and re-plug the USB cable or SATA/Fan Header power connector?|
|If you wish to use SIV to fully control your CL hardware then you need to specify the
command line qualifier typically using a shortcut.
When -AIOCTL is specified SIV will if needed automatically do the EnhancedPowerManagementEnabled registry change
and restart the USB device. If you have any issues and need help then you need to provide screen images of the SIV Initial Screen,
[USB Bus], [Link Devices], [Link Status] and [Link Fans] panels.
Even if you are not using SIV to control your CL hardware you should post these screen
shots on the Corsair forum if you have CL issues and need help resolving them as they enable the root cause of many issues to be understood and resolved.|
|SIV stores the configured Corsair hardware settings such as custom cooling curves in the Windows registry and you can use
Menu->Machine->SIV Setup->SIV Setup 4 to view this. This configuration is setup in the hardware when you start SIV and specify -AIOCTL.
For the and
pressing [Reset] will update the panel
with this saved information and [Apply] will load the panel settings into the hardware.
Should you wish to set all the fans to maximum speed select PWM, set 255 and then press [Apply]. To restore the saved
setup press [Reset] then [Apply]. If either PWM or RPM as selected pressing [Save] is inappropriate, so it is greyed.|
|The Corsair Link reporting and control is only about 2% of SIV and finding the CL panels can be tricky for new users. They are all accessed by the Tools sub-menu
(Menu->Tools->Link ...) or via the [Status|▼] split button drop down menu. All the Corsair Link panels have buttons to directly access others.
When SIV does not find any CL hardware only the panel will be available.|
|On some systems, notably Windows 7 with nVidia chipsets and several RAID controllers,
the [SMART] panel may fail to report information. In many cases this issue can
be resolved by using the -SCSI command line option. When this option is selected all
requests to read the drive SMART information are routed via the SIV Kernel Driver which actions
them using IRP_MJ_SCSI requests (hence -SCSI). Note that -SCSI is sticky, so you only
need to specify it once and need to use -NOSCSI to stop the IRP_MJ_SCSI mode of operation.|
|On some Dell systems when no Temperatures, Fan Speeds or Voltages are displayed specifying the -DELL
command line option may resolve this. When this option is selected SIV will attempt to read this
information from the Dell BIOS. I use this option on my Dell 490 Workstation and Dell 1720 Laptop.
Note that -DELL is sticky, so you only need to specify it once and need to use -NODELL to
stop the Dell BIOS mode of operation.|
|In addition to the command line options the
(Menu->Tools->Configure->SIV Configuration) which can be used to set the -SCSI and -DELL modes of operation.|
|If programs are accessing the SMBus and either not using the locks at all or create them in the Local\
rather than the Global\ namespace the SMBus access will not work correctly. SIV detects
when the Local\ namespace is being used and will switch to using it which will work when
there is a single session. If there are multiple sessions then Global\ needs to be used.
The page displays the
namespace the locks are currently within;
shows SpeedFan 4.41 incorrectly
using Local\ and SIV having switched to also using Local\.
has been corrected
to use to use Global\ as should
Some SMBus drivers interlock SMBus operations using the INUSE_STS semaphore.
SIV also implements this regime as addition to using the Access_SMBUS.HTP.Method mutex.
If you have any additions, corrections or need guidance in implementing locking then
|By default all SMBus slave addresses are scanned (0x10 <= slave < 0x80).
If SIV detects as issue with accessing a slave device it will automatically add the address
to the exclusion list along with the previous device which is often the cause of the issue.
It is quite common for an access to slave 0x69 to lock the system, so this is by default excluded.
If there is an SMBus lock up you may need to re-boot to get the SMBus working again.
You can also use the
manually update slave address exclusions and/or update the SMBus Scan Range.|
|When SIV, on the
page, does not have a device description and you know what that chip is please
details so I can add it. If you have the datasheet for the chip please attach it.|
|Currently SIV supports almost all Intel, most Ali, ATI, nVidia, SiS, and VIA SMBus controllers. If you
have a system with an unsupported chipset, would like me to add support and are happy to test a
SIV Beta then e-mail me the SIV save files (Menu->File->Save Local) from your system.|
|If there is an issue with ACPI method evaluation (Menu->System->ACPI Eval)
then the command
siv -dbghal -save=[initial][acpi-hal][acpi-eval]=acpi.txt > acpi.log | more
should be used to find and then report the ACPI method causing the issue. The last line of
acpi.log will indicate the ACPI method that caused the issue.
When UAC is enabled STDOUT is not available so acpi.log may be empty and the
information will be in SIV_DBGOUT.log.|
|If you find an issue with SIV and wish to get it resolved then please e-mail the details along with the SIV save
files. In the event of an application failure please keep a copy of the memory dump file in case this is needed.
The memory dump is generated by either Windows Error Reporting (WER) on Windows 7/Vista/Server 2008
or by Dr Watson on earlier systems. Both of these will provide better information when the Symbol Tables
(.PDB files) are available, these will be e-mailed to you on request.|
|To configure WER to generate |
Local Dumps for SIV navigate to the
(Menu->Windows->Parameters->Error Reporting) panel and press the
[Set Mini Dump for SIVXXX.exe] button. You should repeat this each SIV add-on that is used.
Microsoft provide detailed information.
|To setup Dr Watson dumps navigate to the
(Menu->Windows->Parameters->Dr Watson) panel, if the Debugger is not
drwtsn32 -p %ld -e %ld -g press [Dr Watson -I] which will set this up, next press [Dr Watson]
which will pop up the Microsoft
panel which is used to configure the dump options and file locations.
Microsoft provide detailed information.
||Monitor ID definitions update program
||Monitor ID definitions
||PCI Device ID definitions update program
||PCI Device ID definitions
||PCMCIA ID definitions update program
||PCMCIA ID definitions
||PNP Device ID definitions update program
||PNP Device ID definitions
||USB Device ID definitions update program
||USB Device ID definitions