View Single Post
Old 23 January 2011, 19:46   #2
Registered User
Join Date: Oct 2009
Location: Salem, OR
Posts: 1,203
OK, now I'm not sure how much of it was which fix (and I know no one cares, but too bad..), but here's what I found.
I went down to AmiTCP 3 (as AmiTCP 4 has a "Click OK" and I found out easynet uses AmiTCP 3), and starting having that problem again. Off and on..
I was pinging, but not browsing on all sites...
Then I noticed something...
When pinging, I was actually pinging ???
And that was pinging, BUT it was pinging because my ISP is helpful, and resolves EVERYTHING that doesn't resolve to it's own search servers... And THAT is what I was pinging...
I remembered that when I setup AmiTCP, it asked me for my home network, and I just typed "home."

So, I found that in the config file in AmiTCP:db (OK, I forgot which file already, but it was in there... :-) ) and I just commented that line out... Then I did a "ping" and responded...

I'm still not sure why it was sometimes working and sometimes not before, but it seems happier now..
I must have made that change earlier when I was having trouble, but around the same time I installed CardPatch...

(old before edit below)
Got it...

The ClassicWB install didn't have CardPatch going, and while I thought CardPatch was for other things, apparently, it can present ... er... uniquely...

I'm still not sure why it was doing what it was doing, but it was fixed with CardPatch.


p.s. It was also nice that the glitch let me get to, as I used it to DL CardPatch.. ;-) Tried it this morning, still failed to and Went to and DL'd CardPatch. Installed it. Rebooted, and now work.

p.p.s. Sorry TCD.. Will do next time.. (Just noticed...) :-(

Last edited by desiv; 26 February 2011 at 05:52.
desiv is offline  
Page generated in 0.04263 seconds with 10 queries