Free Republic
Browse · Search
Bloggers & Personal
Topics · Post Article

To: Knitebane

I know Dell excels at screwing things up. I’ve got Del PowerEdges that probably have the same network adapter, or at the very least it has the same Intel chipset in the network adapter. It doesn’t get recognized by Win2K3 either, it knows it’s a network adapter but it can’t figure out what kind. Now I could probably go through the trouble of telling it’s an Intel blah blah, ie doing what Dell failed to do, or I could just install Dell’s drivers. The driver install takes 3 minutes and doesn’t even require a reboot. It’s not that tough.

It’s not just the Intel chip, it’s what Dell does with the chip. There’s a lot more to PnP than the core Intel chip and if you have half the experience you claim you know that.

My my you sure do love logical fallacies, no I don’t have any personal stake, and it wouldn’t matter if I did. Any winding up happening here is the frustration of watching you hammer the same 100% unsupported assumptions over and over and over. It’s really pathetic. None of your arguments are even slightly supported by facts, they’re all built on your assumptions. You assume too much.

And here’s where you run into a problem because you haven’t touched Windows since 1999. Any time there’s hardware in the computer that XP (and every version of Windows since) does not have drivers installed and configure for there’s a New Hardware wizard displayed on boot, unless the user has explicitly told Windows not to ignore the fact that it doesn’t know what that hardware is. Meaning on the first boot if there’s hardware that didn’t get properly detected and configured during the install there WILL be a New Hardware wizard, period, not negotiable, not avoidable. That’s how he knows Windows didn’t recognize the card, because a New Hardware wizard popped up and said it didn’t recognize the card. Not assuming, actually having experience with what we’re talking about.


95 posted on 07/23/2008 12:46:14 PM PDT by boogerbear
[ Post Reply | Private Reply | To 87 | View Replies ]


To: boogerbear
It’s not just the Intel chip, it’s what Dell does with the chip.

Ok, fair enough to blame Dell for screwing up the implementation.

But Microsoft still doesn't get off the hook. Using the default Linux driver, the one that hasn't changed since 2002, the Linux Mint install saw the NIC just fine.

And here’s where you run into a problem because you haven’t touched Windows since 1999

Boy, talk about making assumptions.

Just because I'm personally Microsoft free, doesn't mean that I haven't worked with Microsoft products since 1999.

Any time there’s hardware in the computer that XP (and every version of Windows since) does not have drivers installed and configure for there’s a New Hardware wizard displayed on boot,

Only if Windows recognizes the device to some extent.

That’s how he knows Windows didn’t recognize the card, because a New Hardware wizard popped up and said it didn’t recognize the card.

Odd, Windows XP SP2 on VirtualBox doesn't see the IntelPro adapter and doesn't pop up anything. It just doesn't see the card at all.

97 posted on 07/23/2008 12:57:13 PM PDT by Knitebane (Happily Microsoft free since 1999.)
[ Post Reply | Private Reply | To 95 | View Replies ]

Free Republic
Browse · Search
Bloggers & Personal
Topics · Post Article


FreeRepublic, LLC, PO BOX 9771, FRESNO, CA 93794
FreeRepublic.com is powered by software copyright 2000-2008 John Robinson