[Daan]

Can't believe no one experienced the same problem?

[weaz1dls]

I could be wrong here....

A basic NT volume is prob in reference to the partitions you have created through PE with PE permisions. Permisions must be granted to EVERYONE and/or already in NTFS file system.

ok
there is no need to create and format more partitions than you need for setup.
When you boot from pe then you will have the security permisions of the pe version you booted with. If you do not "/makelocalsource" then setup will have to track any letter changes if applicable. Does your answerfile specifically say to convert to ntsf? If so there may be a permisions issue with the conversion. Did you make the system partition active? Keep it as simple as possible for setup. Sure installing from pe has many advantages however each is with it's own set of rules. Are you trying to use the same procedure you had used when installing from a functional 32bit enviro/remote install? Think it through or give more details. My suggestion would be do a test,

A) invoke the install without an unattend switch and with the noreboot switch. If the istall prepairs for textmode as it should then I would look in your answerfile to be sure the ntfs conversion entries all jive and do not contradict other settings.
If however it gives the same error/prompt then it is prob a permision issue and I would reboot(after deleting the setupfiles created from previous test) and
after reboot start off by creating an active ntfs partition and no others until the os is completely installed. Then go to A) follow the same steps as before.

check your pe version/update/modify with xpsp2. or at least xp. NT even with all the service packs and updates will not grant appropriate permission to a setup invoked directly following a Fat32/any partition creation in the manner you are doing it. Gosh I believe touches on this issue. http://www.msfn.org/board/index.php?showtopic=10181&st=0#

This post has been edited by weaz1dls: 23 June 2005 - 05:23 AM

[mbouchard]

I have used WinPE to create a NTFS partition and have successfully installed Win2000 (all flavors), WinXP (all flavors), and Win2003 Ent and Std and have not had any issues.

As to the message you get, when are you getting it?

[Daan]

I didn't try /makelocalsource switch. The answer file specifically says to convert to NTFS. I succesfully installed W2K (with a NTFS partition). I always activate the system partition. I tried start setup manually from WinPE (with NTFS/FAT32 activated system partition) same problem. I get the error message just before (I think) file copying..
I will try creating another WinPE and use /makelocalsource switch.

[Shoshoni]

Hello !

I'm a bit lost here! This's what's goin' on:

I have one little glitch in my XP unattended install.

This is the command that runs:

X:\XP\i386\winnt32 /syspart:c: /tempdrive:c: /unattend:winnt.sif

Which makes Setup ask for an upgrade check!

If I run the command with

X:\XP\i386\winnt32 /syspart:c: /tempdrive:c: /makelocalsource /unattend:winnt.sif

it doesn't happen.
It then takes longer so I wanted to speed up things a bit by excluding this command. putting

NTupgrade=No

in winnt.sif doesnt help either.

Thanks in advance for your time and help !

This post has been edited by Shoshoni: 12 August 2005 - 04:09 AM

[JuMz]

Shoshoni, on Aug 12 2005, 04:03 AM, said:

Hello !

I'm a bit lost here! This's what's goin' on:

I have one little glitch in my XP unattended install.

This is the command that runs:

X:\XP\i386\winnt32 /syspart:c: /tempdrive:c: /unattend:winnt.sif

Which makes Setup ask for an upgrade check!

If I run the command with

X:\XP\i386\winnt32 /syspart:c: /tempdrive:c: /makelocalsource /unattend:winnt.sif

it doesn't happen.
It then takes longer so I wanted to speed up things a bit by excluding this command. putting

NTupgrade=No

in winnt.sif doesnt help either.

Thanks in advance for your time and help !
<{POST_SNAPBACK}>

I believe it is asking for an upgrade check because it detects the other windows folder on the C drive...are you formating the drive before install? if you are booting with factory -winpe setting, you can use the diskwipe technique write in the winbom.ini

[SyKik]

is anyone having troubles getting the $oem$ to copy itself across to the target hd?

[pmshah]

Yesterday I came across a plugin for the purpose called "XPSetupLuncher". It probably is not an unattended version but one should be able to install Xp once the initial dialog box/form is filled in.

I will be testing it over the weekend & see how it behaves.

[SlimShady]

pmshah, on Nov 11 2005, 01:18 AM, said:

Yesterday I came across a plugin for the purpose called "XPSetupLuncher". It probably is not an unattended version but one should be able to install Xp once the initial dialog box/form is filled in.

I will be testing it over the weekend & see how it behaves.

Could you post the results?

[Radimus]

You can get it over at 911cd.net

The newer vesion is supposed to read your winnt.sif.

I'm testing it also.

[dwchan69]

I make a x64 WinPE 2005 (not using ramdisk yet) and boot into the PE environment. By default, it map the CD Drive as Drive X. Also on the CD, under the folder x:\sysmgt is my windows 2003 source directory

x:\sysmgt\i386
x:\sysmgt\amd64

after I diskpart the local drive (c: drive) i try to run the following command but keep getting out of memory error

x:\sysmgt\amd64\winnt32.exe /syspart:c: /tempdrive:c /s:X:\sysmgt\amd64 /unattend:x:\sysmgt\lzunattd.txt

where x:\sysmgt\lzunattd.txt is my winnt unattended file

Do anyone have any idea or suggestion

dwc

[JuMz]

I am also having this same problem now. Mine was working before and then I reformatted my PC and lost everything and now i am starting from scratch in and i can't get it to work! I have seen numerous people post with the same problem:

we reach a screen "Setup was unable to verify drive C:. Your computer may not have enough memory..." blah blah

This is what i notice:

Once the text portion of the setup completes, its reboots (ok so everything is normal). Now from what i recall, the gui portion of the setup should begin. INSTEAD, the text based portion of the setup starts AGAIN! and soon after, this error occurs. Does anyone have any idea why the text portion of the setup attempts to start TWICE?

[JuMz]

I have found a solution to the problem,

http://ryanvm.net/fo...p?p=21951#21951


This has to do with insallations using RyanVM's update pack which is what I was using...