Re: no txtsetup.oem file with driver

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

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: no txtsetup.oem file with driver
    ... What is the "bdd 2.5 wizard" and where do I find it? ... > do you have a disk problem or a nic problem, you talk about two things, for ... > you can even use the wizard to add nics, mass storage doesn't seem to work ... >> the iso image fails because the new/correct driver does not have a valid ...
    (microsoft.public.sms.tools)
  • Re: How to test a nic card?
    ... check yours against the photos on the download page for the proper driver ... it resolves the problem- some nics have trouble negotiating link speed with ... >>Windows 2000 IP Configuration ... >>Ethernet adapter Local Area Connection: ...
    (microsoft.public.win2000.networking)
  • Re: 2nd NIC ifconfig
    ... also assume eth0 and eth1 are different types of nics and thus need ... then ifconfig eth1 to bring the card up ... if you don't know the driver needed for the secound card. ... I know by using each NIC one at a time that all four NICs I've tried ...
    (comp.os.linux.networking)
  • Re: ethernet inteface: lost connection
    ... chipset nVidia, with a AMD64 CPU, and onboard NIC is nForce. ... While I'm having a problem with the onboard NIC, it's driver ... Why do you assume I have 2 "onboard" NICs? ... unknown hardware address type 776 ...
    (comp.os.linux.hardware)
  • Re: Univeral Protocol Driver (using UNDI) in Linux
    ... driver for Etherboot 5.4. ... It currently supports PIO NICs (e.g. cards ... Memory Mapped I/O, MMIO, is putting the device registers in memory space. ...
    (Linux-Kernel)