cdob Posted September 9, 2012 Share Posted September 9, 2012 OK, I used nlite to inject the USB3 Drivers, and then I edited TXTSETUP.SIF adding these manuallyDid 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 AutomaticallyWhy do you like to do this? SCSI is working too. Link to comment Share on other sites More sharing options...
Damnation Posted September 9, 2012 Author Share Posted September 9, 2012 Did you include default USB3 drivers?XP doesn't have default USB3 DriversDid you used a txtsetup.oem?yes I didIf 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 Link to comment Share on other sites More sharing options...
cdob Posted September 10, 2012 Share Posted September 10, 2012 XP doesn't have default USB3 DriversLet's clarify: did you include USB 3 drivers as provided by the manufacturer?yes I didThat's a edited driver.]but the TXTSETUP.OEM did not add the BootBusExtender entries, or can it work without them?Yes, it can workTry 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,nusb3xhcinf=disk1,nusb3xhc.infcatalog=disk1,nusb3xhc.cat[Files.SCSI.nusb3hub]driver=disk1,nusb3hub.sys,nusb3hubinf=disk1,nusb3hub.infcatalog=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" Link to comment Share on other sites More sharing options...
Damnation Posted September 10, 2012 Author Share Posted September 10, 2012 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,nusb3xhcinf=disk1,nusb3xhc.infcatalog=disk1,nusb3xhc.cat[Files.SCSI.nusb3hub]driver=disk1,nusb3hub.sys,nusb3hubinf=disk1,nusb3hub.infcatalog=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.loadLet's clarify: did you include USB 3 drivers as provided by the manufacturer?http://www.clevo.com.tw/en/e-services/download.aspmodel is p150hmthe version 2.0.30.0 is not as recent as the one I got from intelThat's a edited driver.but I'm not altering the .inf files at all Link to comment Share on other sites More sharing options...
cdob Posted September 10, 2012 Share Posted September 10, 2012 it did not add any additional lines to bootbusextenders or bootbusextenders.loadYes, this is the expected result. It's using SCSI section.but I'm not altering the .inf files at allYes, 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. Link to comment Share on other sites More sharing options...
Damnation Posted September 11, 2012 Author Share Posted September 11, 2012 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 onsee "before I start XP Phase2" Link to comment Share on other sites More sharing options...
kitnoos2002 Posted September 19, 2012 Share Posted September 19, 2012 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 Link to comment Share on other sites More sharing options...
cdob Posted September 20, 2012 Share Posted September 20, 2012 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. Link to comment Share on other sites More sharing options...
kitnoos2002 Posted September 20, 2012 Share Posted September 20, 2012 Thank you for your fast response.I will add this line : dll=disk1,nusb3co.dllIn what section should I add it ?[Files.SCSI.nusb3xhc] or [Files.SCSI.nusb3hub] ? Link to comment Share on other sites More sharing options...
cdob Posted September 20, 2012 Share Posted September 20, 2012 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] Link to comment Share on other sites More sharing options...
kitnoos2002 Posted September 20, 2012 Share Posted September 20, 2012 Thank you very much for the explanations!I will test intégration and install soon. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now