Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1590
  • Last Modified:

ExtendOemPartition not working

Hi experts

I try to do an unattended installation of Windws XP by using the unattend.txt. Everything works fine, except that the partition is not resized. I want to use the whole 80GB of the HDD, and I can not use the CD-ROM or a network based source for installation.
This is the unattend.txt I'm using:

[Unattended]
DisableDynamicUpdates=Yes
DriverSigningPolicy=Ignore
ExtendOemPartition=1
FileSystem=ConvertNTFS
Hibernation=1
OemPreinstall=Yes
OemSkipEula=Yes
OverwriteOemFilesOnUpgrade=Yes
TargetPath=\WINDOWS
UnattendMode=FullUnattended
UnattendSwitch=Yes
WaitForReboot=No

[GuiUnattended]
AdminPassword=*
AutoLogon=Yes
AutoLogonCount=4
OEMSkipRegional=1
OEMSkipWelcome=1
TimeZone=110

[UserData]
ComputerName=726-A002
FullName="My Computer"
OrgName="My Company"
ProductID=XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

[Proxy]
Proxy_Enable=0

[URL]
AutoConfig=0
Home_Page=about:blank

[FavoritesEx]
Title1="MyHome.url"
URL1="http://www.ourserver.tld/"

[Branding]
BrandIEUsingUnattended=Yes

[GuiRunOnce]


[Display]
BitsPerPel=16
Vrefresh=60
Xresolution=1024
Yresolution=768

[RegionalSettings]
InputLocale_DefaultUser=100c:0000100c
InputLocale=100c:0000100c
Language=0000100c
LanguageGroup=1
SystemLocale=0000100c
UserLocale_DefaultUser=0000100c
UserLocale=0000100c

[TapiLocation]
AreaCode=0
CountryCode=41
Dialing=Tone

[Components]
accessopt=off
calc=on
cdplayer=off
certsrv=off
certsrv_client=off
certsrv_server=off
charmap=off
chat=off
deskpaper=off
dialer=off
fax=off
fp_extensions=off
fp_vdir_deploy=off
freecell=off
hearts=off
hypertrm=on
ieaccess=off
iis_common=off
iis_ftp=off
iis_htmla=off
iis_inetmgr=off
iis_nntp=off
iis_nntp_docs=off
iis_pwmgr=off
iis_smtp=off
iis_smtp_docs=off
iis_www=off
iis_www_vdir_printers=off
iis_www_vdir_terminalservices=off
iisdbg=off
indexsrv_system=off
media_clips=off
media_utopia=off
minesweeper=off
mousepoint=off
mplay=on
msmq_ADIntegrated=off
msmq_Core=off
msmq_HTTPSupport=off
msmq_LocalStorage=off
msmq_MQDSService=off
msmq_RoutingSupport=off
msmq_TriggersService=off
msnexplr=off
mswordpad=on
netcis=off
netoc=off
objectpkg=off
paint=on
pinball=off
rec=off
reminst=off
rstorage=off
solitaire=off
spider=off
templates=off
TSClients=off
TSEnable=off
vol=on
wms=off
wms_admin_page=off
wms_admin_mmc=off
wms_server=off
zonegames=off
oeaccess=off
wmpocm=off

[Networking]
InstallDefaultComponents=No

[Identification]
JoinWorkgroup=WORKGROUP

[NetAdapters]
Adapter01=params.Adapter01

[params.Adapter01]
InfID=*

[NetProtocols]
MS_TCPIP=params.MS_TCPIP

[params.MS_TCPIP]
AdapterSections=params.MS_TCPIP
DNS=No
EnableLMHosts=Yes
UseDomainNameDevolution=No
AdapterSections=params.MS_TCPIP.Adapter01

[params.MS_TCPIP.Adapter01]
SpecificTo=Adapter01
DefaultGateway=193.8.212.1
DHCP=No
IPAddress=193.8.212.101
NetBIOSOptions=0
SubnetMask=255.255.255.0
WINS=No

[NetClients]
MS_MSClient=params.MS_MSClient

[params.MS_MSClient]

[NetServices]
MS_Server=params.MS_Server

[params.MS_Server]

[NetBindings]

[NetOptionalComponents]
LPDSVC=0
SimpTcp=0
SNMP=0
WINS=0

[SNMP]

[Data]
AutoPartition=1

