1 reply to this topic

[Jon Henry]

I moved to 4.3.0.0. Now, everytime I write  a program to the N+2 from VS2012, after rebooting the N+2, it reinstalls its driver as a 'Microsoft serial ballpoint'. And yes, the cursor then starts doing random things on my screen.

 

Anyone else experiece this?

 

UPDATE: And now Ive gone back to 4.2.2.2 and am unable to communicate with my device. It shows up i the build properties as it should. Disconnecting and reconnecting 10 times per programming attempt (as was normal with my previous boards) doesnt seem to do the job either. All my references are correctly back to 4.2.

 

LAST UPDATE: I successfully went back to 4.2.2.2 and still havent been able to connect. I run MFDeploy, select USB and the netduino shows up as it should. Go to Target>Device Capabilities and all I get is 'Not Supported' in the text window. Boxing up and shipping back tomorrow.

[ziggurat29]

sorry for your troubles, nothing more frustrating than not being able to communicate with the device

 

apparently this serial ballpoint mouse mis-enumeration is a common thing irrespective of netduino, as there's a bunch of complaints found when I google on 'microsoft serial ballpoint'

 

In this page:

http://answers.micro...3c-5754f06ec3b5

 

about halfway down, a post from Rawleigh on Jan 29 2011 who claims he resolved with some registry tweak (which he got in turn from somewhere else, so you can probably do some google diligence and find even more info).