<= Weeks -- Comments

Daynotes: Week of 17 - 23 May, 1999

©
This week:
Monday
Tuesday
Wednesday
Thursday
Friday
Saturday
Sunday
 
WikiForum
 
Next week
Previous
 
Top

Daily notes and commentary -- Week 20

* Link to: last modified 23:50 GMT+2 on 23.05.1999

Hi, welcome to this week's daybook page. AnyBrowser

himselfSee the update-link (above) that points where I last added some text, which should simplify your keeping up to speed. Of course, you may still have to scroll back a bit and see if I've updated more than once since you last visited, but that is easily done.

Associated links:

  • Write me at: bo@leuf.com -- if private, mark it as such!
  • Posted mail/discussion, see the WikiForum remoteLeufNet
  • Occasional thematic articles, see "DisISay" remoteLeufOrg

See also the Daynotes index.

©
Monday
Tuesday
Wednesday
Thursday
Friday
Saturday
Sunday
 
WikiForum
 
Next week
Previous
 
Top

Monday 17.05

A hint of the summer that will be...

Let's see. The new ISP account details were in the mail today, so I set out to try out what will now be my primary connection to the wonderful world of the Internet. <configure...configure ... dial and try> Ok, everything worked ok, user ID and password more than usually cryptic, but this can to some extent be changed, and is in any case as a rule set once and forget.

Telia (the main Swedish telco) has I know been expanding capacity, and my initial verdict here is that it shows. Absolutely no hesitation at all during the day. Here callers all dial the same freephone number (nation wide, one for modems, one for ISDN), and the local exchanges transparently route the call to the nearest available modem or ISDN line pool. My previous ISP uses the local number approach, with different numbers for each local call district -- with varying loading effects noticeable, both in the modem pools and in the connections to the servers.

Anyway, the package includes 5 POP accounts, and 5 websites, but I suspect I will not use the latter much. I will be reviewing the email POP and forwarding tree somewhat, now with two separate ISP connections. This has relevance mostly for.administrative purposes, such as domain owner details and a couple of forwarding accounts. You want to keep a couple of email routes open no matter what the situation is with a particular domain or host. Especially in case you want to move domains, the owner account should be external to the domain itself in case problems arise. You want to be able to send properly authorized emails to e.g. InterNIC or a host and receive the replies even if the domain itself should for some reason be down.

