Скопировал нужные драйвера и установил систему с флешки - драйвера были подхвачены.
решил скопировать в эту папку немножко больше драйверов на все случаи (точнее на самые распространенные) но установщик отказывается устанавливать систему и ругается на то, что не все драйвера необходимые для системы были найдены.
в чем тут может быть загвоздка?
1) слишком много драйверов
2) Есть не совместимый с таким методом установки драйвер
Кто может подсказать что-нибудь по этому поводу?
цитата из документации по Server 2008
читать дальше »
Windows Server 2008 Automatic Driver Injection
In Windows Vista, the driver injection during Setup depends solely on the Unattend answer file during the Windows PE phase of Setup. There is no automatic pulling of drivers from a $OEM$ directory, as existed in Windows XP, because of changes in the Windows Setup model.
However, because many server systems ship without a preinstalled operating system, Windows Server 2008 requires support to automatically search for predetermined directories on the system to look for drivers. During Windows PE the system looks for the directory that is named $WinPEDriver$ at the root of all visible drivers given a drive letter of C or greater. If this directory exists, the module then adds this path to the list of paths that it maintains to search for driver packages. When this operation is complete, the module continues to scan the answer file, if present, for additional driver paths.
Because of this operation, drives that contain a WinPEDriver$ directory in the root cause Setup to recursively search this directory for driver packages to be imported into the image during the Windows PE phase. This includes hard disk partitions and removable media like floppy disk drives and flash drives. Type-27 hidden partitions are assigned a driver letter during the Windows PE phase of Setup and are also searched.
Drive letters A and B are not searched during this operation. These drives are considered reserved for floppy disk driver media and, because of potential error conditions, are omitted from the search algorithm.
This enables scenarios in which a server system is shipped without an operating system and gives OEMs more flexibility in provisioning boot storage and other drivers to enable Setup on these systems. One potential consequence is a situation in which Windows PE cannot access the hard disk that contains the $WinPEDriver$ directory because the storage driver has not yet been loaded in Windows PE. This dilemma can be solved in one of the following ways:
• Boot to a customized Windows PE image that already has the storage driver installed.
• Place drivers on an embedded flash drive that is accessible from Windows PE.
• Place drivers on removable media such as flash or CD Rom. (Floppy disk drives are not supported.)
это все что удалось найти на данный момент
