Version 1.09.23 ---------------------------------------------------- 1. release.txt updated Version 1.09.22 ---------------------------------------------------- 1. MP systems are identified by a registry key. Treat them the same as IOAPIC systems. Version 1.09.19 ---------------------------------------------------- 1. Check if it is a CardBus card before scheduling DPC Version 1.09.18 ---------------------------------------------------- 1. Do not mark all devices as REMOVABLE in the MPD. This was done to fix an issue seen with some of the cards where, when checked the "Removable" box in device manager the system gives a bluescreen if the device is removed while copying. This was done in version 1.09.15. But some how we lost it. Redoing it here again. Version 1.09.17 ---------------------------------------------------- 1. Program bit 0x2 in register 0xA2 for ricoh controller if HKEY_LOCAL_MACHINE\\SOFTWARE\\Softex\\WinRoute\\R5C478IIFIX" is set to 1. Version 1.09.15 ---------------------------------------------------- 1. Do not mark all devices as REMOVABLE in the MPD. This was done to fix an issue seen with some of the cards where, when checked the "Removable" box in device manager the system gives a bluescreen if the device is removed while copying. Version 1.09.14 ---------------------------------------------------- 1. Fixed the IOAPIC boot problem. Interrupt is now set to Masked by default. 2. We now check the subsysID and revId of the controller to determine if it's a new one. 3. Under TI controllers, we reset reg 0c90 only for the ATA cards and not for the other cards. This fixes the WLAN issue and the Toshiba ATA card issue. 4. Modified the logic of interrupt detection for TI controllers in the W2K driver. The IREQ bit in PCI REG 0x91 was not a correct indicator of the cards functional interrupt (as is the case with the CINT bit in SOCKET_PRESENT_STATE). So we had to use a peculiar combination of checks for these two bits to detect the card interrupt. Version 1.09.13 ---------------------------------------------------- 1. Modifed the logic of scheduling the DPC in the W2K driver. For ATAs we will re-schedule the DPC even though it is already been done. Where as for all other card types the DPC is scheduled only the first time. Version 1.09.12 ---------------------------------------------------- 1. Mark all devices as REMOVABLE in the MPD. This was done to fix an issue seen with some of the cards where, unless we check the "Removable" box in device manager the system will not assign a drive letter. 2. Fixed the scheduling of DPCs. They will not be scheduled on every interrupt but only in those cases where the DPC is not scheduled before. Version 1.09.11 ---------------------------------------------------- 1. Added code in Win2K driver to parse the LocationInformation registry entry so that it will be language independent. Version 1.09.10 ---------------------------------------------------- 1. Raising and lowering IRQ before and after accessing PCI registers. 2. Inside OnInterrupt routine: - Issuing a DPC now only we find our controller. - returns TRUE only when we issue a DPC and in all other cases, we return FALSE. Version 1.09.09 ---------------------------------------------------- 1. Added IOAPIC support. There are still some problems booting up with a Ricoh controller on Win2K Version 1.09.08 ---------------------------------------------------- 1. Check the registry to see if the driver for the PCMCIA controller is installed. If not, do not connect to the PCI interrupts and show a message to the user. Version 1.09.07 ---------------------------------------------------- 1. Restore cf8h on every PCI access in our driver. This fixes the ATA card file-playing hang problem. Version 1.09.06 ---------------------------------------------------- 1. Added a check in the APP before replacing the PortDriver with our MPD. We will do this only if the card is using ESDI_506.PDR. 2. INQUIRY cmd in the MPD should be sent to the master device only and not to slave. Infact any command coming for slave should be sent back with an error. There may be ATA cards that respond as slaves also. This fixed the issue where some cards take a long time to configure or blue screen. Version 1.09.05 ---------------------------------------------------- 1. Fixed the issue when two cards are inserterd at same time the machine will generate spurious int and hang. To bypass the generation of spurious interrup we where disabeling them thru 4d0/4d1.This will work if you insert one card at a time,the interrupt is generated when we issue ide cmd before we install interrupt handler.So the fix is don't issue any ide command until we install the interrupt handler. Version 1.09.04 ---------------------------------------------------- 1. win9x/mpd/driver.c ->FindDevices(). some ata cards generate int when we send them any command like inquiry, even though we told them not to generate interrupt's. Since we are not yet hooked to catch them system trap's. We could solve the problem by setting bit 7 of 0x3e register of parent (pcmcia controller) to 1 and at the end of this function reset it. But at this point we don't know who the parent is and in which slot the cards is in. so to solve this problem we put this hack in place.disable the interrupt in 4d0/4d1 here and re-enable it at the end of the function. //RC:12/16/2001. Version 1.09.03 ---------------------------------------------------- 1. In the timer, if the card is unconfigured, set BridgeControl to PCI. Version 1.09.01 ---------------------------------------------------- 1. Added loop in DPC to fix ATA cards MPEG2 problems. Version 1.09.00 ---------------------------------------------------- 1. Added DPC to forward interrupts. 2. Inside the DPC, check if the ISA interrupt is masked. If so, the timer will keep checking the PIC until it is unmasked and forward the interrupt. 3. Clear ATA status before scheduling DPC. Since the card driver is not clearing it sometimes. Version 1.08.01 ---------------------------------------------------- 1. Using the timer to forward interrupts. 2. Clear ATA status before forwarding. 3. Support both TI and Ricoh controller 4. Check Socket Present State for Ricoh, check reg 0x92 for TI Version 1.08.00 ---------------------------------------------------- 1. Load baymgr.mpd for Win98/ME. 2. Chnage the registry for all ATA card to use baymgr.mpd Version 1.07.00 ---------------------------------------------------- 1. Added WinRoute service on Win2K to fix the log-on box shutdown problem. 2. Fixed the wake-up hang with PC cards present by returning TRUE even if the interrupts are not from our cards. Version 1.06.00 ---------------------------------------------------- 1. In the interrupt handler, it will check whether the controller is enabled before proceeding. 2. Fixed the 3COM 3c589C hang. 3. WinRoute release version sent to Allied Telesis. 4. This WinRoute hooks itself to enabled controllers only. Version 1.04.00 ---------------------------------------------------- 1. Stop timer for ResetBridgeConrol when a shutdown notice is received. Version 1.03.00 ---------------------------------------------------- 1. Setup bitmap is changed 2. Program PCI Command register 4 periodically. Can be enabled/disabled by the registry entry HKLM\Software\Softex\Winroute\SetCommandRegister 3. SetCommandRegister and SetDevicePowerState added in the setup.lst file 4. Setup will add "MF" key for Win98. 5. CardBus PCI Command register need to be programmed manually.Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.