I have a class to attend and it starts an hour earlier than my usual -- and at a location father away. But it may serve double duty: I'm hoping to get a Hidden Frontier vignette out if it.
Actually made some progress yesterday, and on the "Robinson Crusoe" project at that! (Just in time for Friday?) Despite a frustrating start -- described below -- and a bad scare thanks to a backwards-functioning bypass switch -- "on" means "device online," not "bypass on!" it all worked out in the end, last I knew. There may be forty-'leven e-mails on my work account complaining otherwise.
Network issues ate up my day and not the solving of most of them; not only is that "by others," most of it was happening hundreds of miles away at Corporate HQ, where very frustrated IS/IT types recently discovered they had ad-hocked and extemporized themselves into a serious, ugly tangle and have been struggling to untangle it ever since, with occasional deleterious effects on access to e-mail, the external Internet and other unsubtle issues.
My networking puzzle was simpler: the device I needed to bootstrap (along with my laptop, back and forth) in order to upgrade can be accessed via a modem over dial-up ("What's that funny noise?"*), a direct serial connection, or a network port. Naturally, you want the fattest pipe, so once I had everything to the point where I could connect, I plugged them both into a dumb hub and fired up the software. I'd skimmed through the manual and expected smooth sailing. Nope. Would not connect. The default address in the software was 127.0.0.0 (!) and there was no clue what it ought to be anywhere in the manual when I sat down and read through.
Finally gave up and went to serial (after a hunt for the one "transparent" USB-to-RS232 adaptor), getting the job done at a crawl with a few glitches but succeeding eventually. Poking around, I discovered the "default address" in the device itself wasn't. It's blank. E-mail from the manufacturer confirms this is normal: you have to connect via one of the other two methods and set the ip address. Good to know.
Over the top again today, what-what?
___________________________________
* A long, long time ago, when everything was amazing and Usenet wasn't a forgotten spam-sump, the Internet went "bong-ba-bong-screeeeeeeee...." when you connected to it. No, really, it did.
Update
2 days ago
9 comments:
A long, long time ago,
when everything was amazing
and Usenet wasn't a forgotten spam-sump,
the Internet went "bong-ba-bong-screeeeeeeee...."
when you connected to it.
No, really, it did...
Am I the only one who read this to the tune of Don Maclean's 'American Pie'?
Oh, thanks Anonymous Phssthpok; now I'm going to have that earworm all day.
...I discovered the "default address" wasn't. It's blank.
And of course that's not mentioned in the documentation...
And, yeah, now I'll be walking around all day hearing my old unit's parody version of "American Pie".
I thought the Internet went "Bing bing bing bing bing bing bing bing khkhkhkhkhkh..."
What is IS as in frustrated IS types?
Chris
Bee-eewee-eeeweeee-baaaaaaahhhhhh-shrcshscscshshc. Then connected at a blazing 14,400 baud.
Then we hit the September that Never Ended, and "You've got Mail!".....
IS - Information System, aka IT...
Years ago I was doing a firmware update on a tape library where the backup software using the reported SN to identify the unit. Said update wiped the SN, you had to read it off the nameplate and manually re-enter via a serial line too. The missing SN was documented on the inserted errata page in the docs... That was a fun few hours chasing the problem down.
Ahhhhh... Good 'ole Usenet.
At a smokin' 1200 baud.
The not so good 'ole.
It made alt.binaries.smut a real pain to keep up with.
*cough*
(Actually, the huge number of discussion groups were awesome, I never much cared for web-surfing then, I was an nntp junkie)
"...now I'm going to have that earworm all day."
Mine is an evil laugh...
https://www.youtube.com/watch?v=kTE96NXwGjU
I'm so old I still call it data processing.
Chris
Post a Comment