Fast connecting to host, almost instant access fix

I thought that I'd share this with everyone, since this has turned out to be usefull to me. I had a personal issue with the filebrowser's "Host" connection procedure, that I had to first initially browse to the host, wait about 10-20 seconds, for the first attempt to fail (I understand that this is not a fixable issue, just the nature of it), then re-browse to the host again to get a connection, ps2clientloader immediately goes green on the first attempts failure, that establishes the connection. Well, I had an idea: since I don't use the default launch, anyway, I edited my laucnhelf.cnf's second line so that it reads (this is the first 2 lines):

CNF_version = 3
LK_auto_E1 = host:/C:/Connecting to Host

Then I made the timeout 0, so now, ulaunch elf immediately attempts to connect on startup to this fictitious program (I started with an actual elf in C:\, it will fail, anyway) on startup, getting past that first attempt failure have to copy over then run, I can set a key to whatever.elf I have in progress on my pc, and run it just as quickly from there. In the end, I suppose that a couple of seconds more at every startup is far less bothersome to me than the whole 2 try, 20 second old way to connect, given the frequency that I use the host protocall, whcih again, I can now use just like any other adress, except the HDD, whautomaticly, and I noticed something quite odd: instead of 10-20 seconds, it gets over that in 2 or 3 seconds, showing me that "not found" dialog, and connecting, now my R2 menu keys to host apps or directories, as well as regular menu keys to host apps, work the instant that ulaunch defaults to it's browser, again, in a couple of seconds.
I use the host protocall frequently, exparamenting with whatever, and this saves me lots of time, I no longerich still takes substantially longer to startup than this arrangement takes to access host directories.

I hope that this is usefull to anyone else, it was one of my few good ideas, floating in a sea of bad ones.

Quote:

---

Originally Posted by Rotosound_rb666

I thought that I'd share this with everyone, since this has turned out to be usefull to me. I had a personal issue with the filebrowser's "Host" connection procedure, that I had to first initially browse to the host, wait about 10-20 seconds, for the first attempt to fail (I understand that this is not a fixable issue, just the nature of it), then re-browse to the host again to get a connection, ps2clientloader immediately goes green on the first attempts failure, that establishes the connection.

---

In fact PS2ClientLoader doesn't really check the server connection. It just performs a normal IP 'Ping', and if there is a reply it assumes that the 'host:' server is active, though the reply is in fact sent by lower level network drivers on the PS2. That's why there can sometimes be 'misunderstandings' so you may have to terminate PS2ClientLoader on the PC when using other servers on the PS2. This doesn't affect your idea of course, but since you use host: a lot it's something you should keep in mind.

Quote:

---

Well, I had an idea: since I don't use the default launch, anyway, I edited my laucnhelf.cnf's second line so that it reads (this is the first 2 lines):

CNF_version = 3
LK_auto_E1 = host:/C:/Connecting to Host

Then I made the timeout 0, so now, ulaunch elf immediately attempts to connect on startup to this fictitious program (I started with an actual elf in C:\, it will fail, anyway) on startup, getting past that first attempt failure have to copy over then run, I can set a key to whatever.elf I have in progress on my pc, and run it just as quickly from there. In the end, I suppose that a couple of seconds more at every startup is far less bothersome to me than the whole 2 try, 20 second old way to connect, given the frequency that I use the host protocall, whcih again, I can now use just like any other adress, except the HDD, whautomaticly, and I noticed something quite odd: instead of 10-20 seconds, it gets over that in 2 or 3 seconds, showing me that "not found" dialog, and connecting, now my R2 menu keys to host apps or directories, as well as regular menu keys to host apps, work the instant that ulaunch defaults to it's browser, again, in a couple of seconds.

---

I'm glad it worked out well for you this way, but I'm also a little concerned about that huge delay you got when 'opening' the server by manual browsing. You see, here that delay is also just 2-3 seconds normally, and I don't think I ever saw a delay of as much as 10 seconds (not to mention 20 !!!).

Quote:

---

I use the host protocall frequently, exparamenting with whatever, and this saves me lots of time, I no longerich still takes substantially longer to startup than this arrangement takes to access host directories.

I hope that this is usefull to anyone else, it was one of my few good ideas, floating in a sea of bad ones.

---

You're idea is a great one for all who use host: in every session (which I also tend to do), and even for people who never saw your long delays it's still valid, as it does eliminate the need for any 'ineffective' manual browsing.

Best regards: dlanor

