I agree, but I'm not an expert of things and like we say in Dutch: "van 't kastje naar de muur". Litteraly: "from the cupboard to the wall" but loosly translated being bounced around.
So perhaps you could reply on that issue, or take some other actions? If you need me to test anything, you know how to contact me

The hang on deployment and the following BSOD on disconnect or reset is driving me crazy; makes serious development an absolute pain. It's happening to me on about 50% of deployments. Is there any known workaround? Is the 4.1 driver better than the 4.2? Is it happening only to a few people or everybody? Only 4 votes on codeplex. I'm using Win7 64bit and VS2010 Pro.

Edward

We build the tuning down of buffer sizes into the v4.1.0.0 firmware, and it's now included in the v4.2 firmware as well.

What is the FAT file access count memory issue? If that has been changed in the 4.2 codebase, it's included as well.

The GC bugfixes are included for sure.

We'll be posting v4.2 beta 2 later this weekend, now with "WithEvents" support for VB programmers.

Chris

Not FAT file access count - in a previous thread (that I can't now find) relating to out of memory issues you'd said you were going to reduce both the number and size of buffers allocated by the FAT file system. You also said in that thread you were going to change the wording of the GC message "Failed to allocate..." to clarify that it was a compaction trigger rather than an out of memory situation. The old wording remains so I wondered if the memory tuning got done and whether all this is in 4.2.

Thanks for clearsing this up.

Edward

My 2GB SD cards arrived but only hours before going on vacation. A quick test suggested that they do >not< exhibit the access problems described abover for the 128MB card. One question; clarification about what is in and what in not included in the 4.2 B1 release - is the tuning down of buffer sizes and counts for SD card FAT file access to alleviate memory allocation problems included in this firmware?

Thanks all for the various helpful suggestions but no change for any of them. I'm awaiting delivery of some 2GB cards to compare results against. Will update again as soon as I get my hands on them.

The code is:

using System;
using System.IO;
using System.Net;
using System.Net.Sockets;
using System.Threading;
using Microsoft.SPOT;
using Microsoft.SPOT.IO;
using Microsoft.SPOT.Hardware;
using SecretLabs.NETMF.Hardware;
using SecretLabs.NETMF.Hardware.NetduinoPlus;
using SecretLabs.NETMF.IO;

namespace SD_Card_test
{
    public class Program
    {
        public static void Main()
        {
           var fs= Directory.GetFiles(@"SD");
        }

    }
}

and the exception is:
A first chance exception of type 'System.NotSupportedException' occurred in Microsoft.SPOT.IO.dll
An unhandled exception of type 'System.NotSupportedException' occurred in Microsoft.SPOT.IO.dll

By the way, remember, beta software can always contain a few flaws, it's a risk using Beta firmware.
appairently you found a flaw

yup - trying to help find them and fix them!

Spoke to soon. The problem seems to be a power cycling one. If the netduino is powered up with the card in the slot then the exception is thrown. If I take the card out and re-insert it with the power kept on then the progtam will run. So is the problem that the card isn't being mounted at power on only on insertion?

I reinstlled everything, reflashed everything and reformatted the card. And all is working fine now. Thanks for taking the time to run those tests it gave me the confidence to give 4.2 another try. Hopefully my next feedback will be more worthwhile!

Thanks for trying to replicate. I'll install the firmware here again and retry.. Card is a 128MB SanDisk (dug out from the back of a dusty drawer, came with an old phone) Formatted as FAT32/2048 by Win7 - files were written by Win7. Path \\SD\www.

I tried the v4.2 firmware briefly. Had big problems working with SD card (256MB) on the Plus. Seemed like it would only work with files in the root directory. Trying to access anything in a sub-directory (eg, GetFiles) would throw a NotSupported exception. Same code working fine in the 4.1 beta so rolled back to that for now.

Kudos to KodeDaemon for doubling the available RAM on the plus. And it made me wonder, RAM feels like it's the main constraint on the NetDuino platform, is there any way of expanding it? I know RAM almost always ends up being a key constraint on embeded devices - and for me that's part of the fun - but is the on-chip stuff (512K) a hard limit? I know you can get little-bitty (8K) SPI chips but I'm thinking of an extra 512K; preferably at the full speed of the on-chip RAM. A possible future Netduino variant? Edward