Rod Speed said:
[snip]
The last time I was at Fry's I happened to notice that
they sell SATA removable drive bays and I think they
sell external Firewire and USB hard drive kits.
Thats the route I would take myself, that last, if
you do want to put the drive in a fireproof safe.
I prefer the other approach, dont bother to put full
drive backups in a fireproof safe, just write the stuff
that is irreplaceable to removable media like CDRs
and have one copy offsite. If the house burns down,
I dont care if I have to do a clean reinstall of the OS
and apps, thats a pretty small amount of work compared
with the hassle involved in replacing the house etc.
I live in an apartment. Re-installing all of my aps would be one of my
biggest hassles if my apartment burned down.
Incidentally, my fire retardant safe (one of those ice cooler-sized
boxes from Sam's Club) came with a note saying that it is not safe to
store temperature-sensitive materials in it. Things like photographs,
pearls and compact disks would likely be ruined by the heat in the
safe caused by a major house fire; the paperwork that came with the
safe specifically lists those items as outside the intended scope of
the safe. The way these safes work is that the heat of the fire
actually melts and seals the external, plastic case of the safe. I'm
hoping that metal- or glass-based objects (hard drives) would fair
better, though the plastic parts might be a problem. In any event, the
safes are only really intended to protect paper documents and maybe
metal valuables.
So, I made a special Christmas CD a few years ago that contained all
of my photographs, and mailed them to several of my friends and family
members. Odd, no one wrote me thank-you cards...
[snip]
What makes sense changes over time. Tape has passed
its useby date for personal desktop systems now.
I agree, but, unfortunately, I don't have any other copies of some of
the files stored on my tapes. Nothing on the tapes is worth spending
very much money to recover, but I still would prefer to recover it, if
possible.
[snip]
There's plenty of decent boot managers around.
Which would you suggest?
[snip]
Sure, but thats an entirely separate issue to removable drive bays.
The nice thing about the removable drive bay is that I don't have to
crack open my case, unplug my cables and cords, unscrew the old drive,
screw in the new drive, re-connect the cables and cords and button up
the system. I simply unlock and remove my drive.
[snip]
Mindless bigotry. And you aint even using their non toy OSs.
Hah, I like the story of the Navy ship that was configured to run on
MS Windows NT-based computers, only to be left dead in the water when
NT crashed! I'm a Navy veteran, too.
**********
"'This is the only time this casualty has occurred and the only
propulsion casualty involved with the control system since May 2,
1997, when software configuration was frozen,' Vice Adm. Henry Giffin,
commander of the Atlantic Fleet's Naval Surface Force, reported in an
Oct. 24, 1997, memorandum.
"Giffin wrote the memo to describe 'what really happened in hope of
clearing the scuttlebutt' surrounding the incident, he noted.
"The Yorktown lost control of its propulsion system because its
computers were unable to divide by the number zero, the memo said. The
Yorktown's Standard Monitoring Control System administrator entered
zero into the data field for the Remote Data Base Manager program.
That caused the database to overflow and crash all LAN consoles and
miniature remote terminal units, the memo said.
"The program administrators are trained to bypass a bad data field and
change the value if such a problem occurs again, Atlantic Fleet
officials said.
"But 'the Yorktown's failure in September 1997 was not as simple as
reported,' DiGiorgio said.
"'If you understand computers, you know that a computer normally is
immune to the character of the data it processes,' he wrote in the
June U.S. Naval Institute's Proceedings Magazine. 'Your $2.95
calculator, for example, gives you a zero when you try to divide a
number by zero, and does not stop executing the next set of
instructions. It seems that the computers on the Yorktown were not
designed to tolerate such a simple failure.'"
"Software glitches leave Navy Smart Ship dead in the water"
http://www.gcn.com/archives/gcn/1998/july13/cov2.htm
**********
Hrm, Microsoft's Windows NT was one of the non-toy OSes, which
currently form the basis of Windows 2000 and Windows XP... Of course,
Microsoft said it wasn't really their fault. That's because Bill Gates
cannot take responsibility for his failures.
I think the comments of an IBM rep (who happens also to like
Microsoft's software a lot) are worth considering. He says that one of
the advantages of the AS/400 computer is that it keeps its data stream
separate from its application stream. Microsoft typically does not,
and it always comes back to bite the user. No software system can be
professional unless it keeps bad data from overrunning application
data; there is no excuse for buffer overflow exploits. There is no
excuse for software that does not gracefully handle processing errors.
Unfortunately, software vendors--and Microsoft is a big one--get away
with selling ill-conceived code, which the public assumes is
high-quality code.
In most cases, you are correct! That in no way negates the fact that
today's software is just so much toy code, masquerading as
professional software. The most generous name I could give it would be
"experimental." Microsoft has long sold beta software as debugged
code; that is common throughout the software industry. For a long
time, Microsoft kept quiet about known issues, until exposed by
outside agents. Recently, they have announced that they are going to
start dealing with these issues, instead of waiting for them to become
a problem before dealing with them.
There was a time when software was written by physicists and other
highly-skilled, careful professionals, whose goal was producing
quality code. The modern business model values quantity over quality.
It is far more important to churn out multiple releases of buggy code
than to turn out any number of releases of rigorously-tested code.
There is a reason that our air traffic systems are 30+ year old, and
it isn't just because of money.
These things I've mentioned are also mentioned in various trade
journals. It has been noted that code burned into hardware often is of
higher quality than code written for sale directly to the public.
Intel had that Pentium bug several years ago; you don't find very many
errors like that in their product.
Now, there are a lot of computer-savvy people who defend Microsoft on
almost every issue I put forward. But, these folks have always had (in
my experience) an ulterior motive, which they usually admit freely.
They like Microsoft because quirky, buggy software means job security
for the techs who service it. I knew a systems administrator who
admitted that he thought it was great that Microsoft's networking
software required specialized training to maintain, because it kept
his pay high. The high tech industry is not where I would have
expected to find Luddites, but that is what many computer industry
techs are--Luddites!
[snip]
OK, here's one for you.
I have a 20-Gig Maxtor hard drive with Windows Me on it. I also have a
30-Gig Seagate hard drive with the same version of Windows Me on it.
Both worked in my old 800 MHz Duron machine (the one with a removable
drive bay). But, my 30-Gig drive won't work in my new Athlon 2200+
machine. It isn't the removable bay(s), because I completely
disconnected the removable bays in my new system, and connected the
30-Gig using a standard, flat, 80-conductor cable.
The symptoms are unstable and inconsistent booting, usually to a gray
screen, other times to a completely blank black screen. In the former
case, the mouse cursor moves around a gray rectangle. Nothing else
works.
I booted off my Windows XP CD, and took installation right up short of
formatting the disk. On some boot attempts from the hard drive, I was
able to get my desktop icons, but the screen options were
misconfigured. At least half the time, Windows left blank spaces where
file folders would be in a directory, and attempting to open folders
caused Windows to identify them as an unknown file type.
Eventually, I gave up. I made the 30-Gig a slave and booted from my
20-Gig drive, used Norton and McAfee to clean it up, switched it back
to master and installed it into my old machine. It is happy there. I
can boot from it, listen to music, play my videos and generally use it
as I had been doing. What I cannot do is boot from it in my new
computer.
[snip]
So it cant have been that bad.
And clearly it must have worked well enough
for most to have become the most popular.
I said, "polar," not "popular." Windows Me was one of the LEAST
POPULAR of any Microsoft operating systems.
[snip]