[wimb]

Quote

The new "final" method, thanks to ilko_t and cdob is repeatable:
http://www.msfn.org/...o...1384&st=128

Thanks a lot to porear and jaclaz, ilko_t and cdob

The method that ilko_t described for installing Windows XP from a bootable USB-stick works perfect !
I have used an Apacer HT203 1GB USB-stick and Windows Setup on my laptop took only about 30 minutes !

The GRUB4DOS grldr was complaining about the CHS values of the USB-stick obtained from my BIOS,
but the warning was no problem for beginning Windows Setup.

There were some small differences with the normal setup from CD.

I obtained an extra file NTBOOTDD.SYS in the root of my C-drive,
which is an ATAPI IDE Miniport Driver.

Also in the boot.ini file there was an extra entry beginning with signature(87538753) ,
although UseSignatures="no" was used in the winnt.sif file.
The entry was marked as the default entry and slows down the booting of the computer by 20 sec.

Replacing signature(87538753)disk(0)rdisk(0)partition(1)\WINDOWS by
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS in the boot.ini file and removing the second entry,
solved the problem and now the computer is booting as fast as normally

I understand that the procedure is not yet applicable to SATA harddisks,
but for the many people that use PATA harddisks, it is already an excellent solution

This post has been edited by wimb: 13 May 2007 - 03:27 AM

[wimb]

ilko_t wrote on Apr 22 2007 about SATA problem:

Quote

A way I can think of is somehow to force TXT SETUP to see USB stick as second drive, or removable if it is not seen as such, this will make it place the needed boot files on the hard drive, either by driver or by relevant registry entries placed by migrate.inf.

In the Help file of the Deployment Tools I saw the following sentence in the
description of the Unattended parameter TargetPath:

"If you want to specify the target drive, you must use the /tempdrive command-line switch
when you run Winnt32.exe

and:

/tempdrive:drive_letter:
Directs Setup to place temporary files on the specified partition.
For a new installation, Windows will also be installed on the specified partition. "

So I think it might be that using the command: winnt32.exe /makelocalsource /noreboot /tempdrive:C:
can help to force Windows Setup to use the C-drive of your SATA harddisk.

I have no SATA drive, so I cannot test the idea ....

This post has been edited by wimb: 09 May 2007 - 12:26 PM

[jaclaz]

@wimb

Happy to hear a story of success!

wimb said:

There was a small difference with the normal setup from CD.
The GRUB4DOS grldr was complaining about the CHS values of the ATA harddisk obtained from my BIOS.
Probably as a result of that I obtained an extra file NTBOOTDD.SYS in the root of my C-drive,
which is an ATAPI IDE Miniport Driver.

Also in the boot.ini file there was an extra entry beginning with signature(87538753) ,
although UseSignatures="no" was used in the winnt.sif file.
The entry was marked as the default entry and slows down the booting of the computer by 20 sec.

Replacing signature(87538753)disk(0)rdisk(0)partition(1)\WINDOWS by
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS in the boot.ini file and removing the second entry,
solved the problem and now the computer is booting as fast as normally

This is a very interesting report, for two reasons:
1) it confirms that when booting Windows can use NTBOOTDD.SYS even if it is a ATAPI driver, not only SCSI and SATA, I am very interested in this as it is another little step on the road of using the possibility to use ANY driver, as long as it is a Miniport one, to boot.
2) it confirms that the signature sintax works perfectly, though with a delay

