Quickdev16
Moderator: Moderators
Forum rules
- For making cartridges of your Super NES games, see Reproduction.
Quickdev16
https://www.assembla.com/wiki/show/quickdev16
Needless to say, I'm impressed. This is the exact kind of quality + design that's needed for _NES_ console development. :-)
Needless to say, I'm impressed. This is the exact kind of quality + design that's needed for _NES_ console development. :-)
1) Because I don't do parallel ports any more. The year is (nearly) 2010, not 1991. I'm not going to deal with direct I/O "passthrough" drivers/SYS/DLLs on Windows either. USB or nothing -- and yes, I've worked with it (USB stacks, that is).Jeroen wrote:So why not get a copynes?
2) It's difficult to discern if the software is really up to snuff. If I remember right, a large portion of it is based on QBasic... come on.
Sorry, that's just how I feel about it.
If those are your only concerns, have some blatant advertising: USB CopyNES 
USB interface, Windows software written in C, other people working on Linux/MacOS apps.

USB interface, Windows software written in C, other people working on Linux/MacOS apps.
Like bunny said...theres a usb version nowkoitsu wrote:1) Because I don't do parallel ports any more. The year is (nearly) 2010, not 1991. I'm not going to deal with direct I/O "passthrough" drivers/SYS/DLLs on Windows either. USB or nothing -- and yes, I've worked with it (USB stacks, that is).Jeroen wrote:So why not get a copynes?
2) It's difficult to discern if the software is really up to snuff. If I remember right, a large portion of it is based on QBasic... come on.
Sorry, that's just how I feel about it.


Hmm... I'm a little confused at how this actually works. Well, that is to say, I understand what the device *does*, but I'm confused as to how one would, say, use it to develop an MMC3 game for example.bunnyboy wrote:If those are your only concerns, have some blatant advertising: USB CopyNES :)
USB interface, Windows software written in C, other people working on Linux/MacOS apps.
Nah -- I have no real problem with EPROMs, just that I've been down that road when it comes to development and it's tedious; a lot of wasted time, especially when debugging is required.Roni wrote:so I guess that would make those of us still using EPROMS stone-agers, huh?
My point is that it's 2010 and overall development tools/processes should have improved. Just because we're working on a device from 1986 doesn't mean we have to do development like back then. :-)
For MMC3 you would have to make a RAM cart (easy) and uploader plug in (easy). For many simple mappers and MMC1 I have the PowerPak Lite. Then just like the Quickdev16 you just upload your game over USB and play within seconds.koitsu wrote:Hmm... I'm a little confused at how this actually works. Well, that is to say, I understand what the device *does*, but I'm confused as to how one would, say, use it to develop an MMC3 game for example.
A separate USB RAM cart would be a benefit for easy installation, but then the mappers problem hits.
- NESHomebrew
- Formerly WhatULive4
- Posts: 415
- Joined: Fri Oct 30, 2009 4:43 am
- Contact:
Has anyone implemented this successfully? I always assumed the powerpak lite was the only cart compatible. Then again, I haven't done a whole lot of research on the project. All I've seen is what is on the product page.bunnyboy wrote:
For MMC3 you would have to make a RAM cart (easy) and uploader plug in (easy).
I probably would have considered a copynes sooner if I knew you could make other mappers supported.
Provided you can find someone to build your CopyNES.bunnyboy wrote:For many simple mappers and MMC1 I have the PowerPak Lite. Then just like the Quickdev16 you just upload your game over USB and play within seconds.
In that case, would it be possible to add a built-in USB CF reader to another version of the PowerPak, in much the same way that the EFA flash card for GBA has a USB port on it?A separate USB RAM cart would be a benefit for easy installation, but then the mappers problem hits.
Several years ago I made a cart that supports UNROM, for 256kB FlashROM that works with CopyNES. kevtris wrote a plugin for it. I imagine that plugin should work with the USB version as well, but I haven't tried it yet. I have the parts for those, so I could always supply those as kits or built ones if there was enough interest. But the PowerPak Lite would be better for development, writing Flash is much slower than SRAM.WhatULive4 wrote: Has anyone implemented this successfully? I always assumed the powerpak lite was the only cart compatible. Then again, I haven't done a whole lot of research on the project. All I've seen is what is on the product page.
I had a ROM emulator before I had a CopyNES, so I never really used it for development. What really bugged me was the idea of having to navigate through a GUI to program the cartridge, I'd rather have a command-line program.
Back to the original topic though, that Quickdev16 looks awesome. That is the best approach for a devcart, on the NES though everyone gets tripped up by the mappers. So I think a seperate ROM emulator makes good sense for NES, since there are some many different boards.