Macster

Ilko_T, Okay I see what is going now. It turns out that this is the case of the missing identy. Here in my case I have two locations I didn't know about. One location has the recent installment of WinSetupToUSB and the other (which I just found out) is the old installment (which is where my shortcut is pointing to). The old installment is the one that is missing this file. I was not aware that the my short cut itself would reference the old location even though I thought it was running from the other location on the HD. Hence every time I ran it, it would keep saying missing file. Oops. In one way, maybe this a good thing cause I would not have the history of the old install logs had I known this. Again my apologies. I didn't see where it said to install this Beta into the old location and it doesn't matter anyway because of the short cut I was using. So I see what happened when it came to the installment of McAfee, it must have thought that the file was a virus and locked it away somewhere or deleted it. Either way, it made your program unusable. But this still doesn't explain what happened when I uninstalled McAfee, that Windows 7 would become severly hampered. This is something I will need to bring up with McFee when I write a formal complaint to them in regards to your file in question that caused all this. Well in the words of the great Sherlock Holmes - This mystory is Solved! This indeed did fix the problem. I now have a usable bootable USB Thumb Drive to install XP from and I have you to thank. So Thank You. I am deeply in your dept for the mounds of time and effort you have devoted to this project. Thanks Again, Macster

Ilko_T, Here is the logs from the past 6 attempts that have failed. There are more but these (I hope) should answer any questions. If you need some with successful runs let me know. I should still have those too. Thanks, Macster backups.zip