What would be interesting, if you could make some tests and report, it would be to understand whether the delay is due to:
a. the "sheer" presence of the signature syntax (hence the need to scan Hard Disk(s) MBR to check it
b. the presence of the Miniport driver renamed as NTBOOTDD.SYS (maybe different timings in initialization that cause the delay)

Proposed testing (given that you are familiar with procedures needed should the system become unbootable):
1. Only re-copy the NTBOOTDD.SYS to root of drive
2. Only re-add the signature syntax line in BOOT.INI
3. Both of the above

wimb said:

So I think it might be that using the command: winnt32.exe /makelocalsource /noreboot /tempdrive:C:
can help to force Windows Setup to use the C-drive of your SATA harddisk.

I have not any SATA equipped hardware, but I don't think that what you suggest is feasible/useful, as when you run the WINNT32.EXE C: will be almost invariably the First Active Partition of your First Hard Disk, and NOT the USB stick, moreover, if I am not mistaken, executing such a command will modify your "resident" BOOT.INI to start install at next reboot of the PC....


Cheers,

jaclaz

[ilko_t]

Hi wimb, thanks for posting your results and welcome to the party

In my setup NTBOOTDD.SYS was not used, and I don't remember any delays when signature was present in BOOT.INI, I have no idea why it was used for your PATA drive/controller. Will you post your Motherboard model and what controller it uses along with its Hardware PID and VID, ?

As for the SATA disks, I am still nowhere, after days in researching on i-net and messing with TXTSETUP.SIF I beleive that the order Setup detects disks is hard coded, may be in DISK.SYS or somewhere else, PATA goes first, then USB, then SCSI/SATA. I have a new motherboard to test on with Intel ICH8R and the next few days I will study how Setup behaves when controller is in IDE, AHCI and RAID mode and will report results.

For now I see 4 ways for overcoming SATA drives issue:

1. Make the stick formated (and bootable at the same time) the same way as SETUP will see it during TXT part and write MBR and ntldr/ntdetect.com on it, so even when those are written the information will remain intact, then copy those files to the hard disk using PRESETUP.CMD or any other way.
2. Somehow "force" SETUP not to write this information on the first active hard drive, I have no clue how
3. Somehow "force" SETUP the way it detects the hard drives, or "fool" it to see SATA/SCSI disks as ATA, detecting them before USB.
4. Anything else which one could suggest

As for the long delay at T-1 we could use CMDLINES @ T-12 to lift write-protection, rename the two folders on the stick and later use GUIRUNONCE to rename them back. Due to lack of time I haven't tested this yet and am not sure whether GUI setup would re-read registry information about USB write protect at that stage. I consider it as cosmetic issue and will test it after SATA/SCSI issue is fixed.

@jaclaz - what do you think of 1.- about the formating?
I looked on the new GRUB release, for compatibility reasons for now I prefer to stick with the method I posted- 1 manual selection for TXT setup, the GUI part remains the default selection.

[jaclaz]

ilko_t said:

Make the stick formated (and bootable at the same time) the same way as SETUP will see it during TXT part and write MBR and ntldr/ntdetect.com on it, so even when those are written the information will remain intact, then copy those files to the hard disk using PRESETUP.CMD or any other way.

hmmm, I don't get it, you CANNOT copy a MBR from stick to hard disk, the partition entry will be invalid (due to different size and geometry of partition) AND disk signature will be duplicated, which has been proved in the past to be a NO-NO due to the problems it causes in drive letter assignments; can you better elaborate?

I may be wrong, as often happens, expecially when guessing an undocumented or poorly documented feature, but I think the right approach could be to create a second migrate.inf entry for the SATA disk, linking it's first partition to C:, directly from scratch as per these posts of mine:
http://www.911cd.net...showtopic=19663
http://www.boot-land.net/forums/index.php?...c=2085&st=3

And find a way to write the signature to the SATA drive before starting install.

Signature should not be altered by FDISK /MBR or whatever similar action setup does when booting to prepare the HD.

This would probably lead (through a signature syntax boot.ini entry AND the appropriate SATA driver copied to root as NTBOOTDD.SYS) to make setup correctly attribute letter C: to the SATA drive.

If you could experiment a bit in this direction manually, we will later see if and how it is possible to replicate the procedure automatically, though this would probably mean having grub4dos/grub.exe and some flavour of DOS on the stick, thus, alas, substantially back to square one of the original method 1) through DOS and WINNT.EXE.


jaclaz

This post has been edited by jaclaz: 09 May 2007 - 01:38 PM

[ilko_t]

jaclaz, on May 9 2007, 08:35 PM, said:

..you CANNOT copy a MBR from stick to hard disk...

You didn't' get me right, SETUP writes that, thus making the stick unusable. Setup writes that using the geometry it sees the stick during TXT mode, which is different than the way its formated by HP format utility for example.
Formating the stick by XP will result probably in the same geometry which TXT setup will see it, and will not corrupt files, but USB stick formated by XP was in my tests non bootable, no matter FAT16/32 ot NTFS.
The idea is to leave TXT setup to rewrite that, and use BOOT.INI on the stick, in this scenario GRUB is not needed (or may be just for the GUI part) and we wouldn't care about improper boot.ini entries, as we could automatically copy a generic one to the hard drive later.

This post has been edited by ilko_t: 09 May 2007 - 02:23 PM

[jaclaz]

I'm still a bit lost about it.

The rewriting of the MBR on the stick only happens when a SATA drive is present, doesn't it?

ilko_t said:

Setup writes that using the geometry it sees the stick during TXT mode, which is different than the way its formated by HP format utility for example.

Can you use an utility like Dimio's HD hacker:
http://dimio.altervista.org/eng/
(or any other similar one)
to extract:
1) Stick MBR as formatted anew (before starting install)
2) Stick MBR modified by SETUP
3) HD MBR as written by SETUP

and attach them in a .zip file so that I can have a look at them?

And, sorry, I know I seem a bit tough, and maybe I'm becoming a nuisance but can you re-cap for me if:

Quote

Continuing installation when SATA drive is second cause XP boot sector and NTLDR/BOOT.INI being written to the USB stick, corrupting the partition table, then SETUP complains about damaged drive D (or U when old mounted devices was used) and a new boot from the stick is not possible. Repairing GRUB MBR fixes boot, but some files are missing.

means that you are running the stick with GRUB MBR and not with the "standard" MBR + NTLDR + Boot.ini with entry C:\GRLDR?

