I was having intermittent and incredibly annoying problems where, just as I was starting to get my SG-4 autoguider working programs start freezing. Using the SBIG SG-4 Interface software I could setup, test, expose, calibrate and (for awhile) track fine. Then out of the blue almost everything would work but if I tried "Start Autoguiding" the program would just freeze and become nonresponsive. I chalked it up to perhaps some flakiness of the software on my hardware setup. I then got the guider working in MaximDL through the ASCOM driver, everything was working (though the guiding seemed to be jumping too much) and after I tried hitting "stop tracking" all of MaximDL froze (I'm running 5.12 currently). Then I simply couldn't connect to the autoguider via either MaximDL or the interface software. When I tried connecting to the guider via interface software, I got a suspicious debug log(attached) that suggests windows really doesn't want to open COM5 where the guider is on. Resetting the computer seemed to allow me to connect again. I am going to try attributing this behavior to the serial to USB convertor, I'll pick up a FTDI US232R-10-BLK as the manual suggests; but I thought I'd ask if the driver devs have any insight or magic switches to help me solve my quite fragile interface to the SG-4 autoguider. I don't seem to see any firmware that I need to download if that is the cause.