Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Re: Bleeding-edge technology
48 views
Skip to first unread message
Message has been deleted
Mike Andrews
Feb 9, 2012, 3:50:15 PM2/9/12
to
rob...@att.net wrote in <jgvvit$8k1$1...@dont-email.me>:
> So, there is this brand new technology that hardly anyone has ever
> implemented before. It is called Rgurearg and is full of mystery and
> wonder. One of the mysterious and wonderful things about it is the
> zrqvn npprff pbageby address.
>
> 1. A different tentacle of $ORK was building a piece of hardware that
> goes into our product. [0]
>
> Cow-orker: "We already own a block of ZNP addresses because we use
> them on other products. But on the module we build for you, it's
> really a pain in the butt to keep track of the addresses and program
> them in on the production line. Would it be OK if we just built all
> of them with the same ZNP address? I mean, you only ever use one
> of these modules per system, right?"
Haven't I already told that story? I'm sure I have; still, it is available
on application. Cow-orker needs corrective discipline. Is there a place
nearby that sells lumber?
> Really? Forever is a long time... can you *guarantee* we'll never
> want to use two at once? Also, since you aren't implementing a
> bunch of the stuff I put in the FAZC spec, we won't be able to get
> esoteric details like the module serial number over the phone, so
> the ZNP address might be the only way we have to tell them apart!
FURRFU!
> 2. $VENDUH sells us boards. Most of them work, but one exhibits a
> strange unwillingness to load the software correctly. After much
> head-scratching on the part of me and a co-worker [1], we discover
> that $VENDUH has done *something* strange, and that all the Rgurearg
> interfaces on the board are sharing two ZNP addresses. I write up
> the problem and put it on the pile of problem children.
>
> A few weeks later, a different new board refuses to load. This
> time, I check the ZNP addresses early - sure enough, another one to
> go back.
>
> One of these two is now on its third round of "It's still broke" and
> "WFM", while the other one has only gone two rounds. Much of my
> time for the past few days has been spent discussing this issue with
> $VENDUH, instead of doing productive work (like trying to figure out
> when the big layoff will be).
>
> Mysterious and wonderful. I need a drink.
Just one?
> Matt Roberds
>
> [0] A long time ago, our location was allowed to own soldering irons.
> Now we outhouse everything. It's so much easier and cheaper to have
> every bug fix or production change involve program managers and
> lawyers and accountants, rather than just walking out to the floor
> and saying "Start doing it like this."
>
> [1] Since poached away for silly things like more money and competent
> upper management.
Where are you orking now? Can you arrange to be laid off for redundundancy
now, ahead of the wave, so you can collect unemployment while you look for
unrecovery? "Lord! What fools these mortals be!"
And can you arrange for the same-MAC people at $VENDUH to not die, but to
have health issues such that they can't ork any more. "Lord! What fools
these mortals be!"
Also, would you like to be (back?) on the cap-hams mailing list?
--
No trees were destroyed in the sending of this message.
However, a large number of electrons were terribly inconvenienced.
> So, there is this brand new technology that hardly anyone has ever
> implemented before. It is called Rgurearg and is full of mystery and
> wonder. One of the mysterious and wonderful things about it is the
> zrqvn npprff pbageby address.
>
> 1. A different tentacle of $ORK was building a piece of hardware that
> goes into our product. [0]
>
> Cow-orker: "We already own a block of ZNP addresses because we use
> them on other products. But on the module we build for you, it's
> really a pain in the butt to keep track of the addresses and program
> them in on the production line. Would it be OK if we just built all
> of them with the same ZNP address? I mean, you only ever use one
> of these modules per system, right?"
Haven't I already told that story? I'm sure I have; still, it is available
on application. Cow-orker needs corrective discipline. Is there a place
nearby that sells lumber?
> Really? Forever is a long time... can you *guarantee* we'll never
> want to use two at once? Also, since you aren't implementing a
> bunch of the stuff I put in the FAZC spec, we won't be able to get
> esoteric details like the module serial number over the phone, so
> the ZNP address might be the only way we have to tell them apart!
FURRFU!
> 2. $VENDUH sells us boards. Most of them work, but one exhibits a
> strange unwillingness to load the software correctly. After much
> head-scratching on the part of me and a co-worker [1], we discover
> that $VENDUH has done *something* strange, and that all the Rgurearg
> interfaces on the board are sharing two ZNP addresses. I write up
> the problem and put it on the pile of problem children.
>
> A few weeks later, a different new board refuses to load. This
> time, I check the ZNP addresses early - sure enough, another one to
> go back.
>
> One of these two is now on its third round of "It's still broke" and
> "WFM", while the other one has only gone two rounds. Much of my
> time for the past few days has been spent discussing this issue with
> $VENDUH, instead of doing productive work (like trying to figure out
> when the big layoff will be).
>
> Mysterious and wonderful. I need a drink.
Just one?
> Matt Roberds
>
> [0] A long time ago, our location was allowed to own soldering irons.
> Now we outhouse everything. It's so much easier and cheaper to have
> every bug fix or production change involve program managers and
> lawyers and accountants, rather than just walking out to the floor
> and saying "Start doing it like this."
>
> [1] Since poached away for silly things like more money and competent
> upper management.
Where are you orking now? Can you arrange to be laid off for redundundancy
now, ahead of the wave, so you can collect unemployment while you look for
unrecovery? "Lord! What fools these mortals be!"
And can you arrange for the same-MAC people at $VENDUH to not die, but to
have health issues such that they can't ork any more. "Lord! What fools
these mortals be!"
Also, would you like to be (back?) on the cap-hams mailing list?
--
No trees were destroyed in the sending of this message.
However, a large number of electrons were terribly inconvenienced.
Message has been deleted
Message has been deleted
mrob...@att.net
Feb 16, 2012, 5:48:43 AM2/16/12
to
Mark L Pappin <m...@acm.org> wrote:
> Mike Andrews <mi...@mikea.ath.cx> writes:
>> rob...@att.net wrote in <jgvvit$8k1$1...@dont-email.me>:
>>
>>> [woe]
I read the man page. It told me to see the info page. The info page
told me to look in /usr/share/doc/drink/README.txt.
/usr/share/doc/drink/README.txt had a URL...
> sydharb
> pacificbasin
Not those two. Fish fuck in them. Although I wouldn't mind *visiting*
sydharb again.
I think slow and steady is the way forward.
while true; do drink -vessel helmet; sleep 43200; done;
Matt Roberds
> Mike Andrews <mi...@mikea.ath.cx> writes:
>> rob...@att.net wrote in <jgvvit$8k1$1...@dont-email.me>:
>>
>>> [woe]
>>> Mysterious and wonderful. I need a drink.
>>
>> Just one?
>
> drink: vessel unspecified
>>
>> Just one?
>
I read the man page. It told me to see the info page. The info page
told me to look in /usr/share/doc/drink/README.txt.
/usr/share/doc/drink/README.txt had a URL...
> sydharb
> pacificbasin
Not those two. Fish fuck in them. Although I wouldn't mind *visiting*
sydharb again.
I think slow and steady is the way forward.
while true; do drink -vessel helmet; sleep 43200; done;
Matt Roberds
LP
Feb 16, 2012, 5:58:13 AM2/16/12
to
On 2012-02-16, mrob...@att.net <mrob...@att.net> wrote:
>
> ISTR someone in here telling the story of buying several cheap network
> cards, possibly in thin net days, and discovering that putting any two
> of these network cards on the same segment would Break Things. After
> more investigation, they figured out that the cards were all *exact*
> clones of each other, down to the ZNP address.
I haven't seen two consumer grade laptops (or broadband routers for
that matter) with the same ZNP address for ooooh... at least 6 months
now, and the last one we saw with a ZNP of 00:00:00:00:00:00 was about a
year ago (from a bought-off-qrnyrkgerzr-for-next-to-nothing router iirc)
Oh the joys of providing internet connections to university accomodation!
We see all sorts of crap like that. Constantly. Usually because for
students "cheap" trumps "working" when it comes to buying their own
hardware.
-Paul
--
http://paulseward.com
>
> ISTR someone in here telling the story of buying several cheap network
> cards, possibly in thin net days, and discovering that putting any two
> of these network cards on the same segment would Break Things. After
> more investigation, they figured out that the cards were all *exact*
> clones of each other, down to the ZNP address.
I haven't seen two consumer grade laptops (or broadband routers for
that matter) with the same ZNP address for ooooh... at least 6 months
now, and the last one we saw with a ZNP of 00:00:00:00:00:00 was about a
year ago (from a bought-off-qrnyrkgerzr-for-next-to-nothing router iirc)
Oh the joys of providing internet connections to university accomodation!
We see all sorts of crap like that. Constantly. Usually because for
students "cheap" trumps "working" when it comes to buying their own
hardware.
-Paul
--
http://paulseward.com
c...@nospam.netunix.com
Feb 16, 2012, 6:47:58 AM2/16/12
to
mrob...@att.net wrote:
>
> ISTR someone in here telling the story of buying several cheap network
> cards, possibly in thin net days, and discovering that putting any two
> of these network cards on the same segment would Break Things. After
> more investigation, they figured out that the cards were all *exact*
> clones of each other, down to the ZNP address.
BTDT, so it was probably me.
>
> ISTR someone in here telling the story of buying several cheap network
> cards, possibly in thin net days, and discovering that putting any two
> of these network cards on the same segment would Break Things. After
> more investigation, they figured out that the cards were all *exact*
> clones of each other, down to the ZNP address.
Not an uncommon problem though so many monks will have suffered.
--
From the quill of Chris Newport g4jci.
Mike Andrews
Feb 16, 2012, 8:26:02 AM2/16/12
to
mrob...@att.net wrote in <jhim9u$3ok$1...@dont-email.me>:
> Mike Andrews <mi...@mikea.ath.cx> wrote:
>> rob...@att.net wrote in <jgvvit$8k1$1...@dont-email.me>:
>>
>>> So, there is this brand new technology that hardly anyone has ever
>>> implemented before.
>
> This quote trimming sort of defeats the X-N-A I put in the original.
>> Is there a place nearby that sells lumber?
>
> There are places nearby that at least make and/or own all sorts of
> interesting things, given that it isn't that far from IAD. Don't know
> if they are willing to sell, though.
> one it was.
"First the man takes a drink;
Then the drink takes a drink;
Then the drink takes the man."
-- Old Japanese proverb
>> Where are you orking now?
>
> In an office.
Passive-aggressive much?
>> Can you arrange to be laid off for redundundancy now, ahead of the
>> wave, so you can collect unemployment while you look for unrecovery?
>
> On one hand, the redundancy claim wouldn't hold, because I am currently
> the only US employee of $ORK who has commit access to the source of what
> is probably our best-selling product right now. On the other hand,
> given the way companies don't think, I realize this makes me a prime
> candidate for a layoff.
Yes. And if you were at the top level, where all you do is make decisions
about who should be making decisions about who makes decisions, you'd be
set up with a golden parachute. Instead, because you only do important
things, you're at horrible risk. Makes sense to me.
*NOT*
>> And can you arrange for the same-MAC people at $VENDUH to not die, but
>> to have health issues such that they can't ork any more.
>
> Maybe. They are in sunny California; is there a reliable way to trigger
> earthquakes yet?
Sorry. If I knew about that, I wouldn't be able to talk about it. As it
is, I can neither confirm nor deny that any TLA has developed National
Technical Means to accomplish that. You can bet that it's on the to-do
list of at least one TLA, though.
>> Also, would you like to be (back?) on the cap-hams mailing list?
>
> If that EXPNs the way I think it does, I only qualify for the "ham"
> part.
Location isn't all that important. Neither is ham. It's the interest(s)
that will get you on the list if you want.
That holds for the rest of you, too.
<http://mikea.ath.cx/mailman/listinfo/cap-hams> is a mailing list for
amateur-radio-related (and not) stuff, primarily for folks in the
OKC.ok.us area, but with tentacles elsewhere.
It's low activity, but so are a lot of the subscribers.
--
It's having to actually make money that tends to turn media outlets right
wing, as most left-wing rags go to the wall fairly quickly when they find
that you can't keep the presses running on tofu and group hugs alone.
-- Peter Corlett
> Mike Andrews <mi...@mikea.ath.cx> wrote:
>> rob...@att.net wrote in <jgvvit$8k1$1...@dont-email.me>:
>>
>>> So, there is this brand new technology that hardly anyone has ever
>>> implemented before.
>
>
>>> "Would it be OK if we just built all of them with the same ZNP
>>> address?"
>>
>>> "Would it be OK if we just built all of them with the same ZNP
>>> address?"
>>
>> Haven't I already told that story? I'm sure I have; still, it is
>> available on application.
>
>> available on application.
>
> ISTR someone in here telling the story of buying several cheap network
> cards, possibly in thin net days, and discovering that putting any two
> of these network cards on the same segment would Break Things. After
> more investigation, they figured out that the cards were all *exact*
> clones of each other, down to the ZNP address.
Certainly I have done so; others may have had the same story to tell.
> cards, possibly in thin net days, and discovering that putting any two
> of these network cards on the same segment would Break Things. After
> more investigation, they figured out that the cards were all *exact*
> clones of each other, down to the ZNP address.
>> Is there a place nearby that sells lumber?
>
> interesting things, given that it isn't that far from IAD. Don't know
> if they are willing to sell, though.
>
>>> Mysterious and wonderful. I need a drink.
>>
>> Just one?
>
> It only takes me one drink to get drunk. I just don't always know which
>>> Mysterious and wonderful. I need a drink.
>>
>> Just one?
>
> one it was.
"First the man takes a drink;
Then the drink takes a drink;
Then the drink takes the man."
-- Old Japanese proverb
>> Where are you orking now?
>
Passive-aggressive much?
>> Can you arrange to be laid off for redundundancy now, ahead of the
>> wave, so you can collect unemployment while you look for unrecovery?
>
> the only US employee of $ORK who has commit access to the source of what
> is probably our best-selling product right now. On the other hand,
> given the way companies don't think, I realize this makes me a prime
> candidate for a layoff.
Yes. And if you were at the top level, where all you do is make decisions
about who should be making decisions about who makes decisions, you'd be
set up with a golden parachute. Instead, because you only do important
things, you're at horrible risk. Makes sense to me.
*NOT*
>> And can you arrange for the same-MAC people at $VENDUH to not die, but
>> to have health issues such that they can't ork any more.
>
> earthquakes yet?
Sorry. If I knew about that, I wouldn't be able to talk about it. As it
is, I can neither confirm nor deny that any TLA has developed National
Technical Means to accomplish that. You can bet that it's on the to-do
list of at least one TLA, though.
>> Also, would you like to be (back?) on the cap-hams mailing list?
>
> part.
Location isn't all that important. Neither is ham. It's the interest(s)
that will get you on the list if you want.
That holds for the rest of you, too.
<http://mikea.ath.cx/mailman/listinfo/cap-hams> is a mailing list for
amateur-radio-related (and not) stuff, primarily for folks in the
OKC.ok.us area, but with tentacles elsewhere.
It's low activity, but so are a lot of the subscribers.
--
It's having to actually make money that tends to turn media outlets right
wing, as most left-wing rags go to the wall fairly quickly when they find
that you can't keep the presses running on tofu and group hugs alone.
-- Peter Corlett
Message has been deleted
Joe Zeff
Feb 16, 2012, 1:49:29 PM2/16/12
to
On Thu, 16 Feb 2012 10:58:13 +0000, LP wrote:
> We see all sorts of crap like that. Constantly. Usually because for
> students "cheap" trumps "working" when it comes to buying their own
> hardware.
Well, yes. Of course. One of the many things that they haven't learned
> We see all sorts of crap like that. Constantly. Usually because for
> students "cheap" trumps "working" when it comes to buying their own
> hardware.
yet is to ask *why* the hardware is so cheap. Another thing they haven't
learned is the exact meaning of the words, "As is, no warranty."
--
Joe Zeff -- The Guy With The Sideburns:
http://www.zeff.us http://www.lasfs.info
Bloody kids these days! - Give 'em a logic probe & they wouldn't know
where to stick it.
Lawns 'R' Us
Feb 16, 2012, 2:48:51 PM2/16/12
to
On 2012-02-16, Joe Zeff <the.guy.with....@lasfs.info> wrote:
> Well, yes. Of course. One of the many things that they haven't learned
> yet is to ask *why* the hardware is so cheap. Another thing they haven't
> learned is the exact meaning of the words, "As is, no warranty."
It's not just students that haven't learned that. Shortly after the
> Well, yes. Of course. One of the many things that they haven't learned
> yet is to ask *why* the hardware is so cheap. Another thing they haven't
> learned is the exact meaning of the words, "As is, no warranty."
Christchurch earthquake a year and a bit ago (maybe closer to two
years ago now), one major store had a large quantity of stock that was
written off by the insurance company. So it was sold off at auction:
no reserve, "as is, where is". Amongst other things in the goods being
auctioned were a large number (over 60) of vCnqf: 64 GB, 3G. (First
model; this was before the second model was released by Nccyr.)
RRP in NZ: somewhere around $1289 (can't remember what it was back
then, that's what it is now.)
The first lot was bid up to the point where, with buyer's premium[1],
each buyer was paying approximately $1100 for one.
Personally, I would have ponied up the extra $200-odd and bought a
brand new one. Oh well.
[1] I know why they do it, but it strikes me as a rather deceptive
practice to tack on an extra 15% after bidding has closed.
Message has been deleted
stevo
Feb 16, 2012, 7:39:42 PM2/16/12
to
Mike Andrews <mi...@mikea.ath.cx> wrote:
> mrob...@att.net wrote in <jhim9u$3ok$1...@dont-email.me>:
these TLA's? The idea is so stupid governments would be lining up to buy
exclusive rights to it.
--
Stevo st...@madcelt.org
> mrob...@att.net wrote in <jhim9u$3ok$1...@dont-email.me>:
>
>> Maybe. They are in sunny California; is there a reliable way to trigger
>> earthquakes yet?
>
> Sorry. If I knew about that, I wouldn't be able to talk about it. As it
> is, I can neither confirm nor deny that any TLA has developed National
> Technical Means to accomplish that. You can bet that it's on the to-do
> list of at least one TLA, though.
Do you think I could sell my idea of elephants on pogo sticks to one of
>> Maybe. They are in sunny California; is there a reliable way to trigger
>> earthquakes yet?
>
> Sorry. If I knew about that, I wouldn't be able to talk about it. As it
> is, I can neither confirm nor deny that any TLA has developed National
> Technical Means to accomplish that. You can bet that it's on the to-do
> list of at least one TLA, though.
these TLA's? The idea is so stupid governments would be lining up to buy
exclusive rights to it.
--
Stevo st...@madcelt.org
Graham Reed
Feb 16, 2012, 6:33:59 PM2/16/12
to
c...@NOSPAM.netunix.com writes:
> BTDT, so it was probably me.
> Not an uncommon problem though so many monks will have suffered.
And just to make sure everything sucks, I've seen it done with the UUIDs
> BTDT, so it was probably me.
> Not an uncommon problem though so many monks will have suffered.
on FireWire and USB. At least USB does (seems to) everything by hub
port address, so it still mostly works. FireWire with duplicate UUIDs
works a lot like an improperly terminated parallel SCSI
bus... everything locks up just when you think you've killed the right
goat.
--
"I'm killing for two now."
-- Dexter Morgan
Message has been deleted
Joe Thompson
Feb 17, 2012, 3:10:49 PM2/17/12
to
On 2012-02-16, Bob Clements <fake.a...@k1bc.com> wrote:
> I never ran across dupes. But I had one card from a nocturnal aviation
> type vendor who hadn't bothered to buy a block of addresses. They just
> used their company's initials in ascii for the first three bytes.
>
> Since the first letter had the low order bit being a one, all sorts of
> interesting effects ensued.
Eh?
<Google>
*Oh*. Oh *yes*, I bet that would be a quite interesting collection of
Hemiptera to deal with... -- Joe
--
Joe Thompson | Sysadmin - Scientificist
E-mail addresses in headers are valid. | http://www.orion-com.com/
"There is no way my emacs is ever getting a credit card!" -- Matthew Vernon
> I never ran across dupes. But I had one card from a nocturnal aviation
> type vendor who hadn't bothered to buy a block of addresses. They just
> used their company's initials in ascii for the first three bytes.
>
> Since the first letter had the low order bit being a one, all sorts of
> interesting effects ensued.
Eh?
<Google>
*Oh*. Oh *yes*, I bet that would be a quite interesting collection of
Hemiptera to deal with... -- Joe
--
Joe Thompson | Sysadmin - Scientificist
E-mail addresses in headers are valid. | http://www.orion-com.com/
"There is no way my emacs is ever getting a credit card!" -- Matthew Vernon
mrob...@att.net
Feb 18, 2012, 2:04:04 AM2/18/12
to
LP <use...@lpbk.net> wrote:
> Oh the joys of providing internet connections to university
> accomodation!
You appear to be across the water. Here, as I understand it, university
> Oh the joys of providing internet connections to university
> accomodation!
'net connections are a lot easier to manage. You turn them up at the
beginning of the semester, and then turn them all down again three days
later when all the (MP|RI)AA notices come in.
> We see all sorts of crap like that. Constantly. Usually because for
> students "cheap" trumps "working" when it comes to buying their own
> hardware.
brand in particular (Mbbz) could just barely handle a shell account, but
couldn't deal with SLIP at all; it would just scroll ??? down the screen
when people tried to connect. They were cheap, though, and therefore
popular. My friend who worked at the helpdesk finally got clearance
from $BOSS to refuse to support that particular brand of, as he put it,
"psuedo-modemized interface".
Matt Roberds
Message has been deleted
Message has been deleted
Joe Thompson
Feb 18, 2012, 8:33:13 PM2/18/12
to
On 2012-02-18, mrob...@att.net <mrob...@att.net> wrote:
> When I was at school, Losemodems had recently been introduced. One
> brand in particular (Mbbz) could just barely handle a shell account, but
> couldn't deal with SLIP at all; it would just scroll ??? down the screen
> when people tried to connect. They were cheap, though, and therefore
> popular. My friend who worked at the helpdesk finally got clearance
> from $BOSS to refuse to support that particular brand of, as he put it,
> "psuedo-modemized interface".
default position on that brand as well. Basically if the customer was
able to get PPP working, at whatever speed, that was a success.
IIRC they were one of the more expensive of the cheap options, so people
thought they were spending "a lot of money" when they bought one. -- Joe
Kevin Goebel
Feb 20, 2012, 12:56:12 AM2/20/12
to
On Sun, 19 Feb 2012 01:33:13 +0000 (UTC), Joe Thompson <sp...@orion-com.com>
wrote:
>
>On 2012-02-18, mrob...@att.net <mrob...@att.net> wrote:
>> When I was at school, Losemodems had recently been introduced. One
>> brand in particular (Mbbz) could just barely handle a shell account, but
>> couldn't deal with SLIP at all; it would just scroll ??? down the screen
>> when people tried to connect. They were cheap, though, and therefore
>> popular. My friend who worked at the helpdesk finally got clearance
>> from $BOSS to refuse to support that particular brand of, as he put it,
>> "psuedo-modemized interface".
>I was working an ISP helpdesk from 1995-97 and that was pretty much my
>default position on that brand as well. Basically if the customer was
>able to get PPP working, at whatever speed, that was a success.
>IIRC they were one of the more expensive of the cheap options, so people
>thought they were spending "a lot of money" when they bought one. -- Joe
At the ISP I worked for back then, the common "pmi" was a Hewlett Packard
desktop computer with a Mexican modem (literally "hecho en México", after
you tore the computer down to get to it's hiding place on the motherboard).
They were a pain to take out or bypass, and we frequently wished we could
take out or bypass the owners of such combinations. Our prayers for them to
vanish were eventually answered... by the dual 56K "standard". Our company
went with the HFEbobgvpf K2 version. Guess which other standard was used in
cheaper products and therefore the favorite of our truculent, obstinate,
antagonistic and obnoxious customers?
Kevin
wrote:
>
>On 2012-02-18, mrob...@att.net <mrob...@att.net> wrote:
>> When I was at school, Losemodems had recently been introduced. One
>> brand in particular (Mbbz) could just barely handle a shell account, but
>> couldn't deal with SLIP at all; it would just scroll ??? down the screen
>> when people tried to connect. They were cheap, though, and therefore
>> popular. My friend who worked at the helpdesk finally got clearance
>> from $BOSS to refuse to support that particular brand of, as he put it,
>> "psuedo-modemized interface".
>I was working an ISP helpdesk from 1995-97 and that was pretty much my
>default position on that brand as well. Basically if the customer was
>able to get PPP working, at whatever speed, that was a success.
>IIRC they were one of the more expensive of the cheap options, so people
>thought they were spending "a lot of money" when they bought one. -- Joe
desktop computer with a Mexican modem (literally "hecho en México", after
you tore the computer down to get to it's hiding place on the motherboard).
They were a pain to take out or bypass, and we frequently wished we could
take out or bypass the owners of such combinations. Our prayers for them to
vanish were eventually answered... by the dual 56K "standard". Our company
went with the HFEbobgvpf K2 version. Guess which other standard was used in
cheaper products and therefore the favorite of our truculent, obstinate,
antagonistic and obnoxious customers?
Kevin
stevo
Feb 20, 2012, 7:09:40 PM2/20/12
to
Kevin Goebel <kevi...@kevingoebel.com> wrote:
> At the ISP I worked for back then, the common "pmi" was a Hewlett Packard
> desktop computer with a Mexican modem (literally "hecho en Mexico", after
> At the ISP I worked for back then, the common "pmi" was a Hewlett Packard
> you tore the computer down to get to it's hiding place on the motherboard).
>
> They were a pain to take out or bypass, and we frequently wished we could
> take out or bypass the owners of such combinations. Our prayers for them to
> vanish were eventually answered... by the dual 56K "standard". Our company
> went with the HFEbobgvpf K2 version. Guess which other standard was used in
> cheaper products and therefore the favorite of our truculent, obstinate,
> antagonistic and obnoxious customers?
>
Ah, the joys[1] of the old 56K modems. I still have my file at home,
>
> They were a pain to take out or bypass, and we frequently wished we could
> take out or bypass the owners of such combinations. Our prayers for them to
> vanish were eventually answered... by the dual 56K "standard". Our company
> went with the HFEbobgvpf K2 version. Guess which other standard was used in
> cheaper products and therefore the favorite of our truculent, obstinate,
> antagonistic and obnoxious customers?
>
from when I worked helldesk at an ISP, with the 76 pages of 56K modem
initialisation strings. I had a string for every modem in existence at
the time. You had a FrogShit 1300? I had the string to get it to
handshake to our system.
I am so glad I neither do helldesk, nor work at an ISP anymore.
[1] for small values of
--
Stevo st...@madcelt.org
0 new messages