Did you try with the second one above (it is possible that SETUP finds a "strange" code (not geometry) in the MBR and replaces it, what happens if the code is ALREADY a Win2K/XP/2003 MBR?


jaclaz

P.S.: did you also try putting on the stick the appropriate SATA miniport driver renamed as NTBOOTDD.SYS? This might avoid the different order of enumeration of the drives...

This post has been edited by jaclaz: 10 May 2007 - 02:48 AM

[wimb]

jaclaz wrote:

Quote

What would be interesting, if you could make some tests and report, it would be to understand whether the delay is due to:
a. the "sheer" presence of the signature syntax (hence the need to scan Hard Disk(s) MBR to check it
b. the presence of the Miniport driver renamed as NTBOOTDD.SYS (maybe different timings in initialization that cause the delay)

Proposed testing (given that you are familiar with procedures needed should the system become unbootable):
1. Only re-copy the NTBOOTDD.SYS to root of drive
2. Only re-add the signature syntax line in BOOT.INI
3. Both of the above

The NTBOOTDD.SYS Miniport Driver is used by the signature(87538753)... entry in the boot.ini file,
and they together cause a 20 sec delay before the Windows logo appears.
In this case removing the NTBOOTDD.SYS file is fatal: Windows won't start due to disk geometry problem.
The signature(87538753) corresponds to the 4 bytes from offsets 1B8h through 1BBh in the MBR,
which are called the Windows™ 2000/XP Disk Signature or NT Drive Serial Number.
For every install from bootable USB-stick they have the same value,
whereas I think that they should change.

see: http://www.geocities...br/Win2kmbr.htm

Quote

However, after a drive has any of the NT-type Operating Systems installed and running,
they will write a Disk Signature in the MBR.

The second entry of boot.ini beginning with multi(0)... does not make use of the NTBOOTDD.SYS file.
Removing the NTBOOTDD.SYS file has in this case no effect.
The multi(0)... entry is also the entry normally occurring in boot.ini when installing from CD.

This post has been edited by wimb: 13 May 2007 - 03:29 AM

[wimb]

ilko_t wrote:

Quote

In my setup NTBOOTDD.SYS was not used, and I don't remember any delays when signature was present in BOOT.INI, I have no idea why it was used for your PATA drive/controller. Will you post your Motherboard model and what controller it uses along with its Hardware PID and VID, ?

I have used a Medion Laptop type MD6100 with a Medion Motherboard with Intel Pentium 4 processor.
The Chipset is from SIS: SIS648 CPU to PCI Bridge and SIS963 South Bridge.

How can I determine the PID and VID ?

[jaclaz]

Quote

How can I determine the PID and VID ?

You can use regedit and explore in the:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\PCI

Or (more simply) use SIW:
http://www.gtopala.com/

or SIV:
http://siv.mysite.wa...-members.co.uk/

jaclaz

P.S.:

wimb said:

which are called the Windows™ 2000/XP Disk Signature or NT Drive Serial Number.
For every install from bootable USB-stick they have the same value,
whereas I think that they should change.

Yes, but how the "signature number" is generated is not at all clear, not even Daniel B.Sedory, who appears one of the first people to document the feature has a clear take on it.
It is possible that some form of "checksum" is generated thus signature on same system (but in subsequent installs) remains the same.
However "normal" installs appear to change the disk signature ONLY if it is not already present (i.e. 00 00 00 00).

This post has been edited by jaclaz: 10 May 2007 - 05:46 AM

[ilko_t]

jaclaz, on May 10 2007, 09:42 AM, said:

...The rewriting of the MBR on the stick only happens when a SATA drive is present, doesn't it?...

When non- native SATA controler (probably IDE too) is used and USB stick is listed first. Have a look at post #130

I will try the other suggestions.

wimb, on May 10 2007, 11:48 AM, said:

ilko_t How can I determine the PID and VID ?

Regards,
ilko


edit: @wimb - you may select the lines 1 by 1 and use ctrl+c to copy-paste contents.

This post has been edited by ilko_t: 10 May 2007 - 05:37 AM

[jaclaz]

@Ilko_t
another question, how did you load the SATA drivers?
1) F6 + floppy
2) TEXTMODE folder:
http://www.msfn.org/board/Unattended_insta...ppy_t13173.html
3) TXTSETUP.SIF ONLY:
http://www.msfn.org/board/Add_slipstream_S...ion_t77999.html

(maybe the last one could "trick" setup into thinking the SATA to be "native" like PATA?)

jaclaz

[ilko_t]

jaclaz, on May 10 2007, 01:06 PM, said:

@Ilko_t
another question, how did you load the SATA drivers?

I am using XP with BTS mass storage drivers pack slipstreamed, so it's via txtsetup.sif. I tried to change the order in txtsetup.sif, moving the Hardware VID&PID lines for USB mass storage and Sil3112 above then below anything else, hoping that SETUP reads the lines and scans for devices according to the order written in txtsetup.sif but that didn't change anything. Also tried to set mass storage drivers as described here, but to no avail too:
http://www.ngine.de/...jsp?pageid=4176

As far as I remember I tried to swap order in these lines, everything was shoots in the darkness:

[DiskDriverMap]
abiosdsk = "%1!u! MB Micro Channel Disk"
atdisk = "%1!u! MB IDE/ESDI Disk"
disk = "%1!u! MB Disk %2!u! at Id %3!u! on bus %4!u! on %5"

and
[SCSI.Load]
........

I believe similar setup could be achieved in VMware, set 2 disks- 1 SCSI and 1 IDE and try to change the order SETUP detects them. Normally IDE goes first, SCSI second. If one could find how to swap them, same method could be used to set USB stick last.
I will try first what happens to the stick when SETUP finds NT MBR on it, instead of GRUB.

