Project

General

Profile

Actions

Emulator Issues #6377

closed

Memory Cards not being detected or created

Added by eoingmaloney almost 12 years ago.

Status:
Invalid
Priority:
Normal
Assignee:
-
% Done:

0%

Operating system:
N/A
Issue type:
Bug
Milestone:
Regression:
No
Relates to usability:
No
Relates to performance:
No
Easy:
No
Relates to maintainability:
No
Regression start:
Fixed in:

Description

Have you searched the issue tracker for a similar issue?

Yes.

Game Name?

No particualr game, just a general issue.

Game ID?

Again, no particular game.

What went wrong?

The program refuses to make new memory card files, even through the memory card manager, and will not recognize them when I attempt to use a game with a save function. When it tries to write to the memory card file, I instead get an error prompt which reads:

"Could not write memory card file ./User/GC/MemorycardA.USA.raw.

Are you running Dolphin from a CD/DVD, or is the save file maybe write-protected?"

I have made certain that it is not a write-protected file, and I am running it from a folder in my desktop.

What did you expect to happen?

I expected it to write a blasted save file.

What steps will reproduce the problem?

Open a rom, (in my case, the rom I ran was one for a United-States [NTSC] ISO of Pokemon XD: Gale of Darkness).

Get to a point where the rom notes you have no save data in memory slot A.

Allow it to write to the memory card.

Prompt will come up.

What version of Dolphin were you using (please test the latest version
from http://dolphin-emu.org/download first, 3.5 or 3.5-367 are not valid
tests!)?

Dolphin 3.5 1413, although this also occurred with base 3.5.

64 or 32 bit Dolphin?

x64.

What version of Dolphin used to work?

None that I have used.

What Operating System were you using and what are your hardware
specifications?

Windows 7, stock HP 2000-410US

64 or 32 bit Operating system?

x64

Actions #1

Updated by Billiard26 almost 12 years ago

  • Status changed from New to Invalid

Placing dolphin in a directory where you don't have write permissions is likely the cause.

Actions

Also available in: Atom PDF