[Shell]
CustomDefaultThemeFile="%SYSTEMROOT%\Resources\Themes\Windows Classic.theme"
DefaultStartPanelOff=Yes
DefaultThemesOff=Yes


First I started off a FAT16 2GB partition with the installation source on it, and at some point (in the text-only portion of the setup), the installer stops because there is not enough disk space left.
If I start with a FAT32 10GB partition with the installation source on it, the installation works fine exept the partition stays the same in size, but is converted to NTFS.

I used more or less the same UNATTEND.TXT for Win2K, and there the repartitioning worked just fine. Is there a limitation in partition size?
0
WebJoe
Asked:
WebJoe
  • 5
  • 4
1 Solution
 
JBlondCommented:
Am I understanding you right that the source files are on the same partition you want to install to?
Does the setup extend the partition if you specify another value? For example 40000 to extend it to 40GB plus the original size.
0
 
WebJoeAuthor Commented:
Yes, the source is on the same partition I want the OS to install on.

I did try
ExtendOemPartition=1, 2048

to extend it to 4GB total (that was the setting I used with Win2K), but with the same result as described above: The partition was converted, but no change in size.
0
 
JBlondCommented:
If you want to specify a specific value you don't need the '1'. That will not work.

In your example the correct line would be:
ExtendOemPartition=2048

But I suppose this isn't the problem. This is now a shot in the dark:
Try

ExtendOEMPartition = 1

(OEM in capitals and with additional spaces)

I searched in my setup files and everytime I used it in that way.
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
WebJoeAuthor Commented:
From the Windows XP Preinstallation Reference:

ExtendOemPartition
Value: 0 | 1 | extra_size_in_MB

The ExtendOemPartition entry is used to extend the partition on which you are installing Windows. This entry causes Setup to extend this destination partition into any available unpartitioned space that physically follows it on the disk.

ExtendOemPartition automatically leaves the last cylinder on the hard disk free to allow dynamic disk support.

0
Setup does not extend the partition.
1
Setup extends the partition to fill out the hard disk.

extra_size_in_MB
Setup increases the current partition size by this amount. This is useful if you want to configure more than one partition on the hard disk.

I misinterpreted that and thougt the extra size in mb is an optional second parameter. That would explain why my Win2K-installations ended up with 6GB partitions (2GB FAT16 start + 2GB extension = 6GB final size ?!?) :)

Anyway, I will try what you suggested. I'd rather not give an exact size, since I don't know what HDD sizes future machines will have.
0
 
JBlondCommented:
Just try it. I remember that i had such a spelling issue myself about a year ago but I don't know if it was this parameter or another.

The extra size extends the partition by the specified value. For example if your partition is 10 GB big and you use "ExtendOemPartition = 10000". The setup should now extend the partition to 20 GB.


0
 
WebJoeAuthor Commented:
Sorry, did not work. I also tried giving a specific value for the extension, and that also didn't work.

So I guess there is something else wrong with my unattend.txt (I do have FileSystem=ConvertNTFS).

Any other ideas?
0
 
JBlondCommented:
Two other ideas:

1. You're right and there's something wrong with your unattend.txt
If I were you I would generate a new one with the setup builder from the XP CD and add only the lines for extending the partition so that the file contains only the minimum entries.

2. The worst case: Extending the partition does not work, if you initiate the setup from the same partition. But I never heard about something like that...
0
 
WebJoeAuthor Commented:
Thanks for the tipp

I thought about 2) too, but it worked in Win2k so why shouldn't it in WinXP.

I will be away for a week, but will test 1) when I get back and post the result here.
0
 
WebJoeAuthor Commented:
JBlond, here's what I did and found out:

1. I built a new unattend.txt using the Microsoft setup manager from the XP CD

2. Since many of the features I had planed are not supported by that, I added them section by section, testing ist every time installing from a network share (and not the local disk as I wanted it)

 -> My original unattend.txt was fine, at the end of my tests all sections were exactly as shown above

3. I copied the whole source including the tested unattend.txt to the FAT formated first partition (the rest of the hard disk was not partitioned so the setup could resize the partition to match the disk size) and ran the setup as bbefore, changing source and unattend.txt-location from W: (my network drive) to C:
 -> Same behaviour as mentioned in my first post.
My conclusion is that, other than with W2K, it is not possible to install WXP the way I wanted it, presumably because the installation source uses up more space than with earlier versions (and with the temporary folders more than 2GB).

Thanks anyway for your help
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now