Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - newbie2

Pages: [1] 2 3
Support / Re: Cannot get n64 plugin to work.
« on: 05/Apr/2019 01:29:56 AM »
Nothing additional comes to mind. I just updated to .25a and tested on a mac, but mine is working fine. Maybe reach out to dragonbox and ask them to verify that the plugin is working for them?

Support / Re: Cannot get n64 plugin to work.
« on: 03/Apr/2019 12:54:32 PM »
Sorry I was thinking of another system. Regarding orientation, at least on the ones Matthias made the instructions were correct and the n64 game works oriented with its label on the same side as the label on the plugin (so label facing out).

This should be more pertinent: Is [forceSystem] set to anything other than auto? Could you see what happens to set it to n64?

Support / Re: Cannot get n64 plugin to work.
« on: 02/Apr/2019 01:50:40 PM »
Just to rule it out as the problem, what slot are you plugging the n64 plugin into?

General Discussion / Re: SNES Enhanced Cart Support (FW v0.22)
« on: 04/Feb/2019 02:50:01 AM »
I used to be a member of the Retrode forums before the "reboot" a few years ago, but I thought I would come back to see what's been going on, and MAN have I missed a lot. One of the biggest things that caught my eye was this thread about a possible Enhanced Cart adapter. I only have a Retrode 1 (gold casing), so I'm not even sure if one of these would be compatible with it, but I'm extremely interested in getting one, if possible. Any updates on this project?

Skaman made some, they work great, not sure if he has any more boards (if not, you likely could order your own board and make one yourself).

The most recent Kazzo (now called inlretro) is also an option:
I was thinking more about an adapter/firmware than a new system

Unfortunately it seems to be the only game in town for NES at this point. If you just opt for the NES connector it is $35 plus shipping which is not that much more than what the retrode plugins cost.

The most recent Kazzo (now called inlretro) is also an option:

General Discussion / Re: Game Gear SMS Plugin Question
« on: 25/Jan/2019 11:22:39 PM »
If anyone sees this in the future and has the same question, just putting the cartridge slot in (and having it flush with the board) worked fine.

Edit: final product

General Discussion / Re: Game Gear SMS Plugin Question
« on: 21/Nov/2018 02:42:28 PM »
That is superhelpful! Any chance you could measure how far the metal part of the connector is from the board?

Also, as long as my connector leaves space for the SMS connector is there any harm in just clipping the pins on the back (after I do the soldering) so that they are shorter?

General Discussion / Game Gear SMS Plugin Question
« on: 17/Nov/2018 11:42:23 AM »
I am working on soldering the game gear cartridge slot (the type sold from eBay) to the SMS plugin and was wondering how the slot should be positioned on the plugin board. If the cartridge slot is flush with the board (see picture linked below) the pins extend pretty far in the back and there is not very much space between the slot and the pins from the SMS slot.

Is that the right position for the slot? Do those pins then need to get shortened after the slot is soldered? Or should the slot not be flush to the board so that the pins don't stick out? Any pictures from other folks who have done the mod would be appreciated!

Support / Re: Issues Dumping Chuck Rock (SMS)
« on: 05/Nov/2018 01:30:20 AM »
Have you tried changing the [forceSize] option in retrode.cfg to the size it should be?

General Discussion / Re: SEGA SMS/GG Firmware (FW v0.24)
« on: 04/Nov/2018 03:56:29 AM »

General Discussion / Re: SEGA SMS/GG Firmware (FW v0.24)
« on: 04/Nov/2018 02:00:02 AM »
Is anyone ever going to consider making a few GG plugins and selling them at a profit for the less technical of us out there?

Realize this isn't a perfect solution for you, but the SMS plugins ( do still contain the gamegear cart slot holes. So you could get that, buy the gamegear connector from ebay that skaman linked and then make one yourself, or pay someone online to do it for you.

Support / Re: Cant Update on Windows 10 (AtLibUsbDfu.dll error)
« on: 29/Oct/2018 08:27:18 PM »
At this point the easiest solution is to try on a different computer. I have seen suggestions to uninstall the usb driver (as a whole, i.e., the driver that controls all of your usb ports) and reinstall as a potential fix, but that is probably more work than you want.

General Discussion / Re: Trouble Updating to v23
« on: 13/Dec/2017 02:56:54 AM »
All credit goes to Skaman for actually updating the firmware, without that all the instructions in the world would be useless.

General Discussion / Re: Trouble Updating to v23
« on: 24/Nov/2017 01:36:29 PM »
This thread might be of help:,134.0.html

Read from Reply #14 to the end.

You mean this?

(Note that this workaround was added in the Windows update that was released on  07/08/2014. If you are applying this update within few weeks of this date, you will need to download and manually install the update from
To apply the workaround for a specific device, add a REG_DWORD value named SkipBOSDescriptorQuery that has a value of 1 to the following registry subkey:
(where vvvv is the device's Vendor ID, pppp is the device's Product ID, and rrrr is the device's Revision number. You can get the VID/PID/REV numbers from the device manager's details tab. This number is encoded in the HardwareIDs of the device)
1. Click Start, click Run, type regedit in the Open box, and then click OK .
2. Locate and then click the following subkey in the registry:
3. On the Edit menu, point to New, and then click Key.
4.Type the name of the new key in the following form:
        vvvv is a 4-digit hexadecimal number that identifies the vendor (idDevice from the USB Deviceescriptor),
        pppp is a 4-digit hexadecimal number that identifies the product (idVendor from the USB Device Descriptor)
        rrrr is a 4-digit binary-coded decimal number that contains the revision number of the device
              (bcdDevice from the USB Device Descriptor).
5. On the Edit menu, point to New, and then click DWORD (32-bit) Value.
6. Type SkipBOSDescriptorQuery for the name of the DWORD Value, and then press ENTER.
7. Right-click SkipBOSDescriptorQuery, and then click Modify.
8. In the Value data box, type 1 , and then click OK.
9. Exit Registry Editor.
10. Unplug and re-plug the device for the workaround to take effect."

Did that, nothing changed. Pictures for proof in the case you might see something I did wrong.

Apologies for providing two links and two attachments to the photos instead of an embedding. The photo button doesn't seem to be working on Microsoft Edge or something.

It looks like you incorrectly named the folder. Instead of naming it it vvvvpppprrrr (those are just variable names meant to be substituted for the VID, PID and REV numbers) you should use the hex numbers from device manager (probably 03EB2FF90000 but check to make sure)

Pages: [1] 2 3