@ Gus
I’ve tried formatting with FAT and FAT32, neither seem to work. I’m using a 2gig card.
Update
Everything seems to work fine if I use the System.IO methods (Directory.GetFiles, FileStream.Write, etc).
This is more than enough to start working with 
There is no “left” and “right”. The motor terminals are numbered 1 and 2.
Does it work fine with non-ethernet firmware?
No none of the two firmwares work for me…
Do the update manually then please. http://wiki.tinyclr.com/index.php?title=Firmware_Update_FEZ_Hydra
I also tried that and this also failed with erasing the first address of the ER_ files.
Do you see COM port under device manager once you place hydra in samba mode?
Yes I have the com port, everything works till deploying with MFDeploy.exe
dos worked I get the log file that everthing was ok and that I need to reset the device
MFDeploy screenshot
How are you powering your device?
Can you ping the device multiple times?
I use the DP unit with external power.
Do you mean pinging just before deploying in mfdeploy?
Yes before. Also, have you tried a different pc?
I just tried pinging a few times, first time I got NoConnection
All other I got:
Pinging... TinyBooter
Bootloader build info: Copyright (C) GHI Electronics, LLC
I’ll try another pc in a few minutes. (But the official release didn’t gave me these problems)
Very strang but after installing VS2010 express, NETMF4.1 and beta files on my other laptop.
The ping is instantly and the deploy went smoothly with MFDeploy.exe.
But I don’t understand that I was able to update the firmware yesterday with my laptop and now the new version I didn’t manage to deploy. Do you have any ideas --> I have a laptop with 12Gb of Rams and i7 quad core.
Please list the specs of both machines and tell us which one is not working.
also is VMware installed?
Failing laptop:
Windows 7 Pro x64
12GB ram
i7 q820
+vmware
Working laptop:
Windows Vista Business
same installation of NETMF from the downloads section of tinyclr.com
VMWare is installed → but I disabled the VMware USB Arbitration Service
I also noticed that with the beta version my visual studio project cannot deploy to the working device anymore
I just tried another USB port that is not USB3 and now the MFDeploy.exe is pinging back very fast and VS project does work again. I still don’t understand why it was working previously before beta dough
you could try rebooting and see if the failing USB port starts working again.