nesdev.com

The FDSStick software looks for the first few bytes of a disk header ("block type 1"). It doesn't find it and gives up. I don't know how you're generating your raw files but something doesn't look right. Compare with a dumped image. Values in a .raw file are just timing between pulses on the data pi...

If you send me sample files I'll try to figure out what's wrong.
There is no header / footer, that's just junk data.

http://3dscapture.com/junk/FDSStick_debug_20171229.exe Use a known good disk (written by a properly calibrated drive) for adjusting your drive. Preferably a real commercial disk, not bootleg/copied. Push the "Test" button to scan a disk. The software shows a graphical representation (blue wavy line...

byuu wrote:Oh boy. The wiki needs some serious updates, then. I'll also add:

The wiki is crap. Brad Taylor's .txt file (linked at the bottom of the wiki) is much more useful.

You're free to use the code however you like, consider it public domain.

That code on github is ancient, it's not compatible with the current firmware. I can put up something more current, it might take a few days though.

It's been ages since I've gone over the powerpak MMC3 code, but I'll dig it up if there's something that needs fixing. I have MMC3A,B,C carts I can test on if needed.

The largest Game Doctor image I have is 66458 bytes (and that's really pushing the limits). The largest Game Doctor game I've seen is 12 sides. I guess 13, if you want to count the saver disk -- some Game Doctor devices do save states which adds another disk, I don't know if you want to accomodate t...

They are just cartridge games ported/hacked to run from disk (that was the purpose of Game Doctor after all). I'm not aware of any original games made specifically for game doctor hardware. There's nothing special about the disks themselves (aside from the size), they follow the standard FDS disk fo...

Even if you're right, why make a format that relies on a bunch of assumptions? Simpler solutions exist, I don't know why you're doubling down on this point.

Welp, you asked for opinions, you got mine. I'm a fan of KISS.
It's your thing, do what you like. As you said, it's for your own emulator and not likely to see adoption anyway so go nuts and make a FDS 2.0.

*shrug* Inconvenience of multiple files, or inconvenience of another new unsupported (except in your own emulator) format. I prefer the former, personally... Every Game Doctor and Magicard disk still uses the \x01*NINTENDO-HVC* disk header, so I do not follow. If a game happens to have 0x01,0x2A in...

If they are Game Doctor images, why not release them as such? (*.A, *.B, etc) To reach the next side, advance 65,500 bytes from the start of the current side, then further until \x01\x2A (begin of block 1) is found" This doesn't seem very safe to me. Since this is a bastardized .FDS format that brea...

I'm hoping that this was somehow an accidental surrogate for the missing bits at the bottom. It seemed strange, but it was the best model I managed to come up with at the time. Could be. Everything matches up when I look at it with a 'scope, I'm fairly confident it's right. How were you doing your ...