Recent Posts

Pages: [1] 2 3 ... 10
1
Support / Re: FW Update fail error Verify device fail at 0x00000
« Last post by skaman on Today at 05:40:22 PM »
You might try reinstalling the driver.

Relevant posts:
http://forum.retrode.org/index.php/topic,134.0.html
http://forum.retrode.org/index.php/topic,384.0.html

Pay close attention to newbie2's posts if you're having difficulty.
2
General Discussion / Re: Trouble Updating to v23
« Last post by newbie2 on Today at 01:36:29 PM »
This thread might be of help:  http://forum.retrode.org/index.php/topic,134.0.html

Read from Reply #14 to the end.

You mean this?

"Workaround
(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 www.microsoft.com/.../details.aspx.)
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:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\usbflags\vvvvpppprrrr
(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:
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\UsbFlags
3. On the Edit menu, point to New, and then click Key.
4.Type the name of the new key in the following form:
        vvvvpppprrrr
        where
        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.

https://isxehg.bn1304.livefilestore.com/y4pMEUi0zve5SOkYMVWYpkAA5MDR6dsFZTGogZVqCEIxnmfpY484s2AY_rPGYQpxzUvd6eyR8TfjhYbfGNxd1Px604nvgNlD6fL4Hy5r1LkRzYmPfL4eTyZErRWDaIIFsoy8Kf1N75twL4wLWupBK_KRzxKSh3YJ6d2_uxUDXERR4Hyz7Ztic0rMPyQWHTz-ERFU56gpHXbSqXXKSJoj69ORQ/regeditretrode.PNG?psid=1

https://isxdhg.bn1304.livefilestore.com/y4poZvfjMRP-dsltAxvlWtRN0xsMQ_GY4DoAJmmvgnufZcg2zgvFjKajHV0HYB6POg9tu8HhHSgIPoicKdtMMCF0_TC5kqQJY5xtx4NncFbRSS2LA0i-Etg9KSqtv6Lsj9ZFVyURuS25m8M4UYXxntmrpsDglqrBCLzUEAp28nxc2UI8-U_Vvigh0f-uoM2u6Pi5vvUTeBtx9Poq9_DzDwzEQ/devicemanagerretrode.PNG?psid=1

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)
3
Support / Re: StarFlight (Sega Genesis) missing RAM file. ROM file ok.
« Last post by skaman on Today at 08:06:29 AM »
Fixed the Starflight SRAM identification.  I also added identification for a bunch of other SRAM games that were missing the SRAM data in the header.

The fix will be rolled into the next v0.24 BETA whenever it gets released to the test group.
4
General Discussion / Re: N64 Save Support (FW v0.23)
« Last post by Lennart on Today at 06:48:29 AM »
FWIW, I managed to dump my Pokémon Snap (PAL) save and play it via Mupen64Plus by using ssokolow's saveswap program.

5
General Discussion / Re: N64 Save Support (FW v0.23)
« Last post by skaman on Today at 03:38:03 AM »
Are you able to open your Pokemon Snap cart? 

I'd like to see the flashram chip on the PCB.  I'm wondering if it is an incompatibility with the flash chip.

I've ordered a copy of Pokemon Snap and should be receiving it soon to run tests on.
6
General Discussion / Re: N64 Save Support (FW v0.23)
« Last post by Raw64life on Today at 03:10:27 AM »
This is awesome. Been waiting years for this. Huge props to skaman.

Also shout out to Eureka for making many of the same mistakes I did while getting my saves working and asking about them here so I didn't have to lol. I also used the wrong voltage at first and then didn't know to uncheck the readme.

While I got .eep and .sra working thanks to the ED64 saveswap, I do have the same problem as kjorteo in that PJ64 will not recognize my Pokemon Snap save. Tried everything I know and everything suggested  in this thread and no dice. It's the only .fla game I have so I can't test anything else.

Still, a small price to pay for having all my other N64 saves preserved for life. Thanks again!
7
Support / Re: Gameboy Camera Not Reading Properly After 1.9 Update
« Last post by hadess on Today at 01:37:56 AM »
I'll look into it, but I need some additional information:
  • Which firmware version have you been using when reading the GB camera save still worked?
  • Please take a look at the .gb file with a hex editor: What are the values at offsets 147 hex (327 dec) and 149 hex (329 dec) of the GB camera ROM?
  • What's the file name of the .gb / .sav file?
  • What's the size of the .gb file?
  • Do the first few hundred bytes from the start of the .gb file repeat at offset 4000 hex (16384 dec)?

