ilko_t

With manual modifications anything is possible, but I'm lazy, would rather create another partition and place second Vista/PE/whatever can't coexist easily there.

Well, that's the third answer coming by quoting the first post in this thread: Would you mind opening that post and read what it says?

So I guess you saw the menus in BOOT.INI from the root of your USB stick, right? If this is true, what exactly happens when you select either of them? Look at this post: http://www.msfn.org/board/index.php?showto...st&p=815523 Does partition number at first screenshot from Text mode matches partition number in BOOT.INI? Are any other disks displayed, rather than your USB disk and the internal disk? It would also help if you go again in recovery console and post here the output of this command: map arc

Your WMI is broken, that's why. It's been discussed a few posts above, along with possible fixes for WMI, please look at the last couple of pages in this thread for WMI. Please do now quote such lengthy posts just to add an answer, there are FAST REPLY and ADD REPLY buttons I did not get what to add where. I believe the entries were added by Windows setup itself, so why would we have to fix them by binifix.cmd? This is a rare case, besides, less interventions=>less troubles.

It's OK. You are starting NTLDR on the USB stick, which is (hd0,0).Add a second line to BOOT.INI on USB stick, start from USB and select GUI mode. Do you see the menu? Please answer:

Did you start from USB second time, for the GUI part? Dell usually have a hidden first partition, is it deleted? What partition is set active? Can you still boot from that USB stick? Blinking cursor usually means that booted disk/partition is not bootable or bootsector is wrong etc., it should not display it if you started the second part through grub4dos menus. If something is wrong with boot.ini it wouldn't throw this error as well

HKCU, a few pictures should explain it better: First partition is hidden, second is our target: You may add a second entry in BOOT.INI as shown, or make the first one, which is default partition 2 and the second- partition 1, entirely up to you: This will produce this BOOT.INI on the root of USB disk, you can make it such manually: [Boot Loader] Timeout=5 Default=multi(0)disk(0)rdisk(1)partition(1)\WINDOWS [Operating Systems] multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Second part of XP Home Edition setup from hd 0 part 1" /FASTDETECT multi(0)disk(0)rdisk(1)partition(2)\WINDOWS="Second part of XP Home Edition setup from hd 0 part 2" /FASTDETECT The part you are playing with is partition(N), which should be the same as on the first screenshot, displaying where Windows is installed in- C: Partition2. Further details: http://www.msfn.org/board/index.php?showtopic=116766 Q4/A4

From the same post: Alternative way, to place them on the same partition: http://www.msfn.org/board/index.php?showtopic=114543

Yep-

