lilas, on Oct 6 2007, 07:21 AM, said:
....Note that the logon is important to rename and change the ini entry to z-1. Since in my installation after GUI setup I do not see any logon, I
access directly to the desktop (maybe with a default user ?). So after checking that boot.ini and folders are not changed/renames, I do a manual
close session and then logon as administrator. And then I did verify that c:\boot.ini is well changed (z-1), and the two folders on the USB key
are renamed back correctly....
Is this problem still persisting?
Do you need to logon as administrator in order to execute binifix.cmd and undoren.cmd? What rights first logged user had?
If yes then we will need to use RunOnceEx.
wimb, on Oct 6 2007, 11:51 AM, said:
NEW RELEASE is Available as usb_prep3.zip file in Attachment....
lilas, on Oct 7 2007, 06:03 AM, said:
We probably need a kind of execution log (maybe simply by just capturing all usb_prep3.cmd output (stdout/stderr) with
"tee" (tee.exe under Win32), e.g. usb_prep3.cmd | tee usb_prep.log), so that by browsing the log problems can be spotted
easily (and for audit/history also). Without the log, some script (like MakeBS3.cmd uses cls command so the output is cleared
in the window command prompt, so even if I have a big screen buffer, I cannot use copy-paste to report/indicate needed messages output).
4) Maybe offer the option to delete the temporary image tempimage.img (after the dialog to accept unmount the temporary drive)....
lilas, on Oct 7 2007, 06:21 AM, said:
OK, after resetting ntldr attribute on my USB key, and after unmount all drives (vdk, ImDisk...) and unplug all drives, and replug USB key,
I got associated physical drive letter.
Then the script executes smoothly without errors and my key is prepared.
So it remains to test in on real hardware, but normally success will be there. Report later.
Edit: I tried this time with hi-speed 8GB key formatted FAT32, but curiously this time the file copy by setup is very slow, much slower
than with 4GB key formatted FAT16 ! So I interrupt the process and rebuild the 8GB formatted with FAT16. Report later.
I am having similar troubles when ImDsk has mounted drive for too long, unmounting and creating a new one it fixes troubles.
Another thing- boot files position on stick is critical in most cases, a fresh format should be performed prior to using usb_prep.cmd. The script copies those files first.
lilas, on Oct 7 2007, 10:25 AM, said:
Some quick report:
- 8GB key cannot be formatted FAT16.
- Even after reformat with FAT32, 8GB hi-speed key is very slow during setup file copy (5 min to have only 10% copy complete).
- Using low-speed FAT16 4GB key freshly formatted, setup file copy is lightening fast (20 s to get 10% complete, total duration (100% complete) = 5 min) !
I believe it's the stick which is slow, many of the copied files are too small and in that case slow sticks perform really bad.
Very nice program to test your sticks speed, AFAIK backing up data is not required, but you never know...
Test on many different USB sticks, thread is in bulgarian, but pictures give very clear idea:
- By the way I chain the test with Vista installation from USB key: no problem so far.
The key has to be bootable, with Vista bootmanager (bootsect /nt60 or using diskpart or using grub4dos to invoke bootmgr).
The USB key content is a copy of the Vista DVD (almost 4GB).
At also should work if you use XP/2k bootsector (PEtoUSB, HP format tool...) and just rename BOOTMGR to NTLDR. Jaclaz's makeBS.cmd is also very handy if want to use multiboot with ntldr/boot.ini.
Question: is it really z-1 or hard coded to zero (since z=1?). What happens if I install to another partition then the first partition? also maybe on another disk
than the first disk, e.g. HDD2 (USB key, HDD1, HDD2) ? Could you confirm that these cases are covered ?
Jaclaz answered already this, just wanted to add a few things:
1. Mixed SATA/IDE devices may break order and how USB disk is seen by TXT Setup- disable or unplug the unnecessary device. Details here:
2. If planning to install in disk/partition other than 0-1 then boot.ini on stick should be amended accordingly.
BTW in my old tests- 341MB source with BTS mass storage and LAN completed in 16 mins. first boot- first working desktop, Barton 2400М @ 2000, 1GB RAM and 400GB SATA disk, motherboard did not support USB2 boot, otherwise a few minutes could have been saved. USB stick- Buffalo FireStix 2GB type R RUF2-R2G-S, it's really fast stick.
1. Use NTFS compressed temp drive, this should save space, 1GB sometimes could be too much and not possible.
2. Ask to detele tempimage.img when script has completed
3. If needed use RunOnceEx instead of GuiRunOnce to execute binifix.cmd and undoren.cmd. Possibly merge these 2 scripts.
4. USB hard drives- reverse dummydisk.sys logic
5. May be add Vista support too? Shouldn't take much effort.