© |
Daily notes and commentary -- Week 24* Link to: last modified 12:40 GMT+2 on 23.06.1999
Hi, welcome to this week's daybook page.
Associated links:
See also the Daynotes index. |
© |
Monday 14.06Whew! Today (and yesterday) ended up being somewhat stressful in that the editing of our two chapters just seemed to go on and on -- as did distractions galore. Our editor is suggesting further rewrites, and I really hope we quickly reach a consensus soon on a content so we can move on to the other chapters. One weird incident during the day occurred when I went from one phone (talking to my brother-in-law) to another (a call from my co-author Tom), when the first phone rang again. Edward, our son, answered. After a while, I began to get distracted from my conversation with Tom and had to finally ask to get back to him, because I could hear that Edward was having problems. Finally he burst into the "office" quite upset, saying that this man was threatening him with lawyers and really telling him off. I went in and took over the call to figure out WTF this was. After some language confusion, I discover that this was apparently some sales representative to a Swedish company with offices in Malmö, who was at a trade fair in Germany, and who was furious at us for calling him in the middle of important business meetings. Say what? This was absurd, but he was initially not listening much to any denials, only demanding to know who the hell we were, and ranting on about how this was really making a mess out of the most important trade event in 6 years. Eventually, the situation clarified. This man, a Swede, had been getting constant calls on his mobile, many times a day, for the past six days at the trade fair. In his meetings, he had the phone turned off for calls as such, but it would still "beep" loudly and present the calling number for him to evaluate if it was important enough to break off and answer. The number, it seemed, was ours, and being unknown to him "not important", but increasingly aggravating. Finally, his patience wore out and he phoned the number and blew up the first person who answered. In due time he wound down to an apology, but we could not figure out why he kept getting "our number" as the calling party. My initial suspicion is that the number may have been "ours" right, but wrong area code, but he was not terribly receptive to suggestions or even letting many words in edgewise in his tirade, so I didn't insist. It's not the first time that this sort of thing has happened, i.e. people phoning what they assume to be a local number, but forgetting to check the area code. He claimed that calls to his Malmö number were being forwarded to his mobile, so what looked like a local number he assumed was originating from Malmö. Hmm, I wonder. Maybe some other office was forwarding calls too, or the exchange was stripping the area code -- I really don't know, but the whole episode was quite surreal.
|
© |
Tuesday 15.06Lacking a back porch (hi Tom) to improve my pale complexion, I spent most of the afternoon out on the town with my daughter (while wife was cycling with son). Starting to feel like summer -- about time too! Mainly, I too needed a breather from intense editing, away from screens and keyboards. Hence, this is just a short posting before another day.
|
© |
Wednesday 16.06My nagging Windows 95 sound problem got solved today. Having nothing better to do <grin>, I decided to take another look at the situation and so booted up into Windows 95 -- Gee, that was a long time ago... :) Being that this was a recent re-installation, there was not a lot apart from the basic bare bones system. There were still a number of "!"-marked devices left since the DirectX debacle, and the sound sub-system was at root complaining about an IRQ conflict. Originally, there had also been complaints about DMA and memory, but these had been resolved in earlier attempts. My notes on this were terse but clear. The IRQ problem boiled down to the fact that although this was the exact same hardware configuration as I had used earlier, i.e. on the original harddisk before I swapped for the new larger one, there did not seem to be enough IRQs to go round now -- which on the face of it seems ridiculous, and at odds with the fact that this particular installation had seemed fine until installing Seven Kingdoms and DirectX broke the sound. This time.I thought of working at it from another angle, MS software sometimes being amenable to negative logic. So I started as far away from the sound sub-system as possible, i.e. the "unknown" device that has never properly identified itself, but which I strongly suspect may be the USB. After examining the two "unknowns", one of which this time clashed at IRQ9 with sound, I simply removed this device from the list. Applying the reboot mantra, the system came up and detected a new device, and promptly installed another incarnation of the sound driver. Non-functional, of course, and now I had two "!"-marked sound devices, whoopiedoo. Ok, I then removed the previous and now duplicate sound device entry, reasoning that the new install might be more correct, Windows 95 this time having selected the PnP-version driver (which it hadn't on original install). Reboot again. This time we came up in desktop to a resounding "Ta-Da", i.e. sound was functional. Phew... Subsequent installing of games worked normally. The kids were greatly pleased.
|
© |
Thursday 17.06(travel day -- there may be no update today)
|
© |
Friday 18.06Good morning all. Yesterday's travels started in hot sunshine and ended in downpour, but the morning is back to sunshine, albeit still rather on the cool side. I started the day by setting up the notebook and seeing what the connectivity was like. It's back to the normal modem card while away from home, and the already "essential" ISDN, but there were no problems. In my mail, I had a curious message from Frank A. Love, that I had Greek on my site. I post the mail and my reply on the wiki, and comments are as usual welcome.
|
© |
Saturday 19.06Most of yesterday was spent offline, in the RealWorld. I did pick up a few computer-related items in a shop we passed by during the day. One thing I had been lacking was a joystick with the 15 pin d-sub plug that would fit my notebook. Obviously, one does not want to travel with any of these "power" sticks that are all the rage, because pretty much anything game-input-related on the shelves these days takes up more space than the notebook itself! However, I found this diminutive "powerpad" for an equally diminutive price, which seemed to fit my requirements admirably (Champ PowerPad 100). There is a "thumb" joystick on the left of an oval box with a screw-in stick (without which you simply have a directional thumbpad), and an assortment of buttons and autofire switches to the right. Because there were a couple of games along for this trip that could use a joystick of some kind, especially PlaneCrazy, this seemed an excellent buy. Real gamers may scoff in disdain at such a "toy", but it has the desired virtue of slipping into a side pocket of the notebook bag with no fuss at all, and provides the functionality needed. It was easy enough to configure in Win95 (2 axel, 8 direction, 4 button). Apart from some oddity in Jedi Knight - DFII that caused a continuous slow turn-to-right, emulating a somewhat drunk knight in the inn :), which I suppose can be a configuration thing, it worked well elsewhere. I might mention another "stick" for the same price found at the same shop. This was designed to clip on over the inverted-T arrow key set, and provided a stick, which when moved depressed these accordingly. Hmm, that's pretty damn basic. It might have been interesting for a far lower price than demanded (about USD 12), but there was no doubt which was the better buy here. Today is a party day, as a good friend is celebrating her 40th.
|
© |
Sunday 20.06* The day rained away, and I got buried under a rewrite of a section of one of our chapters.
|
All original material Copyright 1999 Bo Leuf. |