" /> BRAINPAN LEAKAGE » phone
  • Who Is This, And How Did You Get In My Computer? PART 2

      0 comments

    Continued From:

    Who Is This, And How Did You Get In My Computer? PART 1…

    The modem had finally negotiated a compatible communications protocol and was “speaking” to another device somewhere. For all I knew, that somewhere was halfway around the world, or just right next door – remember, Caller ID was just an idea from the land of Sci-Fi back then…

    I waited impatiently for what was going to happen next… Having seen Wargames more than once – I did work at a video store, after all – I was pretty much bracing myself for some idiot to type in “SHALL WE PLAY A GAME?” then tell me his name was Joshua and that he controlled all of the nuclear missiles in the country. If that happened, I was going to be even less happy than I already was.

    The screen cleared and the phosphor green cursor winked at me from the upper left corner of the monitor. I sat watching, my hands in my lap and one eyebrow raised as I waited for something more to appear. After what seemed like a full thirty seconds had passed, the cursor dropped down two lines on the screen of its own accord, as if some phantom had just hit the enter key twice.

    A second or two later, one laborious letter at a time, the word “hello” appeared.

    I was still perturbed, but now I was also slightly curious. Obviously I had a live person at the other end, and I was assuming they were aware that they had one too. After all, they had just kept calling and calling until they managed a connection, so this apparently fit into their plan somewhere along the line.

    Of course, I did have one thing going through my mind. BBS’s (Bulletin Board Systems – a precursor to the Internet) were seriously gaining popularity around this time. I, myself, frequented several, and while I ended up actually hosting and running one a few months after this incident, I wasn’t doing so at that moment. Of course, someone with a number close to mine could have been, and this could all be a matter of a mis-dial. This would mean the person at the other end might be just as confused as me right now since there was no welcome screen or login prompt being displayed.

    I stared at the glowing word on the screen a moment longer. The thing was, BBS popularity was big among the 11-14 year old crowd, so I really needed to avoid typing back a string of expletives damning this person for interrupting my night, lest it be some tween with a Commodore 64 who would go running to mommy and daddy screaming that some guy at XXX-XXXX telephone number was cussing at him.

    Keeping this in mind, I rested my fingers on the keys. “Hello,” I typed back, much faster than my mystery caller had. Of course, I typed around 85wpm back then. Now, it’s more like 60wpm. Arthritis seriously sucks… But, I digress…

    The person at the other end slowly typed again, “hello”.

    I rolled my eyes. It seemed I didn’t have a rocket scientist calling me, so the likelihood of it being a tween with a hastily – and incorrectly – scrawled BBS number from a buddy at school instantly grew.

    I set my fingers flying across the keyboard once again. “Sorry, but this number isn’t a BBS. It’s the number for a private individual.”

    I waited for a response.

    It came. “ya so”

    Apparently the mystery tween was also a smartass who didn’t have a shift key or a grasp of punctuation. The latter two, while irritating, I could forgive. The first one, not so much… So, not really having patience for that sort of thing – I was young, remember…not that I have all that much patience for it now either, but I was much worse back then – I control-keyed myself over to the command menu and disconnected the call without bothering to type an answer.

    Now, the thing about modems is this – they only do what they have been told to do. And, back then (even today for that matter, though it is far more transparent than it was in the good ol’ days) you would generally tell them to do something with what was called an “AT” command. Why? Because all commands started with the letters “AT” of course, which more or less stood for “ATTENTION”… So, it was pretty much “Attention modem, do this” – although it took the form of commands like ATA (Attention modem: Answer) or ATS13=0 (Attention modem: set bit on register 13 to zero – essentially “off”… binary and all that jazz…)

    My point here is that with the exception of telling the modem to disconnect the annoying a$$wipe kid who was connected, the last thing I had told the device to do was initialize in the Auto Answer mode. Since I had not “reset” any registers, as far as it was concerned, it was going to answer the phone.

    So, when the phone inevitably rang again, it did what it was intent on doing.

    I suppose I could have picked up the phone, or  quickly entered a re-init code before the third ring had sounded, but I didn’t. I just muttered, “Little f*cking bastard,” and sat there as the system connected and warbled through a fresh protocol negotiation.

    The screen cleared and I was faced with “hello” once again.

    I keyed in, “Don’t you have anything better to do?”

    “no” was the response.

    I typed back, “Some of us have to go to work in the morning.”

    “ya me to,” my mystery caller laboriously returned. (BTW, I am misspelling my mystery caller’s entries as close to the way they were misspelled as I can remember.)

    I raised an eyebrow… Okay, either I had an adult or a lying tween. I was leaning toward lying tween, but one never knew. You still don’t these days. Susie Silky Thighs in the hot sex chat room could be a 52 year old drunk guy sitting there in his underwear pulling his pud for all you know. I think there was even a viral video out on the net where someone used that idea for a commercial or something… Yeah, I know… Oh look, a chicken… (I really, really do think that chicken thing is friggin’ hilarious…) Oh, and BTW, I don’t hang out in hot sex chatrooms… I’m married to E K, so why would I bother? My ex-boss did, however, and probably still does… yeah, ‘nother blog.

    So, anyway, mystery caller says he/she has to go to work in the morning too.

    “Okay, so don’t you think it’s bedtime?” I typed back.

    “not yet,” was the reply. “what ar you dooing”

    “Getting annoyed,” I replied.

    “ya”

    I decided to ask the obvious question. “Who is this?”

    “you no” came across the screen.

    I replied, “Obviously I don’t or I wouldn’t have asked.”

    By way of a response I got, “pool open yet”

    This one gave me pause. Obviously this was someone who knew me, or  at the very least knew I had a pool. If it was one of my friends then they already knew whether or not the pool was open, so I couldn’t imagine them asking such a question. I turned in my seat to look around at my windows. The blinds were drawn so I didn’t figure I was being watched, unless this whack job on the other end had X-ray vision or something. I allowed my gaze to linger for a moment on the headboard of the bed where I had my loaded .357 magnum stashed. I considered getting it out and laying it beside the keyboard, but thought maybe that was being just a bit too paranoid.

    “Who is this?” I typed again, none to excited about the creepy stalker feeling I was now getting.

    “i see you tammarow” was the only answer I received before the modem clicked and the call disconnected.

    I sat for nearly an hour waiting for another call, but it never came.

    Before finally climbing back into bed I saw to it that I checked the load on my pistol and shifted it to be within reaching distance if something awakened me unexpectedly… You know, like a psycho killer stalker or something, know what I mean?

    The next morning I was still ruminating over the whole incident, and doing a lot of looking over my shoulder as well. I called all my friends with computer equipment and asked them if they were screwing with me, to which I received believable answers to the negative. I told my co-workers about it and even a couple of my regular customers who had become slightly more than acquaintances but not quite good friends. They all agreed that it was a bit weird, and one even suggested I contact the police. Of course, even then I knew better than to believe the cops would do anything about it. I mean, after all, what could they do other than take a report? That way there would be a paper trail when my corpse was found hanging from a swing set in the park with my hands chopped off, or some oddball crap like that.

    Yeah… big help…

    It was sometime after lunch – mid afternoon as I recall – when Scott Ruddle wandered into the store and listened to me tell the story.  (In case you are new here, or don’t remember previous references to Scott, he ended up being my best man when E K and I married. He’s also the person upon whom the character Detective Benjamin Storm, from the RGI novels, is based… Yeah, that Scott Ruddle…) So, anyway, this was well prior to the beer can tossing… (see: There I was, Just Sitting By The Pool…) In fact, we had only just recently met and the friendship we eventually developed hadn’t even officially been launched just yet. At this point he was one of those “pretty good acquaintance – semi almost friend” types. As he stood there nodding his head and adding an occasional “no sh*t?” to let me know he really was listening, it suddenly dawned on me.

    I stopped mid sentence and stared at him, then started shaking my head. “You friggin’ bastard,” I said.

    No longer able to contain himself he started laughing.

    And, so began my psyche damaging, sometimes very odd, but lasting and incredibly true friendship with Sergeant Scott Ruddle and his wife.

    Now you know why I’m just a bit addled in the head…

    And, yeah… Now he’s a cop. Like I’ve said before, welcome to my world…

    More to come…

    Murv

  • Who Is This, And How Did You Get In My Computer? PART 1

      0 comments

    What you are about to read is probably going to seem just a bit bizarre. But, then again, all of my blogs have a tendency to read that way, or so I am told. In any event, this is a “two-parter”, and as bizarre as it may seem to you folks as you read it, bear in mind that it is true… actually happened… no kidding… so, imagine how I felt at the time…

    The phone rang and I looked over at the over sized digits on my LED alarm clock. (Yeah, this was back when big, wood grain veneered LED alarm clocks were exceptionally cool and it showed just how amazingly hip you were if you had one…seriously… Owning such an alarm clock wouldn’t necessarily get you laid, but it didn’t hurt…) Even though one of the segments in the display was having a tendency to flicker on and off, probably due to a cold solder joint I hadn’t bother to repair just yet, I had learned to decipher the numbers and know generally what time it really was, no matter what they displayed.

    It read something like 10:38 PM. In this particular case, that meant something like 10:38 PM. Yeah, go figure. The segment happened to be working at that particular moment.

    I sat up,  stared across the room at where the phone was sitting on my desk and furrowed my brow. I couldn’t actually see the phone since the lights were out and all, but I knew right where it was. It rang again and I continued to stare in its general direction. You see, even though I was in my early twenties – like really early twenties – and was all about partying just like anyone else my age, I had to go to work the next morning. I even had to go in early because I was the assistant manager of a VideoConcepts™ at the Northwest Plaza mall and it was my turn to open the store.

    This is not to mention, although I already mentioned it,  that the hour was 10:38 PM give or take a few minutes, depending upon whose version of accurate you happened to be following.

    “Why is that important,” you ask?  Well, because you just don’t call someone after 9 PM or before 8 AM unless 1) Someone is dead, 2) Someone has been in a bad accident, or 3) You’re in jail and need to be bailed out. There are even sub-qualifications, like with #1, if the person who is dead isn’t all that close to the person being notified, then instead of disturbing them that night, you should add them to the list of people to call after 8 AM the next day.  Or with #3, if the offense is so minor that they are just going to spring you in the morning, grab a nap and leave your friends alone. You got yourself into the mess, not them. There is, of course, the “I just killed someone and I need you to help me hide the body” clause, but that can only be invoked with certain friends, so you have to be careful with it.

    In any event, that’s just the way it is. Everybody knows the rules.

    Seriously. Those are the rules. At least, they are in the south, where I am from. I know,  I know… Since I was living in St. Louis I wasn’t technically “in” the south, but since I was at home, it was kind of like a foreign embassy – i.e. when within the confines of that property line you were on southern soil and therefore you obeyed southern rules and etiquette.

    At this particular moment, I was pretty well convinced that I had a breach of etiquette on my hands.

    I continued staring in the direction of the phone. For the life of me I couldn’t imagine who would be calling at this hour. I doubted anyone close enough to me to qualify for any of the pre-requisites listed above was out and about, so I knew there were no deaths or injuries to be reported. And, all I could say was that if bail was involved, someone was going to need to do some fast talking.

    The infernal device hadn’t yet stopped clamoring so I climbed out of the bed, flipped on the light switch then padded around the end of my king sized waterbed to my desk and picked up the handset.

    “Hello?”

    Click!

    “Lovely,” I thought. Well, I’m not actually sure what it was that I thought. I am, however, fairly certain I muttered something on the order of “F*ck you too.”

    I settled the phone back into the cradle then turned around and started back toward the bed. Before I’d made it two steps the  nuisance began to ring again. I turned in place, went back to my desk, and snatched up the handset.

    “Hello?”

    Tick, Tick, Tick… Click… Tick… (silence) Skrrreeeeeee-warble-skreeeeeee…

    “What the f*ck?” I muttered aloud.

    Remember, this was nineteen-eighty-five. Fax machines weren’t exactly commonplace so picking up your phone and hearing a carrier signal from a misdial… Well, that just didn’t happen all that much. (BTW, just as a point of interest – Facsimile Machines – as we called them back then before truncating words became all the rage – were also huge, had a  rapidly spinning drum to which you attached your document, and took approximately 7 1/2 minutes to transmit a single page at low resolution… I know this because we used one at the VideoConcepts™ store to transmit customer credit applications to the corporate office.)

    Still, even though hearing a warbling carrier in your ear wasn’t exactly heard of in that day and age – at least for the average Joe – I had a bit of a clue. I had been working with computers since I was 15 – anything from programming to tech work – when I could get that sort of work, that is.  And, when I had started in the biz, communication between systems was done by acoustic coupling modem. If you don’t know what that is, rent the movie Wargames with Matthew Broderick and watch it. When he dials the phone, listens for a carrier, then plunks the receiver down on box with some foam inserts that look like they were designed just for a telephone handset to fit into… Well, that’s an acoustic coupling modem.

    My point is, I had been around this block. I knew exactly what a modem carrier signal sounded like. However, I certainly didn’t consider it normal that I was hearing one screech out of my personal telephone line.

    Now, in 1985 we had actually moved beyond acoustic couplers. We were using A-D modems – either internal or external – to which you simply plug in your phone. Of course, back in 1985, a speed of 300 bits per second was the norm, and 1200 was high end. 2400 was a brass ring on the nearing horizon.  If all that means nothing to you, I understand… But, to give you a comparison, your average home computer talks to the internet via low end DSL at around 512 – 768 Kilobits per second. High end you are talking about 3 Megabits per second or better. See the contrast? Figured you might.

    But, anyway, the roundabout point here is that I knew very well what I was hearing.

    Out of curiosity, and nothing more, I sat down at my computer, still holding the phone in my hand. I flipped on the monitor, then the CPU and watched the green cursor wink at me from the monochrome screen while it booted up. I was running an an actual IBM model 5150 CPU, but I had pulled a Millennium Falcon on it, and to quote Han Solo, had “made a few special modifications myself.” Yeah, soldering irons, discrete components, and some tech knowledge can get you into serious trouble. So, I was running an overclocked processor and some fast DIP RAM, so my “big blue streak” was pushing about 6.5 Mhz instead of the stock 4.77 Mhz… woohoo… whoa! slow down before you hit something. Again, the perspective thing for those not familiar – the average CPU speed these days is 1.7 Gigahertz or higher.

    Yeah…So you can see what I was dealing with. But, look at it this way. It was 1985 and for its day, that box was lightning fast. Relatively and metaphorically, of course…

    The system finally booted up, to DOS, from diskettes. (No hard drive… I didn’t get my first hard drive for another several months and it was a whopping 10 Megabytes in size and cost me right at $600 with the controller.) Unfortunately, although I had now arrived at a command prompt, the phone had clicked and gone dead.

    I dropped the handset back into the cradle, then slipped a modem communications program diskette into the B drive (I had TWO, count ’em, TWO 5 1/4″ 360Kb floppy disks… big time stuff.) I had only just started typing in the command to execute the program (yeah… we had to do stuff like that back then… no pointy, no clicky… A whole lotta typie though…) when the phone started ringing again.

    Instead of answering it I sat there gesturing at the screen in hopes that doing so would make the program load faster.

    It didn’t, but I still tried.

    The communications protocols loaded, the core of the program bootstrapped, and then finally, the application screen appeared. I cursored down the menu (this was a pretty fancy piece of software) and hit enter to drop myself into the command mode. As fast as I could I typed an alternate initialization string to reset the modem and put it into auto answer mode. When I hit enter at the end of the string of characters, the screen cleared, the phone cut off mid peal, and several lines of gibberish scrolled across the monitor.

    There was a quick screech, then a loud click from speaker on my internal modem, and then silence. The cursor just sat winking at me.

    On a hunch, I “control keyed” myself back to the command mode, reset the modem with the same initialization string as before, then waited. A few seconds later, the phone did indeed start to ring. My init string had included a command to keep the modem from picking up until after the third ring, so I waited impatiently as the old bell on the desk phone rattled, rattled again, and then rattled a third time. As it started to ding a fourth time, it was interrupted and the modem clicked.

    Once again a screech issued from the speaker inside the box, then warbled, then screeched again. A warble-screech-hiss combination followed and the modem clicked again, but it was a different kind of click, and it was one I recognized.

    It was a connection.

    More to come…

    Murv

    … NEXT: Who Is This, And How Did You Get In My Computer? PART 2