You know, when I had 50 for them for sale for $50 each about ten years ago, no one bought any. Serves people right paying $500 now.
Which N64 deck is described in this post ? http://retro-treasures.blogspot.com/2007/05/nintendo-64-dd-dev-kit.html "Japanese N64 (debugging unit) with a unique dome expansion cover."
The question is more like - what are the chances of getting a COMPLETE kit? OK, why do you ask how rare the dev kit is, then post a link with photos of one and ask what it is?? You said it. The site said it. 64DD dev kit. Including a dev N64. It says debug. Didn't the DD64 dev usually go with the Partner N64? http://shiggsy.gbadev.org/section.php?s=n64 http://assembler.roarvgm.com/Nintendo_64_developer_kit/nintendo_64_developer_kit.html http://devkits.handheldmuseum.com/SN64.htm http://nekochan.net/wiki/index.php/N64_Emulator_Kit
The reason I ask is, on this page: http://assembler.roarvgm.com/64_DD_Developers_unit/64_dd_developers_unit.html It explicitly states that the DD dev kit consists only of: "The developers DD comes with 5 blank DD disks, a DD inerface cart, as well as the adapters needed to modify the N64 development cartridge to work with the DD." No mention is made of a special N64 console. But then, on the page I mentioned originally: http://retro-treasures.blogspot.com/2007/05/nintendo-64-dd-dev-kit.html in addition to all of the above, there is also a "Japanese N64 (debugging unit) with a unique dome expansion cover." So I am wondering: a) Is it correct that the N64 DD dev kit can be used with a normal, plain old N64 b) where can I learn more about this special debug console in the second link - it's not something I have seen referred to elsewhere ... as you say, usually I see stock n64 consoles with Partner dev kits, etc. Thanks.
a) The only difference between a regular N64 and the "debug" N64 was the hardware reset thing wasnt it? And you can mod a regular N64 to become a "debug" N64. b) See above. Regarding "Japanese N64 (debugging unit) with a unique dome expansion cover.", I would say chances are it's just a 3rd party expansion pack (I seem to remember the 64dd needed the expansion pack). Shiggsy
Only if you want to use a partner card. for the dd drive itself a simple n64 makes it too (from the correct region that is). You can perfectly program a retail 64dd from a n64 with a v64jr. Period. Correct. AND support for the u64 debugging stubs. Here is a doc on how to mod a retail N64 to become a debug-compatible: http://www.yntproject.net/index.php?section=docs (Howto make your N64 mature). You need a N64 modified like that to be able to use a Partner N unit with it (maybe also an ISV, but it hasnt been tested so far).
Ok. Thanks for that clarification. So, it would seem that these two recipes: - Partner N64 + Partner RAMcart+EISA + DD dev kit - Retail N64 + retail DD + top-sitting backup unit actually provide identical development capability for the N64 DD, just using different software tools ... yes ? And further, since a backup unit can have 512 megabits, and the dd itself has (roughly) 512 megabits of space on a disk, really the only thing you gain in a homebrew dev environment by having the dd AT ALL is the enhanced sound library, yes ? So, other than: a) rarity/collectibility b) the actual ability to write a DD disk there is nothing else a working DD dev kit gives you over a typical homebrew (backup unit + retail console/dd) ? All correct assumptions ?
it can give you debug, which I consider valuable if you're making an application - plus tons of official documentation and applications of course.
Yes, I suppose that is true, but if you test in an emulator there are plenty of good debug tools for the homebrew scene as well, yes ? Although I suppose no debug tools for actual 'dd' code, but again, the only actual _feature_ gain of the dd is the better sound hardware. Otherwise, it's just a bigger storage medium, which is almost a moot point if you have a 512megabit copier, yes ?
Trust me I have been fiddling around with that machine for over a year now, and i can tell the 64dd is no more than a floppy disk on steroids with a real-time chip included. A storage medium, it has no means of anything that looks like a programmable interface (if we dont consider the disk controller). You poke the address of the data into it and tadá it spits back out the data. The data itself is plain common ROM code, executed by the N64 cpu (or RSP / RDP code). This means that once it's loaded in the RDRAM it can be debugged just like any other common code.
