Some memory card issues

[Belqua]

Im getting a message saying the device inserted in slot a is not a memory card. Any way to fix it?

[LPFaint99]

check <dolphin folder>/user/gc/MemoryCardA.<region>.raw it may be damaged.
if the filesize is 0, your memorycard is unfortunately lost, delete it.
if filesize is greater than zero, move the memorycard and dolphin will create a new one, upload the old one and i'll see if any of it is salvageable

[Belqua]

Well, the filesize was 0 so i deleted it. I really dont want to lose all my saved games again.

Is there anything i can do to prevent this from happening again?

[DefenderX]

Just use the latest git version of Dolphin.

[Belqua]

Okay, ill make sure to do so.

But im already using the latest version. It says version 3.0589 dirty.

Why is it called dirty?

[Shonumi]

Dirty versions are basically unofficial builds. Usually people like DefenderX or Lectrode compile their own builds optimized for certain instruction sets. Any time users change something in the source, and they compile it, the result is a "dirty" build. Technically, my current build is "dirty" because I compiled it myself with some optimizations.

[AnyOldName3]

But recently even MaMario's compiler bot has been calling its builds dirty, and they're the ones on the download page.

And actually anything made by anything not the compiler bot should be labelled dirty, even if it's the same source code and compiler as MaMario's.

[Shonumi]

(04-11-2012, 01:28 AM)AnyOldName3 Wrote: But recently even MaMario's compiler bot has been calling its builds dirty, and they're the ones on the download page.

And actually anything made by anything not the compiler bot should be labelled dirty, even if it's the same source code and compiler as MaMario's.

Maybe MaMario's been messing with something. I'm not on Windows for Dolphin playing, so I get mine straight from Git.

But I'm not so sure about that last statement. I've pulled from Git and built Dolphin myself with no optimizations before, pure source code, and it never indicated that my build was dirty. Once I started adding optimizations (really just changed one line in a CMakeList file) then I started getting dirty builds.

[AnyOldName3]

It's supposed to, though, although it doesn't.

[Shonumi]

(04-11-2012, 01:49 AM)AnyOldName3 Wrote: It's supposed to, though, although it doesn't.

I'm not completely convinced. I'm pretty sure the CMakeList.txt file tell CMake to see if any local changes have been made to any files. If so, the build's dirty. if not, nothing gets added to the revision name. Though I'm no expert on CMake.

(03-22-2012, 03:18 AM)neobrain Wrote: dirty = the person who created the built made some local changes to the upstream source code.

That jives with what I've been getting; whenever I make a change, dirty build. Whenever I just leave it alone, just a plain old regular build. That doesn't make sense to have every compiled version labeled dirty, regardless if the source is not altered, because most Linux users often compile Dolphin by hand anyway. In the past, I'm not sure MaMario's bot did anything special to not generate dirty builds. As of late though, there's something up with his bot, apparently.