tstaddon

Beta 7 is giving me TiruScan Alerts on two files in the PyronSetup\I386 folder (setup_dbg.ex_ and setup.ex_). I've applied the usual workaround (extract to machine without McAfee).

Can't dispute that, I should've known better but in fairness I've only had my 32GB pen drive for a couple of weeks, the previous pen drive I was using only had room for two builds so while it was annoying it wasn't going to take me forever to rebuild the thing from scratch. I haven't really had much time to actually look at the way the ISO works in relation to the extracted folder, when using WinSetupFromUSB. Out of curiosity, what's the best way to configure the build so that installing from pendrive also dumps the I386 folder to the system drive and re-points the registry to look at that folder for the source files in the future? I've got a few PCs now that think the Windows install media is located on a non-existent U drive.

Hi, I would use a newer one, but I must be thick because I can't find a download link for any version newer than Beta 6. Certainly the first place I would've looked would've been in the top post of this thread and that only goes up to Beta 6. I renamed the WINSETUP folder so it's clear which ones are which. In my house (large family, long story) there are at present: three Dell desktops, two HP laptops, one Dell laptop, one clone with a LEGAL retail OEM build, and a Philips Freeline mini desktop PC also with its own retail OEM build. Using your method to cover all the machines for a recovery situation without a DVD to hand, the folder structure my super-duper-recovery-pen-drive would end up looking a bit like this: Recovery media --- First part of OEM XP Pro SP3 Slipstreamed install with drivers, hotfixes and applications (for the clone PC and the Philips Freeline) --- First part of Dell XP Pro SP3 Slipstreamed install with updated F6 drivers, hotfixes, and preinstalled applications (for the desktops) --- First part of Dell XP Home SP3 Slipstreamed install with updated F6 drivers, hotfixes, and preinstalled applications (for the laptop) --- First part of HP XP Home SP2 vanilla install for the Pavilion (the drivers and software can all be installed from a second ISO which has SP3 already configured to go) --- First part of HP XP Pro SP3 vanilla install with F6 slipstreamed drivers for the NC6320 --- Second part of install This would mean the WINSETUP folder would end up being a single point of failure; I've already had the annoyance of my eldest son borrowing the pen drive and deleting the WINSETUP folder causing me to lose two OS install routines already in there and I shudder to think what would happen if I'd spent a week putting them ALL onto the pen drive only for the same thing to happen again! That is why I would prefer the folder structure to be more like this: Dell Desktop PC Recovery Media --- First part of Dell XP Pro SP3 Slipstreamed install with updated F6 drivers, hotfixes, and preinstalled applications (for the desktops) --- Second part of install Other Desktop PC Recovery Media --- First part of OEM XP Pro SP3 Slipstreamed install with drivers, hotfixes and applications (for the clone PC and the Philips Freeline) --- Second part of install Dell Laptop Recovery Media --- First part of Dell XP Home SP3 Slipstreamed install with updated F6 drivers, hotfixes, and preinstalled applications (for the laptop) --- Second part of install HP Laptop Recovery Media --- First part of HP XP Home SP2 vanilla install for the Pavilion (mount the SWSETUP.ISO after the reboot and install the rest from there) --- First part of HP XP Pro SP3 vanilla install with F6 slipstreamed drivers for the NC6320 --- Second part of install I'm quite happy to do this manually, of course...

Hi, I'm using Beta 6 at the minute. I use NLITE to bundle in the post-SP3 hotfixes, then driverpacks.net to slipstream in the drivers. Finally, I use WinSetupFromUSB to put the completed build onto the pen drive. The issue seems to be that the menu name is always going to be the same if I'm using XP Service Pack 3. I've now resorted to manually renaming the WINSETUP folder and the associated paths in the lst files prior to using WinSetupFromUSB to commit a new build to the pen drive. I'm using an OEM XP Service Pack 2 CD, slipstreamed to SP3 and burnt to an ISO, as the basis for each setup and I have created several different NLITEd packages from this ISO, for different PC builds. So if you're looking at txtsetup.sif the description will always be the same. It's never asked me for a custom menu name so the "first part of..." menu entries all look exactly the same, e.g. "First part of Windows XP Professional SP3 setup" appears many times even though the "Second part of..." entry only appears once.

Hi, Great tool, I use it in conjunction with RMPREPUSB. Slight issue though: if I try and build a second install on a pen drive with an existing install could you possibly change it to create a seperate winsetup.lst file or let the name of the XP install get edited? It gets a bit confusing when the same file has two options for step 1 and the text descriptions are similar... Also, is there a dev build of WinSetupFromUSB or is it just a case of keep coming here and checking the version hasn't been updated?