Ooh, doesn't seem to work that way at all. I'll rewire and post up.
Updated FuseGL (again, it is 2011-05-20b now).
This will not flash the digital outputs within FuseGL. Still flashed with Virtual COM, but it is a logic problem. It is not "flashing" it is going at a really really really slow PWM mode. The new firmware updates the PWM speed. Now it will be 'dim' but not flash.
Also D:xx:1 command will now make it dim (i.e. 1/255 PWM cycle).
To turn on, you will have to do D:xx:255. Problem is the firmware doesn't know what "255" is, so I just need to write some code to take the ASCII value and make it an integer value. I will do that tomorrow. I remember I did that in first year uni. What do you know, I will actually have to use something I learned!
Alright, I need to get to bed. I do have a 9-5 as well. :)
No more blinky! Thanks! I try D:00:10 and D:00:100 and they have the same result. Is that what you meant? D:00:200-255 doesn't work too.
Update 20-05-2011 #3:
Fixed a bug with legacy systems not liking the Vista/7 system icons used and sometimes preventing the application from starting
New link available in the first post
I don't know why the other thread was locked, sonicx if you are reading in here. The FB uses the following drivers, you should be able to delete them all and reinstall. \DRIVERS\usbser.sys <- is a windows one, should be fine. \DRIVERS\winusb.sys another windows one i think, then wdfcoinstaller01009.dll, winusbcoinstaller2.dll, wudfupdate_01009.dll. Those numbers may be different if you didn't install the latest drivers.
2k are there any more?
The drivers are actually just the WinUSB drivers from Microsoft, and then the inf file just says, "hey I am one of those". The way I uninstall is plug in the device, look in device manager, right click and uninstall. Select the "uninstall drivers" box. Then unplug and replug. Keep doing this until windows can no longer automatically install drivers for your new device.