Windows 7/XP USB driver issue

I've just started using the MakingThings microcontroller kit v2.0.  I've followed all the steps to let Windows recognize the device.  The first time the microcontroller kit (v2.0) was plugged into a Windows 7 and XP Home computer, I installed the usb drivers provided on the Download section.  This worked; the computer recognized the board and mchelper and mcbuilder both were able to communicate with it.

But, after looking through this forum if anyone had the same issue, I could not find a solution for this:

On the Win7 computer, clicking Erase board in mchelper would show Erasing board in the log window, and show No Make Controller found.  Windows would see that a "new device" is plugged in and if I let it... search Windows Update to install a GPS camera driver or something for it (ugh).  Even when I would stop Windows' stupidity, trying to reinstall the usb drivers (that I used the first time) would only get me to messages telling me that Windows knows better and has a driver better than the one I'm trying to install.  It will not let me install these drivers.  Unplugging it and replugging it, would recognize the device again and mchelper would be back where it started (with the firmware still on there and functional).

On the WinXP computer, installing the usb drivers for the first time also let the os, mchelper and mcbuilder recognize the controller.  Erasing board brought the controller offline and Windows saw the "new device" again.  And the same problem with trying to install the same usb drivers occured.  Only this time, replugging it into the USB did not let me recognize the board on either computer (seems that it actually erased it, which leaves me in a worse situation).

Any help would be appreciated as this is for a project with short deadlines.  Thank you.

Same issue.  New board arrived in the mail, plugged in the usb.  I got both red and the blinking green light.

MCBuilder and MCHelper could see it.

Both OSC terminals seemed to allow commands to be sent but the make controller was not responding. (Activity window in mchelper and USBConsole window in MCBuilder)

I tried to Build and Upload the BLINK example project.

Build Succeeded.  But upload claimed the device was not Unprogrammed.

Tried Reset Device... Nothing

Tried Erase Device... Nothing

Unplug usb, Plug in USB

"No Make Controllers found..."

Went to device manager

Sure enough under Ports I find "GPS Camera Detect (COM1)"

Right click    "Update driver"

"Browse my computer"

"Let me pick from a list of device drivers on my computer"

"Have Disk"

"Browse"

Found the "make_controller_kit.inf" I downloaded from http://www.makingthings.com/resources/downloads

"ok"

in the list was "atm6124.Sys ATMEL AT91xxxxx Test Board"

"next" "Install this driver software anyway"

"Windows successfully updated your driver"

MCHelper now says " Unprogrammed Board"

Right clicked, "Upload New Firmware"  "heavy20-1.6.2.bin" from the link above

Message says "Upload Complete from Uploader"

name of device changed to "Make Controller Kit : USB (COM1)"

typed   /

hit send

got back

14:52:26 / appled from USB (COM1)
14:52:26 / dipswitch from USB (COM1)

14:52:26 / servo from USB (COM1)

14:52:26 / analogin from USB (COM1)

14:52:26 / digitalout from USB (COM1)

14:52:26 / digitalin from USB (COM1)

14:52:26 / motor from USB (COM1)

14:52:26 / pwmout from USB (COM1)

14:52:26 / led from USB (COM1)

14:52:26 / debug from USB (COM1)

14:52:26 / system from USB (COM1)

14:52:26 / network from USB (COM1)

14:52:26 / serial from USB (COM1)

14:52:26 / io from USB (COM1)

14:52:26 / stepper from USB (COM1)

14:52:26 / xbee from USB (COM1)

14:52:26 / xbeeconfig from USB (COM1)

14:52:26 / webserver from USB (COM1)

and

/appled/0/state 1

/appled/2/state 1

/appled/3/state 1

/appled/4/state 1

turned on all 4 of my LEDs (though in an unexpected order (0 is LED 1) (1 is LED 2) (2 is LED 4) (3 is LED 3) go figure)

OK,

Erased board

worked, "Un programmed Board" again, went to McBuilder

Opened the Example Program "Blink"

Modified loop a bit to make an SOS signal (so I would know It was really my program running)

Built "Blink"

uploaded blink

Unplugged board from USB and plugged it into 12V

I got a green Blinking Light SOS!!

Plugged it back in to windows, Device not Recognized...  MCHelper "No Make Controllers found..."

Go to devices, find "Unknown Device"

so Same as before, specify Driver Browse.. ..Have disk.. ..atmtestboard.. , get the message

"Update Driver Warning"

"Installing this device driver is not recommended because Windows cannot verify that it is compatible with your hardware.  If the driver is not compatible, your hardware will not work correctly and your computer might become unstable or stop working completely. Do you want to install this driver?"

I thought about it while my make controller blinked SOS at me...

Clicked YES

"Installing Driver"

Blue Screen of Death

Computer restarts.

Same thing if I restart first.

Have to wipe using the "Short the Holes" method

Tada, Unprogrammed Board on (COM 1)

SO

WHY DOES THE INTERFACE DRIVER BSoD WINDOWS 7 AFTER UPLOADING A PROGRAM?

At least I can work around this.