Agreed, this was something I meant to get feedback on options but forgot.

Option 1:
Panic alert about write access
(Change config setting?)
fall back to raw memcard
Potential panic alert from raw mc

Option 2:
Panic alert about write access
Work only in memory, save is gone when game is closed, unless save state
was made

2 is similar to what happens if raw access fails, and only 1 alert is needed

Thoughts?
 On May 22, 2014 5:13 AM, "Tony Wasserka" <notifications@github.com> wrote:

> In Source/Core/Core/HW/EXI_DeviceMemoryCard.cpp:
>
> >
> > -	pFile.WriteBytes(data->memcardContent, data->memcardSize);
> > +	if (!File::Exists(strDirectoryName)) // first use of memcard folder, migrate automatically
> > +	{
> > +		MigrateFromMemcardFile(strDirectoryName + DIR_SEP, card_index);
> > +	}
> > +	else if (!File::IsDirectory(strDirectoryName))
> > +	{
> > +		if (File::Rename(strDirectoryName, strDirectoryName + ".original"))
> > +		{
> > +			PanicAlertT("%s was not a directory, moved to *.original", strDirectoryName.c_str());
> > +			MigrateFromMemcardFile(strDirectoryName + DIR_SEP, card_index);
> > +		}
> > +		else // we tried but the user wants to crash
> > +		{
> > +			// TODO more user friendly abort
>
> Incorrect configuration should never be able to put the emulator into an
> unusable state. Would it be too complex to properly fail here, or to fall
> back to the behavior prior to this branch?
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/dolphin-emu/dolphin/pull/243/files#r12946446>
> .
>