ilko_t

If it's ATA, then there is no need to add that drivers pack. Are you sure you created a new ntdetect.com following the link in FAQs and replaced the one in USB root? If that doesn't help I am out of ideas, may be only an updated BIOS. Can you prepare the USB disk selecting USB stick in the menu, and test if Text Setup loads fine? Do not continue installation, just check if you can reach the screen with Hard disks available.

If still giving BSOD try changing in BIOS SATA mode to IDE, do you have a similar option? Like AHCI off, SATA mode- IDE.... Is it's hard drive SATA? Do you have any mass storage drivers slipstreamed? Have you tried slipstreaming BTS mass storage drivers? http://driverpacks.net/DriverPacks/

Good, look at the FAQs and find what you can try about 0x0000007B. http://www.msfn.org/board/FAQs-t116766.html

Did you look at the sticked FAQs? What model is your laptop? Did you select USB hard disk (option 0), although it shouldn't be the cause for the BSOD.

I wish it was possible, but it is not. XP will bluescreen 0x7B at some point as it will lose connection to the emulated drive since has no drivers for it. Install from ISO into RAM disk, using 2003 ramdisk.sys is also not possible, as reported a while ago by cdob. http://www.msfn.org/board/Installing-Unatt...906#entry584906 http://www.msfn.org/board/Installing-Unatt...006#entry588006 http://www.msfn.org/board/How-to-boot-inst...040#entry659040 http://www.msfn.org/board/XP-x64-Install-t...805#entry749805 ilko

FAQs: Q1: Is there a guide with screenshots? A1: http://www.911cd.net/forums//index.php?sho...st&p=143701 You should also have a look at the Help files in \Help_Info folder. Note/addition by jaclaz on 15/05/2013: I happened by pure chance to come across another guide with screenshots, that though aimed at HP's, can be of general use, here: http://h30434.www3.hp.com/t5/Notebook-Operating-Systems-e-g-Windows-8-and-Software/How-to-install-Windows-XP-from-USB-flash-drive/td-p/529005 Q2: I am getting BSOD, error 0x0000006F during Text mode Setup, what is wrong? A2: When using Nlite to slim down your source do NOT select "Operating System Options-->Manual Install and Upgrade for removal". This option is crucial for installing from USB. Q3: I get BSOD 0x0000007B during text mode of Setup. A3: On some motherboards USB booting is tricky, common example are many Dell systems. Try using a modified NTDETECT.COM as mentioned here: http://www.msfn.org/board/index.php?showto...mp;#entry738009 Another reason could be missing mass storage driver. Make sure you have it, or integrate BTS mass storage driver pack in your source. This must be done AFTER Nlite. Q4: I am getting HAL.DLL or NTOSKRNL.EXE not found error, why? A4: You are installing Windows to a disk/partition other than first disk/first partition. Amend BOOT.INI on USB disk to reflect your setup. For example- if installing windows on SECOND disk/third partition, and FOLDER name is MYWIN, that line in BOOT.INI should look like: multi(0)disk(0)rdisk(2)partition(3)\MYWIN="2. GUI Mode Setup Windows XP, Continue Setup + Start XP from HD 1" /FASTDETECT Please note that rdisk(0) means first hard disk. Because we are booting from USB disk it becomes first, hence the first internal hard disk (which is second when start counting from our USB disk) gets rdisk(1), second- rdisk(2) and so on. Q5: What Windows versions can be used? A5: The method works without issues using Windows XP SP2. If using others than this (2000, 2003, XP x64, XP SP1...), some compressed files will be deleted from your USB disk when installation is completed. In order to preform a new installation you will have to syncronise I386 (and AMD64 for x64) folders in your source and USB disk. You may want to use KillCopy for example and copy YourSource\I386(and AMD64 for x64) to USB disk\$WIN_NT$.~LS\ telling it to skip all existing files. Q6: How about installing multiple Windows from USB? A6: Please read this guide: http://www.msfn.org/board/index.php?showtopic=114543 Q7: How about adding multiple (Bart)PE on the same USB? A7: Please look here: http://www.msfn.org/board/index.php?showtopic=115156 Q8: I got "Insert WinXP CD" Error, why? A8: The correct value in WINNT.SIF is MsDosInitiated="1". This is done automatically by the script. You must have changed WINNT.SIF after prepared USB disk. Q9: I cannot start my freshly installed windows without the USB disk A9: When installing you have to leave USB disk plugged in until after first normal windows desktop. This is because at first logon undoren.cmd is executed, which amends BOOT.INI on your new disk using binifix.cmd, and also renames 2 folders and txtsetup.sif back to their original names. If you are in such situation and don't want to reinstall, manually start UNDOREN.CMD and BINIFIX4.CMD located in your \WINDOWS\SYSTEM32 folder with the USB disk connected. Q10: I want to use [unattended] section in WINNT.SIF A10: It shoudn't be used when installing from hard disk like media. Setup will not ask you where to install windows to. Look here for workaraounds: http://www.msfn.org/board/index.php?showto...424#entry734424 http://www.msfn.org/board/index.php?showto...434#entry734434 In recent versions $OEM$\$1 and $OEM$\$$ folders are copied by REN_FOLD.CMD, which is executed at T-9 by the Section [setupParams] of winnt.sif file) as usual to systemdrive (usually C:\) and systemroot (usually C:\WINDOWS) respectively if found. Q11: Will my Nlite add-ons install as if installing from a CD? A11: Generally- yes. Q12: Everything on USB disk was deleted after Setup, why? A12: You have replaced WINNT.SIF after executed the script, there are number of lines added and removed by it. You should change it before launching the script, so it can add and remove the lines required. Q13: My hard disk got letter F(G,E...), why? A13: If you have a card reader or any other USB mass storage disable it or turn off prior to installation. If you cannot, then partition the hard disk during Text mode Setup, then quit using F3, reboot and start Setup again. Once you have partitioned and formatted hard drive, it should get letters starting from C:. Q14: What is RDUMMY.SYS used for? A14: Look here for detailed answer: http://www.msfn.org/board/boot-install-usb...7-page-417.html Q15: I have a mixed SATA and IDE disks/CD/DVDs, any problem with that? A15: If you are installing on SATA/SCSI disk, while having IDE present, preferred boot drive may become your USB disk, this is bad, Setup will overwrite MBR/bootsector and (re)place boot files on it. If during TEXT MODE your usb disk is listed first when SETUP searches for disks , above SATA/SCSI disks, disable in BIOS IDE channels including the ones with CDROM/DVD attached or just disconnect them temporarily, this should fix the order. Do not continue install if USB disk is listed first, this will corrupt files and MBR on it. Details: http://www.msfn.org/board/index.php?showto...345#entry655345

