[jaclaz]

wimb said:

Already sometime ago I tried your script, but was not able to use it.

Well, this does not help much in correcting it (if needed ), does it?

Can you reply to the original topic on boot-land (as to not clutter this one) and tell me more about the problems you had?

I tested it on two separate machines, and it worked, but since both PC's are my own, they have very similar setups so they do not represent a good test.


@ilko_t

I'll try and see what I can come out with.
About the "already" present lines, it should not be a problem since, if I a not mistaken the "new" entry will be by default the "default" one (pardon me the pun ).
What I mean is, if on First hard disk there is already a "complex"BOOT.INI like this:

Quote

[Boot Loader]
Timeout=5
Default=multi(0)disk(0)rdisk(0)partition(5)\WINNT
[Operating Systems]
multi(0)disk(0)rdisk(0)partition(5)\WINNT="Microsoft Windows 2000 Professional IT" /fastdetect
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Microsoft Windows XP Home Edition" /fastdetect
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP" /fastdetect
C:\Bootsect.w98="Windows 98 Command Line" /win95
C:\BOOT\FDOS1440.bin="Test boot"

The result when modified by the new install, let's say on first hard disk, partition 3, will be:

Quote

[Boot Loader]
Timeout=5
Default=multi(0)disk(0)rdisk(z)partition(3)\WINDOWS
[Operating Systems]
multi(0)disk(0)rdisk(0)partition(5)\WINNT="Microsoft Windows 2000 Professional IT" /fastdetect
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Microsoft Windows XP Home Edition" /fastdetect
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP" /fastdetect
C:\Bootsect.w98="Windows 98 Command Line" /win95
C:\BOOT\FDOS1440.bin="Test boot"
multi(0)disk(0)rdisk(z)partition(3)\WINDOWS="Microsoft Windows XP Professional" /fastdetect

And what the batch has to do is to look at the arcpath specified in "Default=" and change just that entry and the corresponding menu one below with same arcpath as follows:

Quote

[Boot Loader]
Timeout=5
Default=multi(0)disk(0)rdisk(z-1)partition(3)\WINDOWS
[Operating Systems]
multi(0)disk(0)rdisk(0)partition(5)\WINNT="Microsoft Windows 2000 Professional IT" /fastdetect
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Microsoft Windows XP Home Edition" /fastdetect
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP" /fastdetect
C:\Bootsect.w98="Windows 98 Command Line" /win95
C:\BOOT\FDOS1440.bin="Test boot"
multi(0)disk(0)rdisk(z-1)partition(3)\WINDOWS="Microsoft Windows XP Professional" /fastdetect

Am I correct?
What happens with SATA drives?

jaclaz

[wimb]

jaclaz, on Jul 10 2007, 03:36 PM, said:

wimb said:

Already sometime ago I tried your script, but was not able to use it.

Well, this does not help much in correcting it (if needed ), does it?

Can you reply to the original topic on boot-land (as to not clutter this one) and tell me more about the problems you had?

I tested it on two separate machines, and it worked, but since both PC's are my own, they have very similar setups so they do not represent a good test.

I have used your script and was able now to use it successfully !

In Boot-land Forum http://www.boot-land...?showtopic=2362
is described the solution of the problem I had on first use of the script.

[ilko_t]

jaclaz, on Jul 10 2007, 02:36 PM, said:

....And what the batch has to do is to look at the arcpath specified in "Default=" and change just that entry and the corresponding menu one below with same arcpath as follows:

Quote

[Boot Loader]
Timeout=5
Default=multi(0)disk(0)rdisk(z-1)partition(3)\WINDOWS
[Operating Systems]
multi(0)disk(0)rdisk(0)partition(5)\WINNT="Microsoft Windows 2000 Professional IT" /fastdetect
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Microsoft Windows XP Home Edition" /fastdetect
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP" /fastdetect
C:\Bootsect.w98="Windows 98 Command Line" /win95
C:\BOOT\FDOS1440.bin="Test boot"
multi(0)disk(0)rdisk(z-1)partition(3)\WINDOWS="Microsoft Windows XP Professional" /fastdetect

Am I correct?
What happens with SATA drives?

jaclaz

Yep, that's it.
About SATA drives- if it is a mixed environment- SATA+ATA, USB stick would be listed fisrt when hard drives are detected by TXT Setup, if one plans to install on ATA when SATA is present, SATA disk must be disconnected or controller disabled, and vice versa, if installation is on SATA and IDE (no matter CD or HD) is present it must be disconnected/controler disabled. This might be BIOS dependant.
Therefore SATA/ATA shouldn't matter for script's functionality.

