Skip to content
View in the app

A better way to browse. Learn more.

MSFN

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Install XP on USB3 stick

Featured Replies

OK, I used nlite to inject the USB3 Drivers, and then I edited TXTSETUP.SIF adding these manually

Did you include default USB3 drivers?

Did you used a txtsetup.oem?

If you used txtsetup.oem, don't edit txtsetup.sif.

just wondering what to add to it so it will add the lines to BootbusExtenders Automatically

Why do you like to do this? SCSI is working too.


  • Author

Did you include default USB3 drivers?

XP doesn't have default USB3 Drivers

Did you used a txtsetup.oem?

yes I did

If you used txtsetup.oem, don't edit txtsetup.sif.

but the TXTSETUP.OEM did not add the BootBusExtender entries, or can it work without them?

Why do you like to do this? SCSI is working too.

Because TXTSETUP.OEM doesn't add BootBusExtender entries

XP doesn't have default USB3 Drivers

Let's clarify: did you include USB 3 drivers as provided by the manufacturer?

yes I did
That's a edited driver.
]but the TXTSETUP.OEM did not add the BootBusExtender entries, or can it work without them?

Yes, it can work

Try txtsetup.oem

[Disks]
disk1="RENESAS USB3 Installation Disk",\nusb3xhc.inf,\

[Defaults]
SCSI=nusb3xhc

[SCSI]
nusb3xhc="Renesas USB3 Controller Driver"
nusb3hub="Renesas USB3 HUB Driver"

[Files.SCSI.nusb3xhc]
driver=disk1,nusb3xhc.sys,nusb3xhc
inf=disk1,nusb3xhc.inf
catalog=disk1,nusb3xhc.cat

[Files.SCSI.nusb3hub]
driver=disk1,nusb3hub.sys,nusb3hub
inf=disk1,nusb3hub.inf
catalog=disk1,nusb3hub.cat

[HardwareIds.SCSI.nusb3xhc]
id="PCI\VEN_1033&DEV_0194","nusb3xhc"

[HardwareIds.SCSI.nusb3hub]
id="NUSB3\ROOT_HUB30","nusb3hub"
id="NUSB3\CLASS_09","nusb3hub"

  • Author

OK I tried the txtseup.oem you provided.



[Disks]
disk1="RENESAS USB3 Installation Disk",\nusb3xhc.inf,\

[Defaults]
SCSI=nusb3xhc

[SCSI]
nusb3xhc="Renesas USB3 Controller Driver"
nusb3hub="Renesas USB3 HUB Driver"

[Files.SCSI.nusb3xhc]
driver=disk1,nusb3xhc.sys,nusb3xhc
inf=disk1,nusb3xhc.inf
catalog=disk1,nusb3xhc.cat

[Files.SCSI.nusb3hub]
driver=disk1,nusb3hub.sys,nusb3hub
inf=disk1,nusb3hub.inf
catalog=disk1,nusb3hub.cat

[HardwareIds.SCSI.nusb3xhc]
id="PCI\VEN_1033&DEV_0194","nusb3xhc"

[HardwareIds.SCSI.nusb3hub]
id="NUSB3\ROOT_HUB30","nusb3hub"
id="NUSB3\CLASS_09","nusb3hub"

it did not add any additional lines to bootbusextenders or bootbusextenders.load

Let's clarify: did you include USB 3 drivers as provided by the manufacturer?

http://www.clevo.com.tw/en/e-services/download.asp

model is p150hm

the version 2.0.30.0 is not as recent as the one I got from intel

That's a edited driver.

but I'm not altering the .inf files at all

it did not add any additional lines to bootbusextenders or bootbusextenders.load

Yes, this is the expected result. It's using SCSI section.

but I'm not altering the .inf files at all

Yes, however a added txtsetup.oem is a edited driver package.

This is nice too.

As for XP USB installation: there is no final answer.

Remember: approach is without OS manufacturer support.

There are different results at different used BIOS and used hardware.

Try it.

  • Author

You were right, the Bootbusextender entries aren't required, so thanks!

Ilve run into another problem now, says it cannot copy winvblk32.sys,

but I get the option at F6 to select it, so not sure what's going on

see "before I start XP Phase2"

  • 2 weeks later...

Hello everyone!

I'm on XP SP3 X86 with PCI Renesas USB3.0 (Drivers 2.1.36.0).

I want to install XP from USB3.0 key.

Just to know :

1) Why you don't add the file "nusb3co.dll" in "txtsetup.oem"?

2) I can only see "NUSB3\ROOT_HUB30" in my Device Manager. What is "NUSB3\CLASS_09"? Should I remove it from section [HardwareIds.SCSI.nusb3hub]

Thank you very much!

Chris

1) Why you don't add the file "nusb3co.dll" in "txtsetup.oem"?

Yes, that's a good idea. Add nusb3co.dll[ too.

2) I can only see "NUSB3\ROOT_HUB30" in my Device Manager. What is "NUSB3\CLASS_09"? Should I remove it from section [HardwareIds.SCSI.nusb3hub]

NUSB3\CLASS_09 is another HardwareID from nusb3hub.inf. This HardwareID may be used at other machines.

This is not a conflict. Keep this HardwareID for future.

Thank you for your fast response.

I will add this line : dll=disk1,nusb3co.dll

In what section should I add it ?

[Files.SCSI.nusb3xhc] or [Files.SCSI.nusb3hub] ?

In what section should I add it ?

[Files.SCSI.nusb3xhc] or [Files.SCSI.nusb3hub] ?

The file nusb3xhc.inf does refer the filename nusb3co.dll.

Hence add nusb3co.dll to section [Files.SCSI.nusb3xhc]

Thank you very much for the explanations!

I will test intégration and install soon.

Create an account or sign in to comment

Recently Browsing 0

  • No registered users viewing this page.

Account

Navigation

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.