edit: interesting line in txtsetup.sif, not sure is it used only when upgrading :

[Directories.DeleteOnUpgrade]
1, Prefetch
2, ReinstallBackups
2, os2
1,"Driver Cache\i386"
2, CatRoot2
1, $NtServicePackUninstall$
1, ServicePackFiles
124, x86_comctl32_6.0.0.0_0000
124, x86_GdiPlus_1.0.0.0_0409
124, x86_Microsoft-Visual-CPlusPlus-Runtime-Libraries_6.0.0.0_0000
124, x86_Microsoft.Tools.VisualCPlusPlus.Runtime-Libraries_no-public-key_6.0.0.0_x-ww_4d05e542
124, x86_Microsoft.Windows.Common-Controls_no-public-key_6.0.0.0_x-ww_cd4c0d12
124, x86_Microsoft.Windows.GdiPlus_no-public-key_1.0.0.0_x-ww_fad9507f
124, InstallTemp

This post has been edited by ilko_t: 10 May 2007 - 07:28 AM

[wimb]

ilko_t, on May 10 2007, 01:33 PM, said:

wimb, on May 10 2007, 11:48 AM, said:

ilko_t How can I determine the PID and VID ?

I have used a Medion laptop MD6100 with SiS PCI IDE-controller:

PCI\VEN_1039&DEV_5513&SUBSYS_55131039&REV_00\3&61AAA01&0&15
with Hardware-id's:
PCI\VEN_1039&DEV_5513&SUBSYS_55131039&REV_00
PCI\VEN_1039&DEV_5513&SUBSYS_55131039
PCI\VEN_1039&DEV_5513&CC_010180
PCI\VEN_1039&DEV_5513&CC_0101

Thanks a lot also jaclaz for al the information on how to determine this value.

Regards, wimb

This post has been edited by wimb: 13 May 2007 - 03:31 AM

[ilko_t]

Mistery solved

When you have an IDE device attached, along with SATA disk, this breaks the order. IDE device could be CD/DVD or hard disk, and boot order on BIOS makes no difference. In this case the order SETUP enumerates devices is IDE-USB-SATA. If IDE device is disconnected or primary/secondary channel is disabled in BIOS order becomes SATA-USB.

On Gigabyte DS3P with Intel ICH8R (6 SATA ports) and JMicron 363 (2 SATA/1 IDE) if both controllers are in AHCI or RAID mode order is SATA1-SATA2-USB.
If Jmicron is in IDE mode this makes no difference, as its a separate controller, order is SATA1- SATA2- USB.
However, if Jmicron is in AHCI or RAID and ICH8 is in native IDE mode order changes to IDE (ICH8R) - USB - SATA (Jmicron). 1 hard drive attached to both controllers and a DVDRW to the JMicron IDE port, DVD was never disconnected or disabled.
So if IDE device is attached to external controller such as JMicron, this doens't change the order SETUP finds devices, and USB goes last, if a native IDE is connected it always goes first, then USB, and last is SATA.

If only IDE hard disk and USB stick are connected (CD/DVD disconnected or primary/secondary channel disabled in BIOS) order is IDE disc- USB. This was confirmed on Abit AN7 too. If CD (secondary channel) is disabled order was SATA-USB, when IDE disc was connected order becomes IDE-USB-SATA
That should clear any further issues with device order, once we ensure that USB is not first we can carry on with installation.

Here is what I did to overcome signature problem in BOOT.INI and make the installation as universal as possible.

Stick is formated by PEtoUSB, copy NTDETECT.COM, NTLDR and BOOT.INI, which is:

BOOT.INI

Quote

[Boot Loader]
Timeout=15
Default=multi(0)disk(0)rdisk(1)partition(1)\WINDOWS
[Operating Systems]
c:\grldr="Start GRUB"
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="GUI Setup" /FASTDETECT

If you are going to install on another partition/disk amend entries to reflect that.

Copy GRLDR to the root of stick and create

MENU.LST

Quote

color black/cyan yellow/cyan
timeout 15

default 0

title Phase 1 WinXP Text Mode Setup
chainloader (hd0,0)/ntldrstp

Create a folder BOOTFILES in root, and copy NTDETECT.COM, NTLDR and your custom BOOT.INI which will be copied on hard disk. Set them system, hidden and read-only in advance.

BOOT.INI

Quote

[boot loader]
timeout=15
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="XP Professional 0 1" /noexecute=optin /fastdetect
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="XP Professional 0 2" /noexecute=optin /fastdetect
multi(0)disk(0)rdisk(0)partition(3)\WINDOWS="XP Professional 0 3" /noexecute=optin /fastdetect
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="XP Professional 1 1" /noexecute=optin /fastdetect
multi(0)disk(0)rdisk(1)partition(2)\WINDOWS="XP Professional 1 2" /noexecute=optin /fastdetect
multi(0)disk(0)rdisk(1)partition(3)\WINDOWS="XP Professional 1 3" /noexecute=optin /fastdetect

In $WIN_NT$.~LS make a new folder if you don't have already $OEM$ and create in it

CMDLINES.TXT

Quote

