Re: no txtsetup.oem file with driver

The "config.hta" tool included in the Solution Accelerator for Business
Desktop Deployment (available from
http://www.microsoft.com/desktopdeployment) is able to create a custom
Windows PE ISO containing additional drivers (network and mass storage).
This can then be used to "Update Windows PE" to get OSD to use that new
image.

That said, it should be possible to have OSD do this (during the image
deployment for a refresh or when building the OSD CD for bare metal). For
network drivers, just put all the driver files (the INF and all the files it
references) into one directory and specify that directory to OSD. (There is
no TXTSETUP.OEM file for network drivers; this is only for storage drivers.)

-Michael Niehaus
Systems Design Engineer
Core Infrastructure Solutions
mniehaus@xxxxxxxxxxxxx


"colson" <colson@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:88136FDB-5A42-4C33-9AC6-0C3266B49F36@xxxxxxxxxxxxxxxx
> What is the "bdd 2.5 wizard" and where do I find it?
> Thanks,
> CO
>
> "ahojky" wrote:
>
>> do you have a disk problem or a nic problem, you talk about two things,
>> for
>> adding mass storage you need a txtsetup.oem for adding nic you need to
>> put
>> the files in the correct location, .sys in drivers, .inf in inf folder
>> etc
>>
>> you can even use the wizard to add nics, mass storage doesn't seem to
>> work
>> in osd
>>
>> or better create a generic winpe with the bdd 2.5 wizard
>> "colson" <colson@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:0A6BC856-7607-4458-9EA5-FE5F1E6F7C6E@xxxxxxxxxxxxxxxx
>> > In running the ICW, I got a blue screen after the reboot with
>> > WindowsPE.
>> > It
>> > is referencing the hard drive or hard drive controller so I pulled a
>> > driver
>> > off the server installation CD to create another ISO file. However,
>> > creating
>> > the iso image fails because the new/correct driver does not have a
>> > valid
>> > txtsetup.oem file. Driver is Gigabit Ethernet NIC Driver for Windows
>> > 2000.
>> > (Q57W2k) I've gone to HP/Compaq's website but this driver does not
>> > include
>> > a
>> > txtsetup.oem file. The OSDFP installation guide states, "A valid
>> > txtsetup.oem
>> > file must be present in the driver location." I'll try to contact them
>> > but
>> > if
>> > any of you know another way out of this, let me know.
>>
>>
>>


.

Relevant Pages

  • Re: OSD: Scripting changes to OemPnPDriversPath in sysprep.inf
    ... injection at deployment time and a deployment database. ... BDD 2007 adds so much missing pieces and best practices to OSD that I ... This side of things work fine, the drivers ... using the labshell version of Windows PE). ...
    (microsoft.public.sms.tools)
  • Re: Computer Freezing
    ... There are some known unresolved issues with Catalyst 7.7 with Windows ... does seem like everytime my computer freezes I get this atimtag CRT ... one connected via USB but I never installed the drivers or used it. ... to install all my programming applications (VS, DirectX SDK, V ...
    (microsoft.public.windowsxp.hardware)
  • Re: RUN TIME ERROR!!!
    ... Second suggestion - figure out what is needing to write there.. ... using Windows XP "prettifications". ... Why you should use a computer firewall.. ... You also have hardware on your machine that requires drivers to interface ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: RUN TIME ERROR!!!
    ... Second suggestion - figure out what is needing to write there.. ... using Windows XP "prettifications". ... Why you should use a computer firewall.. ... You also have hardware on your machine that requires drivers to interface ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: Toshiba S100 Problem With RAID Driver
    ... Add RAID drivers and Service Pack 2 to your original Windows CD! ... Windows XP setup CD ... Our next objective is to extract Service Pack 2 to a folder so we can ...
    (comp.sys.laptops)