what's a callback?

there

*reliable*

(although the

MMUs for

This is precisely what makes me so mad about windows. The PC hardware is perfectly capable of protecting the OS from this sort of thing, but MS simply chooses to not do it right. :-(((((( Having spent >20 years digging around the innards of mainframe OS's, I'm really disappointed at what is passed off as "enterprise quality" today.

Namely, MS can never tell the difference between code and data; they have finally managed to allow worms in jpeg files, something that was once considered to be a hilarious joke. When in doubt, execute it.

John

No, kind of fuzzy on C++, mostly into Java.

Widgets (COM, Active-X) you code aren't part of the DHTML DOM, but can be scripted as if they were.

And how often does Grandma change the hardware in her computer? I don't know about you, but I *know* when I make physical changes to my computer, and would be quite happy to tell it that it needs to re-scan the hardware (USB and the like are obviously a different matter).

Last time I changed network cards on a Red Hat pc, I was informed on boot-up that the network card had changed, and would I like to transfer the old card's settings to the new card? Worked perfectly, even though the cards were from different manufacturers. Last time I did the same thing with windows (w2k), I was informed I had new hardware and the system could look for suitable drivers. Of course, I couldn't download them because the PC wasn't online, as the network card had no drivers. Thus I had to figure out exactly what the new card was - this involved reading chip types and other info and doing web searches (why can't manufacturers put their name and the card type on the board?), followed by a download of around 2.5 MB for a network driver ! This, of course, is too big for a floppy and thus involved split zip files (or I could have burned a CD...). Once I'd finally got the drivers installed and working, I then had to manually re-configure the new card with my old (static) settings.

What was that you were saying about how impressive windows hardware detection is?

Well, sure. What's wrong with that?

But not if the vector is determined at compile time, right?

So I guess I'm not a programmer. OK.

John

Of sorts... even if it's a static vector, as it implements a non-linear program flow back to the "application's" code.

a

Judging by the length of this thread and your post count, I think it's clear which group you're in ;-)

Well, I know from sorry first-hand experience you can't take a W2K drive and plunk it down in a different computer and expect it to work. It's the first time I've ever seen a _red_ Screen of Death. It was some hysterical warning, which boiled down to, "I've Been Stolen! Call Daddy!"

So I booted Slack Live! 10.0, mounted the NTFS partitions, and copied everything by hand. Luckily, I was getting paid by the hour. ;-)

Cheers! Rich

Eh? How did you do that? I've plugged several Win2K drives into new machines without any untoward behavior.

What did they come out of, Dell, hp, or some other "name" brand that puts proprietary crap on their drives?

That's why I now only buy "parts-in-a-box" machines.

...Jim Thompson

--
|  James E.Thompson, P.E.                           |    mens     |
|  Analog Innovations, Inc.                         |     et      |
|  Analog/Mixed-Signal ASIC's and Discrete Systems  |    manus    |
|  Phoenix, Arizona            Voice:(480)460-2350  |             |
|  E-mail Address at Website     Fax:(480)460-2142  |  Brass Rat  |
|       http://www.analog-innovations.com           |    1962     |
             
I love to cook with wine.      Sometimes I even put it in the food.

No, actually Rich is quite right. W2K installs special drivers for a few things as mundane as IDE controllers, instead of using generic drivers like previous versions of Windoze. It won't boot if it has the wrong ones for the m/board the disk is attached to. You've probably just been lucky.

Isn't there some special boot sequence that will cause it to re-discover everything? I recall finding something like that *after* re-installing all the software on a computer that I replaced the motherboard on.

Best regards, Spehro Pefhany

--
"it's the network..."                          "The Journey is the reward"
speff@interlog.com             Info for manufacturers: http://www.trexon.com
Embedded software/hardware/analog  Info for designers:  http://www.speff.com

I'm sure there's some secret backdoor of some kind, but sitting in front of a red screen of death with the boss literally breathing down your neck (don't they have any idea how annoying that is?) didn't seem like a good time to go searching for one. ;-)

I have a perfect opportunity to test that right now. The comp. with the 80G drive pooped out the other day, and I'm pretty sure it's only the power supply, but I'm too short on cash to go get a new PS, so I took the 80G drive and have put it in the other computer, where it's now secondary slave. It'll be interesting to see what happens when I go try to have LILO boot it.

(Oops! Don't let Watson catch me talking about Linux! It's "Off- Topic." ;-) )

Cheers! Rich

Cheers! Rich

[Snipped]

Even worse, I updated the BIOS on a dual-boot W2K, Redhat machine. W2K went absoltely haywire on rebooting - even though only some of the PCI addresses had changed. Redhat had no problems. It informed me that it had detected changes in the addresses of various cards and whether I would like to use the existing driver.

Regards Anton Erasmus

As have I. There is no difference between drives, other than the obvious. There are differences between motherboards, and booting to "safe mode" will allow one to rediscover the IDE drivers. Sometimes it even works. ;-)

I've built only KeithKits for a decade because all the others *suck*.

--
  Keith

*ALL* windows versions since Win 3.11 have had their own drivers for IDE devices (and everything else). That's the only way to use the hardware acceleration features of the chipsets. In any case, the BIOS hooks are still there and can be used in "safe mode". one can generally get into safe mode and install the needed (usually automatically detected) drivers from there.

The best way to transfer an OS disk to new hardware (motherboard transplant) is to go into the device manager and delete all the devices before changing hardware. On boot, WinBlows will then auto-detect the new hardware (driver disks and a Win CD are often needed here) and you're off-n-running.

--
  Keith

I was about to do a google search for "KeithKits", but then I noticed your name...

Rufus

Yeah, at work they're known as "FrankenClones", but I prefer "KeithKit". ;-)

--
  Keith