Verified Rom Still Not Working

[ViewtifulDom]

Here's what happened:

On my old PC (XP), Majora's Mask worked just fine, it saved and everything. Last year I transferred my roms to my new PC (7), and everything else works fine. When I load up Majora's Mask, it also works. I closed it and opened it up the next day, and after the menu screen, (just before the file selection screen), I get a pop-up reading 'error reading flashram'. Now, I can't load it up at all, and Project64 reads it as a bad rom. I've uninstalled/reinstalled Project64 at least three times, and checked the rom with GoodN64 and all that. I've used the old .rdb, the new .rdb, and no .rdb. (I don't even really know if that is necessary or not; figured I'd mention it). I have no idea what's wrong.

TL, DR: Project64 is telling me a good rom is a bad rom.

[squall_leonhart]

you have 2 instances of project64 running locking the flashram.

[dsx_]

why would it be read as a bad rom though?

[squall_leonhart]

the rdb is locked.

[dsx_]

ahhhhh yes

[squall_leonhart]

can also happen if the rom is no longer in the directory or it hasn't been refreshed after changes.

[HatCat]

He just said he tried re-installing Project64 and using the old and new RDB versions. How is the RDB locked from read access if he has write access to the whole installation?

He had also said "after I opened it the next day"; not all of us leave things running without ever restarting the machine, which would have cleared the ghost process of Project64 from RAM.

Originally Posted by ViewtifulDom

On my old PC (XP), Majora's Mask worked just fine, it saved and everything. Last year I transferred my roms to my new PC (7), and everything else works fine. When I load up Majora's Mask, it also works. I closed it and opened it up the next day, and after the menu screen, (just before the file selection screen), I get a pop-up reading 'error reading flashram'. Now, I can't load it up at all, and Project64 reads it as a bad rom. I've uninstalled/reinstalled Project64 at least three times, and checked the rom with GoodN64 and all that. I've used the old .rdb, the new .rdb, and no .rdb. (I don't even really know if that is necessary or not; figured I'd mention it). I have no idea what's wrong.

First just in case you hadn't restarted your PC since before the problem I would restart it.

When you load Project64 press F5 to refresh the ROM browser to see if the game is still there.

See if you have write access to the FLASHRAM save.
In $Project64\Save, look for the FLA save file named after Zelda MM. Try moving it to a different folder where Project64 doesn't check.
Also check the file size of the FLA; maybe it's corrupted.

[ViewtifulDom]

Just so we're clear, the problem is not the flashram error. That was the old error. The current error is that Project64 is seeing the rom as a bad rom when it is really a good rom. I can't even get the flashram error because the game won't ever start.

[HatCat]

Check to see that the RDB updates you did were to install the Project64.rdb file in the same folder as Project64.exe.
You should have both write and read access privileges to the file.

Is Zelda MM the only game being detected as a bad ROM of those games you've installed?

Also hit F5 when Project64 starts, or load Zelda MM using File > Open in the program menu.

[ViewtifulDom]

Originally Posted by rswedlow

Check to see that the RDB updates you did were to install the Project64.rdb file in the same folder as Project64.exe.
You should have both write and read access privileges to the file.

Is Zelda MM the only game being detected as a bad ROM of those games you've installed?

Also hit F5 when Project64 starts, or load Zelda MM using File > Open in the program menu.

All of those things have been tried, I'm afraid. The .rdb was installed correctly, and it is fully accessible. Majora's Mask is the only game reacting this way. No matter how many times I hit F5 or which way I open it, it still reads 'bad rom' and the screen remains black even though it shows a frame rate and all that.