[gosh]

Someone asked how to do this but didn't get a reply. You can install win2k or XP from winpe, but there's a special way to do this. Installing win2k or xp from winpe doesn't neccessarily make the install faster, but it does present some very interesting unattended situations.

Edit startnet.cmd or whatever the winpe batch file is called. Add the following:

For win2k installs add this:

FORMAT D: /fs:ntfs /q /V:gosh /y <--this will auto format the drive!
cacls c:\ /p Everyone:F
.\i386\winnt32.exe /syspart:c: /tempdrive:c /unattend:D:\Flats\Win2k\ProSP3\winnt.sif

For winxp installs put this:

FORMAT D: /fs:ntfs /q /V:gosh /y <--this will auto format the drive!
.\i386\winnt32.exe /syspart:c: /tempdrive:c /unattend:D:\Flats\Win2k\ProSP3\winnt.sif

You'll obviously need to edit the command to fit you. I successfully installed win2k from winpe using that command. The reason you need to change the permissions is because win2k has different root permissions than xp. The xp version of autofmt.exe will format the partition using the xp permissions.

As you can see above, you can specify an unattend file. So when the computer restarts, it starts setup unattended.

If you're interested in auto partitioning and making drive letters, search google. With XP's unattend.txt file you cannot auto specify what partition to format, with winpe you CAN.

Make sure you use the /syspart command, otherwise the drive won't be bootable!

-gosh

[Tbone2]

gosh,

You have to stop this dude !!!

I will not have any questions if you keep answering them before I ask

Thanks again

[Thanatos]

Quote

/syspart:drive_letter

Specifies that you can copy Setup startup files to a hard disk, mark the disk as active, and then install the disk into another computer. When you start that computer, it automatically starts with the next phase of Setup. You must always use the /tempdrive parameter with the /syspart parameter.

Are you syre syspart is needed? One question about that, does the last command copy the CD to C? and if so, wouldn't the unattended file always be in C:\i386

[gosh]

You can use other drives or variables if you want, i just didn't test it.

-gosh

[Bachus]

How does this work with a multiboot cd? I think I might have an idea...

[gosh]

You boot from winpe, then run setup from the cd. However you cannot use my method to reduce source, since this requires winnt32.exe.

The real benefit from winpe is you have a full 32 bit OS to run in. You also can make scripts to auto format and repartition. You also have network access, which you don't have under dos.

-gosh

[RyanVM]

Welcome back, gosh :punk:

[gosh]

::kiss:: i missed you too

-gosh

[baliktad]

I just wanted to add that I don't think very many people grasp just what WinPE will allow us to do. I have been experimenting with Bart's PE Builder and you can make some *killer* tools with it. Since this is an installation thread, however:

I keep various windows source files on my hard disk: Windows 2000, Windows XP, and Windows 2003. Originally I was copying those my WinPE CD and installing from there but then I realized... a significant portion of operating system installation is just brute force copying from the CD. And even with today's 52 speed CD-ROM drives, optical drives are still orders of magnitude slower than hard disks. Since I reinstall about monthly on this box, I decided to try using WinPE to boot but the hard drive as my installation source.

The results: shocking. What was normally a ~40 to 45 minute process I have reduced to just short of 15 minutes(!). I kid you not. That doesn't include about a minute for WinPE to boot up, but it does include formatting of my old OS partition and a complete unattended installation. You'll obviously need separate partitions for your OS and data but that's a good idea anyway.

For those interested, here's the batch script I start as soon as WinPE loads:

set AnswerFile=.\unattend.txt
set SetupFiles=F:\Working\WinXP\cdroot\WXPFPP\I386 

format d: /fs:NTFS /q /v:WINXP /y
%SetupFiles%\winnt32 /s:%SetupFiles% /unattend:%AnswerFile% /tempdrive:d:
exit

Comments or suggestions welcome.

[Bachus]

