laddanator

Do you mean using the mbr Fbinst installs and then use the boot code to boot a partition that has g4d installed to?

I have used WinSetupFromUSB Beta 8 to format 37 plus drives...some USB 3 and some USB 2 and some internal HDDs. I am using the FBInst auto format with end results as NTFS. I can say as of today I have had no issues with any model make of computer I boot to other than older XP machines that don't like USB booting anyway. I wish I had an answer but as of today any HP (other than super old ones) I try to boot my WinSetupFromUSB FBinst auto format NTFS drives to always work for me. I will stay tuned as I am curios for an answer or if I think of anything, I will post.

I am not asking for help on modded sources, I am just making a statement about Win7 installing fine with WinNTSetup after the source has been "modded" and Vista which is a NT6x just like 7 and "modded" in the very same way fails. I looked at your link and may leave IE9 out and install with silent install on bootup. My point was that you can see where this is confusing to me that a "modded" 7 will work with this great program but not a "modded" Vista and both are built off the same technology. I know that 7 is different from Vista but both have the same NT6x base and I was just stating my confusion on the matter. Sorry if I came across as "asking for help to get a modded source to work" but just an answer if nothing but a guess as to why 1 works and 1 may not

Using 32 bit created with ChrisR Winbuilder 082. Not sure what you mean by EFI? Thanks for your help on this matter by the way. I also have hex searched every bootmgr file I could find and could not find the Loading file message.

I am using a custom build Win7PE SE and would like to change the Message of "Windows is loading files.." To a custom message Like "Loading Win7PE SE.."

I think this got missed on the previous page with the users long unreadable post! This is the part that is confusing. I have IE9 injected into my Windows 7 sources the same way with DISM and WinNTSetup installs Windows 7 Fine. The only difference is when you use DISM on Vista, Dism calls package manger to do the job but still the same end results. I understand what your saying about not supporting modded sources but why would Windows 7 install fine with WinNTSetup with IE9 and Vista will not with IE9, both Win 7 and Vista are modded in this case?

I know this thread is old but has anyone figured out a way to mod the Windows 7 SP1 bootmgr to change the "Windows is loading files" message

This is the part that is confusing. I have IE9 injected into my Windows 7 sources the same way with DISM and WinNTSetup installs Windows 7 Fine. The only difference is when you use DISM on Vista, Dism calls package manger to do the job but still the same end results. I understand what your saying about not supporting modded sources but why would Windows 7 install fine with WinNTSetup with IE9 and Vista will not with IE9, both Win 7 and Vista are modded in this case?

Vista will load fine if I install it without WinNTsetup. I will look into the DLL file thing and see what I find. B) Ok, the source I was using at first, I forgot I injected IE9 into the source and I used a true clean source and WinNTsetup loaded the Vista fine but why would the source with IE9 cause and issue? I used DISM to make the injection as the same with Windows 7 and WinNTsetup loads it fine. I can use the same Vista source with the IE9 and load it fine from DVD or USB. What do you think WinNTsetup is having an issue with?

I am getting an error trying to install Vista with WinNT 2.3.2. This is a fresh source and Premium. Uploaded with ImageShack.us And This Uploaded with ImageShack.us

The choose your $OEM% folder deal works great, JFX! Thanks for added that!

To be honest, I would say more than half of XP installers mod the source in someway or another and it would be great if your tool would work with a mod XP source but hey if it never does, your tool already does enough. XP will be gone in a year so NT6x stuff is the more important now. Thanks for your work and testing the new build now!

I didn't think this program supported a modded XP source or did I miss something? What did you think about adding the browse for $OEM$ folder button? ?

Look forward to the test. Thanks, JFX!

Got a suggestion if that's ok. I got XP covered on the way I install it but I love the idea you have here with installing NT6x stuff. I use a weird folder setup on my USB drive and like the user above, I use setupcomplete.cmd in the $OEM% folder but I do not keep this folder in sources. I made a universal setup to cover all the current NT6x stuff on reloads so I wouldn't have 4 of the same stuff taking up USB space. Could there be a tab added to browse from an $OEM$ folder to copy over if outside of sources folder?

. Your right, the driver problem is something with this stupid Asus board lol. I mean will your program install XP if I use the integration method above and will it still be considered a "clean" source?

Are you saying if I use the method here http://unattended.msfn.org/unattended.xp/view/web/23/ then this is the way Microsoft intended to be done and your program will load XP if this method is used?

1. It runs the entire text setup and get to the part Setup is Starting Windows, the part right before it shows you the list of HD to install to and blue screens 2. I have not made and iso of this test version I am using but my modded version (update packs) with the same driver packs slipstream boot from my USB and installs fine. I will make an ISO today and test. Also, just wondering, what is the deal with not being able to using a RVM_Integrated XP source as far as not working with your tool? Is it considered illegal to add updates to XP this way? Or is it a conflict with your script and to much to write one to work with an integrated XP source? Not picking your work apart. I love how fast this tool sets up Win 7. Just wondering because if you use a fresh XP source, tons of updates on a fresh install.

Ok, been trying to read all the pages and I must be missing something. Tried this newest tool for the first time today and XP txt setup portion went well and then BSOD (the x000000000007) so not sure if I did the drivers right. Should the source I am using already have Driver Packs slipstream to or should I leave driver packs out and just point to my mass storage drive folder to be copied to c when all the files are being copied with the add driver tab? I also tried Win 7 and everything worked well, just having issues (driver issues) with XP. The only mod to my XP source is the Driver Pack Stuff. Thanks for your work.

Cool beans! Testing now

I was using the extracted version but nod32 sometimes will delete everything in the DPMS folder except chkpci and fat (weird I know) So I started using the ISO unextracted to prevent this.

I have been using the ISO format with this in my menu.lst map %USBDrive%/XP/DPMS.ISO (0xff) map --rehook (0xff)/dpms.bat Not sure if this is the proper way but it works so far. I noticed in the dpms.bat, the ISO is mapped this way map /DPMS.ISO (0xdf) || map --mem /DPMS.ISO (0xdf) Not sure what the 0xdf is

Ahead of you on this. My Asus will work with anything that is mapped to (fd0) except the IMA project. Maps to (fd0) fine but get "can't copy firadisk " and so on error on XP install from the IMA file unless I map to (fd1). Once I map to (fd1)...everything copies fine What? DPMS loads to (fd1) anyway

Anyway this method can be used with DPMS driver stuff from chenell? What I mean is that the cdob's IMA is mapped to "floppy" but so is the driver if found from DPMS. Would this not cancel one or the other out? I notice that the driver is loaded to (fd1) but on my Asus, the stuff from cdob's IMA will only works from (fd1) so you can't have two txtsetup.oem in the same "floppy" right?

Never done one but would be glad to with, cdob, permission. Also, if I do a write up, I would cover all three options 1.With firadisk only 2.With, cdob's IMA file or USB Helper as I like to call it 3. Complete integration of firadisk into ISO source