pmcclory

I've got a Windows 8 x64 machine (HP Envy 3040nr) and when running the DfuSe Demo (v3.0.3) to upload the dfu file to my Netduino Go and the app crashes when running the 'verify' step--Running without this is obviously not the ideal, but without fail--even when run via the 'Verify' button, the app crashes with the following error (Windows event log):

Faulting application name: DfuSeDemo.exe, version: 3.0.3.0, time stamp: 0x4ecd2975Faulting module name: STDFUPRT.dll, version: 3.0.1.0, time stamp: 0x4ecd296eException code: 0xc0000005Fault offset: 0x0001075aFaulting process id: 0x1da8Faulting application start time: 0x01ce4b238beb0fd0Faulting application path: C:Program Files (x86)STMicroelectronicsSoftwareDfuSeBINDfuSeDemo.exeFaulting module path: C:Program Files (x86)STMicroelectronicsSoftwareDfuSeBINSTDFUPRT.dllReport Id: e51717de-b716-11e2-be7c-88532ed523c9Faulting package full name:Faulting package-relative application ID:

Using the .net Micro Framework Deployment Tool, I'm able to get back the proper values for versions on the device:

HalSystemInfo.halVersion:			   4.2.0.0HalSystemInfo.halVendorInfo:		    Netduino Go (v4.2.1.0) by Secret Labs LLCHalSystemInfo.oemCode:				  34HalSystemInfo.modelCode:			    177HalSystemInfo.skuCode:				  4099HalSystemInfo.moduleSerialNumber:	   00000000000000000000000000000000HalSystemInfo.systemSerialNumber:	   0000000000000000ClrInfo.clrVersion:					 4.2.0.0ClrInfo.clrVendorInfo:				  Netduino Go (v4.2.1.0) by Secret Labs LLCClrInfo.targetFrameworkVersion:		 4.2.0.0SolutionReleaseInfo.solutionVersion:    4.2.1.0SolutionReleaseInfo.solutionVendorInfo: Netduino Go (v4.2.1.0) by Secret Labs LLCSoftwareVersion.BuildDate:			  Nov  7 2012SoftwareVersion.CompilerVersion:	    410894FloatingPoint:						  TrueSourceLevelDebugging:				   TrueThreadCreateEx:						 TrueLCD.Width:							  0LCD.Height:							 0LCD.BitsPerPixel:					   0AppDomains:							 TrueExceptionFilters:					   TrueIncrementalDeployment:				  TrueSoftReboot:							 TrueProfiling:							  FalseProfilingAllocations:				   FalseProfilingCalls:						 FalseIsUnknown:							  False

I think this is ok, but I'd love it if someone could confirm for me.  Thanks!