Microsoft installers have consistantly asked for driver software, when installing operating systems. Since 'Dos 3.0' this has consisted of a note on the screen generally 'insert driver disk'. When a software is made available ( through disk, search or directory ) the installer says 'not found' or installs the driver. If the installer knows what ii is looking for, why can't the *** thing let us in on the secret. I also appreciate the 'unknown device' in device manager. OK, in Dos3.0 this was understandable, limited resources one or two devices,... Installing Vista, this is the result of sheer laziness :( The peripherals, are self identifying, the drivers are 75% identification, and Vista knows it's the wrong driver without Beginning to install it. But we still get the Dos3.0 prompt 'guess which driver I'm looking for - and i'll tell you if your wrong, Sorry no hints!!!' Oh, sorry it's not laziness, Microsoft isn't using the P4, 512Meg, 80Gig, and 128meg graphics, to process data, it's to display the 35 full-color graphic desktops.

General driver installation question
Here's how this works in simple terms.
When Windows starts up, the Plug-And-Play (PNP) enumerator polls to see what devices might be plugged into the various PC motherboard slots, serial ports, USB ports, etc. If it finds a device, it asks that device what it is and the device replies with a simple PNP ID. Windows then looks up this PNP ID in its internal tables to see if it already knows about this particular device. If it finds the PNP ID in the list, Windows then can categorize the device (disk drive, modem, printer, graphics adapter, etc.) and actually name it ("Printer", "Modem", etc.). If Windows doesn't find the PNP in its tables, or if the device doesn't return a PNP ID, it classifies the device as an "Unknown Device". At this point Windows tries to load a driver for the device. Again using the PNP ID information, Windows searches its inventory of drivers already loaded with Windows. If it finds the right driver, it installs it and activates the device. If Windows can't find an appropriate driver already in Windows, it then goes through the process of asking you to provide the driver disks, look online, etc. If the device is classified as an "Unknown Device" but has a valid PNP ID, it's still possible that you can provide the right driver disk and the device will install properly.
Again, the above explanation has been simplified.
If Windows reports an "Unknown Device", it really is an unknown device. Windows might know it's PNP ID, but still not have a clue what kind of device it is. Don't blame Microsoft for this. If you want to blame someone it might be best to blame the peripheral device manufacturer who didn't provide the right driver or PNP information.
"st1" wrote in message
Microsoft installers have consistantly asked for driver software, when installing operating systems. Since 'Dos 3.0' this has consisted of a note on the screen generally 'insert driver disk'. When a software is made available ( through disk, search or directory ) the installer says 'not found' or installs the driver. If the installer knows what ii is looking for, why can't the *** thing let us in on the secret. I also appreciate the 'unknown device' in device manager. OK, in Dos3.0 this was understandable, limited resources one or two devices,... Installing Vista, this is the result of sheer laziness :( The peripherals, are self identifying, the drivers are 75% identification, and Vista knows it's the wrong driver without Beginning to install it. But we still get the Dos3.0 prompt 'guess which driver I'm looking for - and i'll tell you if your wrong, Sorry no hints!!!' Oh, sorry it's not laziness, Microsoft isn't using the P4, 512Meg, 80Gig, and 128meg graphics, to process data, it's to display the 35 full-color graphic desktops.
Windows Vista
User login
Related topics
- Mutiple Windows at boot...
- Problem in installation of VGA Driver for 845glva motherboar
- BitLocker: are 16 sectors appear to be unencrypted?
- Compact (All) Folders?
- VID_04E6 PID_80002000 Unknown Device
- Blue screen on Vista Beta 2 Installation (64 bit version)
- using windows fax and scan client and Windows fax server
- Vista 64 - Can't Join Domain?
- Installed Vista Beta 2
- Toolbar Customization
- 5308-64: Serious file I/O issue?
- EZ Antivirus
- blank mail increasing
- File Find XP Virsus Vista
- News: Performance Enhancers coming Vista
- HP PSC 2410
- How do I see the folder system
- Sound
- Does Nero Work with Vista?
- Vista and sharing a connection?
- Compatibility issues, cannot delete Program using convention
- Boot Manager unreadable with ATI 9600 and two monitors
- Setup cannot validate your product key
- how to boot it
- Windows Vista Origami Edition?
- UbiSoft IL2 Forgotten Battles running OK on native drivers
- "Phantom WAV player"
- Change of Language
- Icons n/a or corrupted after software installation
- Nvidia Dual tuner not recognized in Vista ultimate
- CRCs and MD5s for Vista 5384
- Problem to start Vista : Reboots in loop
- Blocking Posters
- Not able to burn DVD in both Vista MCE and Vista DVD Maker
- Can't D'load Vista
- Two monitors on Radeon 9250