I know not a lot of people will have more than perhaps a single ISP with email and website, or a single ISP and an external IPP hosting a website, but consider making a proper dependency tree of how they interact. It can save you problems when settng up or changing forwarding or registrations some day. An example:

  1. Primary ISP dial-up (3 x POP)
    1. UserID1@ISPcom.net
      -- InterNIC domain owner for mycom.com
      |__(email forward from)
      • UserIDxyz@freemail.net
      • UserID123@mymail.com
        |__(email forward from)
        • user@freeweb.com (free website owner)
    2. UserID2@ISPcom.net (e.g. wife's account)
      |__(email forward from)
      • UserIDabc@freemail.net
        note: member of mailing list mem-jokes@laughs.org
    3. (not activated)

    .

  2. Work Internet account (intranet)
    1. userID1 (no forwarding, intranet only)
      • internal distribution lists
    2. userID2 (no forwarding, externally accessible POP)
      |__(email forward from)
      • UserIDpqr@bizgroup.net (conference)

  3. ...etc.

Set this up as a local webpage on your system, reached only from the local overall contents page you can set up to access your local website copies, and you can review and plan changes.

Make another section giving a similar overview of the different webpage sections and their structure., and set up local hyperlinks between website structure, email accounts, and other relevant items (mailing lists and userIDs for these, services, changes). You'll end up with a page that shows you at a glance where you are. More importantly, you will see which things can be changed or removed freely, and which are critical to your flow of e.g. email. (It is easy to overlook that a legacy account was used to register a service or mailing list.) This may also suggest weak links and alternatives, if important forwarding goes through an unreliable intermediary.


©
Monday
Tuesday
Wednesday
Thursday
Friday
Saturday
Sunday
 
WikiForum
 
Next week
Previous
 
Top

Tuesday 18.05

Spent most of the day (and evening) seriously writing on a core chapter of the Outlook book, attempting to rework the sample chapter material into the current understanding of the consistent format and content we want/need.


©
Monday
Tuesday
Wednesday
Thursday
Friday
Saturday
Sunday
 
WikiForum
 
Next week
Previous
 
Top

Wednesday 19.05

More serious and concentrated writing, expanding the material in the core chapter, like yesterday only more so.

More later... maybe...

(Nope, guess not :)


©
Monday
Tuesday
Wednesday
Thursday
Friday
Saturday
Sunday
 
WikiForum
 
Next week
Previous
 
Top

Thursday 20.05

Just had a new, larger HDD delivered for my system. Ordered it Tuesday afternoon via my distributor's online shop. Everything is just a click away... la-di-dah...

Toshiba 2.5", 6495 Mb, "Super Slimline": just a tad over 8 mm thick, or should I say thin.

Geez, this has to be the cutest little HDD I've seen yet! (I know there are smaller drives around, e.g. the PC-card ones, and IBM has been researching really high-capacity 1" drives, but I have not personally handled anything smaller/denser than this new 6 Gb unit. Awe-some...) The tiny thing was safely tucked into a foam pocket in the center of a 1 cu-foot delivery box.

I wonder when they will start sending out HDDs as breakfast cereal box prizes? ("Oh, look mommy, the Crunchy Bogglies box has a 14 gig drive in it this week! Please? Can we??")

Ok, that's my project for the (long) weekend, apart from a number of birthdays (wife, brother-in-law and mother-in-law) -- to migrate what's on my current 2 Gb drive to the new 6 Gb one. Finally, I will have adequate space for a decent Linux installation.

I will report on this migration when start, because it is not exactly a trivial. task

I run a notebook system, in the US known under the label Prostar (in the UK as something else, I forget what just now), and here as a Best system. I described it in more detail last year -- overall description and article written when I bought it.

The reasons for the perhaps-problematic migration?

  • Despite the manual's assurance that I can slide in a second HDD instead of the FDD, it seems that I cannot buy the tray for this, and it is unclear whether the current system will accept a slave IDE in this way.
  • T-connectors/extenders for 2.5" IDE are not available here, otherwise I could jury-rig something in the main HDD tray (both drives are slim enough together that this ought to work, or failing that, temporarily extend the IDE bus the maybe 15 cm needed to run one drive outside the case).
  • Support recommended an "external HDD cradle". I'm not sure if they mean something related to the port replicator accessory, which I would also need. Too expensive by far.

So much for hardware. The "softer" approaches would be to:

  • Re-install everything from zero.
    • - Naw, too simplistic. No sport. :)
    • - Several stages because of applied patches.
    • - Must dig out all the registration codes and original disks/CDs, and not forget the web-downloaded packages or the links to these versions!
    • + Fresh registry. "Clean" setup.. (But complicated installs and patches churn registry a lot and make new problems, and refragment a lot. Zero-sum gain?)
  • Make fresh backups and restore from this.
    • - NT backup goes via tape. Don't have tape.
    • + Could backup everything from Win95b, of course (everything is on FAT16 partitions).
    • - File-by-file Windows 32bit backup is problematic, as noted in an earlier Daynote (week 10), because of the way long filename support is dynamically tacked onto 8+3 DOS-style real filenames... Oh, Waltzing Ma~, come waltz with me :).
  • Make partition-backup images and restore partitions one by one from this, then use Partition Magic to adjust and tweak to fit the new drive capacity.
    • + Holds a certain attraction. I think I will try this. I have a 1 Gb SCSI-in-a-box that I have used as backup and transfer between my various systems. This can be used to move (compressed) partition images between swapped drives in the notebook.

Oh well, something to write about. I will keep you all posted.


