#ATMEL USB INSTALLER INSTALL#

Thanks to a very helpful AVRFreaks member however, I now have FLIP up and running, via his own custom signed drivers. I realise why signing is important - but really Microsoft, is *requiring* signing really the only option? Under 32bit versions you only get a warning which you can dismiss, but under 64bit you either boot into вЂњTest ModeвЂќ (which results in an ugly banner on the desktop), or you, well, complain about it. Nevertheless, I persevere and point it manually to the correct location вЂ“ only to have Windows barf on it because itвЂ™s not signed. Of course, the Jungo driver fails to install. Not happy.ДЄs a backup, I thought IвЂ™d use FLIP and test out some problematic code on one of MattвЂ™s great Micropendous boards. Subsequent attempts either resulted in AVRStudio not detecting it, or more bluescreens.

#ATMEL USB INSTALLER INSTALL#

After manually fixing up the driver installation (automated install doesnвЂ™t work under 64bit Windows) I managed to get it working in AVRStudio briefly, before it caused my machine to bluescreen. Case in point my beloved JTAG-MKII, with itвЂ™s cruddy Jungo drivers.

Granted, the present situation is much better than it used to be, but it only takes the one or two вЂњgotchasвЂќ to turn a good experience sour. This is because the MSDNAA licensing only allows one license of each product to each user, although products are usually split up by their 32bit or 64bit versions.ДЄ week later and IвЂ™m beginning to see why everyoneвЂ™s so wary of 64bit. Yay, free software! So I could install it on both my main laptop and my netbook, I decided to install the 64bit version on the larger laptop, leaving the 32bit version for the tiny Atom powered netbook.

A week or two ago, I decided to replace my main laptopвЂ™s aging Vista installation with Windows 7, via my UniversityвЂ™s MSDAA subscription.

Atmel usb installer