36 replies to this topic

[was_jaclaz]

SERVICE EDIT:

This thread was splitted from this one:
http://www.boot-land.net/forums/index.php?showtopic=7721&hl=

Does "<os>" only accept Win98 ?

Has anyone a good solution to update the PBR that it's load NTLDR?

It depends on what you call good.

A bootsector can be extracted, just like the MBR, from a system file in the source, the original "BOOTMGR" bootsector can be extracted fromthe formatted volume, then the two can be manipulated via batch and rewritten through dsfo/dsfi.

In other words the things that I do with mbrbatch/makebs:
http://www.boot-land...?showtopic=3191
http://www.boot-land...?showtopic=2362

jaclaz

[pscEx]

Has anyone a good solution to update the PBR that it's load NTLDR?

Maybe I still misunderstand everything.

But some posts above I explained how to extract it from spcmdcom.sys

Peter

[Lancelot]

You missed one thing Peter,

adding drivers take more attention, for me especially xp64 .

But i am experienced enough to listen/read gurus carelfully (which i do a lot before joining boot-land, remembering my trials to lego up the pieces on jacklaz posts ), just after your post the code is in the script because i am sure i will use it for mbr task when focused on it .

Cu

edit

[pscEx]

You missed one thing Peter,

adding drivers take more attention, for me especially xp64 .

I agree that I missed a lot!

I did not understand the correllation between extracting a PBR from a file, and adding a driver.

Maybe Jaclaz explains ...

Peter

[Lancelot]

If you read carelfuly i am giving a shot,
if not than great Italian will find a way (i guess he always finds the right way with you)

WinNTSetup prepares HD for XP/2k3-x86/x64 setup from LiveXP by using source cd without need of winnt32.exe (maybe missing or etc)
Well to be honest, i focus on x64 part .
so there are some copy tasks for WinNTSetup to do which so far does it very successfully
now there left 2 more tasks, making a bootable HD and driver injection.
"driver injection" takes more attention than "boot HD" but because JFX used bootsect.exe from first day, removing it (legal) was the subject for a short while, than you came and i got the tip and quicly add to script for future look etc.
Driver injection part looks easy, but a bit tricky
x86 easy, there is dps etc.
x64 --> no ready dps package i found so far.
and everybody dont know editing .inf's easly .
So I focus on tricky mass storage part, and leave "boot HD" part for future.

And currently i guess author give a break for a week, and me too .

I hope you get , if not Great Italian is probably on his way

[pscEx]

Understood a bit, but not all.

Maybe Italian help is still needed ...

Peter

[was_JFX]

Thanks Lancelot, you explained it very well

Oh, Im really Sorry Peter,

I use your programm like this :

bootExt.exe -I:SPCMDCON.SYS -O:BOOTSECT.BIN

and get an BOOTSECT.BIN for use with an CD Image, I havent realized there it also a -D Option , that extract an clean NTFS Bootsector.

Injecting Partioninformation could be possible. Maybe Barts mkbt could be use to write the new sector back to disk.


I used bootsect.exe cause it is a very easy and safe method

bootsect.exe /nt52 X: /mbr

update the MBR/PBR to load NTLDR --> boot.ini --> X:\$WIN_NT$.~BT\BOOTSECT.DAT --> X:\$LDR$ (renamed SETUPLDR)

just like normal Windows XP Setup would do.

[pscEx]

I havent realized there it also a -D Option , that extract an clean NTFS Bootsector.

Injecting Partioninformation could be possible.

Repeating my offer:

If something can be patched here, describe the patch, and I'll implement an additional switch doing so.

Peter

[pscEx]

Maybe Barts mkbt could be use to write the new sector back to disk.

@Jaclaz:
Any other possibility besides bart (=Third party) mkbt?

Peter

[was_jaclaz]

Let's do a deal.

Let's assume that you (meaning JFX and Lancelot) ONLY care about the driver injection and that we (psc and me) ONLY care about the MBR and bootsector.

It could be ther right and unique moment in a life that I can have a programmer's attention (which normally refuses to delve in the topic) on the MBR and PBR.

But still I miss some basis to (maybe) understand the problem and help peter in adding the needed features to his program.

Which what does the actual partitioning/formatting?

i.e. what is on the drive MBR and PBR when the tool is run?

jaclaz

[Lancelot]

I can have a programmer's attention....

me always learning from gurus attention when they write . I will be glad for any tip.

Which what does the actual partitioning/formatting?

any partition software, lets say hdm8.5 (or another as you wish). And lets say the guy bought a new hd and create 3 partitions, 1st extended, 2nd primary, 3rd primary and gave them a drive letter on livexp with in the same order C: (extended) D: (primary) E: (primary) . And wants hd bootable from 2nd primary hd (E:)

[was_jaclaz]

any partition software, lets say hdm8.5 (or another as you wish). And lets say the guy bought a new hd and create 3 partitions, 1st extended, 2nd primary, 3rd primary and gave them a drive letter on livexp with in the same order C: (extended) D: (primary) E: (primary) . And wants hd bootable from 2nd primary hd (E:)

I still don't get it.

What bootsector does the "any" write?

• A DOS one invoking io.sys
• A NT/2K/XP/2008 invoking NTLDR (and thus there is NO need to change it)
• A Vista/2008/Windows7 invoking BOOTMGR?

Under which OS does the "any" tool run?

Under which OS/PE is the WINNT32.EXE replacement program meant to run?

jaclaz

[Lancelot]

Under which OS/PE is the WINNT32.EXE replacement program meant to run?

Livexp, pe1

What bootsector does the "any" write?
--A NT/2K/XP/2008 invoking NTLDR

well, i need to read more about this mbr stuff, and time is a .... it seems JFX get what he needs from guru peter's tips, just writing to inform as much as i know .