Hi, Have a look at this post, it's a summary what actually is happening: http://www.msfn.org/board/index.php?showto...st&p=797585 ~BT and ~LS folders are renamed at T-9, the last possible place before end of GUI mode. They are renamed back upon first login. You can put any script, using the various options you have BEFORE SetupParams (T-9), when ~LS/~BT names are intact. You may also add your script or launch it by ren_fold.cmd, before the renaming occurs. Or use presetup.cmd if that early stage suits you. If you need to launch a script during first logon, you can add it to undoren.cmd or make it launch by the same, after the renaming part in it. In all scripts USB drive letter is already found for you. http://unattended.msfn.org/unattended.xp/view/web/13/ If I add our stuff, the timeline would look like: »Text-mode Setup 1. Loads Drivers 2. Copies files required for Setup to the Hard Disk 3. Copies the contents of your $OEM$ folders to the Hard Disk <--- this is done by presetup.cmd because we have to remove unattended section in winnt.sif 4. Reboots the PC... » GUI-mode Setup 0. Presetup.cmd is launched 1. DetachedProgram executes from winnt.sif at T-39 stage 2. Installs Devices 3. Installs Network 4. Installs Start Menu Items 5. Registers Components 6. svcpack.inf executes at T-13 minute stage 7. cmdlines.txt executes at T-12 minute stage 8. SetupParams executes from winnt.sif at T-9 minute stage <----ren_fold.cmd is launched renaming ~BT and ~LS in order to avoid 10. 9. Saves Settings 10. Deletes temporary files then reboots... » First Logon 1. Windows logs you in and loads personal settings 2. Both GUIRunOnce from winnt.sif and RunOnceEX executes at the same time <----undoren.cmd is launched to rename back ~BT and ~LS folders 3. Desktop and Taskbar loads Note: What presetup.cmd does: 1) merges the removed unattended section from winnt.sif to \windows\system32\$winnt$.inf 2) If oempreinstall=1 is found in winnt.sif, copies $oem$ folders 3) If OemPnPDriversPath is found spdrvscn32/64.exe is launched to add those paths in registry, details 4) launches binifix.cmd to fix boot.ini on the target hard disk from rdisk(Z) to rdisk(Z-1) In vers. 0.2, which is nearly ready, ~BT and ~LS folders will not be renamed anymore, instead, $winnt$.inf is changed by binifix.cmd to msdosinitiated=0 thus at T-1 Setup does not delete ~LS and ~BT folders and we do not need to rename them to avoid that. 0.2 was delayed until figure out how to amend $winnt$.inf on x64 windows from 32bit environment, but luckily this is now resolved with the help of this excellent info: http://blogs.sepago.de/nicholas/2008/03/13...on-windows-x64/ I hope knowing more how all this works, will let you add whatever you want to the USB stick. Can you post your menu.lst and winsetup.lst in root of the USB disk?As I get it you select Second part of setup, but actually the first part (Text mode) is launched instead, right? The program does not add anything extra to winnt.sif, except a few required lines. If you used the earlier versions- they use unattended.txt if found in your I386 folder AND if winnt.sif was not found.The program does not add anything to $OEM$ as well, it's copied unmodified from your source. As for the boot.ini- if you do a few installations one after another, Setup reads the existing boot.ini and add it's contents to the new boot.ini, hence the duplicate lines. The last line is to be able to perform repair install from USB or Recovery console if started from USB to be able to see your installation. Without it neither will happen.

