nesdev.com

You mean the speed measuring is done on the Game Doctor itself? That is unfortunate. Still, the disk drive is connected to the RAM Adapter as normal, so the measuring must be done entirely from the information you can get from communicating with the drive. I might not really know what I'm talking a...

Very cool. Preordered. Thanks for the heads up

I have a stack of Roland sample disks, if you want to play around with them. Density is exactly the same as FDS. I've used FDSStick to read them out before, but haven't tried analyzing the format.

I think the gap issues, and mechanism behind it is pretty well understood. There are games larger than 64k per side, so a 64k restriction doesn't make sense to me. NewRisingSun proposed a "kitchen sink" format that seemed reasonable to me but it was pulled. Seems like something like that is necessar...

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.