[COMMANDS]
"BOOT_REN.CMD"

In the same folder create

BOOT_REN.CMD

Quote

@echo off
SET TAGFILE=\BOOTFILES
FOR %%h IN (C D E F G H I J K L M N O P Q R S T U V W X Y) DO IF EXIST "%%h:%TAGFILE%" SET USBDRIVE=%%h:
xcopy %USBDRIVE%\bootfiles\*.* %SYSTEMDRIVE%\ /y /h /r /k
exit

Leave space between %SYSTEMDRIVE%\ and /y /h /r /k

WINNT.SIF

Quote

[data]
msdosinitiated="1"
floppyless="1"
AutoPartition="0"
UseSignatures="no"
InstallDir="\WINDOWS"
EulaComplete="1"
winntupgrade="no"
win9xupgrade="no"
Win32Ver="a280105"
uniqueid="C:\WINDOWS\NKH"
OriSrc="A:\i386"
OriTyp="5"

[unattended] section and oempreinstall=yes is not needed.

The rest is same as the first guide. This way GRUB mapping is not used, and once GUI setup is completed USB stick is no longer needed, we have brand new shining BOOT.INI along with all necessary boot files on the hard disk.

This post has been edited by ilko_t: 15 May 2007 - 12:41 PM

[ilko_t]

Some help needed here:
I did a few attempts to resolve the long wait at T-1, used only write protection in MIGRATE.INF. No files are deleted during TXT part. I added these lines to BOOT_REN.CMD :

Quote

ECHO %TIME% > %SYSTEMDRIVE%\CMDLINES.LOG
ren %USBDRIVE%\$WIN_NT$.~BT WIN_NT.BT
ren %USBDRIVE%\$WIN_NT$.~LS WIN_NT.LS

and created UNDOREN.CMD, which is executed by [GUIRunOnce] in WINNT.SIF along with the relevant entries in TXTSETUP.SIF
UNDOREN.CMD

Quote

@echo off
SET TAGFILE=\BOOTFILES
FOR %%h IN (C D E F G H I J K L M N O P Q R S T U V W X Y) DO IF EXIST "%%h:%TAGFILE%" SET USBDRIVE=%%h:
ren %USBDRIVE%\WIN_NT.BT $WIN_NT$.~BT
ren %USBDRIVE%\WIN_NT.LS $WIN_NT$.~LS
exit

TXTSETUP.SIF and $WIN_NT$.~LS get deleted, $WIN_NT$.~BT - not
Removed UNDOREN.CMD and can confirm WIN_NT.BT is on stick, properly renamed.
This means for me that either $WIN_NT$.~LS was deleted earlier, before T-1, or is in use or somehow protected and script cannot rename it on time.

Here is result of exact time when BOOT_REN.CMD is executed as logged in CMDLINES.LOG:

Quote

1:31:28.95

Here is part of SETUPLOG.TXT

05/15/2007 01:31:22.656,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,5948,END_SECTION,DoRunonce
05/15/2007 01:31:22.656,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,5957,BEGIN_SECTION,Configuring Setup
05/15/2007 01:31:23.046,d:\xpsprtm\base\ntsetup\syssetup\services.c,334,,MyChangeServiceConfig: LockingServiceDatabase for service Spooler
05/15/2007 01:31:23.062,d:\xpsprtm\base\ntsetup\syssetup\services.c,408,,MyChangeServiceConfig: Unlocked ServiceDatabase for service Spooler
05/15/2007 01:31:23.062,d:\xpsprtm\base\ntsetup\syssetup\printer.c,131,,StartSpooler: Just opened service Spooler
05/15/2007 01:31:23.062,d:\xpsprtm\base\ntsetup\syssetup\printer.c,134,,StartSpooler: Just started service Spooler, ret=0, error=1056
05/15/2007 01:31:23.062,d:\xpsprtm\base\ntsetup\syssetup\printer.c,253,,StartSpooler: Just closed service handler Spooler
05/15/2007 01:31:23.234,d:\xpsprtm\base\ntsetup\syssetup\services.c,334,,MyChangeServiceConfig: LockingServiceDatabase for service EventLog
05/15/2007 01:31:23.250,d:\xpsprtm\base\ntsetup\syssetup\services.c,408,,MyChangeServiceConfig: Unlocked ServiceDatabase for service EventLog
05/15/2007 01:31:23.250,d:\xpsprtm\base\ntsetup\syssetup\services.c,334,,MyChangeServiceConfig: LockingServiceDatabase for service ClipSrv
05/15/2007 01:31:23.250,d:\xpsprtm\base\ntsetup\syssetup\services.c,408,,MyChangeServiceConfig: Unlocked ServiceDatabase for service ClipSrv
05/15/2007 01:31:23.250,d:\xpsprtm\base\ntsetup\syssetup\services.c,334,,MyChangeServiceConfig: LockingServiceDatabase for service NetDDE
05/15/2007 01:31:23.250,d:\xpsprtm\base\ntsetup\syssetup\services.c,408,,MyChangeServiceConfig: Unlocked ServiceDatabase for service NetDDE
05/15/2007 01:31:23.250,d:\xpsprtm\base\ntsetup\syssetup\services.c,334,,MyChangeServiceConfig: LockingServiceDatabase for service NetDDEdsdm
05/15/2007 01:31:23.250,d:\xpsprtm\base\ntsetup\syssetup\services.c,408,,MyChangeServiceConfig: Unlocked ServiceDatabase for service NetDDEdsdm
05/15/2007 01:31:23.265,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,3794,BEGIN_SECTION,Loading service pack (phase 4)
05/15/2007 01:31:23.265,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,3796,END_SECTION,Loading service pack (phase 4)
05/15/2007 01:31:23.265,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,3803,BEGIN_SECTION,Network setup handling Internet Server issues
05/15/2007 01:31:23.265,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,3809,END_SECTION,Network setup handling Internet Server issues
05/15/2007 01:31:23.281,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,3836,BEGIN_SECTION,Setting up virtual memory
05/15/2007 01:31:23.296,d:\xpsprtm\base\ntsetup\syssetup\log.c,133,,SetUpVirtualMemory: ENTER

