Some of you may remember (and may suffer from this ailment): Classic TCP/IP
DNS behave poorly after sleep, or when on a modem which is not connected to
the web on my Pismo/400 OS X 10.2.3/.4 (i.e. I get DNS not responding errors
that can only be fixed by restarting).
Well, it seems that those problems have *finally* settled down. I'm not
*entirely* sure what I did to get it to become less of a pain but I have
three theories (one of which I still have to check out).
#1 I knew that my B&W OS X install was perfectly happy with Classic and
sleeping and *never* gave me said errors. I also used the location manager
to give me different LAN settings (I consider the B&W a "portable" computer
with its 'handy' carry handles ;) in OS X and it would also create a TCP/IP
preference for OS 9 which would be automagically updated.
I tried creating different locations on the Pismo but they never seemed to
get communicated to Classic's TCP/IP settings (i.e. when I booted into OS 9,
OS 9 TCP/IP would still have the settings I'd left it with last time I
booted into it, and not OS X's (unlike the B&W which would change TCP/IP
depending on my OS X TCP/IP settings)). Anyway, I tried creating a new set
of locations and changed them a number of times and under different
circumstances (I haven't checked in OS 9 to see if TCP/IP has adopted OS X's
settings yet... will do that soon).
#2 I tried rearranging the list of DNS servers depending on whether the
connection is on the LAN or on dial-up (they are the same set, but their
order of importance is *slightly* different). That didn't work last time I
did it, but maybe it took this time.
#3 After reading about a 'work around' in a Micro$oft USENET list I tried
running Internet Explorer after I received the error and it would eliminate
the DNS not responding error after trying to load a few pages
Anyway, whatever it was I did I'm not having to restart Classic anymore. I
do get the DNS no responding error in Classic if it takes the dial-up a long
time to connect, or if I have 'connect automatically when needed' turned
off, but simply pressing send/receive e-mail will work.
Who knows? I can't say precisely which thing fixed the problem! I'm just
happy that things are settling down.
L8r, Eric.
PS a neat OT tid bit I learned today about the Boer war (where the [EMAIL PROTECTED]
British royalty (& Canuks & others) were killing off the Dutch ("boer" =
farmer) settlers in South Africa around the turn of the last century).
Apparently the most damning piece of newsreel footage which galvanised the
British public (it showed the boers slaughtering a Red Cross camp) was
staged on behalf of the British crown, and the 'reports' of atrocities were
similarly manufactured for domestic British (and Empire) consumption to get
the public on-side with an expansionist (South African gold mines) war.
--
G-Books is sponsored by <http://lowendmac.com/> and...
Small Dog Electronics http://www.smalldog.com | Refurbished Drives |
-- Check our web site for refurbished PowerBooks | & CDRWs on Sale! |
Support Low End Mac <http://lowendmac.com/lists/support.html>
G-Books list info: <http://lowendmac.com/lists/g-books.html>
--> AOL users, remove "mailto:";
Send list messages to: <mailto:[EMAIL PROTECTED]>
To unsubscribe, email: <mailto:[EMAIL PROTECTED]>
For digest mode, email: <mailto:[EMAIL PROTECTED]>
Subscription questions: <mailto:[EMAIL PROTECTED]>
Archive: <http://www.mail-archive.com/g-books%40mail.maclaunch.com/>
---------------------------------------------------------------
>The Think Different Store
http://www.ThinkDifferentStore.com
---------------------------------------------------------------
