nesdev.org

toggling the control lines works fine as well using the standard POSIX functions:
(i have built this part):

http://pastebin.com/mc4b978a

I have been working on a proper program.. but I'm slow.

Sorry I meant to add that:
even though only the data port is being used here, the program will fail if you don't open both ports.

As far as I know there is no special initialization required first on the copynes side. It should run immediately when you plug it in to the linux box. Here is the code: http://pastebin.com/meaf9cec Now, I know the first character always gets screwed up in this sample (don't know why yet, but it cou...

I don't see offhand the problem with your code, but I'm pretty sure the kernel driver works fine, and it looks like it is set up right from your posted info. I have been able to get the internal copynes version and bios version using this driver and put the thing into play mode. Some commands need t...

I don't believe that an app built for the old parallel copynes would work directly with the new usb copynes without modification. The new usb copynes has a dataport and a control port which are both treated as seperate serial ports when plugged in through the usb->serial driver in linux. I *believe*...

Well I heard that you were changing to a new system and had to manually port over anything done before it went online so I have been trying to dump my whole collection in the mean time just to be difficult

Hello, Thanks for your help with this! I sent you the files, but I found out some new information in my testing that is probably more useful anyway: The string that I put into the CHR / PRG field is what was causing the dumps to be bad. I'm not sure if it's too long, or contains bad chars (=, .), bu...

I am not using an adapter w/ resistors on the data lines.. I haven't build one yet. I am aware that some Sachen carts require that sort of adapter, but my plan was to first dump the games that didn't need one and then see if I can pull off the others once I've made an adapter. Do you think this coul...

So I've got my copynes up and running again, and I've got a stash of new Sachen games... Well, my plan was to figure out how to dump them using the CopyNES Win32 Client, and then once I had the proper working plugin & mapper / Unif boardname, dump them with Bootgod's db to submit the results. Wh...

I was able to successfully a new USB copynes that doesn't seem to be susceptible to being fried by the killer Sachen game by following your advice and severing the lockout chip related lines and moving the USB board over. Also: I was able to dump my Action 52 game after this change, so obviously the...

Hmm, thank you for your reply. The reason I ask is because I have been having trouble with unlicensed games that use surges to circumvent the CIC permantly frying the copynes somehow (it's happened to me on 2 seperate systems now), and they did not have such problems before I installed the copynes.....

Can anyone tell me what the purpose of switching out the Nes' .1uF capacitor with the 1uF one while installing the CopyNES / USB CopyNES? As far as I can tell, this sits directly between the cart and the lockout chip.

Thanks for the advice guys, I'm hoping I can salvage this unit, but if not, I'll try disconnecting the lockout related lines on the next go.

Yeah, I thought it might be something with the CIC stun process... Maybe this game overkills on the CIC Stun... I would like to protect the next Unit from this type of damage rather than trying to pull the parts off the individual carts. Do the carts not need to communicate with the lockout chip to ...

btw, bootgod I did read that thread re the Namco 106, but for a few reasons, I didn't think the read conflict referred to there was causing my problems: - This game actually did run once before my first copynes died, and I was able to make a successful dump from that time - It didn't sound to me tha...