Changing the boot.ini file

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi.

The target builder generates automatically the boot.ini file. How do I
control this process ? I need to add some entries such as
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Embedded"
/MAXMEM=999 /noexecute=optin /fastdetect

and I don't want to perform this manually every time I build my configuration

Thanks
 
No control there at all.
You have to create your own boot.ini and manually replace it in the pre-FBA (just built) image.

Note: boot.ini gets generated very late [last thing] at the build process - when it builds so called Base Component - so even if you
are going to try to replace it by using your own component or TD Extra Files section - it is not going to work :-(

The only way to make changes in the boot.ini file during the build process in an automated way is to use undocumented CMI.

--
=========
Regards,
KM

PS. If you are up to CMI approach, please take a look at the BootSwitches property of the global Platform object.
 
You could create a little application that runs during FBA that will swap
out the boot.ini created by TD for your own custom boot.ini, thus elimintate
the manual step.

Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
XP Embedded Book Author - XP Embedded Advanced, XP Embedded Supplemental
Toolkit


KM said:
No control there at all.
You have to create your own boot.ini and manually replace it in the
pre-FBA (just built) image.

Note: boot.ini gets generated very late [last thing] at the build
process - when it builds so called Base Component - so even if you are
going to try to replace it by using your own component or TD Extra Files
section - it is not going to work :-(

The only way to make changes in the boot.ini file during the build process
in an automated way is to use undocumented CMI.

--
=========
Regards,
KM

PS. If you are up to CMI approach, please take a look at the BootSwitches
property of the global Platform object.

Hi.

The target builder generates automatically the boot.ini file. How do I
control this process ? I need to add some entries such as
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP
Embedded"
/MAXMEM=999 /noexecute=optin /fastdetect

and I don't want to perform this manually every time I build my
configuration

Thanks
Click to expand...
Click to expand...
 
I should've probably done that long time ago but never had too much trouble with manual boot.ini replacement myself.
Here is update version of the XPETools that includes the functionality. On the XPeTools macro component settings page you will find
new field to add extra Boot.ini switches that are persistent across the build:
http://www.xpefiles.com/viewtopic.php?p=115#115

Please let me know is if there is any issues with the component.

--
=========
Regards,
KM

No control there at all.
You have to create your own boot.ini and manually replace it in the pre-FBA (just built) image.

Note: boot.ini gets generated very late [last thing] at the build process - when it builds so called Base Component - so even if
you are going to try to replace it by using your own component or TD Extra Files section - it is not going to work :-(

The only way to make changes in the boot.ini file during the build process in an automated way is to use undocumented CMI.

--
=========
Regards,
KM

PS. If you are up to CMI approach, please take a look at the BootSwitches property of the global Platform object.

Hi.

The target builder generates automatically the boot.ini file. How do I
control this process ? I need to add some entries such as
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Embedded"
/MAXMEM=999 /noexecute=optin /fastdetect

and I don't want to perform this manually every time I build my configuration

Thanks
Click to expand...
Click to expand...
 
Another thing that MS should add in the future....

Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
XP Embedded Book Author - XP Embedded Advanced, XP Embedded Supplemental
Toolkit


KM said:
I should've probably done that long time ago but never had too much trouble
with manual boot.ini replacement myself.
Here is update version of the XPETools that includes the functionality. On
the XPeTools macro component settings page you will find new field to add
extra Boot.ini switches that are persistent across the build:
http://www.xpefiles.com/viewtopic.php?p=115#115

Please let me know is if there is any issues with the component.

--
=========
Regards,
KM

No control there at all.
You have to create your own boot.ini and manually replace it in the
pre-FBA (just built) image.

Note: boot.ini gets generated very late [last thing] at the build
process - when it builds so called Base Component - so even if you are
going to try to replace it by using your own component or TD Extra Files
section - it is not going to work :-(

The only way to make changes in the boot.ini file during the build
process in an automated way is to use undocumented CMI.

--
=========
Regards,
KM

PS. If you are up to CMI approach, please take a look at the BootSwitches
property of the global Platform object.

Hi.

The target builder generates automatically the boot.ini file. How do I
control this process ? I need to add some entries such as
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP
Embedded"
/MAXMEM=999 /noexecute=optin /fastdetect

and I don't want to perform this manually every time I build my
configuration

Thanks
Click to expand...
Click to expand...
Click to expand...
 
Sean said:
You could create a little application that runs during FBA that will
swap out the boot.ini created by TD for your own custom boot.ini,
thus elimintate the manual step.
Click to expand...

I added that functionality to my shell loader. If it finds boot.in~ it
deletes boot.ini and renames boot.in~ to boot.ini.

-Mike
 
KM said:
I should've probably done that long time ago but never had too much
trouble with manual boot.ini replacement myself. Here is update
version of the XPETools that includes the functionality. On the
XPeTools macro component settings page you will find new field to add
extra Boot.ini switches that are persistent across the build:
http://www.xpefiles.com/viewtopic.php?p=115#115
Click to expand...

Excellent. Thanks Konstantin.
 
Mike, Sean,

Do you mean the boot.ini is replace at runtime? But then you perform a few (or just the first one) "boots" with the wrong boot.ini,
right? That is less convenient than, say, changing the boot.ini at build time.

My opinion on this is that there should be a simple option in TD that allows you to edit the BOOT.INI manually. The entire content
of the file.
Basically here is how I would implement this:
1) In Configuration settings there should be a button or a link to open a multi-line edit box (could be on the same settings
page). The link could only be seen from "Advanced" user mode set in TD.
2) The edit box by default is populated by what the config is set up for (default section, ArcPath, etc.)
3) If the content of the edit box is changed/modified/etc. the build system will use it instead of the one automatically
generated. The new boot.ini content should be stored as a part of the config (e.g., an advanced property, etc.)

The above sounds easy to use to me as a TD user. If I don't want to mess around the boot.ini, I will go with the default one
automatically generated. If however I do, e.g. I need to add one of the hundreds custom boot.ini options available or I want to set
up a dual/triple boot environment, then I would edit the boot.ini myself and I want to do that once.
 
KM said:
Do you mean the boot.ini is replace at runtime? But then you perform
a few (or just the first one) "boots" with the wrong boot.ini, right?
That is less convenient than, say, changing the boot.ini at build
time.
Click to expand...

Yes. In my case I just want to add /noguiboot and /bootlogo to it.

My opinion on this is that there should be a simple option in TD that
allows you to edit the BOOT.INI manually. The entire content of the
file.
Click to expand...

I agree. To me this functionality should have been included from the
start with TD.
 
What I have is a simple utility that echanges the boot.ini files during FBA.
I use this for the custom splash screen solution.

I agree, it would be better to have this in TD.

Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
XP Embedded Book Author - XP Embedded Advanced, XP Embedded Supplemental
Toolkit
 
Back
Top