Daily notes and commentary -- Week 39* Link to: last modified 19:10 GMT+2 on 3.10.1999 Hi, welcome to this week's journal.
These pages best viewed with
Associated links:
Earlier weeks, see the Daynotes index. |
© |
Monday 27 SeptemberThis afternoon I followed my co-author's advice to after a prolonged effort grab a beer (or was that a bear (growl!)?) and go off to the back porch to contemplate one's place in the universe, but I stopped short realizing that I didn't have a back porch. About then things started to seem, well, a bit fuzzy around the edges -- a bit like when the transporter coils get misaligned or the holodeck malfunctions. I found a horizontal, padded surface -- my bed I believe, and returned to consciousness only many hours later. 9 p.m. to be precise. Feeling somewhat better, I staggered up and took my temperature, just to verify from where the heat wave was coming. Yup: well over 38C -- which for me is pretty serious. The family joke around here is that when I'm feeling poorly, I have "thirty-sick-point-sick", since I rarely go over 37.
Anyway, I have some fragmentary memory shards from the day... I
pretty much finished the chapter I was working on this morning. I also caught
an interesting item in the news about Antarctica. Hmmm... a quick search
and
here
is the full
article
They figure that the lake was isolated from the rest of the environment about 2 million years ago. (Though I take that with a pinch of salt, since there is no real consensus on the age of the antarctic ice cover. The ice cores of the region have been dated back to about 200,000 BP.) BTW, the October 1999 issue of Scientific American has a feature on Europa's oceans. Another interesting read from yesterday was an article about fuel cell technology, recent research being focused on miniature cells suitable for cellular phones and notebook computers. Intriguing thought to be able to pour in half a liter of methanol in a computer "powerpack" no larger than today's battery packs and run the notebook for 100+ hours straight. One envisions small ampoules you could buy in packs at the local shop, and stick one in the phone to provide a week's standby and perhaps 20 hours of talking. Related article: SciAm July 1999: SPECIAL REPORT The Future of Fuel Cells (quick summary)
|
© |
Tuesday 28 SeptemberFever-induced fantasies...
Gah! I hope to get back to you all with something useful later in the day.
|
© |
Wednesday 29 SeptemberMatt Beland commented the yesterday's entry with a message that simply said:
The turf is always greener on the other side of the web. How about this profound thought instead:
Kind'a makes a guy wonder... Anyway, seriously, grammar and style are bottom-line determined by "consensus" current usage -- and if current usage is anything to go by, grammar and style have really gone to the dogs. Clearly, we could use some new html content tags here: <ui>, <gi>, <pi>, <ti> come to mind. (usage incorrect, grammatically incorrect, politically incorrect (aka please ignore), and totally incorrect)
|
© |
Thursday 30 SeptemberI've been coughing my guts out the past few days, and this coupled with the fever has cut deeply into any productivity, including web updates. Just for a change of pace, our daughter became really ill last night. Oh joy... Isabel took the worst of it, staying up a larger part of the night.
Yesterday afternoon, I managed to process all the
end-of- I was looking at www.syroidmanor.com earlier. Some nice features, but as I wrote to Tom, "I would have to add to the choir that I generally dislike white-on-black -- and I don't care that some say that this is the most readable color scheme for LCD displays, such as I use -- in fact I disagree." Something I had on the legacy Atari/Falcon machines was a software toggle that could switch from black-on-white to white-on-black -- actually inversion of colors in case I was in yellow-on-blue, something I preferred when working evenings with a CAD program (that had its own toggle). Line drawings were in a dark ambient lighting easier to work with when one could periodically swap color schemes like this. Even writing text could be less tiring with periodic swaps and lighting changes (some wp still provide a white on blue option). That particular issue has however receeded as displays have got better and given higher color and resolution capability. I could probably figure out some way of doing this on the PC, but e.g. swapping Themes is so incredibly slow with several app windows open. The Opera browser with its "toggle document settings" is however the next best thing for web context. Partly I can disable the webpage settings (and so toggle white-on-black to black-on-white, albeit I lose formatting info as well, partly I can set up local CSS sheets for preferred format. The latter would be much more useful if sites used CSS consistently in a way that really was cascadable.
|
© |
Friday 1 OctoberThe day was consigned to the dustbin of history, so I spent part of the day watching the historical dustbins of others -- i.e. the news. The nuclear power sector in Japan is looking pretty battered at the moment, but Japan is of course highly dependent on power generated in this way. I see figures like 30% quoted. But that is actually a minor worry, because the ripples in other sectors are more interesting. Hitachi apparently had to close 12 plants in the region during this incident, and the consequences of that are only now beginning to felt downstream in the modern JustInTime supply chain. Factor in the Taiwan earthquake, and we are getting major disruptions in the semiconductor business. This is not the cost-optimal time to be upgrading memory. Informed guesses suggest that Q2 next year is when prices will come back down to normal, assuming nothing else happens to screw things up further... Y2k, West coast US quake, etc. Western Digital issued a recall for almost half out of a million unit production run of drives. Defect chip can cause a failure of the drive after a few months use. Nasty. Once, I heard good things about WD drives, but the few I tried then (92) were failures in the context of where they were to work -- couldn't disable parity check on the data bus. Actually, what bothered me most about them was the surprising noise level as they spun up. I never tried WD again.
Neat! O'Reilly made the cover art for the book and our editor sent us a capture of it. Adds a certain extra dimension to what Tom and I are doing, to see a cover layout with our name on it.
|
© |
Saturday 2 OctoberSlow start to the day. Some cleaning, but not enough, so tomorrow sees a continuation plus wash day. Despite the dark and threatening clouds, and a stiff wind, we made a sort of outing during the afternoon. One issue was to pick up some kind of solid branch to make an interesting scratching pole for the cats. Our wallpaper has been suffering a lot lately. Bob Thompson mentioned a DMA-check utility on his site, which reminded me of this easily overlooked detail. I had reflected only the other day that my system tended to feel somewhat sluggish lately, but put it down to all the temp file clusters generated by Word. However, when I ran Dmacheck, it reported that DMA was turned off. Aha! I "turned on" this feature, which simply tells NT to try and detect and use DMA instead of PIO on the next reboot. Sure enough, things were much snappier afterwards, more like what I expect from a machine of this capacity. Several intriguing bits of news today:
I've noted that my server is receiving some pummeling lately by extensive robot probes -- probably an email-address scavanger ("miner" is too neutral a word). This is bad for two reasons: it could block legitimate visitors, and the scavanger ignores robots.txt. The latter is particularily resource costly, because it means that the robot is hitting the wiki servers thousands of times in rapid succession. One of the wiki links is the title at the top, which starts a fulltext search of all pages. Spawing a whole set of such searches, one for each page hit, can really bog down the server for a while. I have changed the functionality of this particular "backlink" search to deny it to such robots, without making it more difficult for legitimate users. Actually, it becomes easier, since you see a button labled "Backlinks" instead.
|
© |
Sunday 3 OctoberThe trouble with weekly timekeeping is that one barely registers Monday before one has already reached Sunday. This week has been especially bad because of the fever and cough haze. A number of things that should have been done were simply pushed into next week.
The week's site worthy of mention is still relatively little known
The 1999 Ig Nobel Prize
Winners
Anyway, the different awards this year were:
Do visit the site and look back on previous years' awards as well.
* I spent a fair part of today redoing some of the screen captures from the chapter I just finished rewriting. Tom wrote me after his first look at it asking if there was any particular reason I was doing the captures in black and white. Gee, no... oops. Somehow the save settings on the capture program had shifted into 4-bit gray-scale instead of the 256-color mode that was required. I hadn't really reacted at the time to how gray the shots were. Unfortunately, some of those shots were kind of "cunningly crafted" and optimized to show numerous interesting features. And since this was about Outlook's Calendar component, everything was tied to specific, now past dates. As you can imagine, I had to drag around and recreate a number of example appointments, and also reset a few reminders to get back something close to the same contexts that I had so carefully set up. Even so, there were some changes required in the text because of the way the new captures turned out. Anyway, the extra work was perhaps useful, because I could make a few improvements in the new versions, and it also gave me an excuse to do the image filelist that should go with the chapter.
My NT no longer creates Emergency Repair disks. It appears that the system configuration file SOFTWARE is too large (7+ Mb, over 1.3 Mb compressed) so that the repair utility just reports disk-full when trying to create the diskette. I've seen a couple of tips on how to "compress" your registry, but as I recall, they were all arcane manual operations characterized as moderate-to-high-risk. Absurd. RegClean finds nothing wrong with registry, and I have heard of many who have larger registry hives than I have (10 Mb total of 19 allocated) -- 20-30 Mb are figures I've seen. Unfortunately, I have no idea if they can create a repair diskette or not.
|
© |
All original material Copyright 1999 Bo Leuf. |