05/15/2007 01:31:28.859,d:\xpsprtm\base\ntsetup\syssetup\log.c,133,,BuildVolumeFreeSpaceList: C:\, spc=8, bps=512, freeclus=1042209, totalclus=1279167

05/15/2007 01:31:28.859,d:\xpsprtm\base\ntsetup\syssetup\log.c,133,,BuildVolumeFreeSpaceList: C:\, FreeSpace = 04268888064

05/15/2007 01:31:28.859,d:\xpsprtm\base\ntsetup\syssetup\log.c,133,,BuildVolumeFreeSpaceList: C:\ had 120586240 byte pagefile, new FreeSpace = 194507008

05/15/2007 01:31:28.859,d:\xpsprtm\base\ntsetup\syssetup\log.c,133,,BuildVolumeFreeSpaceList: Free space on C:\ is 4186 MB

05/15/2007 01:31:28.859,d:\xpsprtm\base\ntsetup\syssetup\log.c,133,,BuildVolumeFreeSpaceList: U:\, spc=64, bps=512, freeclus=48429, totalclus=62454

05/15/2007 01:31:28.859,d:\xpsprtm\base\ntsetup\syssetup\log.c,133,,BuildVolumeFreeSpaceList: U:\, FreeSpace = 01586921472

[b]05/15/2007 01:31:28.859,d:\xpsprtm\base\ntsetup\syssetup\log.c,133,,BuildVolumeFreeSpaceList: Free space on U:\ is 1513 MB[/b]

05/15/2007 01:31:28.859,d:\xpsprtm\base\ntsetup\syssetup\log.c,133,,SetUpVirtualMemory: loc 1

05/15/2007 01:31:28.859,d:\xpsprtm\base\ntsetup\syssetup\log.c,133,,Setup configured the system to place a 1536 MB pagefile on drive C:.

05/15/2007 01:31:28.859,d:\xpsprtm\base\ntsetup\syssetup\log.c,133,,Crashdump was enabled.

05/15/2007 01:31:28.859,d:\xpsprtm\base\ntsetup\syssetup\log.c,133,,SetUpVirtualMemory: EXIT (1)

05/15/2007 01:31:28.859,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,3844,END_SECTION,Setting up virtual memory
05/15/2007 01:31:28.859,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,3855,BEGIN_SECTION,Processing [RunPrograms] section
05/15/2007 01:31:28.859,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,3857,END_SECTION,Processing [RunPrograms] section
05/15/2007 01:31:28.859,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,2622,,Power scheme: desktop.
05/15/2007 01:31:28.875,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,2626,,SetActivePwrScheme succeeded.
05/15/2007 01:31:29.140,d:\xpsprtm\base\ntsetup\syssetup\log.c,133,,The external program boot_ren.cmd returned exit code 0.

05/15/2007 01:31:29.187,d:\xpsprtm\base\ntsetup\syssetup\log.c,133,,The external program rundll32 advpack.dll,LaunchINFSection nLite.inf,U returned exit code 0.

05/15/2007 01:31:29.187,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,3915,BEGIN_SECTION,Saving hives
05/15/2007 01:31:29.203,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,3929,END_SECTION,Saving hives
05/15/2007 01:31:29.203,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,3958,BEGIN_SECTION,Copying optional directories
05/15/2007 01:31:29.203,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,3963,END_SECTION,Copying optional directories
05/15/2007 01:31:29.203,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,5959,END_SECTION,Configuring Setup
05/15/2007 01:31:29.218,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,5964,BEGIN_SECTION,Configuring Common
05/15/2007 01:31:29.218,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,4231,BEGIN_SECTION,Generating security templates
05/15/2007 01:31:38.906,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,4233,END_SECTION,Generating security templates
05/15/2007 01:31:38.906,d:\xpsprtm\base\ntsetup\syssetup\copy.c,627,,SETUP: Marked file perfmon.msc read-only
05/15/2007 01:31:38.921,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,5966,END_SECTION,Configuring Common
05/15/2007 01:31:38.937,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,6065,BEGIN_SECTION,Fix the security on <All Users\Application Data\Microsoft\Windows NT>
05/15/2007 01:31:38.937,d:\xpsprtm\base\ntsetup\syssetup\log.c,133,,Setup invoked the external program shmgrate.exe Fix-HTML-Help.

