"As for your complaint about the SB16 ISA card, I have an old ISA NE2000, made by Realtek, that Windows will not detect period, but installs and works in Linux just fine, all I have to do is tell it what I/O it uses. It sounds to me like six of one, have a dozen of another."
Linux uses Legacy Plug and Play (APM spec) by default. Windows uses ACPI, the newer spec. If your device works in Linux and not in Windows then either your BIOS or the device is not ACPI compliant. Remember -> Windows does not detect your hardware -> the BIOS does. Windows supplies drivers based on firmware IDs by the BIOS and the device
I can do everything you listed here in 2 reboots. You need to read up on W2k deployment guide. I feel sorry for whatever company (and employees) you work for.
"Even without reboots, Win2K will force you through the stupid hardware configuration wizard once for every driver you need to install"
I dont see any wizards in linux now do i... wish i did..
"Quite often, Win2K isn't capable of finding the appopriate driver on a disk that contains the same driver for multiple versions of Windows"
nice _guess but you are incorrect;) the driver vender did not author the txtsetup.oem correctly or did not place this file in the correct place on the install disk.
"So quite often you end up needing to guess yourself which is the right driver by browsing through the driver disk."
incorrect again;) if the hardware vendor is following PCI spec then you can not install a driver that is not intended with your hardware.
"Plus, Win2K has a nasty habit of not telling you what your hardware actually is."
wow man -> you are really nailin'em home tonite. actually it is the resoponsibility of the device to let us know what it is... not windows... once again a PCI spec issue.. maybe you should go find some PCI PHA-Qs
"Plus, if there is a generic driver available Win2K may not decide to automatically present that as an option."
lol! i have a suggestion for you -> know what you are talking about before making such bold and stupid statements
- boot from XP CDROM and copy files (reboot)
- complete install (reboot)
- hit desktop and install and configure apps update everything (reboot)
lol! do you know what takes a few reboots Xconfigurator testing on a new video card! what a joke
Slashdot Mirror
"As for your complaint about the SB16 ISA card, I have an old ISA NE2000, made by Realtek, that Windows will not detect period, but installs and works in Linux just fine, all I have to do is tell it what I/O it uses. It sounds to me like six of one, have a dozen of another."
Linux uses Legacy Plug and Play (APM spec) by default. Windows uses ACPI, the newer spec. If your device works in Linux and not in Windows then either your BIOS or the device is not ACPI compliant. Remember -> Windows does not detect your hardware -> the BIOS does. Windows supplies drivers based on firmware IDs by the BIOS and the device
"Linux is very ready for the desktop"
LOL - All the desktop OEMs share your opionion?
- your number one fan PHA-Q
I can do everything you listed here in 2 reboots. You need to read up on W2k deployment guide. I feel sorry for whatever company (and employees) you work for.
"Even without reboots, Win2K will force you through the stupid hardware configuration wizard once for every driver you need to install" I dont see any wizards in linux now do i ... wish i did..
"Quite often, Win2K isn't capable of finding the appopriate driver on a disk that contains the same driver for multiple versions of Windows"
nice _guess but you are incorrect ;) the driver vender did not author the txtsetup.oem correctly or did not place this file in the correct place on the install disk.
"So quite often you end up needing to guess yourself which is the right driver by browsing through the driver disk."
incorrect again ;) if the hardware vendor is following PCI spec then you can not install a driver that is not intended with your hardware.
"Plus, Win2K has a nasty habit of not telling you what your hardware actually is."
wow man -> you are really nailin'em home tonite. actually it is the resoponsibility of the device to let us know what it is... not windows... once again a PCI spec issue.. maybe you should go find some PCI PHA-Qs
"Plus, if there is a generic driver available Win2K may not decide to automatically present that as an option."
lol! i have a suggestion for you -> know what you are talking about before making such bold and stupid statements
- boot from XP CDROM and copy files (reboot) - complete install (reboot) - hit desktop and install and configure apps update everything (reboot) lol! do you know what takes a few reboots Xconfigurator testing on a new video card! what a joke
and why would i want to waste my time with all of your FA-Qs? I want to click a button and move on to larger tasks...