John, I had similar problems with Win8 and the SSAG
(see this thread).
In my case the issue was the way Win8 was identifying the device and reporting an incorrect VID/PID.
I found that installing the SSAG on a USB2 port (luckily my laptop had one USB2 port) AND a clean OS install was the only way I could get the driver loaded, as once the device had been incorrectly identified, no amount of driver removal, inf file manipulation or registry massaging could fix the problem.