I've replied in the newer thread at http://forum.retrode.org/index.php/topic,383.0.html
8
Support / Re: Cannot grab sram from Game Boy Camera
« Last post by hadess on Today at 01:37:22 AM »
I couldn't get the SRAM file at all from mine. Using the 0.20 Beta firmware that my Retrode 2 came with, I could only see a 1.2 megs "WMuzoysMur.gb" file on the Retrode. It works in 3 different Game Boy types, and I cleaned the contacts with alcohol first, then contact cleaner as a second pass, having removed the cartridge shell.

The "[forceSize]" configuration option you added is probably not going to change anything, as that's just for the ROM size, not the SRAM size.

Answering @Wannado's question in http://forum.retrode.org/index.php/topic,335.msg2334.html#msg2334
Quote
Which firmware version have you been using when reading the GB camera save still worked?

It never worked for me, and it's the only version of the firmware that I ever used. Maybe someone else can help?

Quote
Please take a look at the .gb file with a hex editor: What are the values at offsets 147 hex (327 dec) and 149 hex (329 dec) of the GB camera ROM?

This is hexdump's output for those values:
00000140  59 7f 7f 7f 36 31 7b fc  75 76 7d 33 7f 9d ba f9  |Y...61{.uv}3....|

Quote
What's the file name of the .gb / .sav file?

No .sav file, the ROM is "WMuzoysMur.gb".

Quote
What's the size of the .gb file?

The file is 1192960 bytes long.

Quote
Do the first few hundred bytes from the start of the .gb file repeat at offset 4000 hex (16384 dec)?

No, here's about 10 lines of the stuff:
00004000  f2 59 fb 59 76 5a 6d 5a  56 5a 4f 5a aa 5a d1 5a  |.Y.YvZmZVZOZ.Z.Z|
00004010  6a 53 53 53 4a 53 4d 53  52 53 57 53 74 53 8d 53  |jSSSJSMSRSWStS.S|
00004020  ee 53 57 56 ae 56 d9 56  fe 56 57 55 de 55 5d 56  |.SWV.V.V.VWU.U]V|
00004030  b6 56 e3 56 3c 57 a9 57  ce 57 77 4a 2e 4a 39 4a  |.V.V<W.W.WwJ.J9J|
00004040  4e 4a 6f 4a 96 4a 9d 4a  ae 4a bf 4a d6 4a e9 4a  |NJoJ.J.J.J.J.J.J|
00004050  f2 4a fb 4a 6c 49 5d 49  22 49 27 49 2c 49 31 49  |.J.JlI]I"I'I,I1I|
00004060  36 49 3b 49 5f 49 55 49  56 49 67 49 7a 49 a9 49  |6I;I_IUIVIgIzI.I|
00004070  9a 49 ab 49 b4 49 bd 49  ce 49 df 49 f6 49 7d 4a  |.I.I.I.I.I.I.I}J|
00004080  52 4a 23 4a 9c 4a a9 4a  a6 4a ab 4a b6 4a b5 4a  |RJ#J.J.J.J.J.J.J|
00004090  ba 4a bf 4a d4 4a c9 4a  ce 4a d3 4a da 4a dd 4a  |.J.J.J.J.J.J.J.J|
000040a0  e2 4a f3 4a 76 4b 55 4b  26 4b 37 4b 4a 4b 65 4b  |.J.JvKUK&K7KJKeK|
9
General Discussion / Re: Multiple Retrode Controllers with Linux
« Last post by hadess on 23/Nov/2017 11:20:08 PM »
See my comments on this thread as well: http://forum.retrode.org/index.php/topic,366.0.html as well.
10
Support / Re: FW Update fail error Verify device fail at 0x00000
« Last post by Pat1986 on 23/Nov/2017 05:12:28 PM »
Hm, ok. i'm in Dortmund. That's quiet a route.  ;D
Pages: [1] 2 3 ... 10