You are welcome. However, please use search function, or at least have a quick look at the subforum, it's new and has a few pages only. I guarantee you, this question has been asked and answered every third or fourth thread.

This option is in Nlite and must not be selected. Make a new XP source without selecting the option.

What is your source? Is it Nlite-ed? Did you select Operating System Options-->Manual Install and Upgrade for removal? You must NOT. That's the most common reason.

What is your source? XP? SP1,2,3? 2003? SP? Is it Nlite-ed? Did you select Operating System Options-->Manual Install and Upgrade for removal? That's the most common reason. What is your USB device? Hard disk? USB stick? How did you format it? What file system? What do you mean "1) Nothing happens"? Nothing from what you expected, or nothing indeed? This is the most interesting part. You should not use that unless you have installed windows on the SECOND hard disk. is to start grub4dos, from it you can launch whatever else you want, including, not only Vista.ilko

You don't copy anything manually, unless you want to add something not supported by default, i.e. some Linux distro... "usb content source" leave as it is. Once USB stick is ready plug it in the machine you going to perform install on, make sure in BIOS USB stick is set as first boot device or use F11/F8/ESC/whatever you have to change boot order without entering BIOS. On first run Select Text mode. Complete it. Second step is to start from USB again. Select "2. GUI Mode Setup Windows XP, Continue Setup + Start XP from HD 1" Third step- start from USB again- Select 2 again. Once windows is completely loaded, give it a few minutes to finish the startup scripts, which change a few things on the USB stick and then you can remove it. You are done. Is it any clearer now? ilko

