Search

[bommy]

Just trying to get to grips with my new R4DS, which is my first card for the DS (Lite).

I've patched Savsender with the GUI version of the DLDI tool, and it said this was successful. I've transferred this onto my card, and created the config in the right place.

I run the cmd prompt and Windows Firewall prompted me to unblock the process, which I did.

Now I run the app on my DS and all I get is the first line - "Welcome to savsender 1.1!" - with the power light blinking to show that it's trying to connect by WiFi. I've turned off WEP on my router, gone into Mario Kart and connected successfully (both with auto-detecting IP/DNS settings and manually configured ones, then saved and rebooted) but nothing will let me get past "Welcome to savsender 1.1!"

Any ideas/help thoroughly appreciated.

[dantheman]

Hm, is SSID broadcasting enabled?  Keep using manual settings, even though you said that didn't help.  Have you checked the two threads my first post links to?

[bommy]

Thanks for that mate. Yes, I read those links, and yes, SSID broadcast is enabled. Any other thoughts?

[dantheman]

I think it should be able to continue to a certain point and then give an error if it can't connect.  Have you tried launching it through Moonshell or DSOrganize?

Otherwise I'm out of ideas, sorry.

[bommy]

It was launching through Moonshell. Would DSOrganize make a difference? Are there any other simlpe homebrew apps you'd recommend to see if they can connect to my WLAN?

[dantheman]

DSO might, but it might not, I'm not sure.  You could use the official Wifi lib test from http://www.akkit.org/dswifi/wifi_lib_test.nds but I'm not sure if this link is the most recent one.  I'd also try the wireless features of DSOrganize, as I know those use the updated lib that supports all DS systems.

[bommy]

Thanks Dan, I'll try that now.

If I can't get this working (my friend has had the same problem) I was planning on getting a Supercard, using it once for save dumping, then eBaying it. Would my R4DS work in place of the Superkey, or would I need one of those too?

[bommy]

The Wifi test connects without problems.

Am I right in saying the savsender app should show the "Connected to AP" status info as soon as it connects, and before it encounters, say, a problem with portforwarding and netcat? I don't know what to troubleshoot - I'm presuming that as I only get that one line - "Welcome to Savsender 1.1" - it's simply having problems connecting to my router.

[dantheman]

Yeah, looking at my screenshot it appears that SavSender connects to the AP before reading the config file, or something like that.  I'm honestly not sure what the issue is.  Unfortunately, I'll be gone for a week with no Internet access soon, so I won't be able to help troubleshoot the issue.

But yes, there is a function of the R4 that acts as a NoPass device for a slot-2 device.  I'm not sure exactly how to activate it, but the feature is there.

[phlip]

Am I right in saying the savsender app should show the "Connected to AP" status info as soon as it connects, and before it encounters, say, a problem with portforwarding and netcat? I don't know what to troubleshoot - I'm presuming that as I only get that one line - "Welcome to Savsender 1.1" - it's simply having problems connecting to my router.

Looking at the source, the chain of events seems to be that it:
- prints the welcome message
- initialises FAT (printing a message if it fails, but staying silent if it succeeds)
- initialises WiFi (silently)
- connects with the WFC settings (showing either a success message or a failure)

So, if it's failing with just the welcome message up, one of those steps must be hanging.

But yes, there is a function of the R4 that acts as a NoPass device for a slot-2 device. I'm not sure exactly how to activate it, but the feature is there.

It's the third option on the boot menu... the one labelled "Boot Slot-2"

[bommy]

Thanks for that. The power light does flash, which suggests wifi is initialising, but then it doesn't give me an error or success message. Hmm.

I've borrowed a SuperCardLite and SuperKey now, although I've not managed to get eepinator running yet.

[raidensnake]

for some reason the program doesn't transfer the entire file. only a small bit of it. when I check the link between the DS and the pc the dos program closes during transfer and crashes the DS. I did everything suggested and nothing seems to have helped. What could be the problem?

[Hickey]

I followed the instructions perfectly on the original post for restoring saves. However, when I get to the part where I enter the "nc.exe -l -p 1234 < savefile.sav" and enter in all the information, in the command window it says, "The system cannot find the file specified." Can anyone help me?

[dantheman]

"savefile.sav" is the name of the save file you're attempting to restore to the official DS cartridge.  If your save file is named "Super Mario 64 DS.sav" then your command should look like the following:

Code Select Expand

nc.exe -l -p 1234 < "Super Mario 64 DS.sav"

Note that if the filename has spaces in it, you'll need to enclose it in quotation marks.  You can also just type the first couple of letters and hit Tab to have it automatically complete the filename for you, adding the necessary quotes.

[Hickey]

Thank you! That solved that problem, heh. However, when I try to connect my DS to my computer using SavSender, I get an error message saying, "Could not connect to AP! Aborting." I'm sorry I'm having so many problems with this...