 |
| Register | Login | |||||
 |
Main
| Memberlist
| Active users
| ACS
| Commons
| Calendar
| Online users Ranks | FAQ | Color Chart | Photo album | IRC Chat |
|
| | ||
|
| Register | Login | |||||
|
Main
| Memberlist
| Active users
| ACS
| Commons
| Calendar
| Online users Ranks | FAQ | Color Chart | Photo album | IRC Chat |
|
| | ||
| 0 user currently in General Emulation. |
| Acmlm's Board - I2 Archive - General Emulation - Help with Nester |
 |  |  |
| Pages: 1 2 | Add to favorites | "RSS" Feed | Next newer thread | Next older thread |
| User | Post | ||
|
Kefka Indefinitely Unbanned Level: 81 Posts: 2978/3392 EXP: 4826208 For next: 166641 Since: 03-15-04 From: Pomona, CALIFORNIA BABY! Since last post: 4 hours Last activity: 4 hours |
| ||
| Am I the only one who thinks it's folly not to use FCEUXD over Nester? I mean, Nester was ok, but FCEUD and FCEUXD are just WAY better. Granted, it may be that the emulator used has nothing to do with this, but I still just found this kind of... well, I saw it and couldn't help but think what I said. | |||
|
HyperLamer <||bass> and this was the soloution i thought of that was guarinteed to piss off the greatest amount of people Sesshomaru Tamaranian Level: 118 Posts: 4340/8210 EXP: 18171887 For next: 211027 Since: 03-15-04 From: Canada, w00t! LOL FAD Since last post: 2 hours Last activity: 2 hours |
| ||
| Disch, I always thought you were pretty bright, but you're hardly coming off that way here. Diskdude was a moron for using those reserved bytes and thus breaking the ROM, yes, but fixing it isn't going to cause more problems. When he did this, those bytes were all unused - or reserved as you call them as if it meant something different - meaning they could not have been anything but 00. Thus it's perfectly safe to assume that if bytes 8-F are THAT SPECIFIC PATTERN, that they're supposed to all be 00. No ROM is ever going to have that pattern in its header legitimately - the chances are 1 in 18,446,744,073,709,551,616! (That's one in eighteen quintillion four hundred forty-six quadrillon seven hundred forty-four trillion seventy-three billion seven hundred nine million five hundred fifty one thousand six hundred sixteen. You couldn't begin to comprehend how big that number is.) For that matter, why complicate the issue by having one program fix the games and the other play them? If the emulator can detect that the game is broken, and knows exactly what needs to be done to fix it, then by all means fix it. It's somewhat annoying to have a "do you want to fix this" prompt for every bad ROM you load (not that a prompt is even needed - make the file read-only if it's absolutely necessary to keep it), but it's much more annoying for it to close with a "This ROM is corrupt, do this and this and that and try again" message, forcing you to find and download some obscure program and figure out how to work it. Not to mention, what happens when you download a new ROM and it's corrupt? Now you have to run the program and re-scan every single ROM again! (edited by R2H2 on 05-03-05 03:11 PM) |
|||
Dish Spiny Level: 38 Posts: 384/596 EXP: 355646 For next: 14801 Since: 03-15-04 From: Disch Since last post: 18 days Last activity: 18 days |
| ||
Originally posted by R2H2 I guess I'm just arguing the principle. Most people (dan, and you apparently) seem to be saying "hey, just do whatever to make it work and to hell with the standards." -- I'm saying "The standards should mean something, and you shouldn't make exceptions for boneheads who don't want to follow them".
That's the thing -- this ISN'T fixing it. This is just feeding it. If these ROMs didn't play in emulators, the problem wouldn't even exist because people wouldn't be spreading around busted ROMs. Like i said before -- if emus were more strict about this kind of thing we wouldn't even be debating this -- since the problem wouldn't exist. So lax header checks are part of the problem. I can't believe it's gotten to the point where an emulator is frowned upon by actually interpretting the file format PROPERLY. I mean seriously -- stand back and look at what you're actually saying, you guys. It's madness. You're saying an emulator should intentionally do things WRONG in order to get a handful of BROKEN games playable. Dress it up with your rationalizations and stats all you like --- but that's what you're saying. I, for one, think that's not only awful, but one of the worst things an emu could do. And no emu should do that. EVER.
Fix it, fine. As long as it prompts me before writing over any of my ROMs. Ignores it, NO. Never. No how. That's absolutly bad. That just feeds the problem. As for making the user find and run obscure programs to fix the problem -- maybe that is a little off the top. I really REALLY wish GoodNES and all the other auditing tools would actually address this problem rather than just completely ignoring it. I mean a simple "[bad header]" in the GoodNES name would work WONDERS towards reducing the number of dumb DiskDude roms around. |
|||
|
HyperLamer <||bass> and this was the soloution i thought of that was guarinteed to piss off the greatest amount of people Sesshomaru Tamaranian Level: 118 Posts: 4364/8210 EXP: 18171887 For next: 211027 Since: 03-15-04 From: Canada, w00t! LOL FAD Since last post: 2 hours Last activity: 2 hours |
| ||
| Well I do agree that there wouldn't be a problem if the emulators had proper support for these standards. Thing is, back when this was done, they didn't. I really doubt any new ROMs are being released with this problem, so there isn't really anything wrong with fixing the ones that were. And now that more emulators do support them properly, such things may not happen so often in the future. Personally I think it'd be great if the emulator just fixed it silently on disk. That way anyone who uses a corrupt ROM ends up with a non-corrupt ROM, even if they have no idea what that means, and poof, the problem basically disappears. |
| Pages: 1 2 | Add to favorites | "RSS" Feed | Next newer thread | Next older thread |
| Acmlm's Board - I2 Archive - General Emulation - Help with Nester |
| | |
