Memory Card Error

[AllApologies96]

Whenever I start up a game, no matter what it is, I always get an error that says

failed to open Eeprom/flashram/etc.

depending on the settings. Every different one of those gets the error and it's preventing me from saving anything.

How can i fix this?

 

[snesmaster40]

It means PJ64 is still running in the background.

Bring up the task manager (press Alt+Ctrl+Del), then click on "Processes", locate Project64.exe, and "end task" it.

 

[Smiff]

"no matter what it is"? zombie pj shouldn't lock all native saves?
hmm check file permissions aswell, mustn't be read only.

 

[AllApologies96]

"no matter what it is"? zombie pj shouldn't lock all native saves?
hmm check file permissions aswell, mustn't be read only.

By no matter what it is i meant no matter what the game is. Which files are we talking about exactly?

It means PJ64 is still running in the background.

Bring up the task manager (press Alt+Ctrl+Del), then click on "Processes", locate Project64.exe, and "end task" it.

I tired that and all it did was close PJ64. There was only one instance of it running.

 

[WhiteX]

I got that when using rage plugin i did not configured the mempaks correctly, try going to your plugin config and see if you got that configured.

 

[Smiff]

Which files are we talking about exactly?

the save files.. reboot your PC and check PJ (or logged on user) has write access to the save files. this could be simply readonly attribute or NTFS permissions.

 

[AllApologies96]

I got that when using rage plugin i did not configured the mempaks correctly, try going to your plugin config and see if you got that configured.

The only input plugin I have where you can choose if you have a memory card or not is Jabo's DirectInput7 1.6 and thats whats giving me the trouble. I do know that using that you can go to Options --> Settings --> and on the Rom Settings tab you're able to tweak the type of save (flashram, eeprom etc.) but I have no idea what any of it means so I can't do it. If thats what you mean, could you provide more information about changing it?

 

[AllApologies96]

the save files.. reboot your PC and check PJ (or logged on user) has write access to the save files. this could be simply readonly attribute or NTFS permissions.

No you don't understand, I can't even make a save state or file because of this. The moment I boot up the Rom an error message saying "Failed to open [insert save type here]" (save type meaning flashram, eeprom etc.) so it prevents all types of saving. If you mean and actual file in the PJ64 directories, which folder and/or files?

 

[Allnatural]

If you mean and actual file in the PJ64 directories, which folder and/or files?

The 'Save' directory, obviously. Can't create or write to save files in a protected directory.

 

[q_armando]

Actually you should check on the controller plugin settings that the memory pack is enabled.
You see on the real N64 the memory pack has to be inserted in the controller, then if you want to use a rumble pack you have to manually switch them.
Obviously on the emulated hardware you can't do that phisically, but under the Options->Configure Controller Plug-in you have to check the box on " controller plugged in " and then select from the pull down menu on its right where it usually says " none " to " memory pack".
Then you will be allowed to save. That is of course if you are using Jabo's direct input plug-in.

 

[Allnatural]

Actually you should check on the controller plugin settings that the memory pack is enabled.
You see on the real N64 the memory pack has to be inserted in the controller, then if you want to use a rumble pack you have to manually switch them.
Obviously on the emulated hardware you can't do that phisically, but under the Options->Configure Controller Plug-in you have to check the box on " controller plugged in " and then select from the pull down menu on its right where it usually says " none " to " memory pack".
Then you will be allowed to save. That is of course if you are using Jabo's direct input plug-in.

Although you make a good point, the problem (as stated in the first post) isn't limited to mempak saves.

 

[AllApologies96]

The 'Save' directory, obviously. Can't create or write to save files in a protected directory.

Still fails to open, it wasn't read only although some of the files were but even now it won't open.

 

[Smiff]

are you an admin?
have free disk space?

 

[AllApologies96]

are you an admin?
have free disk space?

I'm the only one who uses this computer so I do have full acess and I have over forty gigs of space left.

 

[Smiff]

something is stopping it writing save files.. you could get FileMon from http://www.sysinternals.com/FileAndDiskUtilities.html and try to see what's going on.. i've no idea, never seen this problem where one of the suggestions in this thread won't fix it.

edit: here's what you should see when you open and close Mario64, filtered to show only *.eep activity.

the 2nd pic is what you should see the first time you run Mario64 (theres 100 lines i just show the first bit)