©
Monday
Tuesday
Wednesday
Thursday
Friday
Saturday
Sunday
 
WikiForum
 
Next week
Previous
 
Top

Friday 21.05

Couldn't help myself, I started moving from the 2 gig to the 6 gig disk last night. It did not quite go as planned.

The reason Windows NT is so stable is that it forces you to reboot so often. -- a past-midnight reflection

I'll start at the end of the story so far:

  • The ERD utility now informs me that there is not enough space on a newly formatted 1.44 diskette to save all the system repair files. Interesting. Then what?
  • I have all the main working partitions transferred this afternoon and can go back to work. Phew.

The bare progress notes:

  1. Swapped in the new IDE(2). Gigs of virgin media... With PartitionMagic, I then set up the pre-planned partitions: Win95b, Linux, NT, Apps, swap, Web, and a number of "spares".
  2. Swapped back to IDE(1). Discovered that the proposed partition image would not perform as required.
  3. Think, think, thunk...
  4. Plan B: Use Win95 Backup. If I ran into any 8+3-tilde issues for my NT system, I could if need be resolve them manually, from a the fresh install of Win95b. (All FAT16.)
  5. A few hours pass with icon-papers being tossed from icon-drive to icon-drive, as thousands upon thousands of files get scrunched up into QIC files on the external SCSI. One file for each major partition.
  6. Swapped to IDE(2). Install of a fresh Win95b from CD. Hmm, this was the beta-build. Ok, "restore" from the fresh IDE(1) backup of C (updated build). More time passes with icon-papers being tossed from icon-drive to icon-drive.
  7. Reboot. The restored version works. For a while. Crashes. Restarts, ok a while, then crashes. Then it refuses to go anywhere but fatal exception on kernel start, safe mode or not. 1 AM -- Use PartitionMagic to kill C. Find the other install, build 1111, and install this. Stable start. Ok, enough for one night (2 AM) -- zzzZZZzzzZZZ.
  8. Next morning, "restore" the NT and Apps partitions. More hours pass with icon-papers drifting from icon-drive to icon-drive.

Now came the interesting part: how to quickest set up the bootloader for multiple OS.

  1. I fired up the NT install CD. This installs a temporary NT kernel and the bootloader when e.g. Win9x is present.
  2. Exit and look at the file boot.ini in the C root.
  3. Replace with boot.ini from IDE(1), copied to the SCSI of course. Won't boot -- can't find the kernel loader.
  4. Hmm, D is a different physical partition number on IDE(2).
  5. Make boot.ini writable, never mind the system flag, and edit the number ...partition(2)\WINNT="...
    • the elegant method, figure out what number it should be -- turned out to be wrong of course.
    • the quick method, copy the menu entry n times with increasing numbers -- reboot and select each in turn until NT loads.
  6. Bingo. NT is alive and well!
  7. Re-apply SP4 to update the CD's bootloader version.
  8. Make valid repair disk -- the note I started with.

The rest is optional :) I have a couple of QIC files and other folders left on the SCSI to "restore". I will probably ignore the backup Win95 version for now, and reinstall the games using the fresh version. The IDE(1) system is admittedly a later build, but has for various reasons a somewhat checkered registry history. I suspect that the 8+3 alias problem hit this, rather than the NT system. Mainly, I don't feel like putting any more time on it.

Speaking of registry, the NT registry is currently 9 Mb and ERD warned me that I had to increase the allocation for this (from the 14 Mb default max). Before it died on disk creation. I should perhaps see if I can shrink it some. Another project, another day.


©
Monday
Tuesday
Wednesday
Thursday
Friday
Saturday
Sunday
 
WikiForum
 
Next week
Previous
 
Top

Saturday 22.05

Something every computer-enhanced male runs into at some time or other, usually recurringly and severely, is the complaint that he is "always" at the keyboard. This can come from family members (especially wife or girl-friend) or friends, but is almost invariably from the female of the species. (My son for instance never complains about this, except when my being at a particular keyboard prevents him from being there! Usually, however, he is too busy at another system... My daughter on the other hand, despite being just as adept on the computer, will. -- Both of me and her brother.)

