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
General Discussion / Game Gear SMS Plugin Question
« on: Today at 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)

Support / Re: Mega Man X2 Comatability Fix Possible?
« on: 16/Oct/2017 04:13:44 PM »
We're preparing to release the sources to the firmware. From then on, if you have time, go for it.

@Matthias_H has any further thought been given to releasing the source? (I realize there are multile reasons why you might not release the sorce, including a concern that you would need to put time into cleaning the source up and that such time might not be available). To the extent you don’t have short term plans to release the source, I would ask that you consider releasing it in the future if you ever decide to step away permanently, I think the recent work that has been done with respect to N64 save support shows how important folks having access to it can be.

General Discussion / Re: Progress on N64/GBA save support?
« on: 07/Oct/2017 05:42:31 PM »
Amazing work @skaman!

Today I tried to dump Mother 3 but it didn't work. Although a file named Mother3.A3UJ.gba is displayed, but it's 0 kb in size. I've tried it several times, but it doesn't work. :(

Is there a known issue with Mother 3? I use a Retrode 2 (from dragonbox) with the firmware v0.22.

Two things to try:

1) Clean the game contacts, sometimes a 0 kb message just means it can't read the game.
2) Try using the "Force" config options to force the size to the correct size.

General Discussion / Re: Progress on N64/GBA save support?
« on: 27/Aug/2017 11:59:53 PM »
Amazing work!

General Discussion / Re: Progress on N64/GBA save support?
« on: 23/Aug/2017 08:07:15 PM »
FlashRAM is controlled using the status register and command register.  We don't see the actual programming algorithms.  I've never disassembled an N64 ROM but I would assume that the program identifies the flash type based on the chip ID and adjusts to match.  This is what I do in the Retrode firmware.

There is a difference in how the data is addressed.  The new flash (MN63F81 and MX29L1101) can be addressed identical to the SRAM.  The old flash (MX29L1100) uses 128 byte blocks which presented a problem on the Retrode.  I had to shift the addresses for the old flash in order to read out complete blocks.

Is there a list of games that use old flash, I've only seen the list of US games that support flashram. Have you already released an updated beta or are you waiting until writing is done?

If you go to device manager, double click the entry, and click details, and in the "Properties" drop down select  "Hardware Ids." it should show the VID, PID, and REV. With respect to Retrode 2, it should probably be VID_03EB PID_2FF9, and REV_0000.  If the computer can't get that information from the device (for example, it says the VID and PID are both 0000) then the work around won't help. In that case, I'd recommend trying a different PC. (Note, this VID/PID combination match the entry for AT90USB64 in the atmel_USB_dfu.inf file that is installed as part of Flip 3.4.7).

General Discussion / Re: Progress on N64/GBA save support?
« on: 19/Aug/2017 01:33:48 AM »
Really appreciate the work you put into this!

Pages: [1] 2