[was_jaclaz]

Livexp, pe1

Then, WHATEVER bootsector has been written by the "any", one can simply run FORMAT to make one invoking NTLDR.

Still don't see the problem.

jaclaz

[pscEx]

Then, WHATEVER bootsector has been written by the "any", one can simply run FORMAT to make one invoking NTLDR.

Still don't see the problem.

jaclaz

WOW!
That does not mean "Windows On Windows". That means the German "Endlich"

Until now our private competition rate looks like 99:0 for you.
But now I lowered to 99:1, if you cannot explain:

How to FORMAT a directory on your host, which you want to "burn as ISO" to a CD or copy "as USB bootable" to an USB stick?

Peter

[was_jaclaz]

But now I lowered to 99:1, if you cannot explain:

How to FORMAT a directory on your host, which you want to "burn as ISO" to a CD or copy "as USB bootable" to an USB stick?

Hmm, unilateral changes of ratios are generally frowned upon , but I will gladly allow for a handicap of up to 9 (i.e. allowing you to start from 9 instead of 0) if only you could rephrase your question or expand it a bit.

I simply cannot understand the concept of FORMATting a directory.



jaclaz

[was_JFX]

Still don't see the problem.

Ok, the problem is the programm should be as simple as possible, the user shouldn't have to care about how the Bootsector looks like.

Under LiveXP / Real XP (any) partition software will probably create a bootable enviroment with NTLDR loading BS.
But under Vista/Server2008/7 it will probably create a BOOTMGR loading Bootsector.

Actually I want it to be compatible with these OS.

Using bootext, mbkt (or dsfo/dsfi) and mbrfix could be a solution but would make the programm bigger. Size matters (my opinion ).

So I made a preliminary decision to let WinNTSetup check the Bootsector:

If it's a NTLDR one everything OK

If it's a BOOTMGR one SETUPLDR will be renamed to BOOTMGR

If it's a unknown one it will give a warning message that bootsect.exe is required.

bootsect.exe will be optional, is it present it will be used.

But for now I have a lot of changes and code cleanup's to do for the Driverintegration.


@psc I like your bootExt.exe and may also see use in some other places. Could you update it to extract the other Bootsectors and the MBR which is in SPCMDCON.SYS?

[pscEx]

@psc I like your bootExt.exe and may also see use in some other places. Could you update it to extract the other Bootsectors and the MBR which is in SPCMDCON.SYS?

bootExt.exe version 2.0.0 available

bootExt Version 2.0.0

Copyright (C) 2009 Peter Schlang



Syntax&#58; -I&#58;<input file> -O&#58;<output file> {-M|-N|-C|-F|-1}



-M&#58; MBR

-N&#58; NTFS PBR

-C&#58; CD PBR

-F&#58; FAT32 PBR

-1&#58; FAT12 PBR

Download: nativeex.boot-land.net/Programs/bootExt/bootExt.7z

Any patches needed?

Peter

[was_JFX]

Wow, that was fast looks perfect Thank you very much

I now have to go to a barbecue. Have a nice weekend


John

[was_jaclaz]

Any patches needed?

Without having had time to check it, sorry for the possibly stupid question:

How many sectors are extracted for each type?

A few notes:

• If INPUT file is missing throws an error.
• It overwrites existing OUTPUT file without warning
• One of the options {-M|-N|-C|-F|-1} is compulsory
• If any part is missing the program displays syntax and a "misterious" (at least to me ) string:
  

  Click Execute to finish ...

  what is one supposed to do (besides pressing the ENTER key )
• I seem not to find an option for FAT16

jaclaz

[pscEx]

How many sectors are extracted for each type?

As long until the end marker HEX(55AA) is reached

• If INPUT file is missing throws an error.
• It overwrites existing OUTPUT file without warning
• One of the options {-M|-N|-C|-F|-1} is compulsory

Yes to all

• If any part is missing the program displays syntax and a "misterious" (at least to me ) string:
  
  what is one supposed to do (besides pressing the ENTER key

Enter is the right reaction

• I seem not to find an option for FAT16

I did not find one in spcmdcon.sys

Peter

[pscEx]

Version 2.1.0 of bootExt.exe (the Jaclaz hotfix-version ) is online.

Many thanks to Jaclaz for the hint about uncomplete records.

I also tried to make the UI a bit more dummy proof.

Peter

[was_jaclaz]

Version 2.1.0 of bootExt.exe (the Jaclaz hotfix-version ) is online.

Good news.

I also tried to make the UI a bit more dummy proof.

A common mistake people make when trying to design something completely foolproof is to underestimate the ingenuity of complete fools.

Should any fool happen to pass by :

The new version is downloadable at the same place as the old one:
http://nativeex.boot...tExt/bootExt.7z

Click Execute to exit ... (it's a coded message, that you have to decode with the following table, DO NOT waste your time looking for anything labeled "Execute" on which to click on)

Translation:

|psc's slang|	Fools	|

|-----------|-------------|

|  Click	|	Press	|

|-----------|-------------|

| Execute   |	Enter	|

|-----------|-------------|

|to exit ...| to exit ... |<-this part is plain text

|-----------|-------------|

jaclaz

[pscEx]

Translation:

|psc's slang|	Fools	|

  |-----------|-------------|

  |  Click	|	Press	|

  |-----------|-------------|

  | Execute   |	Enter	|

  |-----------|-------------|

  |to exit ...| to exit ... |<-this part is plain text

  |-----------|-------------|

New version 2.1.1 (at known URL) has an (optional and undocumented) switch "-P" (psc's slang).
The default will be Fools' slang.

Peter

[was_jaclaz]

I LOVE undocumented switches.....

...hey, wait, you had to open your big mouth type that info, didn't you?

It's not undocumented anymore.





jaclaz