What this is, is simply a female call for attention. Heed it, whenever possible (even though I know that this may be both difficult and inconvenient), because it is also invariably the expression of a longer period of pent-up discontent. Do not, repeat, do not try to argue logically about the issue, citing balanced working hours statistics or time spent doing things other than computer work, or that she spends more hours on the TV. It is not a logical need that must be addressed here, not a balancing of equal hours, it is an emotional and social need. And one that needs attention right then and there, for it not to become a much more serious problem.

I hear this complaint expressed from many directions, and my wife assures me that everyone she knows who has a computer-active husband or boyfriend has often complained of the very same thing.

Both sides of this divide need to understand something of the background for the contention. Computers are wonderful toys, both for fun and pleasure. One of the traits in males that females find attractive is our capacity for focus and commitment, since this after all is often what makes him pursue her in the first place and settle down to loyal and providing family life. Unfortunately, this same trait will keep him at a keyboard in front of a screen for many hours too long, oblivious to the signals that he should maybe be interacting with her just then.

Look at it from another perspective. She will think nothing of interacting socially while doing several other things at the same time, even while watching TV. He is generally incapable of this kind of social/practical multitasking. -- When working, he must concentrate fully on the task at hand, often until it is completed to some definable stage of satisfaction. This can take hours, days, weeks, ... Until then, he does not want to be disturbed! During such times, she will feel ignored, even rebuffed, and bottle this feeling up far too long before expressing it.

Now it does not matter whether the computer task at hand is work, games, surfing the Web, or just the recurring maintenance involved in keeping a wintel system useful. And there are always things he wants to do with the system; new programs to investigate, tweaks to apply, and so on.

In all these cases, he will strongly radiate the do not disturb signals -- it is in his nature to do so. And he can get quite testy about distractions that break his focus.

If you have occasion to watch a girl and a boy play the same computer game, the difference is as a rule quite marked: he is totally focused on the game, she wants to share the experience. In fact, without the social sharing aspect, the game quickly becomes boring for the girl. This is but one reason why girls are less interested in computer gaming -- there are few games that encourage social sharing, while there are many that cannot be played successfully without total concentration for long periods of time. Most games are also designed by males, so no wonder.

Anyway, I read recently a serious reflection (interestingly by Howard Rheigold, founder of "the Well", that ur-web community) that was more than a little insightful into the oft-cited but little-understood Amish attitude to technology. Amish folk are not against technology as such, instead they carefully weigh the potential influence that using the technology may have on the social interactions in the family and in the community. On the whole, much of modern technology has been judged detrimental to the community. These attitudes are in constant flux and discussion, however, so that for example cellular phones are, at least for now, accepted in large areas; the view being that these do on the balance promote community communication in a way that the ordinary telephone does not.

Rheingold's. point was that we should all reflect more on how our lives are affected by technology, and how its use either promotes or disrupts our social interactivity. This is especially valid in the small circle of family as we become more tied up with computers and "home entertainment" systems in general. We should all make constant efforts to keep the personal touch alive, and focus, at least from time to time, on real-world, liveware, interactions.

Think about it.


©
Monday
Tuesday
Wednesday
Thursday
Friday
Saturday
Sunday
 
WikiForum
 
Next week
Previous
 
Top

Sunday 23.05

(Whitsun)

* I got in a few hours of serious writing today (while Tom recovers from his flu with frequent doses of hot dual-Pentium <grin>). Otherwise the evening was devoted to my wife's and bother-in-law's birthday (twins).

System running smoothly, with lots of empty disk space for a change. Remembered to jot down a few system notes detailing the changes made. I also upgraded Pegasus Mailremote to the new v3.11, while still checking out the more obscure features of Outlook.


© remote
Week list

All original material Copyright 1999 Bo Leuf.
Comments and discussion welcome (bo@leuf.com).


Back to top -- Week list