You probably can tell if its Fusion that is messing up by using the Somewhere on the Keyspan site as using the same driver. I do see one difference, in that my Keyspan device is listed as a I did indeed download ver3.7sįrom the Keyspan website earlier today, dated Dec 12, 2007.

Sorry for the confusion above - at this point I am just feeling luck to have hit a combo that works. It got very confusing along the way, as the system seemed to need WinXP restarts often along the way, and on occasion that 'Connected' checkbox was unchecked. For me the Keyspan port was then assigned to com5, and I reassigned it to com1 as above, as well as switching to the bulk mode on the aforementioned Advanced tab.Įven then, the Adapter did not come up on reboot - I found that I had to click on the Settings Tab at the top of the Fusion WinXP window, then click on the Keyspan unit in the left-hand pane of USB devices, and then click on the 'Connected' box in the right pane. Then I found a tab in the Windows Keyspan Serial Assistant that allowed removing all Keyspan entries in the registry, uninstalled the Keyspan driver, and reinstalled it. I also reassigned com2 to com4, but I suspect that is not necessary. I had to go into the XP ControlPanel-System-Hardware-DeviceManager-Ports window, and reassign com1 to become com3 on the port's Properties-PortSettings-Advanced tab. It seems that WinXPsp2 on Fusion 1.1 defaults to setting up com1 and com2 as ports on some generic bus, which do not seem to correspond to any real physical port. The bulk mode was the last step needed to get my Keyspan port working.įor me the problem was that the Keyspan windows drivers (ver37s) installed the Keyspan port at the next highest com port, above the previous highest one.

Keyspan 19hs usb 2 serial xp driver