ilko_t

I guess yes. This line is made out of winnt.sif and the syntax there seems correct, so I assume this "translation" is also correct.Try modifying winnt.sif to: [GuiRunOnce] Command0=%SystemRoot%\System32\nLite.cmd If still no luck- try adding START /WAIT to each line of nLite.cmd. Ensure nLite.cmd is not executed indeed- add a line on the top: echo TEST > c:\test.txt After install is file c:\test.txt present? ====================== You may also try to modify the original nlite.cmd from svcpack and use this method, replace the top line with this: SET TAGFILE=\$WIN_NT$.~LS FOR %%h IN (U D M N O P Q R S T V W X Y) DO IF EXIST "%%h:%TAGFILE%" SET CDDRIVE=%%h: if "%CDDRIVE%" == "" ( FOR %%h IN (C E F G H I J K L) DO IF EXIST "%%h:%TAGFILE%" SET CDDRIVE=%%h: ) SET Source = %CDDRIVE%\$WIN_NT$.~LS\ Jaclaz- nLite.cmd he used is attached in archive in one of the previous posts. The one you quoted is produced by nLite I guess, unless he modified it.

So everything is in place (C:\install\ exists, right?), but nLite.cmd is not executed. I an not aware with any issue with GUIRunOnce entries and USB setup, actually it has been used successfully since the first batch files to execute undoren.cmd and binifix.cmd. Maybe looking at setup log files may reveal what went wrong Please attach the following files from the target computer: c:\windows\setuplog.txt c:\windows\setuperr.log c:\windows\Setuperr.txt c:\windows\Setupact.log

Was nLite.cmd in \windows\system32\ ? Was directory C:\Install\ present on the target computer? Please attach USB_stick\$WIN_NT$.~LS\I386\presetup.cmd and c:\dir.txt from your computer, which is made after running this: dir /s /a U: > c:\dir.txtReplace U: with the drive letter of your USB stick.

Thanks for that, I have reported the seller. Hopefully ebay will take an action against him. Please put in a zip archive and attach the following files, remove product code and personal details if present: USB_stick\$WIN_NT$.~BT\winnt.sif USB_stick\$WIN_NT$.~LS\I386\tempunat.inf nLite.cmd wherever it is on USB stick \WINDOWS\SYSTEM32\$winnt$.inf <--- this is where you installed windows to \WINDOWS\System32\nLite.cmd

http://www.msfn.org/board/index.php?showto...st&p=846339

Open up ~LS\I386\presetup.cmd on the USB stick. Add /norepair to binifix5.cmd: CALL %systemroot%\system32\binifix5.cmd C: /norepair /msdosinit0

What does the blue screen say? This is the interesting part, not the blue screen itself If it's the 0x0000007B error try the modified ntdetect.com as mentioned in the pinned FAQs topic. Cure for other error messages are also mentioned there.

Is this the same issue like here? http://www.msfn.org/board/index.php?showtopic=131564 Try answering the questions quoted.

Did you run it with options?To keep things together use MkMigrateInf2.cmd from WinSetupFromUSB folder\files\winsetup\. Use in command line: MkMigrateInf2.cmd H: c:\migrate_inf.txt Where H: is drive letter of the USB stick. Re-attach c:\migrate_inf.txt.

Also check the FAQs: http://www.msfn.org/board/index.php?showtopic=116766

Hi, everything seems correct in the posted files. I am really clueless as of what maybe causing this behavior. It still could be the USB stick(s)...

On the machine you used to prepare the USB stick. Please also mention what drive letter was the USB stick last time you prepared it with Windows setup. All this is on the same machine, where you run WinSetupFromUSB or USB_multiboot. Leaving the remote machine alone for a while.

Ok, now missing SATA disk problem is resolved, you can use either source you have as it should not be the problem. USB stick getting D: might be something to do with BIOS or the USB stick Try in BIOS-->Advanced-->USB configuration to change values of BIOS EHCI Hand off to Disabled and maybe Legacy USB support to Enabled if it is Auto. Just random ideas... Another one- open up Regedit, go to HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices, right click on it and export it in a reg file. Attach this file along with the latest migrate.inf in ~BT folder on the USB stick.