ilko

[wrayal]

Hey guys,
I've been following all the stunning progress you guys have been making here - very impressive! I had one other suggestion though, that might work. If you read uberplay's OEM guide (http://uberplay.org/.../oemguide3.html), it demonstrates how it is possible to use sysprep + vistaPE to install any version of windows for which a sysprep exists. Notably, it does a vista-style partitioning system I believe, then simply installs your carefully setup system - you can even integrate all sorts of drivers, hotfixes and programs very easily, and with a faster install time than nlite gives. As vista can easily be installed from a USB disc, I imagine this can? Has anyone tried this?

Wrayal

[jaclaz]

Ok, here is the tentative batch to transform rdisk(z) into rdisk(z-1)

As is, it is a bit complicated by the fact that it is written for debugging, it works with a boot.ini in the same directory as the batch, and, knowing how people love working in directories with spaces in them (why? ) provides support for them.

Once it has been tested with positive results, it could be simplified as to work with %drive%\BOOT.INI.

@ilko_t
BOOT.INI should always be on C:\BOOT.INI, whatever the hard disk(s) setup is, am I correct?

jaclaz

Attached File(s)

•  binifix.zip (1.27K)
  Number of downloads: 13

[wimb]

I have been testing binifix.cmd and got:

C:\>binifix.cmd
Drive is C:
Source is "C:\BOOT.INI"
Druk op een toets om door te gaan. . .
DefaultEntry is
EntryDesc is
Timeout is
4==scsi niet verwacht op dit moment.
C:\>

Is not working yet, approach is interesting, will try to find source of problem.

wimb

This post has been edited by wimb: 11 July 2007 - 11:07 PM

[cdob]

@jaclaz

I like rdisk(z-1) idea.
This should work in most cases. Tests have to follow.
Strange BIOS, like wanderer's BIOS, may get different results.

I changed one line at binifix.cmd.

rem IF "%%A"=="Default" SET DefaultEntry=%%B
IF /I "%%A"=="default" SET DefaultEntry=%%B

Signature compare Post #34
http://www.msfn.org/board/index.php?s=&...st&p=585105
Dosn't signature() contain rdisk(0) already?
Do we habe to change a signature() line?

Nice, your code is already fail safe

Quote

ERROR
DefaultEntry is multi(0)disk(0)rdisk(0)partition(1)\WINNT

The rdisk value is ALREADY 0
You don't want me to set it as -1, don't you?

Yes BOOT.INI should always be on C:\BOOT.INI, but it isn't always in real life.
Please read Post #220, boot.ini is seeked at %SystemDrive%. If this fails, drive letters are seeked in decending order.
This support more cases. Of course this may fail at strange machines.
Given a default MS MBR: How to detect the drive letter of primary active partition?

Can you backup a existing boot.ini as e.g. boot.bak?
%date% from Post #220 was a bad idea. This may fail at different languages.

[wimb]

The line to SET Timeout requires also to be changed by adding /I

IF /I "%%A"=="Timeout" SET Timeout=%%B

But then binifix.cmd does its job OK

Due to delims== the EntryDesc misses the last part =optin /fastdetect

This post has been edited by wimb: 12 July 2007 - 05:47 AM

[jaclaz]

@cdob
@wimb

Good work in bug finding guys!

I'll try and fix the reported misbehaviour of the batch.

@cdob

Yes, I just added the signature(aabbccdd) syntax as a "proof of concept" that the "logic" in the batch can be adapted to ANY situation, you are right, we can get rid of it in "final" release.

About drive letter, I give as assumed that boot.ini is on the root of the drive, I wasn't sure that, at the time when the batch needs to be run, %systemdrive% represents correctly the latter (and I am still NOT convinced of it, I know I am a bit tough ) but as I usually, and from immemorable time, install Windows NT/2K/XP in extended partitions, %systemdrive% does NOT represent the BOOT drive.
I had gathered from the thread that the "definitive" boot.ini is ALWAYS on C:\, boot drive, i.e. First Primary Active Partition of First Hard Disk, no matter where windows is installed, I would like to have a confirm of that, otherwise I think we need to use the batch passing to it a parameter.

cdob said:

Given a default MS MBR: How to detect the drive letter of primary active partition?

No problem if I can access the DosDevices key of the Registry, what I am not sure about is if at the time the batch is meant to run the Registry is accessible (I suppose not) and if the proper entry has already been written to the key.
But, as said, if NO other "strange" setting has been applied, First Primary Active Partition of First Hard Disk, should always be C:\, maybe I can add the drive letter as an optional parameter for the batch (if not supplied willl default to C: )

No prob in adding a BOOT.INI -> BOOT.BAK feature, nice (and safe) idea.

@wimb
Can you post an example of line where the "=" sign is used on the left of the "main" "=" sign for description?
Also, are there any cases where more than one "=" sign is used (besides the "main" one)?

I guess I can modify the "tokens=1,2" "to tokens 1,*" or "tokens 1,2,3", but I need one (or more) example(s) to test the behaviour.

jaclaz

[ilko_t]

Good job .

jaclaz, on Jul 12 2007, 03:10 PM, said:

No problem if I can access the DosDevices key of the Registry, what I am not sure about is if at the time the batch is meant to run the Registry is accessible (I suppose not) and if the proper entry has already been written to the key...

Script could be run at first logon via [GUIRunOnce] along with undoren.cmd, when folders on stick are renamed back to ~LS and ~BT, so it should be OK.

[wimb]

I modified the script so that the EntryDesc includes the last part =optin /fastdetect

FOR /F "tokens=1,2,3 delims==" %%A in ('TYPE %source%') DO (
IF /I "%%A"=="Default" SET DefaultEntry=%%B
IF "%%A"=="!DefaultEntry!" SET EntryDesc=%%B=%%C
IF /I "%%A"=="Timeout" SET Timeout=%%B
)

This works for simple boot.ini but the script needs more adjustment for boot.ini of BOOTFILES folder
or other complex boot.ini

This post has been edited by wimb: 12 July 2007 - 09:01 AM

[jaclaz]

@wimb
This should work as well, takes into account multiple (if any) "=" but the main one, and is a bit more simple :

FOR /F "tokens=1,* delims==" %%A in ('TYPE %source%') DO (
IF /I "%%A"=="default" SET DefaultEntry=%%B
IF "%%A"=="!DefaultEntry!" SET EntryDesc=%%B
IF /I "%%A"=="timeout" SET Timeout=%%B
)

wimb said:

This works for simple boot.ini but the script needs more adjustment for boot.ini of BOOTFILES folder or other complex boot.ini

Please do post some examples of these boot.ini's so that I can adapt the code.

@ilko_t
Ok, I'll see what I can do with the Registry thingy.

jaclaz

[wimb]

The second part of the script needs also some adjustment

FOR /F "tokens=1,2,3 delims==" %%A in ('TYPE %source%') DO (
IF /I "%%A"=="Default" SET DefaultEntry=%%B
IF "%%A"=="!DefaultEntry!" SET EntryDesc=%%B=%%C
IF /I "%%A"=="Timeout" SET Timeout=%%B
)
......
......
FOR /F "skip=4 tokens=1,2,3 delims==" %%A in ('TYPE %source%') DO (
IF NOT "%%A"=="!DefaultEntry!" (
ECHO %%A=%%B=%%C>>boot.txt
.......
........

A problem occurs when trailing spaces are present in the !DefaultEntry! string.
This occurs for the boot.ini in folder BOOTFILES
The traling spaces must first be removed.

This post has been edited by wimb: 12 July 2007 - 12:06 PM

[jaclaz]

@wimb
Hey, I don't want to seem unfriendly, I am not, and at times I am also an extraordinarily friendly guy , but when one asks (I guess politely) for something, like:

Quote

@wimb
Can you post an example of line where the "=" sign is used on the left of the "main" "=" sign for description?
Also, are there any cases where more than one "=" sign is used (besides the "main" one)?

and:

jaclaz said:

wimb said:

This works for simple boot.ini but the script needs more adjustment for boot.ini of BOOTFILES folder or other complex boot.ini

Please do post some examples of these boot.ini's so that I can adapt the code.

One expects two kinds of replies:
#1: Yes, here are the examples required.
#2: No, I will never post what you required.
(and all possible variations of the above)

Quite frankly telling me HOW I should correct a batch file I wrote, because it does not work with some entries of which I have not (and asked for twice) any example is a bit trying for my otherwise good manners.

However, should I have failed in explaining this before, can you please post some examples of boot.ini files that do not work with the tentative batch I posted?

jaclaz

[wimb]

@jaclaz

jaclaz, on Jul 12 2007, 04:10 PM, said:

@wimb
Can you post an example of line where the "=" sign is used on the left of the "main" "=" sign for description?
Also, are there any cases where more than one "=" sign is used (besides the "main" one)?

As fas as I know there is no boot.ini example with a line where the "=" sign is used on the left of the "main" "=" sign for description.

The standard boot.ini of Microsoft is a case where more than one "=" sign is used (besides the "main" one)

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect

In my posts #255 and #257 I indicated that the script does not work for the well known boot.ini of folder BOOTFILES
that we all use in the procedure for Install of Windows XP from a bootable USB-stick, as reproduced here:

7. Create a folder BOOTFILES in USB stick root, and copy NTDETECT.COM, NTLDR and create there your custom BOOT.INI, which will be copied on hard disk later, during the first logon. Set them system, hidden and read-only in advance.

BOOT.INI
CODE
[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

It is not easy to find, why the script does not work for this paticular boot.ini
But when you select the boot.ini you can see there is a trailing space in the line with the entry default.
It is this trailing space which causes the problem,
because it becomes part of the seach string !DefaultEntry! used to determine EntryDesc according to:

IF "%%A"=="!DefaultEntry!" SET EntryDesc=%%B

Due to the trailing space, the search gives no valid result for EntryDesc

When I was writing this result in my post #257, your post #256 was not yet on my screen visible,
but came up after submitting the post. So this explains why I missed your request at that time.
But anyway I indicated in my posts #255 and #257 that the script does not work for the well known
boot.ini of folder BOOTFILES.

This post has been edited by wimb: 13 July 2007 - 12:54 AM

[cdob]

@jaclaz
Assumption was: If %systemdrive%\boot.ini exist, this indicate "definitive" boot.ini.
If %systemdrive%\boot.ini dosn't exist, but C:\boot.ini exist, use C:\boot.ini.
Assumption was not: %systemdrive% contain boot.ini.

A logical partition dosn't cotain a d:\boot.ini by default.
Of course there can exist a c:\boot.ini and a d:\boot.ini.
Assumption will fail at this case.

And there can be several primary partitions.
Each primary partition can hold a different boot.ini.
Assumption may fail too.

Assumption c:\boot.ini is fine in most cases.

Contrary the "definitive" boot.ini is not always on C:\.
Remember the RAM loaded install solution: Primary Active Partition of First Hard Disk got D:
What about several internal hard disk including internal card readers?
I recall another windows installation was not at c: Sorry I don't remember details anymore.

Given a grub4dos MBR, "definitive" boot.ini can be at diferent drive letters.
Contrary most likely after Windows installtion, there is a default MS MBR.

jaclaz said:

No problem if I can access the DosDevices key of the Registry, what I am not sure about is if at the time the batch is meant to run the Registry is accessible (I suppose not) and if the proper entry has already been written to the key.

Textmode setup write a false rdisk(), first reboot fails.
Batch should run at end of textmode setup.

@ilko_t and wimb
Dosn't this replace bootfiles\boot.ini?
Call jaclaz's batch at [SetupParams] UserExecute = "%systemdrive%\windows\system32\boot_ren.cmd" ?


@jaclaz
Just wondering: Rename %SysteDrive% early at installation?
Currently I don't know if this is useful, but maybe I need this one day.
At end of textmode setup:
What happens if DosDevices key in Registry is chaned from c: to d:, or from d: to c: ?
E.g. is there full path to Userinit.exe already?
Compare http://support.micro....com/kb/249321/

[jaclaz]

@all
Please find attached a 2nd tentative version of the batch file.
Unlike the first version, this will ONLY work with a BOOT.INI on root of a drive (or in a path without spaces in it)

Solved three problems:
1) one or more "=" signs on the right of the "main" one
2) one or more leading or trailing spaces in entry or entry description
3) empty lines

Added backup feature for original BOOT.INI, saving a maximum of three versions.

@cdob
I'll look at your suggestions, I have not yet a complete and definite idea on how to find the right drive.

There is a key in Registry:
HKEY_LOCAL_MACHINE\SYSTEM\Setup\SystemPartition
where this values are set:
"SetupType"=dword:00000000
"SystemSetupInProgress"=dword:00000000
"CmdLine"="setup -newsetup"
"SystemPrefix"=hex:c2,0b,00,00,00,40,3f,20
"SystemPartition"="\\Device\\HarddiskVolume1"
"OsLoaderPath"="\\"

Though illogical as it may seem, the "SystemPartition" actually appears to represent the "Boot" partition, as opposed to %SystemRoot%.

"\\Device\\HarddiskVolume1" is a "symbolic" link for which I have not found (at least yet ) a way through pure batch and through "normal" XP included command line tools.

One could however use the vlm.exe utility (part of the DSFOK toolkit) to "couple" this link to actual drive letter.

Otherwise we are back to "square 1" with DMDIAG.EXE.

I would greatly prefer to only use "standard" tools, so any idea is welcome, maybe this is possible through a .wbs script?

jaclaz

P.S.: Please someone have a look at this batch:
http://www.robvander.../bootdrive.html
(I have not handy a XP machine right now)
Does this return "System" or "Boot" drive?

Attached File(s)

•  binifix2.zip (1.58K)
  Number of downloads: 6

This post has been edited by jaclaz: 13 July 2007 - 10:09 AM

[wimb]

cdob, on Jul 13 2007, 12:56 PM, said:

@ilko_t and wimb
Dosn't this replace bootfiles\boot.ini?
Call jaclaz's batch at [SetupParams] UserExecute = "%systemdrive%\windows\system32\boot_ren.cmd" ?

The version of binifix2.cmd will not yet be able to replace the use of bootfiles\boot.ini
because then the signature problem with 20 sec bootdelay described in my post #141 will return:

Quote

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

Also the availability of the Repair Install option of Windows XP Setup from a bootable USB-stick
still requires such a multi-entry boot.ini
But in most cases one does not need this Repair Install option and one can change boot.ini if needed.

Actually I had no problem with the value of rdisk.
The GUI-Phase of Setup always made the correct value of rdisk(0) in boot.ini
For me the problem was that the default entry was set to signature(87538753)... entry, which gives bootdelay.
So I am a bit confused about the purpose of the present binifix.cmd

[SetupParams] runs at T-9 and that seems a suitable moment to use binifix.cmd, but I am not sure.
I remember that ilko_t observed that boot.ini is changing many times during setup.
Testing of the final version of binifix.cmd will be necessary to determine if this moment is right,
or that we use [GuiRunOnce] at First Logon.

@jaclaz
After changing drive W: into C: the binifix2.cmd was tested on two boot.ini files
All boot.ini files were modified correctly and the problem of trailing spaces is solved.
It is nice that a backup of boot.ini is made now as well.
After some modification for unattended use,
it will be interesting to use the final version of binifix.cmd in a real Install of Windows XP from bootable USB-stick.

This post has been edited by wimb: 14 July 2007 - 01:15 AM

[jaclaz]

@wimb

Could not the batch file provide a way to automatically get rid of the signature(aabbccdd) line of your post #141?

If I get it right, that line gets the correct rdisk(z), and as so it would just be a matter of replacing signature(aabbccdd) in the lines with multi(0).

As "normally" there are no entries with signature(aabbccdd) syntax in boot.ini, if one is found it should always be the one created by the install.

Just to be on the safe side one could just correct the default entry and duplicate the [Operating Systems] one, leaving one entry with the multi(0) and one with the signature(aabbccdd) syntax that could be manually selected in case the "direct" one, for any reason, won't boot.

jaclaz

[wimb]

jaclaz, on Jul 14 2007, 09:25 AM, said:

@wimb

Could not the batch file provide a way to automatically get rid of the signature(aabbccdd) line of your post #141?

If I get it right, that line gets the correct rdisk(z), and as so it would just be a matter of replacing signature(aabbccdd) in the lines with multi(0).

As "normally" there are no entries with signature(aabbccdd) syntax in boot.ini, if one is found it should always be the one created by the install.

Just to be on the safe side one could just correct the default entry and duplicate the [Operating Systems] one, leaving one entry with the multi(0) and one with the signature(aabbccdd) syntax that could be manually selected in case the "direct" one, for any reason, won't boot.

jaclaz

The present binifix2.cmd does not change the signature entry, it only changes rdisk(1) in rdisk(0)

You are perfectly right that rdisk(0) need not to be changed for me and that it will be just a matter of replacing signature(aabbccdd) in the lines with multi(0) .
It would be very nice if the binifix2.cmd can be a way to change that.

For the [Operating Systems] I got two lines which became equal after I changed signature(87538753) in multi(0),
so I removed the "double" one. That seems to me always save for a new install,
but for a Repair Install your save solution can be interesting.

But it might be that in the configuration of ilko_t with SATA drives it is different,
but I think he will comment on that.

This post has been edited by wimb: 14 July 2007 - 02:27 AM