Changing $WIN_NT$.~LS to $WIN_01$.~LS in setupdd.sys. GSAR -i -o -s$:x00W:x00I:x00N:x00_:x00N:x00T:x00$:x00.:x00~:x00L:x00S:x00 -r$:x00W:x00I:x00N:x00_:x000:x001:x00$:x00.:x00~:x00L:x00S:x00 setupdd.sys Does it make sense now?

How about hide (hd0,3) and unhide (...) in grub4dos for each partition? Same here, if UBCD4Win is the only one, why don't you leave it in minint and change the rest? Another option is to ask the question in ubcd4win.com and/or 911cd.net forums. ilko

Generally- yes, your addons should work just as installed from a CD. Why don't you give it a try first, and if you have problems then ask?

When using Nlite did you select Operating System Options-->Manual Install and Upgrade for removal? You must NOT in order to install from USB. Check if you have winnt32.exe in your I386, if you don't have it- then you did select that option and will need another source.Is your XP version English? If not- then this file must have been removed by Nlite or you. Find it on your original copy. Well, did you managed to complete Setup or not?That option is as explained above- if you install on SECOND hard disk. Please try to be clear when asking questions, what does FAT16 and NTFS on both disk have to do with anything discussed above?

The only idea for using makeBS is if you start with ntldr/boot.ini to be able to start PE without using another menu (grub4dos), it's entirely up to you what to use WinFLPC does work from USB, just the same way as a regular Bart PE, played with it some time ago. I don't think you are going to have troubles with that. Reconsider using multiple partitions, it's an easy way, instead of all the HEX editing. I think you should have no problems having UBCD4Win on first partition, custom Bart PE on second and WinFLPC on third. Use grub4dos to start each of them: title Start UBCD4WIn from 3rd partition root (hd0,2) chainloader /minint/setupldr.bin title Start WinFLPC from 2nd partition root (hd0,1) chainloader /minint/setupldr.bin and so on. The only limitation that you can have four primary partitions, booting from extended is possible afaik, but cannot give you details. Another limitation could NOT to have txtsetup.sif and winnt.sif on first partition, as setupldr.bin may try to read them first and HEX editing would be necessary.

Hi, Look here and the following replies: http://www.911cd.net/forums//index.php?sho...=21312&st=0 http://www.msfn.org/board/boot-install-USB...640#entry659640 http://www.msfn.org/board/boot-install-USB...751#entry664751 In short: Is your PELDR the original SETUPLDR.BIN renamed? Use an original file for simplicity. Copy SETUPLDR.BIN in USB drive root as PELD1, PELD2 and PELD3. ERD commander- change the first occurrence of txtsetup.sif in PELDR1 to notsetup.sif. This is to prevent setupldr.bin using txtsetup.sif from root and use the one in minint. Change all occurances of minint to mini01. Copy ERD commander to \mini01. Bart PE- change the first occurrence of txtsetup.sif in PELDR2 to notsetup.sif. Change all occurances of minint to mini02. Copy Bart PE to \mini01. UBCD4Win- change the first occurrence of txtsetup.sif in PELDR3 to notsetup.sif. Change all occurances of minint to mini03. Copy Bart PE to \mini03. Use makeBS.cmd: makeBS U:\PELD1 /a "Start ERD Commander" makeBS U:\PELD2 /a "Start Bart PE" makeBS U:\PELD3 /a "Start UBCD4Win" This will produce the needed bootsectors and add the relevant entries in your boot.ini. Change U: to your USB drive letter. Next you will need to take care of PROGRAMS folders. Look at the first link above. Another way- would you like using RAM boot? Are those 3 installation small enough to fit in memory on all the computers you intend to use on? That will make the solution easier. Yet another option- use multiple partitions, use Grub4DOS to launch each of them. ilko edit: use gsar for changing minint to mini0x gsar -i -o -s\minint -r\mini01 stld1 Should change 2 occurrences, PE booted fine. I could not find a way to change only first txtsetup.sif using gsar.