You have no entries for iaStor, neither for PCI\VEN_8086&DEV_3A22 in the txtsetup.sif posted. What is broken? In your first post I see iaStor loaded. You are saying that you have used the same source. Where did iaStor driver come from in your first post and why it is not present in the posted txtsetup.sif? Something must have been changed meanwhile. Presetup.cmd is loaded at start of GUI mode and does not play any role during Text mode where you problem is. No need to play with it at all. I would advice you to start with clean, original, not modified in any way XP SP3. If you cannot find such source use for the tests the trial Server 2003, freely available from MS: http://technet.microsoft.com/en-us/windows...r/bb430831.aspx Since you will be testing Text mode only you won't need a serial number, just get the first English img file from here, extract it somewhere and use it as a source. http://download.microsoft.com/download/5/1...F/X13-04874.img http://www.microsoft.com/windowsserver2003...llinstruct.mspx Use WinSetupFromUSB with Copy Setup boot/RC files only option checked. This will let you test Text mode only without copying the whole source. Files put on USB stick are 6-12MB total size and preparation takes seconds. 1. Try to prepare the USB stick in NTFS, and BIOS in IDE mode. If no luck go to 2. Do not touch anything with nLite yet. 2. Integrate BTS mass storage drivers, selecting Text mode drivers too. Format and rebuild the USB stick with the same option checked, put BIOS in AHCI/SATA mode. Do not touch anything with nLite yet. Is your USB stick now U:? Do you see the internal hard disk(s) now? Please follow the advices blindly, do NOT introduce any changes, which in your opinion may be irrelevant.

Can you attach your txtsetup.sif from USB disk root? What computer is this, brand/model if is laptop? Motherboard model if desktop? Do you know by any chance the HardwareID of the SATA controller? I see iastor used, can you try setting up SATA controller in IDE mode and try again?

You most likely do not have the appropriate mass storage (SATA) driver included, or in BIOS SATA mode was on IDE and now is in AHCI/SATA/RAID mode. Did you use the same windows source? Don't use FAT on this large drive, try FAT32 instead, but be warned- file copy part in Text mode could be painfully slow. NTFS is much faster.

You will fall into compatibility issues, not all BIOSes have an option for USB-ZIP. For the idea- try to put I386 folder, say in XPPRO folder in root. Change txtsetup.sif and add : SetupSourcePath = "\xppro\" SetupSourceDevice = \device\floppydisk1 Put boot files as described in dosnet.inf floppy sections in root. In the beginning stay as close as possible to the original MS design, then amend step by step. Or you might just download the 6 XP Setup floppies set from Microsoft site and put all the files in root, replacing later on TXTSETUP.SIF with your own. Not quite sure of "floppydisk1" proper syntax, you may need to experiment.

Not only. If unattended section is present in winnt.sif Text mode setup will attempt to install windows in the same place where ~BT and ~LS folders are, that's our USB disk. This is by MS design, even if the section is empty.That's why the program removes it into a file, called tempunat.inf, and befora start of GUI mode, by using presetup.cmd that section is merged back into \windows\system32\$winnt$.inf. This file is made off winnt.sif entries and is used of the GUI setup. Got the idea and why your unattended section was not in winnt.sif? As for the OemPnpDriversPath entries- open up presetup.cmd and look if the are already as spdrvscn32.exe parameters. Check also if they were merged into the registry. There shouldn't be any problem with that but double check. I've seen reports that DetachedPrograms does not execute always if the fake Setup.exe (which launches presetup.cmd and then executes the real Setup.exe) is used.Since presetup.cmd is always used, no matter if BTS DP are integrated or not, you'd better put your script in it. It's always launched as it merges the unattended section back into $winnt$.inf, changes msdosinitiated to 0 in the same file to avoid deletion of ~LS, ~BT and a few other files at end of GUI (T-1), copies $OEM$\$1 etc. folders if present, adds via spdrvscn32.exe whatever is present in OemPnpDriversPath, fixes BOOT.INI on the internal disk etc. etc. Can you translate what that command above does exactly? Do you have Drivers.cmd in each subfolder? What actually Drivers.cmd does? Maybe we can find a better way to perform the task required. I an afraid there will be boom of questions "why my ISO didn't start?" since this type of ISO loading requires either grub4dos ISO emulation aware distro (PartedMagic, UBCD are the first two), an OS which boots off RAM (PE via RAMDISK, Linux with only KERNEL and INITRD), or simply a real-mode OS such as DOS.Since that's not universal way to load ISOs and adding such to menu.lst is a trivial task (samples already included in original menu.lst), I'd rather not go into further complications.