05/15/2007 01:31:38.937,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,6067,END_SECTION,Fix the security on <All Users\Application Data\Microsoft\Windows NT>
05/15/2007 01:31:38.937,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,6072,BEGIN_SECTION,Migrating exception packages
05/15/2007 01:31:38.937,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,6074,END_SECTION,Migrating exception packages
05/15/2007 01:31:38.953,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,6090,BEGIN_SECTION,Running SFC
05/15/2007 01:31:39.000,d:\xpsprtm\base\ntsetup\syssetup\registry.c,1551,BEGIN_SECTION,DeleteCurrentProductIdInRegistry
05/15/2007 01:31:39.015,d:\xpsprtm\base\ntsetup\syssetup\registry.c,1564,END_SECTION,DeleteCurrentProductIdInRegistry
05/15/2007 01:31:39.015,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,6216,BEGIN_SECTION,Saving repair info
05/15/2007 01:31:42.734,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,6218,END_SECTION,Saving repair info
05/15/2007 01:31:42.734,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,6227,BEGIN_SECTION,Removing Temporary Files
05/15/2007 01:31:42.750,d:\xpsprtm\base\ntsetup\syssetup\utils.cpp,18,,Setup: Activationrequired
05/15/2007 01:31:42.843,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,4904,,Setup: (Information) activation icons removed

05/15/2007 01:31:42.859,d:\xpsprtm\base\ntsetup\syssetup\cmdline.c,228,,SETUP: SpSetupLoadParameter was unable to find DynamicUpdateAdditionalPostGuiDrivers.
05/15/2007 01:32:04.421,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,5416,BEGIN_SECTION,Setting up Crash Recovery
05/15/2007 01:32:04.437,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,5420,END_SECTION,Setting up Crash Recovery
05/15/2007 01:32:08.234,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,6245,END_SECTION,Removing Temporary Files
05/15/2007 01:32:08.234,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,6252,,SETUP: CallSceSetupRootSecurity completed
05/15/2007 01:32:08.234,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,6269,,SETUP: Changing registry quota from 111848106 to 55924053...
05/15/2007 01:32:08.234,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,6274,,SETUP:	... succeeded
05/15/2007 01:32:08.234,d:\xpsprtm\base\ntsetup\syssetup\services.c,496,,SetupStartService: Sending StartService to <Eventlog>

05/15/2007 01:32:08.234,d:\xpsprtm\base\ntsetup\syssetup\services.c,498,,SetupStartService: Sent StartService to <Eventlog>

05/15/2007 01:32:08.234,d:\xpsprtm\base\ntsetup\syssetup\welcome.c,934,END_SECTION,Copying Files Page
05/15/2007 01:32:08.234,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,6294,END_SECTION,FinishThread
05/15/2007 01:32:08.234,d:\xpsprtm\base\ntsetup\syssetup\welcome.c,1096,BEGIN_SECTION,Finish Page
05/15/2007 01:32:08.250,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,6640,END_SECTION,Wizard
05/15/2007 01:32:08.250,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,6644,BEGIN_SECTION,Recovery
05/15/2007 01:32:08.250,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,6648,END_SECTION,Recovery
05/15/2007 01:32:08.250,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,6650,BEGIN_SECTION,Shutdown
[b]05/15/2007 01:32:08.250,d:\xpsprtm\base\ntsetup\syssetup\log.c,133,,GUI mode Setup has finished.[/b]

Note that at 01:31:28.859 SETUP reports free space on stick as its supposed to be if no files were deleted. Either that's incorrect or $WIN_NT$.~LS is deleted after 01:31:28.859 (about T-12- T-8). Or as I think folder is in use and cannot be renamed on time. May be one can spot something in the log.
Also, the idea to remove stick during T-1 to avoid long wait seems not so good, I can see SETUP is still doing something else at that stage, apart form deleting temp files.

Any ideas how to proceed further?

@Jaclaz - if you are still interested the attached files contains MBR and bootsector saved by HDhacker when formated by PEtoUSB and rewritten by TEXT mode SETUP.

@wimp - The IDs you have are for SIS IDE, and I can't see them in generic XP SP2 CD TXTSETUP.SIF HIDs, that means for me probably that yours are splipstreamed in your CD, SISIDE.SYS, which is later renamed and copied as NTBOOTDD.SYS. Can you search in your TXTSETUP.SIF on the CD for VEN_1039&DEV_5513 and give all results here?

Attached File(s)

•  XP_from_USB.zip (2.72K)
  Number of downloads: 50

This post has been edited by ilko_t: 15 May 2007 - 12:31 PM

[wimb]

ilko_t, on May 15 2007, 01:27 PM, said:

@wimp - The IDs you have are for SIS IDE, and I can't see them in generic XP SP2 CD TXTSETUP.SIF HIDs, that means for me probably that yours are splipstreamed in your CD, SISIDE.SYS, which is later renamed and copied as NTBOOTDD.SYS. Can you search in your TXTSETUP.SIF on the CD for VEN_1039&DEV_5513 and give all results here?