So where do I put these commands? Bart's pebuilder doesn't seem to generate a startnet.cmd..do I do that manually?

[gosh]

startnet.cmd or winbom.ini. Winbom.ini has 2 sections for running files - i believe it's [Oemfilestorun] or some crap. Search google on winbom.ini and runonce and i'm sure you'll find the correct paramters. Or of course you could manually run the batch file once winpe is booted.

-gosh

[Bachus]

Alright, I'm having a small problem starting an unattended XP installation from WinPE. Everything seems to work fine except for when it comes to running winnt32.exe I get this error:

Quote

The specified Setup script file (E:\winnt.sif) is inaccessible or invalid. Contact your system administrator.

I had this problem when using the "reducing size of source" guide and I got around that by removing a large chunk of my winnt.sif file. That isn't an option here, so I'm wondering if anyone can see something I've done wrong that would generate this error. This very same file has worked fine in normal unattended installs so I don't know what winnt32 could be having issues with. At any rate, here it is:

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

[Unattended]
    UnattendMode=FullUnattended
    OemSkipEula=Yes
    Repartition=No
    OemPreinstall=Yes
    TargetPath=\WINDOWS
    AutoActivate=No
    WaitForReboot=No
    UnattendSwitch=yes
    OemPnPDriversPath="Drivers\000\Nforce2\AudioDrv;drivers\000\Nforce2\AudioUtl;drivers\000\Nforce2\Ethernet;drivers\000\Nforce2\GART;drivers\000\Nforce2\IDE;drivers\000\Nforce2\MemCtl;drivers\000\Nforce2\SMBus;drivers\000\Nforce2\USB;Drivers\001\Catalyst3_7;drivers\002\TV_Tuner;drivers\003\HP3320\win2k_xp"
    DriverSigningPolicy=Ignore
    ProgramFilesDir=\Programs
    CommonProgramFilesDir=\Programs\Common

[GuiUnattended]
    AdminPassword=*
    EncryptedAdminPassword=Yes
    OEMSkipRegional=1
    TimeZone=40
    OemSkipWelcome=1

[UserData]
    ProductID=removed
    FullName="Richard Bach"
    OrgName=""
    ComputerName=SHODAN

[Display]
    BitsPerPel=32
    Xresolution=1024
    YResolution=768
    Vrefresh=85

[RegionalSettings]
    LanguageGroup=1
    Language=00000409

[Shell]
    CustomDefaultThemeFile = "%WinDir%\Resources\Themes\Metallic.theme"
    DefaultStartPanelOff = Yes

[Identification]
    JoinWorkgroup=HOME

[Networking]
    InstallDefaultComponents=Yes

[Branding]
    BrandIEUsingUnattended=Yes

[Proxy]
    Proxy_Enable=1
    Use_Same_Proxy=0
    HTTP_Proxy_Server=localhost:8080

[URL]
  Home_Page = http://www.google.com

[Components]
    AutoUpdate = Off
    dialer = off
    iis_webadmin = off
    media_clips = off
    OEAccess = off
    Paint = off
    rec = off
    templates = off
    msmsgs = off
    msnexplr=off 
    freecell=off
    hearts=off
    minesweeper=off
    pinball=off
    solitaire=off
    spider=off
    zonegames=off

[GuiRunOnce]
    command0=%systemdrive%\install\mn.cmd

[gosh]

Did you type in the path right? Is the file read only? The local source you're using is the full i386 folder right (not the reduzed source)?

Try putting a ; in front of each section to see what section is causing the problem. Then put a ; in front of that section to see what switch is causing the problem.

-gosh

[XtremeMaC]

**wrong**

This post has been edited by XtremeMaC: 06 December 2003 - 06:30 AM

[Bachus]

Well, it seems that setup doesn't much care for that command0 line, which is rather strange if you ask me. I mean, of course the file isn't in that location--setup has copied it yet. Am I just going to have to copy the file manually before starting setup? Seems kind of silly to me...