First try installing the program in its default location, check if that makes any difference. Second- use 0.2.1, third- try it on Vista or XP. I have never tested it on Windows 7, there a a few external tools used and ALL them have to support 7. In other words- no reliable support for now of Windows 7.

Uploading 0.2.1 now, the cause remains a mystery for me, since this way to launch grubinst was used since the first versions and I am still unable to reproduce the error. Anyway, glad it's solved now, thanks for participating

Here is another test version, please try it. Interested again if grubinst reports success and if mbrdiskN-date-time.dat and bsdiskN-date-time.dat files are in C:\WinSetupFromUSB\. I am unable to reproduce the issue no matter what I try, thanks for helping. http://www.datafilehost.com/download-e410c895.html Thanks 1. 2.1.8 does not set active partition, that's why WSFUSB won't accept the drive as properly formatted- either MBR is missing or there is no partition set as active. 2.0.6 sets the only partition active. 2. Either grub4dos bootsector was not installed, or the bootsector was overwriten by external program later on. Or maybe we fall into the same case like here: http://www.boot-land.net/forums/index.php?showtopic=5059 Please attach all WinSetupFromUSB log files, the latest one is in program's directory called WinSetupFromUSB.log and the previous ones are cab compressed in directory Backups. Put them in a single zip archive and attach them with your post, or upload them to datafilehost.com for example. Thanks for helping

Try this, just replace the original file in program directory and launch it. http://www.datafilehost.com/download-ab913a8a.html Does grubinst now say "MBR/BS was successfully installed" twice? Does WinSetupFromUSB reports the same error again? edit: before pressing enter at each CMD window to continue, do you see mbrdiskN-date-time.dat and bsdiskN-date-time.dat files in C:\WinSetupFromUSB\

Did you remove any hardware or restart your PC? In the log file there were a few more mass storage devices present: Why the USB stick is hd1 now? Maybe the WMI query returned inaccurate information, if you ahve only 1 internal hard disk USB stick should have been \\.\PHYSICALDRIVE1 ... Can you reboot the PC and try WinSetupFromUSB again? If the error persists please post the new winsetupfromusb.log file along with the output of this handy batch file made by Jaclaz run right after WinSetupFromUSB without removing/disabling any hardware: http://www.boot-land.net/forums/index.php?...c=6492&st=7 You will need dd fro windows in the same folder- http://www.chrysocome.net/downloads/dd-0.5.zip

That would be interesting, need to think in that direction for a while. Strange, everything seems fine, but apparently MBR file was not created.Can you format the USB stick again and then give it another try? If you have a chance to disconnect the card reader you have attached that would be even better. If still doesn't work- try issuing the commands manually- first open up CMD and enter: c: cd \WinSetupFromUSB\files\grub4dos\ grubinst.exe -v -l (hd3)Assuming card reader is still plugged in. If you see hd3 is the USB stick then: grubinst.exe -v -s=mbr.dat -t (hd3) Please copy-paste here all the output from the above- right click in the CMD window, select mark, use the mouse to select everything, press enter then paste it here. Did you get now a file mbr.dat in C:\WinSetupFromUSB\files\grub4dos\ ?

Can you please post your WinSetupFromUSB.log file as attachment?