Creating TXTSETUP.OEM

[Will]

Many of the Compaq / HP Windows 2000 driver downloads only contain .CAT,
..INF, and .SYS files needed to install new devices under Windows. What's
lacking is a TXTSETUP.OEM file, which is used at minimum with the Windows
2000 install CD when you need to add a new device while installing. Is
there a trick to creating the TXTSETUP.OEM file when it is not provided by
the vendor?

--
Will

 

[Dave Patrick]

Re: Creating TXTSETUP.OEM

These two may help.

http://support.microsoft.com/kb/313447
http://www.osronline.com/ddkx/install/txtsetup_1wmq.htm


--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"Will" wrote:
> Many of the Compaq / HP Windows 2000 driver downloads only contain .CAT,
> .INF, and .SYS files needed to install new devices under Windows. What's
> lacking is a TXTSETUP.OEM file, which is used at minimum with the Windows
> 2000 install CD when you need to add a new device while installing. Is
> there a trick to creating the TXTSETUP.OEM file when it is not provided by
> the vendor?
>
> --
> Will
>

 

[Will]

Re: Creating TXTSETUP.OEM

"Dave Patrick" <DSPatrick@nospam.gmail.com> wrote in message
news:3D79B2CF-50C2-4508-87F7-F81FF8EA7561@microsoft.com...
> These two may help.
>
> http://support.microsoft.com/kb/313447
> http://www.osronline.com/ddkx/install/txtsetup_1wmq.htm

So I have to create TXTSETUP.OEM by hand? Kind of ugly.

--
Will

 

[Dave Patrick]

Re: Creating TXTSETUP.OEM

Not sure what else you were expecting.

--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"Will" wrote:
> So I have to create TXTSETUP.OEM by hand? Kind of ugly.
>
> --
> Will
>
>

 

[Will]

Re: Creating TXTSETUP.OEM

> "Will" wrote:
>> So I have to create TXTSETUP.OEM by hand? Kind of ugly.

"Dave Patrick" <DSPatrick@nospam.gmail.com> wrote in message
news:AB43D0E5-0A17-49E9-A3CE-44601DCE32A1@microsoft.com...
> Not sure what else you were expecting.

It would have been nice to have some automation in creating TXTSETUP.OEM
output from the normal Windows .INF files.

--
Will