winpe boot cd & partition size

G

Guest

Anyone know how to get a pebuild to make a , say 10 or 12 gb c:

(boot/system) drive? In my winnt.sif, no matter what I put in the
[Unattended]
ExtendOemPartition=0
ExtendOemPartition=1
ExtendOemPartition=10240

It take the whole drive for C: here is a copy of the whole data

section & Unatteneded sctions.

[Data]
AutoPartition=1
MsDosInitiated="0"
UnattendedInstall="Yes"

[Unattended]
UnattendMode=FullUnattended
OemSkipEula=Yes
OemPreinstall=No
TargetPath=\WINDOWS
Repartition=Yes
ExtendOemPartition=??????

And yes I read the chm in the deploy.cab folder and as I read it

the 10240 entry should have givin me about a 10 gb drive c:?

steve Tretakis
 
R

Rob

Here's how I do it (ignore anything not relevant to you, this is just a cut
paste from documentation I wrote)

The WINBOM.INI file is on your Windows PE configuration floppy created
during the Setup Manager process. This file is processed when WinPE runs
and contains all the information on where WinPE can find your custom
configuration set.

Edit A:\WINBOM.INI and add the following:

[Factory]
Logfile = a:\winbom.log
Logging = Yes
LogLevel = 2
LogPerf = No

This will enable WinPE logging and write the log file to your floppy during
WinPE setup. Also add:

[OemRunOnce]
"Hard Drive Setup","""a:\begin.cmd"" "

This will execute the begin.cmd file which we will be placing on the floppy.
This file will create a 4gig partition on your target hard drive. We must
use this methodology so as not to delete any existing partitions on the
target hard drive (such as the Intel Service Partition).

Create A:\begin.cmd with the following contents:

diskpart /s a:\part.txt
format c: /fs:ntfs /q /y



Create A:\PART.TXT with the following commands:

Sel Disk 0
Create Part Pri Size=4000
active
assign letter=c:
exit
 
G

Guest

My fault Rob, thanks for getting back to me but I guess I didn't mention that
I wasn't using a floppy. I used the "oscdimg -betfsboot.com -n -h d:\source"
d:\targert.iso" run from the winpe directory t build a bootable cd.
One cd has xp & one has w2k3. I did this mainly for my home lab & vm
machines...Im looking at the built iso's I don't even see a winbom file. All
I did was build & unattend.txt file & rename to winnt.sof & place it in the
i386 directory.

Steve Tretakis

Rob said:
Here's how I do it (ignore anything not relevant to you, this is just a cut
paste from documentation I wrote)

The WINBOM.INI file is on your Windows PE configuration floppy created
during the Setup Manager process. This file is processed when WinPE runs
and contains all the information on where WinPE can find your custom
configuration set.

Edit A:\WINBOM.INI and add the following:

[Factory]
Logfile = a:\winbom.log
Logging = Yes
LogLevel = 2
LogPerf = No

This will enable WinPE logging and write the log file to your floppy during
WinPE setup. Also add:

[OemRunOnce]
"Hard Drive Setup","""a:\begin.cmd"" "

This will execute the begin.cmd file which we will be placing on the floppy.
This file will create a 4gig partition on your target hard drive. We must
use this methodology so as not to delete any existing partitions on the
target hard drive (such as the Intel Service Partition).

Create A:\begin.cmd with the following contents:

diskpart /s a:\part.txt
format c: /fs:ntfs /q /y



Create A:\PART.TXT with the following commands:

Sel Disk 0
Create Part Pri Size=4000
active
assign letter=c:
exit


steve tretakis said:
Anyone know how to get a pebuild to make a , say 10 or 12 gb c:

(boot/system) drive? In my winnt.sif, no matter what I put in the
[Unattended]
ExtendOemPartition=0
ExtendOemPartition=1
ExtendOemPartition=10240

It take the whole drive for C: here is a copy of the whole data

section & Unatteneded sctions.

[Data]
AutoPartition=1
MsDosInitiated="0"
UnattendedInstall="Yes"

[Unattended]
UnattendMode=FullUnattended
OemSkipEula=Yes
OemPreinstall=No
TargetPath=\WINDOWS
Repartition=Yes
ExtendOemPartition=??????

And yes I read the chm in the deploy.cab folder and as I read it

the 10240 entry should have givin me about a 10 gb drive c:?

steve Tretakis
Click to expand...
Click to expand...
 