My setup files are slipstreamed with RVM Integrator.
A search for VEN_1039&DEV_5513 in the TXTSETUP.SIF for my slipstreamed and my generic XP SP2 CD
gives the same result: the entry is not found.
The entry can be found in the pcidevs.txt file http://members.dataf...ads/pcidevs.txt

Your solutions for the SATA problem and the boot.ini issue are very interesting.
I will let you know the test results for my case as soon as possible.

[wimb]

ilko_t, on May 15 2007, 12:54 PM, said:

Mistery solved

Here is what I did to overcome signature problem in BOOT.INI and make the installation as universal as possible.

Stick is formated by PE2USB, copy NTDETECT.COM, NTLDR and BOOT.INI, which is:

I have used and tested the new procedure to overcome the boot.ini issue.
I have used the HP USB Disk Format tool instead of PE2USB ( Did you mean PeToUsb ? )
because PE2USB did not remove the MBR installed GRUB4DOS.

ilko_t, on May 15 2007, 12:54 PM, said:

Create a folder BOOTFILES in root, and copy NTDETECT.COM, NTLDR and your custom BOOT.INI which will be copied on hard disk. Set them system, hidden and read-only in advance.

Why are NTDETECT.COM and NTLDR copied by BOOT_REN.CMD from BOOTFILES to SYSTEMDRIVE ?
They will be present there already.

I came through the Windows Setup procedure, but obtained a boot.ini with two entries as given below:
BOOT.INI on Laptop produced by WinXP Setup

Quote

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(1)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect

Interesting is that the earlier NTBOOTDD.SYS file is absent in this case !
And there is no signature( ... ) ... entry anymore in boot.ini.
The default entry does not work: Windows won't start due to disc geometry problem.
But the second ( normal) entry works fine.

So the new procedure is not yet perfect, but works for me,
and it remains confusing for me how and when this boot.ini was made ...
Because according to the BOOT_REN.CMD , I would expect something else appearing.

This post has been edited by wimb: 15 May 2007 - 12:10 PM

[ilko_t]

Quote

Did you mean PeToUsb

Sorry, yes, I will edit the long post.

Quote

Why are NTDETECT.COM and NTLDR copied by BOOT_REN.CMD from BOOTFILES to SYSTEMDRIVE ?

In a few cases I noticed that they are not written there, but may be SETUP tried to put them on stick or skipped because saw them on stick. That way we are sure everything needed to boot is in place.

Quote

I came through the Windows Setup procedure, but obtained a boot.ini with two entries as given below:...

rdisk(1) is because no mapping is made via GRUB, that was the reason we used map (hd0) (hd1) in the previous guide. It also won't add signature, because no mapping is made and SETUP sees the disks as they are.
The working line rdisk(0) I beleive is a copy of the one on the USB stick, I have no idea when SETUP adds it, but I noticed the same behavior. If mapping was used on my last test it was ending with signature and disk couldn't be booted with that signature, no idea why it worked before. That's why I decided to be brutal and replace the whole BOOT.INI as this would resolve all issues with it.

Your BOOT.INI was not copied, I believe CMDLINES was not set up properly, or switches in WINNT.SIF were missing. I am going to repeat all this step by step to make sure I haven't missed anything when was writing the post.
Thanks for your time

edit: Are you sure that CMDLINES.TXT and BOOT_REN.CMD were placed in the right subfolder \$WIN_NT$.~LS\$OEM$ ?
edit2: Ahh, silly me I missed to copy the tag. Post edited.

CMDLINES.TXT

Quote

[COMMANDS]
"BOOT_REN.CMD"

This post has been edited by ilko_t: 15 May 2007 - 12:38 PM

[wimb]

ilko_t, on May 15 2007, 08:25 PM, said:

CMDLINES.TXT

Quote

[COMMANDS]
"BOOT_REN.CMD"

Adding the missing [COMMANDS] tag, solved the problem !

Everything is working now as expected.

@ilko_t - Since you have solved also the SATA problem, it seems we are ready for really using the
bootable USB-stick as a device for installing Windows XP on the harddisk of any computer,
provided the BIOS supports booting from USB-stick.

@ilko_t and @jaclaz :
I am trying now to make a MultiBoot USB-stick with:
1. Unattended Install of Windows XP on Harddisk with Updates and DriverPacks Integrated
http://www.ryanvm.net/forum/index.php?sid=...490d2bd5184b68a and
http://unattended.ms.../unattended.xp/ and http://driverpacks.n...ks/overview.php
2. Booting from DOS, with Ghost for System Backup and System Restore
http://www.911cd.net/forums//index.php?sho...=19621&st=7
3. Adding WPI for Automatic Install of Additional Programs http://wpiw.net/
4. Unattended Install of Office 2003 with Updates Integrated http://www.siginetsoftware.com/forum/
5. Adding WinTools running direct from USB-stick using nu2menu http://www.dirk-loss.de/win-tools.htm

For BartPE it seems that booting from USB-stick is too slow (20 minutes) to be interesting,
as compared to BartPE booting in 2 minutes from DVD. http://www.nu2.nu/pebuilder/
Or do you have a solution for making BartPE boot faster from a USB-stick ?

It is a great solution, Thanks a lot for everything

This post has been edited by wimb: 27 May 2007 - 09:40 AM