What drivers did you integrate? Is any OS installed at the moment on it, Vista? What exactly did you type in grub4dos command prompt? It should be root ( followed by TAB key. Do you have in BIOS option for SATA mode- native, IDE compatible or AHCI off?

Hi, thanks for the guide As for the USB setup- You are saying the file was on the USB stick, right? Could it be a bad copy, due to antivirus interfering while preparing USB or a something else, related to the file copy operation? WinSetupFromUSB copies the whole folder I386 as it is, there is no messing of any kind. Maybe you can compare checksum of sp2.cab on USB and in the source folder... Normaliz.dll is part of IE7 as far as I get it, did you add IE7 as nLite addon, or what method did you use? Are IE7 files outside I386 folder? Because you did not use your answer file winnt.exe /u:(path_to_)winnt.sif /s:.... http://technet.microsoft.com/en-us/library/cc739372.aspx http://labmice.techtarget.com/articles/winntcmd.htm

Why don't you nLite the copy which worked, there are plenty of guides around? AFAIK on Asus EeePC you should be using at least SP2. The post above yours confirms this, and at the same time you are asking why the SP1 copy did not work

If you want to relate winnt.exe (correct is winnt32.exe for this environment), the file parsed is dosnet.inf. winnt.sif is used by winnt32.exe only if /unattended:MyUnattendedFile.ext switch is used. Since usb_prepare8.cmd (looong ago) winnt32.exe is not used at all. Winnt.sif is expected on different locations depending what media Setup is performed from, for HD-like media in our case, it's read from ~BT folder. Winnt.sif is read during (text mode) setup process first by setupldr.bin, next by setupdd.sys. Winnt(32).exe does not play role at all, it's used only to prepare a hard disk so Setup can start with the text part, and is not used in any way during Text or GUI mode parts. The .sif file, sitting next to winnt(32).exe is supposed to be dosnet.inf. In my first reply I answered you accurately, guessing what you exactly mean, ignoring all the technical stuff you obviously don't know, did you miss these parts? If you expected more, here it is- if you want to amend winnt.sif AFTER the program, then do so with the one in ~BT folder, but be careful not to delete the entries added already, as some of them are critical for the process. Do not add unattended section as well, another important part. This is the reason I do not prefer winnt.sif to be touched after the program, unless one REALLY know what he/she is doing. There are people, using directory with XP ISO file as source, complaining that it "doesn't work". After a few posts, it's now clear you are not among them. There are experienced people, using other .sif file- txtsetup.sif to add drivers or even programs, which location on HD-like media install is confusing, it's now clear you are not among them. Ask precisely- you'll get precise answers, don't let the other party guess, there could be number of possibilities, which you may not be aware of. This is what people providing help would appreciate, a well thought out question leads to a precise answer, which is not time consuming at all: Don't you like this better? Is it easier to answer, without a any guessing involved?

You are welcome As for the reason for the joke, which you did not take as such- it's the number of questions, surely not only here, asked without any details in a pretty confusing way, thus making the answering part to guess, ask further, apparently spending own time on that, interpret what the question could mean and so on. Is it really hard to be informative when asking for help?

valkyrie80, the program do not use ISO as a source, it uses directory on your hard disk, mounted ISO or a CD. I guess you are using mounted in a virtual CD ISO file. You can extract the contents of this ISO to your hard disk and use this directory as a source. As for the .sif file, I guess again you mean winnt.sif. You can amend it BEFORE using the program. Change it in the directory where you extracted the ISO file and then run the program. If my guesses are not correct- please provide details, team's crystal ball is for repair and the taro cards set was stolen

How to you make your UACD? There is no much difference, forget for now about USB, prepare your source as you do usually and then transfer it to the USB. If you ask a specific question I might be able to help you some more.

WinSetupFromUSB already does all that, did you try it? What part of the unattended setup fails? If your source is prepared for unattended install, it will be transferred to USB as such, there are very few limitations left. BTW I am assuming UACD stands for unattended CD, not for a custom made jumbo nlited, with hexedited files all-in-one XP/2003/2000 DVD/CD

Use the latest version, this has been fixed...

You also should be using SP2 or SP3 if error code is not 0x0000007B. What is the error code on the blue screen?

Deletion occurs during Text mode of setup, some of the compressed files. You may manually sync the folders- look at FAQ #5 http://www.msfn.org/board/FAQs-t116766.html Alternatively you may want to use the program again- it will notice the present installation and ask you whether you want to delete it, sync it, or create a new source folders, renaming the old ones (and patching the necessary files against the new names). The latter is used to prepare up to 10 different Windows sources on the USB disk. BTW- did you try to repair WMI first?

What did you use to format this hard disk? What file system? Did you set active partition? How is it partitioned?

Thanks for the feedback Keep in mind that with any versions different than XP i386 SP2 or SP3, Text mode setup will delete some of the compressed files and if you are doing a new install, you'd have to synchronize source files first, folders I386 and AMD64. There is no support for now for non English versions. Rename temporarily Programme to Programs, let it copy everything to the USB disk, then rename that folder back to it's original name.If Programme is the only difference I can make it in the next version, it's easy.

A few things which may help:http://www.tek-tips.com/viewthread.cfm?qid...6715&page=2 http://www.nliteos.com/faq.html#Q26 Possible cause of the problem: http://www.msfn.org/board/nLite-XP-Pro-sli...-S-t119487.html Please let me know if there is a result.

Correct It means when you connect USB disk to the target computer, you have to start from USB 3 times, apparently keeping the USB disk plugged in: 1. Text mode part of Setup 2. GUI mode part 3. First start of Windows