Jump to content

Recommended Posts

Posted

Is there a way to have UnattendedInstall = "Yes"

But still have full choice of any partition as target partition (empty or not)?

IOW: Have everything after target partition choice be UA?

Best combination of settings?

Thanks

Example answer file…. \I386\WINNT.SIF

[Data]

Autopartition = 0

MsDosInitiated = 0

UnattendedInstall = "Yes"

[unattended]

OemPreinstall=Yes

OemSkipEula=Yes

OEMFilesPath=.\$OEM$

[GuiUnattended]

OEMSkipWelcome=1


Posted

Thanks TranceEnergy.

So is

Autopartition = 1

when it just auto formats (& installs) on the first partition big enough?

Anyone know of any other settings that might limit choice of target partition?

Thanks

Posted

A word of caution:

Please be aware, i have ONLY used that autopartition = 1 in vmware installs which only has had 1 partition.

I dont know for sure 100% what happens if you have multiple partitions or harddrives.

I would NEVER use autopartition on a multiple harddrives system, unless i knew for sure 100% that windows would detect the harddrives in same way as bios does, and cabling internally in pc.

Some bios detects harddrive startup priority differently. This is especially true for some years older computer where SATA drives are used.

Tip: If windows setup detects you have harddrive with "partition1:empty space (no actual partition), partition 2: logical partition, partition 3: primary partition, it would copy boot files to partition 3, and your windows

to your partition 1 which you create with windows setup.

Posted

Yes

autopartition = 1

can be destructive and why I wanted to get a handle on how to best control choice of target partition.

Tip: If windows setup detects you have harddrive with "partition1:empty space (no actual partition), partition 2: logical partition, partition 3: primary partition, it would copy boot files to partition 3, and your windows to your partition 1 which you create with windows setup.
Are you saying that "non-partitioned empty space" at the start of a disc will become the new system partition that will, eventually, contain the boot files?
Posted

No im not saying that, i am saying that ******************* IF!********** you were to install windows on a harddrive that had those partitions already there, and you were to install windows on the empty **space** as a new

partition, your ntldr and other boot files would go to the partition 3.

IF you install windows onto a empty harddrive, that would never happen. If you install windows into a partition (not empty space) that is primary it would never happen.

But please just forget this, you will most likely not need to know all this, if you are doing installs on systems where windows already is deployed/used.

Still, good to be cautious if one uses autopartition option on systems with several harddrives, or partitions on single drive even.

Posted (edited)
Still, good to be cautious if one uses autopartition option on systems with several harddrives, or partitions on single drive even.
Yes, definitely. Thanks for the tip (word of caution part 2). That bazaar quirk would be a real head scratcher (what now??).

Good reason to try to fit a boot menu & a PE on the install disk (my next goal) for easier partition management.

Thanks for your help

Edited by g555

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...