R

Rob

you can still use a floppy for the WINBOM.INI. If it's in the floppy drive
on the machine you boot the WinPE CD from, it will automatically
load the WINBOM.INI and override the WINBOM on the CD (if you have one).
This is handy in case you have multiple source servers where
you load your apps from. You don't need to create a new WinPE bootable CD
each time, you just edit the WINBOM.INI on the floppy to point
to the new location.

steve tretakis said:
My fault Rob, thanks for getting back to me but I guess I didn't mention
that
I wasn't using a floppy. I used the "oscdimg -betfsboot.com -n -h
d:\source"
d:\targert.iso" run from the winpe directory t build a bootable cd.
One cd has xp & one has w2k3. I did this mainly for my home lab & vm
machines...Im looking at the built iso's I don't even see a winbom file.
All
I did was build & unattend.txt file & rename to winnt.sof & place it in
the
i386 directory.

Steve Tretakis

Rob said:
Here's how I do it (ignore anything not relevant to you, this is just a
cut
paste from documentation I wrote)

The WINBOM.INI file is on your Windows PE configuration floppy created
during the Setup Manager process. This file is processed when WinPE runs
and contains all the information on where WinPE can find your custom
configuration set.

Edit A:\WINBOM.INI and add the following:

[Factory]
Logfile = a:\winbom.log
Logging = Yes
LogLevel = 2
LogPerf = No

This will enable WinPE logging and write the log file to your floppy
during
WinPE setup. Also add:

[OemRunOnce]
"Hard Drive Setup","""a:\begin.cmd"" "

This will execute the begin.cmd file whic
hwewillbeplacingonthefloppy.
This file will create a 4gig partition on your target hard drive. We
must
use this methodology so as not to delete any existing partitions on the
target hard drive (such as the Intel Service Partition).

Create A:\begin.cmd with the following contents:

diskpart /s a:\part.txt
format c: /fs:ntfs /q /y



Create A:\PART.TXT with the following commands:

Sel Disk 0
Create Part Pri Size=4000
active
assign letter=c:
exit


message
Anyone know how to get a pebuild to make a , say 10 or 12 gb c:

(boot/system) drive? In my winnt.sif, no matter what I put in the
[Unattended]
ExtendOemPartition=0
ExtendOemPartition=1
ExtendOemPartition=10240

It take the whole drive for C: here is a copy of the whole data

section & Unatteneded sctions.

[Data]
AutoPartition=1
MsDosInitiated="0"
UnattendedInstall="Yes"

[Unattended]
UnattendMode=FullUnattended
OemSkipEula=Yes
OemPreinstall=No
TargetPath=\WINDOWS
Repartition=Yes
ExtendOemPartition=??????

And yes I read the chm in the deploy.cab folder and as I read it

the 10240 entry should have givin me about a 10 gb drive c:?

steve Tretakis
Click to expand...
Click to expand...
Click to expand...
 
G

Guest

Yeah but my plan was to avoid the whole floppy issue...

Rob said:
you can still use a floppy for the WINBOM.INI. If it's in the floppy drive
on the machine you boot the WinPE CD from, it will automatically
load the WINBOM.INI and override the WINBOM on the CD (if you have one).
This is handy in case you have multiple source servers where
you load your apps from. You don't need to create a new WinPE bootable CD
each time, you just edit the WINBOM.INI on the floppy to point
to the new location.

steve tretakis said:
My fault Rob, thanks for getting back to me but I guess I didn't mention
that
I wasn't using a floppy. I used the "oscdimg -betfsboot.com -n -h
d:\source"
d:\targert.iso" run from the winpe directory t build a bootable cd.
One cd has xp & one has w2k3. I did this mainly for my home lab & vm
machines...Im looking at the built iso's I don't even see a winbom file.
All
I did was build & unattend.txt file & rename to winnt.sof & place it in
the
i386 directory.

Steve Tretakis

Rob said:
Here's how I do it (ignore anything not relevant to you, this is just a
cut
paste from documentation I wrote)

The WINBOM.INI file is on your Windows PE configuration floppy created
during the Setup Manager process. This file is processed when WinPE runs
and contains all the information on where WinPE can find your custom
configuration set.

Edit A:\WINBOM.INI and add the following:

[Factory]
Logfile = a:\winbom.log
Logging = Yes
LogLevel = 2
LogPerf = No

This will enable WinPE logging and write the log file to your floppy
during
WinPE setup. Also add:

[OemRunOnce]
"Hard Drive Setup","""a:\begin.cmd"" "