Oh, and about that \Programs thing--I'd read that if you leave out a drive letter it will create the directory on the same drive as Windows is installed. I haven't actually tested it yet, however.

[tarkan]

@XtremeMaC

I had the same problem with either this 
OemPnPDriversPath="Drivers\000\Nforce2\AudioDrv;drivers\000\Nforce2\AudioUtl;drivers\000\Nforce2\Ethernet;drivers\000\Nforce2\GART;drivers\000\Nforce2\IDE;
drivers\000\Nforce2\MemCtl;drivers\000\Nforce2\SMBus;drivers\000\Nforce2\USB;Drivers\001\Catalyst3_7;drivers\002\TV_Tuner;drivers\003\HP3320\win2k_xp" 
edited :: wow its long i'm cutting it into two lines

WinXY adds to each listed driverspath under OemPnPDriversPath= "C:"
This is hard coded...read manual for unattended installation.
Use the $OEM$ structure and put the PnP drivers to $OEM$\$1\PnP
If the $OEM$ structure is not under the I386 folder you have to use the OemDriversPath entry in your unattend.txt or winnt.sif. This entry should point to your $OEM$ folder. If your folder is in the root => "C:\$OEM$ you have to add C: to the OemDriversPath=

This folder will be used during textmode and guimodesetup.

If you have further questions contact me via Mail and I will post more detailed information to this topic

[XtremeMaC]

I had spelling mistake on my winnt.sif (well a (; & " & \) was a mistake)
sorry for the confusion (I've them all covered now)

@Tarkan well I actually knew those, it was always giving me an error bc of those misplaced (; & " & \).
Thanks anywayz Tarkan...
(btw its been a while since october )

and welcome

[SlimShady]

gosh, on Oct 28 2003, 10:34 AM, said:

You boot from winpe, then run setup from the cd.  However you cannot use  my method to reduce source, since this requires winnt32.exe.

The real benefit from winpe is you have a full 32 bit OS to run in.  You also can make scripts to auto format and repartition.  You also have network access, which you don't have under dos.

-gosh

I'm getting a little bit confused
Can you please post a manual of everything.
With "What do I need" and "where do I get it"
Below is what I know now:

What you need:
* WinXP SP1 on CD
* Bart's PE Builder

Use Bart's PE Builder to create WinPE....
Place/install WinPE (??)...

Boot to WinPE and start the batchfile that automatically formats and contains the path to the XPSP1 folder and answerfile.

I really appreciate everything you do.

[Br4tt3]

A couple off questions.... i am confused off all this WinPE. I have been working with unattended installs (SIF) and PXE (RIS) alot... However, some1 told me abbout WinPE and I tried it out...

1. Is it possible to launch a unattended setup (SIF) setup of, lets say Windows 2003 server for example, from within WinPE? I have tried and all i get is a "out of memory" error.... I have asked the same question @ the MS newsgroups deploy section, and the answer was NO!

2. And if it is not possible, what is the correct way to deploy a Windows setup from within WinPE? Is it sysprep that is used or what?

WinPE seems as a much more flexible tech, especially the disk part seems much better then the unattended / RIS possiblities....

3. and last question... where do I get the white papers, walktroughs, step by step for proceding with WinPE??? I have read the forum threads... and I am not ready for tech nitty gritty, i want to get the big picture first....

However, love this already.... very n1! Think i am gonna hang out here more...
Later dudes...

[mbouchard]

Quote

1. Is it possible to launch a unattended setup (SIF) setup of, lets say Windows 2003 server for example, from within WinPE? I have tried and all i get is a "out of memory" error.... I have asked the same question @ the MS newsgroups deploy section, and the answer was NO!

I do this using unattend.txt, look in this thread for some files that I use to do this.

What I do, is format the C: drive. Xcopy the I386 folder down (goes to c:\nt\i386) then run the setup.