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 02:49:50 AM »
If you can't get it working on Windows, then there are options to update using Mac or Linux.  The instructions are on the Retrode firmware page.

ssokolow wrote a script that has helped many update their units:  http://forum.retrode.org/index.php/topic,374.0.html
2
Support / Re: FW Update fail error Verify device fail at 0x00000
« Last post by Engal on 22/Nov/2017 06:33:12 PM »
Thx for the answer!

I tried it many times and on two win systems (win7 64 and win10 64) and always got the same result.

Where do I find the alternate update options?
3
Support / Re: FW Update fail error Verify device fail at 0x00000
« Last post by skaman on 22/Nov/2017 05:32:20 PM »
Hard to diagnose remotely.

You might want to try the update again.  I had this happen once and I restarted and got it updating again.  If your attempts to update continue to fail, then look into one of the alternative updating options.

People with problems updating on Windows systems are having success using Linux.
4
Support / FW Update fail error Verify device fail at 0x00000
« Last post by Engal on 21/Nov/2017 08:40:30 PM »
hi there from germany,

have retrode2 with fw18.c and wanted to update to newest fw.
did everything as mentioned on retrode.org but got this fail message "verify device fail at 0x00000.
Now my retrode wont let me copy games (f.ex. gameboy via plugin) to pc.

please help, what went wrong????

thx a lot!
5
Support / Re: StarFlight (Sega Genesis) missing RAM file. ROM file ok.
« Last post by skaman on 21/Nov/2017 06:40:23 PM »
Starflight uses SRAM but the ROM header lacks the SRAM data.  Because the SRAM start and end data is missing, the Retrode firmware assumes that there is no save game.

I'm not sure how many games have this problem.  I'll have to go through the save cart list and check each ROM.

I'll try to fix this in a firmware update sometime.



6
I tried out this script on my Mac with macOS Sierra (10.12.6) and it successfully updated my Retrode 2 to the 0.23 firmware. Thanks! :)

Happy to hear it. :)

I've updated the initial post's comment about macOS accordingly.
7
General Discussion / Re: N64 Save Support (FW v0.23)
« Last post by skaman on 19/Nov/2017 12:45:39 AM »
Ok.  That's good that there is no difference.

I'm not familiar with Pokemon Snap save data but it looks like your .FLA has the proper header data at the start of the file.

Maybe someone else can check their Pokemon Snap saves.
8
General Discussion / Re: N64 Save Support (FW v0.23)
« Last post by kjorteo on 19/Nov/2017 12:11:09 AM »
Thank you very much for your suggestions!

Alas, there does not appear to be any difference between the two dumps with that setting toggled, and the emulators continue to treat each like a new file.
9
General Discussion / Re: N64 Save Support (FW v0.23)
« Last post by skaman on 18/Nov/2017 11:59:07 PM »
Try dumping the save twice. 

Once with [saveReadonly] set to 0 and once set to 1.

Compare the files in the hex editor to see if there's any difference.

If there's a difference, then try each in the emulator (after saveswapping).

Remember to uncheck the read-only attribute after putting it in the save folder.


10
General Discussion / Re: Trouble Updating to v23
« Last post by WolfBoy980 on 18/Nov/2017 10:05: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.
Pages: [1] 2 3 ... 10