![]() ![]() ![]() After messing with it, changing settings and such for 3 days solid, I was fed up, and tried using the Keyspan on a native XP machine, and everything is fine. ![]() HOWEVER, when I try to interface with the actual hardware, I get no response. I can run the tests in Fusion, and the unit passes. If I use the KSA in Fusion/XP, the Keyspan is available. So, I plug in the Keyspan, go up to the Fusion menu item to connect to the Keyspan, and it SEEMS to work, in the sense that if I use the Keyspan Serial Assistant in OSX, the Keyspan is no longer available. It doesn't seem that I need SerialClient anymore, as when I try to start SerialClient, the 'connect' button stays as 'connect' when I click it instead of changing to 'disconnect' which would show that it was connected and running. It took me a while to get it going, and it was really picky about the order in which I started things up, BUT it worked.įast forward to the present day, with Fusion. ![]() In OSX, I used a little ditty named 'SerialClient' that, I guess, forced OSX to connect the Keyspan to /tmp/serial so that XP could use it. In XP, it was set up so that the 'serial' port of XP would connect to a file (/tmp/serial). When I connected the Keyspan, OSX would recognize it and take control of it. Now, when I used Parallels, I would load the Keyspan drivers in OSX and in XP. Access is no problem, BUT the hardware I must interface with is a serially connected piece, so I purchased a Keyspan USA-19HS USB-Serial converter. I really only need XP for two things: 1) Access and 2) a proprietary program made for some hardware at work. I recently switched to Fusion from Parallels after getting sick of Parallels' high CPU usage and sluggish performance (how can those two things co-exist?). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |