Recent Posts

Pages: 1 2 [3] 4 5 ... 10
21
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.
22
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.


23
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.
24
General Discussion / Re: Trouble Updating to v23
« Last post by kjorteo on 18/Nov/2017 09:48:46 PM »
I ultimately wasn't able to get the device recognition for firmware update mode to work in Windows.  Every time I tried entering DFU mode, rather than recognizing it as a new device (and prompting me to install drivers, etc.,) it threw a prompt that the USB device had malfunctioned and please reconnect it.  I was able to ignore that and install the drivers in the newfound "Unknown Device" in Device Manager, but I never was able to do so in such a way that FLIP could open the connection.

Instead, since I have a laptop with Linux on it, I tried hooking the Retrode up to that and following those firmware update instructions instead.  Those ones ended up working perfectly on the first try.
25
General Discussion / Re: Trouble Updating to v23
« Last post by RazorX2014 on 18/Nov/2017 09:18:23 PM »
i enter DFU mode by doing the following, it may help:
hold down RESET then while holding it down, hold down HWB then let go of RESET then let go of HWB
26
General Discussion / Re: N64 Save Support (FW v0.23)
« Last post by kjorteo on 18/Nov/2017 08:38:08 PM »
Can someone please verify whether Pokemon Snap works on their end?  I have a cart I just cannot for the life of me seem to confirm.

* Tested and confirmed the save data is still valid and present in the actual cart on an actual N64
* Retrode appeared to read the cart just fine; the .z64 and .fla files were right there and transferred over to PC without incident
* I'm no expert, but peering at the .fla file in a hex editor sure looks like there's data in there and that it's not just an empty file or full of 00/FF or whatever.
* Yet both 1964 and Project 64 act like I've fed it a completely blank file when I load the game, in that there's no "Continue" option on the main menu, etc.
* Yes, I unchecked Read Only and made sure it was on 3.3 volts.
* Possibly a .fla issue?  I am afraid I can't test this with any other .fla saves, as the only other game I have that uses .fla is Pokemon Stadium (which doesn't appear to have a save file even when I test the physical cart in the physical system.)  My other games all work fine, but they also all use .eep.

I've attached the .fla file for reference.  If my attempts to parse the hex editor view are correct and this is a valid data file, then there appears to be some sort of issue with getting either of the emulators I tried to read it.  If it's not, then something is up on the Retrode reading/transferring end, since this is definitely a real and working save on the physical system.

Thank you so much for any assistance you can provide!
27
General Discussion / Re: Trouble Updating to v23
« Last post by skaman on 18/Nov/2017 09:54:20 AM »
This thread might be of help:  http://forum.retrode.org/index.php/topic,134.0.html

Read from Reply #14 to the end.
28
General Discussion / Trouble Updating to v23
« Last post by WolfBoy980 on 18/Nov/2017 07:10:02 AM »
I've been following the updating steps like the Bible, but I can't seem to get the right results. I've installed the device properly using Flip, and the Retrode 2 enters DFU mode perfectly. But when I attempt to connect to the device, Flip can't open the device!

I updated the driver so the device is named AT90USB64. But from there it gets messy...
Some users have reported that their device updates fine with Flip's AT90USB646 driver detection, but i'm not getting scratch. I've uninstalled and reinstalled the Flip software multiple times and attempted updating the Retrode's DFU driver to only get messages saying I have the best driver installed already.I just can't get it to work, I can't seem to find a solution from anyone else!

I saw some users report it was because of driver incompatibility with Windows 10? Is this still true?
29
General Discussion / Re: Need a bit of help making a Mark III adapter
« Last post by hadess on 17/Nov/2017 11:41:50 AM »
Just needs a nice sticker now :)

(I've made such a sticker for the SMS/GG combo, after cutting up a Megadrive case as well, I'll post it once I've actually printed it out for testing)
30
General Discussion / Re: Need a bit of help making a Mark III adapter
« Last post by skaman on 17/Nov/2017 11:36:44 AM »
Here's a few pics with a handcut shell.




One nice thing with the Mark III Plugin is that the Card Catcher works with it.  I've tested a Sega MyCard and a Sega Card.




Pages: 1 2 [3] 4 5 ... 10