This will execute the begin.cmd file whic
hwewillbeplacingonthefloppy.
This file will create a 4gig partition on your target hard drive. We
must
use this methodology so as not to delete any existing partitions on the
target hard drive (such as the Intel Service Partition).

Create A:\begin.cmd with the following contents:

diskpart /s a:\part.txt
format c: /fs:ntfs /q /y



Create A:\PART.TXT with the following commands:

Sel Disk 0
Create Part Pri Size=4000
active
assign letter=c:
exit


message
Anyone know how to get a pebuild to make a , say 10 or 12 gb c:

(boot/system) drive? In my winnt.sif, no matter what I put in the
[Unattended]
ExtendOemPartition=0
ExtendOemPartition=1
ExtendOemPartition=10240

It take the whole drive for C: here is a copy of the whole data

section & Unatteneded sctions.

[Data]
AutoPartition=1
MsDosInitiated="0"
UnattendedInstall="Yes"

[Unattended]
UnattendMode=FullUnattended
OemSkipEula=Yes
OemPreinstall=No
TargetPath=\WINDOWS
Repartition=Yes
ExtendOemPartition=??????

And yes I read the chm in the deploy.cab folder and as I read it

the 10240 entry should have givin me about a 10 gb drive c:?

steve Tretakis
Click to expand...
Click to expand...
Click to expand...
 
R

Rob

then put the WINBOM.INI and all the other scripts I mentioned on the CD that
you burned. i don't recall if it goes into the root directory, the WinPE
documentation should clarify that.

steve tretakis said:
Yeah but my plan was to avoid the whole floppy issue...

Rob said:
you can still use a floppy for the WINBOM.INI. If it's in the floppy
drive
on the machine you boot the WinPE CD from, it will automatically
load the WINBOM.INI and override the WINBOM on the CD (if you have one).
This is handy in case you have multiple source servers where
you load your apps from. You don't need to create a new WinPE bootable
CD
each time, you just edit the WINBOM.INI on the floppy to point
to the new location.

message
My fault Rob, thanks for getting back to me but I guess I didn't
mention
that
I wasn't using a floppy. I used the "oscdimg -betfsboot.com -n -h
d:\source"
d:\targert.iso" run from the winpe directory t build a bootable cd.
One cd has xp & one has w2k3. I did this mainly for my home lab & vm
machines...Im looking at the built iso's I don't even see a winbom
file.
All
I did was build & unattend.txt file & rename to winnt.sof & place it in
the
i386 directory.

Steve Tretakis

:

Here's how I do it (ignore anything not relevant to you, this is just
a
cut
paste from documentation I wrote)

The WINBOM.INI file is on your Windows PE configuration floppy created
during the Setup Manager process. This file is processed when WinPE
runs
and contains all the information on where WinPE can find your custom
configuration set.

Edit A:\WINBOM.INI and add the following:

[Factory]
Logfile = a:\winbom.log
Logging = Yes
LogLevel = 2
LogPerf = No

This will enable WinPE logging and write the log file to your floppy
during
WinPE setup. Also add:

[OemRunOnce]
"Hard Drive Setup","""a:\begin.cmd"" "

This will execute the begin.cmd file whic
hwewillbeplacingonthefloppy.
This file will create a 4gig partition on your target hard drive. We
must
use this methodology so as not to delete any existing partitions on
the
target hard drive (such as the Intel Service Partition).

Create A:\begin.cmd with the following contents:

diskpart /s a:\part.txt
format c: /fs:ntfs /q /y



Create A:\PART.TXT with the following commands:

Sel Disk 0
Create Part Pri Size=4000
active
assign letter=c:
exit


message
Anyone know how to get a pebuild to make a , say 10 or 12 gb c:

(boot/system) drive? In my winnt.sif, no matter what I put in the
[Unattended]
ExtendOemPartition=0
ExtendOemPartition=1
ExtendOemPartition=10240

It take the whole drive for C: here is a copy of the whole data

section & Unatteneded sctions.

[Data]
AutoPartition=1
MsDosInitiated="0"
UnattendedInstall="Yes"

[Unattended]
UnattendMode=FullUnattended
OemSkipEula=Yes
OemPreinstall=No
TargetPath=\WINDOWS
Repartition=Yes
ExtendOemPartition=??????

And yes I read the chm in the deploy.cab folder and as I read it

the 10240 entry should have givin me about a 10 gb drive c:?

steve Tretakis
Click to expand...
Click to expand...
Click to expand...
 
G

Guest

Thats worht a try, Hey thanks for hanging in there i appreciate it...Ill try
it both ways ..

Steve

Rob said:
then put the WINBOM.INI and all the other scripts I mentioned on the CD that
you burned. i don't recall if it goes into the root directory, the WinPE
documentation should clarify that.

steve tretakis said:
Yeah but my plan was to avoid the whole floppy issue...

Rob said:
you can still use a floppy for the WINBOM.INI. If it's in the floppy
drive
on the machine you boot the WinPE CD from, it will automatically
load the WINBOM.INI and override the WINBOM on the CD (if you have one).
This is handy in case you have multiple source servers where
you load your apps from. You don't need to create a new WinPE bootable
CD
each time, you just edit the WINBOM.INI on the floppy to point
to the new location.

message
My fault Rob, thanks for getting back to me but I guess I didn't
mention
that
I wasn't using a floppy. I used the "oscdimg -betfsboot.com -n -h
d:\source"
d:\targert.iso" run from the winpe directory t build a bootable cd.
One cd has xp & one has w2k3. I did this mainly for my home lab & vm
machines...Im looking at the built iso's I don't even see a winbom
file.
All
I did was build & unattend.txt file & rename to winnt.sof & place it in
the
i386 directory.

Steve Tretakis

:

Here's how I do it (ignore anything not relevant to you, this is just
a
cut
paste from documentation I wrote)

The WINBOM.INI file is on your Windows PE configuration floppy created
during the Setup Manager process. This file is processed when WinPE
runs
and contains all the information on where WinPE can find your custom
configuration set.

Edit A:\WINBOM.INI and add the following:

[Factory]
Logfile = a:\winbom.log
Logging = Yes
LogLevel = 2
LogPerf = No

This will enable WinPE logging and write the log file to your floppy
during
WinPE setup. Also add:

[OemRunOnce]
"Hard Drive Setup","""a:\begin.cmd"" "

This will execute the begin.cmd file whic
hwewillbeplacingonthefloppy.
This file will create a 4gig partition on your target hard drive. We
must
use this methodology so as not to delete any existing partitions on
the
target hard drive (such as the Intel Service Partition).

Create A:\begin.cmd with the following contents:

diskpart /s a:\part.txt
format c: /fs:ntfs /q /y



Create A:\PART.TXT with the following commands:

Sel Disk 0
Create Part Pri Size=4000
active
assign letter=c:
exit


message
Anyone know how to get a pebuild to make a , say 10 or 12 gb c:

(boot/system) drive? In my winnt.sif, no matter what I put in the
[Unattended]
ExtendOemPartition=0
ExtendOemPartition=1
ExtendOemPartition=10240

It take the whole drive for C: here is a copy of the whole data

section & Unatteneded sctions.

[Data]
AutoPartition=1
MsDosInitiated="0"
UnattendedInstall="Yes"

[Unattended]
UnattendMode=FullUnattended
OemSkipEula=Yes
OemPreinstall=No
TargetPath=\WINDOWS
Repartition=Yes
ExtendOemPartition=??????

And yes I read the chm in the deploy.cab folder and as I read it

the 10240 entry should have givin me about a 10 gb drive c:?

steve Tretakis
Click to expand...
Click to expand...
Click to expand...
 
Z

ziomamo

Hello guys,

Could you please show me an example for the WINBOM.INI file to point
to a different location?
I appreciate
Thanks
 
G

Guest

[Version]
signature=$CHICAGO$

[Factory]
Username=user1
Password="password1"
NewWinbom=\\server\share1\winbom.ini

[ComputerSettings]
AuditAdminAutoLogon=Yes
SourcePath=%windir%

[NetCards]

[WinPE.net]
StartNet=Yes
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Windows XP Unattend Install 3
Winnt.sif and hardware detection. 1
Unattended installation issue. 6
CD - Winnt.sift Unattended installation 1
xp unattended install, customizing folder display and views 2
Unattended partition size (4096MB) 1
expert question: Howto Add 3th party Mass Storage Drives unattended? 2
Unattended Windows XP Pro install halts when Windows directory already exist 4

Top