I think my delays (maybe they arent quite that long, anyway) are mainly doe to bad computer housekeeping.. that is, just way too may things cluttered up in my directories. Adding to that, I'm using 2 hard drives now, a 320gb, and a just added 500gb (a new SATA2, though my board only supports SATA1, but when I get the SATA2 pci CARD IN, 300mbps write speeds.. whoa!) with 3/4 of a terrabyte, I can lget lost myself. I suppose I need to make a default directory just for ulaunchelf and the ps2, I have a 2gb usb flash that I wanted to use that way (some reason ulaunchelf doesnt seem to like them this big, that or I just didnt wait on it long enough, in the ps2's usb port) but that damn thing ends up with a new drive letter every time I use a different usb port, since I manually edit in adresses for other than my system drive, this gets to be a pain. It's tricky not to get lost with windows explorer, thank goodnes for ulaunchelf's static-ness, now to get isomehow organized....

one other thing I noticed is that I get a very noticable longer delay if I leave my crossover unplugged, which is great, since I forget about that, sometimes, and seeing that hesitation reminds me to check my connections. I usually pop the network adaptor off, and leaving the hard drive in the bay, I just plug on my usb-ide cable and its power supply, since it's so much faster than transfering through the network..... the network adaptor comes off there a lot, the crossover cable gets overlooked, sometimes, I appreciate ulaunchelf's new heads up on that.

I have a thing about early warnings, and the consequences of not heeding them, not that it's in any way related, but I've recently been researching somethiing that had always bother me: I'm something of an authority on "Pearl Harbor", since I'm from Oahu, and that was (even history has greatly wronged us, here) that the attack by the Japanese was a A: a "surprise" and B: was the first blood-blow, this is entirely untrue, and the University of Hawaii's Undersea Research Center has now uncovered irreputable evidence that is was the US who shot first, when the USS Ward engaged, confirmed, and SUNK what was absolutely without any question not "a sonar contact" or "possible periscope" or a whale, or anything . The Ward said that at first they saw what looked like a periscope, so they dropped a charge, wehich, set to detonate at the default 100 feet, went way too deep, and BLEW A SUBMERINE CLEAR OUT OF THE WATER. Now, stunned, and exposed, and right there in plain sight (they said they almost ran over the thing, very true) while it was surfaced they fired+ a shot into this sub's conning tower with a 4 inch deck gun, which the newly found wrecked mini-sub clearly has, a gaping hole. Well the fact that it exisits at all, with only that hole proves this: It was closer than the 100 yards or so it takes one of those shells to arm, they shot point-blank. Nothing left to question here: The USS Ward started WW2 at 05:55 AM, Hawaiin time by sinking an enemy submerine (that was clearly too damn small to get there from Japan by itself, so there had to be a fleet out there, somewhere)
2 hours. what does 2 hours mean? 2 hours could have been the arrival of a flight of B-17's, just as the Japanese had all their planes, fuel, and bobs all spread out on their flight decks (caught with their pants down, big time), and the entire Pacific Fleet, in formation and making fflank speed to catch up, instead of sleeping in the harbor, and "Pearl Harbor" woulkd have been the sinking of 3/4 of the Imperial Japanese Navy, without any significant losses to our own... It would have been over before it began, the Japanese surrender would have been on likemonday, December8th, 1941,
But alas, nobody did what they should have, that morning, I dare to say, "what if"
Here's a creepy footnote: The USS Ward was itself sunk by a Japanese submerine, on December 7, 1944.
Some say an once of prevention is worth a pound of cure, but it's really worth ten tons of it. I keep a picture of that recenly discovered mini-sub, just to remind me of that, though nobody wants to hear that we coulda-woulda-shoulda changed history so drasticly, with just a simple telephone call, at the right time.
It reminds me to backup my data BEFORE the hard drives crash, like when NOTHING is wriong, and that sort of thing.

And at some time, I'm going to publish my PH "what if" scenario as a short story, since nobody seems to get it, and the crew of the USS Ward, deserve t. Nobody gets that if only someone had got that to the right person, sooner, "Pearl Harbor" would have been THEIR loss, insted, as opposed to just not happening to us: 2 hous does not make for we could have defeded ourselves, it would have meant the surprise was on the Japanese, instead.
IN my "what if" version, WW@ doent start at 07:55 on 12-7-1941, sadly, in my almost could have story, the time history says it started, it actually would have ended, since WW@ REALLY started 2 hours earlyer, but nobody got it straight, or simply did'nt believe it. Too bad for us.
This wont make me very popular, but I am right..
Not an once, TEN TONS.

but I never learn, either, or Id make a lot more system restore points than I do.