Thanks ilko_t, I thought the samething as you did, but for different reasons. The program was working fine until just recently I had installed McAfee. So I figured I would just uninstall it... Well this little action has caused no small stir in my system. After the uninstall, things stopped working in Windows 7. So I reinstalled Windows 7 Ultimate 64b with all the upgrades, patches that Microsoft had to offer including drivers for my system, but without the McAfee Antivirus. Still no go. I have downloaded another copy of BETA6 and uncompressed it with 7zip. Still no go. I have copied all the files from my XP SP1 cd thinking that maybe I have a corrupted file. Still no go. Same message comes up all times. I am wondering if Windows 7 during its install, does it utilize files that were part of the previous install. Cause I didn't wipe the partition when I install Windows 7 thinking that Windows 7 would do that for me or give me the option to do so like the XP install does. However I did tell Windows 7 installer to make a fresh install not an upgrade to the existing install. BTW, I know this question may come up at some point, but when I copied all files from XP SP1 CD, I used these very same files untainted by nLite or any other special install routines and it still failed. I am out of options here. Maybe you can think of something that I didn't. Well anyway, I can't think of anything else to say in regards to this. Thanks, Macster Ps. I have updated my previous message with the latest log report hoping maybe you would see something or a trend. Anyway, I am done at this point. Thanks for looking into this and the previous search you did into my problem. I kinda figured with 55 pages of responces there had to be something on this that I just didn't see. Sorry. I am terrible at searching. It requires a creativity that I at times lack. One more thing JaClaz I like your anology on the Dell BOIS coding - your randomization routine example. I couldn't stop laughing and totally agree. I wouldn't own one even if someone gave me money to take it off there hands. (Well maybe...

Hi everyone, It has been a long time since I have posted anything on here. I have a problem was hoping some one could point me in the right direction. I apologize if this problem has been posted before. Here is my dilemma: I am making an XP Pro Sp3 32b install using Windows 7 Ultimate 64b. The version of the WinSetupFromUSB is 1.0 Beta6. Now I have been able to run this quite frequently with no problems up to just recently. The problem is that it is able to load the USB Thumb drive until where it is unable to modify a setup file then it just quits to the desktop. Due to your file quota requirements I am unable to attach the log file to this posting so here it is embedded in the post: 2010/09/21 13:14:56- Ensuring presetup is launched 2010/09/21 13:14:56- Expanding G:\WINSETUP\XPpSP1\I386\setup.ex_ 2010/09/21 13:14:56- Microsoft (R) File Expansion Utility Version 6.1.7600.16385 Copyright (c) Microsoft Corporation. All rights reserved. Adding G:\WINSETUP\XPpSP1\I386\setupWST.exe to Extraction Queue Expanding Files .... Expanding Files Complete ... 2010/09/21 13:14:56- 2010/09/21 13:30:16- Could not replace original Setup.exe, aborting... 2010/09/21 13:30:16- Removing TEMP folder 2010/09/21 13:30:16- ---------------------------------Program quited----------------------------------------------- I have attached the file in question mentioned ubove in the log file. Thanks for any assistance you maybe able to offer. Macster Edited: To make this post smaller. setupWST.exe

Hey ilko_t, cdob, jaclaz, I didn't get a chance to say thanks. And now I don't see the sticky on the forum. Bummer. Um I was wondering where I can add the script in the install directory, so the program 0.2.3 can use it every time I setup the USB for an install. May God bless your hearts for helping. Thanks much!!!! Macster Edit: I found the topic. I was wondering if others will be able to see it too, so they to can benefit from what was done?

@cdob Script output: call === MontedDevices as read call === convert MountedDevices, adjust RomovableMedia warning: MountedDevices does not contain RemovabledMedia#7 fixing S: to RemovableMedia#7 copying file to the XP install .~bt forder. Well I got U: (with NTFS) this time. Interesting? Cause my current topology was (before running the XP install): C: Partition 1 (XP) D: Partition 2 E: DVD F: Partition 3 (Hidden) U: Thumb Thanks to the file that ilko_T gave me. I am wondering if it has anything to do with the ambient topology. Whether the install is reading some of the registry (or the partition tables on the HD) as far as the placing of particians and such? Cause before I was getting D: for the thumb when the thumb was already set at D:. Edit: Well I tried changing the drive reference to the USB to Z: in Windows, reran the script, and it still came up with U: during the install, so it would appear that it is fixed.

Yes, I was able to prepare two installs for the same system in series and they both got the U: reference with the same file. Thanks. As fas as a USB card reader, I really don't understand what you mean. I have a USB hub connected to system as well as other USB printers (HP Deskjet 932C, HP Photosmart C3180 All-in-one) but these don't don't have drivers loaded as of yet when your program was running. If you are meaning a USB SD memory chip reader (the type that goes into phones and cameras), I have one of those on the C3180, but like I said earlier the drivers weren't loaded for it and I didn't see anything in the Device Manager in regards to this not being identified. Further more the printer has of yet to be turned on, it is kept off until needed - so XP doesn't even know of its existance until I turn it on. I hope this helps. @cdob I am trying your last version of the MkMigrate script. I will let you know if it works. thanks.

Try the attached migrate.inf, place it in ~BT directory on the USB stick. Did USB stick get letter U: ? Yep, I got U: ... reference to the Ultra thumb on fat 16 and NTFS. It is amazing one Byte can make that much difference. WOW! So why did you change it from a 7 to an 8? I don't have a hex descriptor, (but I can read ASCII on occasions and mainly numbers) so I do not know where this playes in the file. It would appear that you guys are able to detect why this is happening (meaning the D: instead of the U: stuff). Now I have another question, as soon as I install XP again would the ParentIDPrefix change? If so, would it make the file you just gave me obsolete? <already answered) Thanks all the same. Edit: I just answered one my questions about the file being obsolete, I guess it still maintains the ParentIDPrefix after a ReInstall of XP. So does migrate.inf reintroduce the ParentIDPrefix or does the install come up with it and migrate.inf utilizes that same ID?

Oh sorry for the late responce. ParentIDPrefix for the current install of XP is 8&9013452&0. (Sorry, this is for the Sony 256 MB.) Edit: Oops, I gave you the wrong one. I accually have two USB Thumb Drives. 1. Sony 256 MB Thumb 2. Ultra 2 GB Thumb. Both of these have been used on the current XP install. The ParentIDPrefix for the Ultra 2 GB is 8&35debb9c&0.

It still failed. I still get D: not U: as the reference to the drive. I am now trying HP's Prep tool, but still using 0.2.3 to make the install on the USB without copying the Migrate file. It still failed. And failed when I copied the migrate.inf file over. Let me try with 16 bit fat, where it worked before with HP's prep tool and 0.1 version of the program, but this time will be with 0.2.3 and its prep tool without the migrate.inf file. Well it failed here too. I get D: instead of U:. And I again tried copying the migrate.inf file, it still failed yet again. Not sure what to try next. I have been just going to the text part of the install and I get the D: to the thumb drive. Also before when it did work with 0.1 version, my drive topology was: c: Partition 1 (XP Install) D: Partition 2 E: Partition 3 (Hidden) F: DVD U: USB Thumbdrive Currently on XP: C: Partition 1 (XP Install) D: USB Thumbdrive E: Partition 2 F: DVD G: Partition 3 (Hidden) When I ran the MkMigratge_b.cmd each time (even on 16 bit fat), it could not find #7, and had to make adjustments. I hope all of this helps. It is getting pretty late for me here. So I am going to turn in. Attached is MIGRATE.INF. Thanks so much for any help you can provide to this.

For some reason this has failed. So I am now trying it a new install that is just a plain Jane install, meaning no Extra emenities added into the install like IE8, dotNet, the patches and NLite reg tweaks. I just have SP3 slipstreamed into the install. That is it. BTW sorry for the LLOONNGG explanation earlier, I didn't realise what you was asking until I read Pipsters thread. Truly interesting. Anyway to better answer your question, I ran your program on a fresh install of XP Pro SP3 to make a new install of XP Pro SP3 after which I noticed that some of my programs where being installed on the USB thumb drive. The thumb drive used is an ULTRA 2 gig. which has been used extensively for these purposes. FYI the link in your message post 70 of thread titled, "USBstick take letter D and not U, I choose to assign U to the USBkey.." points to the last page of the thread not to page 3 post 56 where the command file can be found by cdob, if this is even the file you was mentioning earlier. It took me quite a while to find this file in the thead. But it is truly an amazing story. Poor Poor Pipster.... LOL! Sorry couldn't resist. ROTFL!!! He truly made a great test subject.

Oh I am sorry, I ran the program on XP Pro SP 3 to do an XP Pro SP 3 install. I currently have Windows 7 on my lappy and figured that using XP to make the install was the safest especially when making an XP install. I have been using the same 2 gig. USB stick the whole time - setup as an NTFS bootable device (currently), back then I was using 16 bit bootable device for speed. As far as to your other question, I was using your version 0.1 (not the beta) until just recently until I happen to come across your site a couple of days ago and noticed that you had an update. And then felt the urge to find my pilots liscence due to the number of options available for prepping the USB device. LOL! As far as the 0.1 it was still using U: drive reference, but I didn't have HP formating tool set the device to NTFS bootable device either. So it could be the fact that I switched to NTFS, not exactly sure. Are you thinking that this could be a bios thing?

I seem to be missing a key peice of info. I was wondering in 0.2.3 how to setup the USB thumb drive to a specific drive upon boot up like in the previous versions it used to be refered to as Drive U: now it seems it is refered to after the primary particitian or basically in my system drive D: which happens to be where I store my program data and where programs get installed. Is there some provision or way to setup the thumb drive to a specific drive letter? Thanks in advance to any advice you may have or particular post you was able to find to help me in this endevour.

Wow, really? That would figure, being as I have been working at this off and on for about a couple of months now. I have been searching high and low for answers to this delima only to find this registry change being refered to a different sound card with the same UUA bus. There is no reference anywhere on the web about an updated Conexant sound driver being available on the Microsoft Update Catalog until now. I only had just noticed the Registry change a day or two ago, and thought I would give it a try and it worked. So I thought I would spread the word. And even though I noticed the UUA bus driver in the SP 3, I was still having issues trying to get the sound driver to work, hence the Reg Change (thinking that the UUA driver wasn't working). Oh well, Thanks. Sorry, I just find this all to be a little frustrating. I will download the newly updated sound driver from Microsoft. Thanks again for the info. But would you by chance know of any switches to use for the unattended install of HP drivers? Outside of the ones I have already mentioned in the previous message. Or perhaps a utility that can setup an unattended install of HP drivers?

Which version of NLITE are you using? And you don't necessarly get into the Install CD, but if you happen to be using NLITE Version 1.4.9.1, you need to perform these steps: 1. Copy the XP CD to your hard drive. (Remember where you put the copy on the hard drive) 2. Run NLITE. 3. Press <NEXT> at the Welcome Screen. 4. Browse to your copy of the XP CD by clicking on <Browse...> 5. Press <NEXT> 6. Press <NEXT> at the Presets Screen. 7. In the Integrated area click on <DRIVERS> 8. In the Create area click on <BOOTABLE ISO> 8. Press <NEXT> 9. In the Drivers Screen click on <INSERT> 10. Click on Multiple Drivers (I do this so that all options are Integrated into the install) 11. Browse to where your expanded SATA drivers are located, but only click the folder that contains the Sata Drivers... 12. On the Select Multiple Drivers Dialog box, select the path where your drivers can be found. 13. Press <OK> 14. Make sure Text mode is selected. (Cause that is where these drivers will be implemented) 15. Select the Driver that best describes your Hardware. (Mind you that all these options will be loaded into the install anyway so just pick one, but preferably the one that is closest to your hardware) 16. Press <YES> to begin the process. (Here it is integrating your drivers into the install) 17. Press <NEXT> 18. Here under general, click on the Mode Drop down box. 19. Select Direct Burn. 20. Make sure you have a blank Burnable CD in the CD drive. 20. Click on <BURN> And presto, you have a XP CD with SATA drivers integrated into the install. Hopefully this answers all your questions. Happy installing!

For all those who are trying to find a way to install Microsoft's High Definition Audio Universal Audio Architecture (UAA) High Definition Audio class driver, and are having problems installing the sound drivers on a HP laptop (like DV9000) XP SP3 (slipped streamed, not sure if this works with XP SP 3 Retail), I have found away to get the sound drivers to load. The steps are as follows: 1) Change Reg setting: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlWindows\CSDVERSION = 00000200 [REG_DWORD] 2) Reboot machine. 3) Install MS UAA Driver (mine was sp33867.exe) 4) Install Sound Driver (mine was sp34200.exe for Conexant Sound Device) 5) Install other devices that require the SP 2. (Like on my laptop the modem driver also uses the same installer engine as the Sound Driver which happens to be a Conexant). 6) Change Registry Setting back: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlWindows\CSDVERSION = 00000300 [REG_DWORD] 7) Reboot machine. So why the registry changes, because the installers themselves do a check to see if the system is compatible with the driver. By making these registry changes, you are in-fact fooling the installer into thinking that XP is running SP 2. But keep in mind, that XP is still running SP 3 software, so if this doesn't fix your problem then other measures may need to be taken into consideration. Now I was able to get this to work on my DV9200 laptop should your model be different this may or may not work. I am still trying to find a nice casual way of silently installing the HP drivers. I have done quite a bit of searching on this issue and all I can come up with is this page and derivatives of it, but I think that information is dated cause some of the switches work (like the –s, –a, –e, and –f for the expanding SoftPaq software; but not for the installer of the driver the SoftPaq contains) and some don't (like the –silent gives me errors on some drivers and on other drivers it does nothing; but a few drivers actually work with the –silent switch). Some will tell you what switches to use by using the –silent switch, but most will not. Just keep in mind that the switches the driver instructs to use are used after the –s –a switches that are used for the SoftPaq software (not in place of). Well this is all I know for now. Hope this helps. Thanks for your time, Craig (I am not sure if this is the proper place to put this or not. If not please tell me where to go ... um, in a kind way. thanks )

Sorry, I thought niwa_kun was responding to my message. OOPS! Leave it to me to feed my own foot into my mouth! LOL! Is there someway to remove an idoit post lift by myself? ACK! Thanks, Craig

People will also appreciate a less aggressive way to address other members, and expecially when addressing developers that share their knowledge and programs and also spend their time helping members with the problems they may have. For the record, ilko's joke is quite common, and derives from my "standard reply #32": http://www.boot-land.net/forums/?showtopic=2587 jaclaz TACHE!!! I wish more people would take more time with their messages and critique them. It would make for far less interpretation and make it WAY MORE convenient to respond. Instead of having to guess what it is that people are requesting (and/or saying). I really try hard to make my messages readable so others can read them and understand WHAT is being said. I go so far as to reread my messages at least twice (if not a bunch more times like especially when I am tired) for readability, because I really have bad English and I know this. So I take the extra time to critique my messages, I even go so far as to use WORD or some other word processor. I just wish other people would give the same courtesy to others especially when it comes to requesting advice from those who VOLUNTEER their time. ---------------------- Now for another matter, is there some way to add a user developed script to the WinSetupFromUSB program so as to include other files and folders outside of the usual &OEM&, COMPONENTS, I386, etc., etc; that the program (WinSetupFromUSB) uses to make the bootable USB? Because I am having a problem of knowing when the $WIN_NT$.~LS renames to WIN_NT.LS and back again. This tends to make for messy scripts to try to compensate and impossible in certain conditions like when I have multiple reboots to install drivers and access scripts from the USB, during the GUI (user account phase, I don't know what this is called but it would be during the RunOnceEx phase). Cause I have noticed that this folder ($WIN_NT$.~LS) changes at certain times during the install and has broken my scripts on a number of occasions. Anyway the only cure I see is being able to add this user generated script so that other folders and/or files can be added to the bootable USB on an alternate directory that is outside of the usual directories (like $WIN_NT$.~LS and $WIN_NT$.~BS) that is created on the bootable USB. Thanks so much for your time, Craig PS. Oh btw, I forgot to mention that I am still installing XP SP 3 onto a Vista Machine (XP being the secondary OS on an ulternate partition). @Cooldown Which Windows Operating System and Service Pack are you installing with your integrated drivers? I agree with Iko_T more information is needed, before an answer can be perscribed.

@ilko_t and Jaclaz Oh, Okay... I meant no disrespect. I just thought that we was so over the 8.3 format that it never occured to me that it was still being inforced. Granted a lot of these scripts are linux baised, but I would have thought that what you was developing (which was an MS Windows Application) would take into account for the MS Windows naming convention that is all. Mainly an assumption on my part, so it became a learning thing for me. I am still fairly new with all this install stuff. If it weren't for the fact that MS is discontinuing support with XP, I wouldn't be doing this at all. And I choose to use my laptop as the environment to perform all of this on, because it would provide the best environment for me to learn the complexities of putting an unattended install together. I have 7 install stages setup for myself and each one creates a new install with more stuff than it had before. (And right now I just completed the stage 2 of the 7 stages that are to be completed.) Which is where the commas in question came into play. I kind of figured that it had to do with some kind of parse thing, considering commas are used generally as separators (from my software developement days). Which is why I made a note of it in my notes of what not to do. However, thanks for the cookie and I hope there is no hard feelings. I am looking forward to the 0.2 when it is ready to be realised. And again GREAT work with this current version! Thanks again, Craig mac4020@msn.com

@jaclaz Sorry, I thought I was dealing with a Windows program that deals with MS Windows naming conventions especially when it is reading from the source side of things - not DOS. Thanks, Craig mac4020@msn.com

Well I tried it with XP SP 1 install files that were saved to the HD from the Install CD; they worked flawlessly. Great Work!!! I seem to have stumbled upon something after I had slipstreamed SPs 2 and 3 to the install files. So here is what I have in my notes: Well things did not go so well. I got an error saying that: "Booting 'First part of Windows XP Professional setup' Filesystem type is fat, partition type 0x0E chainloader (hd0,0)/$WIN_NT$.~BT/SETUPLDR.BIN Error 15: File not found. Press any key to continue..." (BTW: where is the <any> key anyway? ) Upon investigation, I found that indeed setupldr.bin was not in the $WIN_NT$.~BT directory and that it was in the $WIN_NT$.~LS/I386 directory. So hmm, I guess no cookie tonite. Awe, bummer! I have to report this and look for a response in the morning. (Edited for grammatical errors.) So anyways not sure where to go from here, but I thought you should know. Great work though! REALLY!!! --------------------------- Okay, I found out why this didn't work. Leave it to me to find this one (of all the things!). WinSetupFromUSB 0.1 doesn't like commas any where in the path name. Cause when I took the commas out of the path name and recreated the install on the USB with the WinSetupFromUSB 0.1 program, everything was there in the $WIN_NT$.~BT. So the moral of this story - no commas is a good commas... LOL! (At least when it comes to folder names AND WinSetupFromUSB 0.1.) Boy ilko_t, aren't you glad I found this one? We would be going around at this for days... LOL!

I don't mean to overstep ilko_t (he truly is the authority on this subject), but there is another tool (program) out that works well with XP installs over Vista and it works from either on Vista or XP; 32 or 64 bit platforms.. It is called Vista Boot Pro and its free (only asks for donations). It has a BCD editor in it that works really well in most cases. I use it myself, cause I have a laptop that has Vista Ultimate as its native OS and I like running XP for some apps. So I install XP as a second OS and then run Vista Boot Pro (on XP) to repair the boot strap for Vista and add an entry in the BCD (with Vista Boot Pro) so that you have a choice of starting XP or Vista when your machine starts, thereby creating a dual boot configuration. It really makes things a lot easier. Question: However I have a question regarding unattended installs, can the tool that is provided here allow unattended installs to run off the USB thumb drive? <EDIT> I see there is already an answer to my question before I had it typed. How soon would beta 0.2 be available to test? If it would be possible, I would like to be one of those testers. I must admit I have only glanced through the past two years of messages on this forum and I have to say that I have been really impressed with the amount of time of devotion and achievement that has been made for this project. I was beginning to think there wasn't anything out that allowed XP to install from a USB device. Truly remarkable! My hat goes off to all those who have contributed to such a cause.

Thanks for the suggestion, but Virtual PC only runs in like a pc environment, and I am trying to make an install for my laptop. And the copy of VMWare that I have can't work with XP SP 2.0 much less 3.0. And to make things worse, I am currently unemployed so I have very little funds to put for this. All I have is time, just no $$$. Anyway thanks for the suggestion. I will keep trying to find a way to do a network install. And some other means of making an install cause I really need those "run once" files to run cause they are my drivers for the laptop - the ones that couldn't be include in the drivers section of the nLite (after being uncompressed). Thanks.

Really?! Do you do a formatting before the initial burn? Cause I get an "unkown error" on two different DVD-RWs (fresh out of the box), but not with the DVD-Rs.

All kidding aside. I have run into an issue, where none of my "run once" installs are working. Actually they have never worked ever since trying at this unattended install stuff. I have attached some files, perhaps someone can show me the error of my ways and put me on the path of excellence (if that is EVEN possible ). A side note: Is there anyway to have nLite burn rewrittable DVDs instead of the single shot DVDs? I am waisting a whole gob of em. Or is there some way of setting this up to do a network installation? Ps. I am using nLite 1.4.9.1 and I am installing Win XP Pro SP 3. Oops almost forgot to put this in.