Have you been able to perform USB boot on the same motherboard, using the same USB stick? To save you time- since only USB boot is your issue, do not use USB_multiboot until you ensure you can do USB boot. How to test- after formatting just copy ntdetect.com, NTLDR from your XP source and create boot.ini on the USB stick: boot.ini [Boot Loader] timeout=30 Default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS [Operating Systems] multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Test 1" multi(0)disk(0)rdisk(2)partition(1)\WINDOWS="Test 2" If you reach the menu TEST 1 and TEST 2, then you are good to go.

Have a look at this thread and try the tools mentioned: http://www.911cd.net/forums//index.php?showtopic=21378

Hi, I think you have issues with your USB stick, your problem has nothing to do with any of the batch files. Stuck at letter J as far as I remember indicates exactly problem with MBR and/or bootsector. It happened to me a few days ago while experimenting with different bootsectors and MBR, but can't recall what exactly I did. None of the USB format ways helped me, neither writing zeros to whole stick. I had a backup image of the whole stick and just restored it. After that format worked fine. I don't have an explanation why this happens, may be jaclaz when gets back or somebody else can comment on this. Not saying that your case is this, just a possibility. You may also try to find a low level format utility from the manufacturer of your stick. About HP format utility- it can format BOTH with DOS and NT bootsector, you simply do NOT have to choose "create a DOS startup disk" option. This gives you NT bootsector, calling NTLDR. The other tool which you didn't name, I guess it's PEtoUSB, works just fine too. In short what you may try: - write here what is your USB media, with details and how you formated it last few times - try to find format utility from the manufacturer then format with PEtoUSB or HP USB format utility - attach here a copy of your bootsector and MBR, easy to use is HDHacker for the purpose and be careful which HD you select. Thanks for the suggestion on the updates and for the warm words ilko

Thank you, nice start I guess the author of dummydisk.sys should also be pleased, as rdummy.sys stands for reverse-dummydisk.sys. But that's not interesting matter. If I had to follow your lines, I'd have to write something like "what a retarder question in this forum, don't you read forum names? And lastly- don't you know about google.com...or forum's search option..."But since it's a friendly forum, I will point you to some of the answers: Where it all started: http://www.911cd.net/forums//index.php?showtopic=14181 In Dietmar's signature you will find links to his guides. Some variation, all based on Dietmar's work: http://www.911cd.net/forums//index.php?showtopic=16760 http://www.911cd.net/forums//index.php?showtopic=16696 http://www.ngine.de/index.jsp?pageid=4176 http://www.usboot.org/tiki-index.php <---this might not work for x64 I don't remember reports for using XP x64, but don't think there should be any difference, apart from the mentioned one above. ilko

Good I'm still puzzled about this unicode thingie, why only ~LS string First time when thread was started I opened setupdd.sys in Tiny Hexer and searched for ~LS- not found. Who would guess to change to unicode... Thanks cdob, brilliant find

Did you select unicode? Without that, Tiny Hexer won't find the string. Mine is from XP Pro SP2 Eng, setupdd.sys version 5.1.2600.2180 from 03-08-2004. What do you have at that offset?

Wimb, here is setupdd.sys from Tiny Hexer: Yep, must be XPS01 instead of SETUPLDR1 if using NTFS. If it's FAT16/32 then setupldr.bin names should be used. May be it's a good idea in next release to use only XPSTP, no matter what FS, also to copy only bootsectors and setupldr.bin for the chosen options as we discussed. I.e. BartPE not selected- do not copy PELDR and bootsector for it, same for DOS/Syslinux etc. I used FAT16 and usb_prepare8, normal ntdetect.com, no need to HEX edit it. Strings replacements with gsar as more convenient. ilko

@wimb- the above part from txtsetup.sif is from 32 bit XP. For x64 make sure you use: makebt\fedit -f %usb_temp%\txtsetup.sif -add -once -l "ren_fold.cmd = 55,,,,,,_x,2,0,0" -s SourceDisksFiles makebt\fedit -f %usb_temp%\txtsetup.sif -add -once -l "undoren.cmd = 55,,,,,,_x,2,0,0" -s SourceDisksFiles makebt\fedit -f %usb_temp%\txtsetup.sif -add -once -l "binifix4.cmd = 55,,,,,,_x,2,0,0" -s SourceDisksFiles ilko