If your next reply is not your providing the required information, then I'm locking this thread: "we cant do anything more without the rom or without you debugging why your fceux thinks its broken."
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This ROM had been used earlier on a previous version of FCEUX (I do not know what previous version that I used.), before I used the later version of FCEUX.
While I was using the later version of FCEUX, I replaced the ROM with the different, headerless ROM that has less bytes. Why? Because I love to use the headerless ROMs.
Here.
Dragon Warrior (USA) (Beta) (This is the headerless one from the database, DAT-o-MATIC.)
The rom looks broken. Is it a raw rom mislabeled as .nes?
From what that I can see, it is not really mislabeled as .nes. In other words, it is the .nes file.
Last edit: p7b4 2017-08-28
dunno man. fceux says it's broken. we cant do anything more without the rom or without you debugging why your fceux thinks its broken.
Last edit: zeromus 2017-08-28
Oh. I do not think that the ROM is broken. It is just that the emulator is not working with the ROM, because of the error.
The error says "the rom is broken". You think the emulator is not working with the rom, because of the errror, which is that the rom is broken.
The rom's broken until you prove otherwise.
Just take a look at my image.
That's an image of fceux saying the rom is broken.
Hm. It worked on my previous version of FCEUX, as far as I know. But, the ROM does not work in this version (v2.2.3 (r3363)) of FCEUX.
Last edit: p7b4 2017-08-28
there is no such rom. prototype cart identical to the retail one byte-to-byte. use any other verified rom (check with goodnes)
Actually, there is one, which is from ClrMamePro.
Then it's a bug in CLRMamePro
Then, the bug in CLRMamePro should be fixed on FCEUX.
Also, where can I find the donation page for FCEUX?
Last edit: p7b4 2017-08-29
No, the bug in CLRMamePro should be fixed in CLRMamePro.
There is no donation page.
Then, the bug in FCEUX should be fixed on FCEUX.
What bug in FCEUX? The only bug we have in this bug thread is a bug in CLRMamePro's broken rom. I told you how to prove otherwise.
Did I tell you that the ROM worked on my previous version of FCEUX, but the ROM does not work in this version (v2.2.3 (r3363)) of FCEUX?
The ROM worked on a previous version of FCEUX, so maybe that can be reverted to the later version of FCEUX?
If your next reply is not your providing the required information, then I'm locking this thread: "we cant do anything more without the rom or without you debugging why your fceux thinks its broken."
This ROM had been used earlier on a previous version of FCEUX (I do not know what previous version that I used.), before I used the later version of FCEUX.
[URL]https://www.youtube.com/watch?v=SR8yMABTO3w[/URL]
While I was using the later version of FCEUX, I replaced the ROM with the different, headerless ROM that has less bytes. Why? Because I love to use the headerless ROMs.
Here.
Dragon Warrior (USA) (Beta) (This is the headerless one from the database, DAT-o-MATIC.)
Size: 81903
CRC32: ee92a4b3
MD5: 057acbf474fff3af56de179076f5ed72
SHA-1: 5542f834ed4a0907a5c2c935bd58c1d6e7f1e8ce
And, I never use a debug or a cheat code.
That file size is nonsense.
Your file is BROKEN.
This case is closed.
-
This rom is BROKEN.
It's missing these bytes from the end.
0000FFFFFFFFFFFF3F00FFFFFFFFFFFF3F
This thread is LOCKED.
This rom is BROKEN.
It's missing these bytes from the end.
0000FFFFFFFFFFFF3F00FFFFFFFFFFFF3F
This thread is LOCKED.