Hi,
Having followed the advice that's been handed out over the past few days, I've managed to get my Gamecube to boot perfectly, using the following setup :
Gamecube > Router (Linksys Etherfast) > PC
This works as long as my computer forces it's IP to 192.168.1.100, instead of 10.0.0.5 (the IP it's automaticaly assigned by the router). While the computer's IP is forced, my router refuses to consider it a part of the Network, and won't let it connect to the internet.
In order to solve this, I just went out and bought another Cat5 cable, a crossover adapter and a 2nd network card.
It now goes :
PC > Router > ADSL Line
PC > Gamecube
This seems to work for most people, but the Gamecube won't connect to the 2nd network adapter. It just searches for a DNS server :{
Does anyone have any suggestions, while I fiddle around with it? ^^;
That error usually occurrs when you have a DNS server running on your PC already or if it cannot find an IP address to bind to. Are you statically configuring the 2nd NIC to use the address 192.168.1.100?
as far as you having the PC connected to the router for internet, and your gamecube connected to your PC using another nic... i have something similar
i have my
PC --- wireless --- router
for internet
and i have my onboard nic connected to gamecube
PC --- X-over cable --- Gamecube
and i've found whenever i want my gamecube to connect to my PC, i have to disable my wireless (in your case your first nic) connection, and then start the stream, after about 3 or 4 minutes of the stream going, i can reenable the wireless connection and it'll play just fine still... i don't know why, i dont ask why, but it bothered me for like an hour while i couldnt get it to work right..
so yeah, before you get too frustrated, just disable your internet connection for like 4 mintues while you get the thing streaming to your gamecube, or backing up files from yourgamecube.. whatever works :P
I have a similar problem, I can either do what you suggest, or use PSUL to upload the dol (PSOLoad doesn't seem to like multiple gateways) and use the -i 192.168.1.100 command to force it to bind to my x-over to the GC.
Once you have psul 1.1 downloaded, you'll have a psul.exe file.
Along with that, you'll have your loader, which has two key components, the .exe and the .dol. Say we're using ACL 1.4 as a loader, which has s3-acl.exe and s3-acl.dol.
You prep the dol file for loading to the gamecube like so:
psul -i 192.168.1.100 s3-acl.dol
It'll say waiting for connection.
Then to be simple, cut and paste your .gcm image into the same directory, and do this:
s3-acl whatever-game-you're-playing.gcm
It'll say Waiting.
Then fire up the GC, run thru the menues, it should connect, and load up your game.
On a side note to this... Phoenix 2.3 is great and all because it is all packaged together and you don't really need to understand what's going on behind the scenes.
But I find I achieve the best results when I load up the .dol with PSUL or PSOLoad from command line, and then choose whatever loader I want, and fire it up also from command line. You have access to all those options just like you did in phoenix, except somehow it seems more stable and works when nothing else will.
You should be able in your router control panel( for a linksys you probaly have to put http://192.168.1.1/ into your webbrowser) to set what the default IP addresses are.
For ex/ mine is orginally 192.168.0.XXX
and I changed it to be 192.168.1.XXX
And then I set it so my main desktop ip is
192.168.1.100
I use a dlink router thou so I don't know how specifacly to tell you how to do it.