11 replies to this topic

[Brito]

Hi everyone!

After following the discussions here: http://www.boot-land...-USB-t2428.html

I went to try installing XP from a PE environment with LiveXP.

Placed the whole content of the install CD on a separate folder - in this case - X:\INSTALL and tried running setup.exe from this location - and it will just hang.

Then I've tried using XPsetupLauncher to take advantage of winnt32.exe with unattended install and still no good result since it will still complain about a missing help file.

Been searching on 911 and found some more switches on WINNT32.EXE - but I'm a bit confused on the reason why it won't allow to continue and would like to see this possible.

A tutorial showing how to install XP from PE environments or some pratical methods would surely be welcome..

I'm also preparing a new set of scripts to help replicate my results.

Thanks!!

[was_jaclaz]

Well, happy that
after a few months someone is getting to the challenge:
http://www.boot-land...p?showtopic=644

What I would try first thing would be to leave the folder name \I386.

Then try with \I386\winnt32.exe /noreboot /makelocalsource

Also check this:
http://www.msfn.org/...topic=77526&hl=

jaclaz

P.S.:
By the way, method #4) has been in the meantime finalized and it's almost perfect, in a matter of a couple of weeks there will be a "final" tutorial, this should be the "latest" one:
http://www.msfn.org/...o...1384&st=199

[carfan]

Well, happy that
after a few months someone is getting to the challenge:
http://www.boot-land...p?showtopic=644

What I would try first thing would be to leave the folder name \I386.

Then try with \I386\winnt32.exe /noreboot /makelocalsource

Also check this:
http://www.msfn.org/...topic=77526&hl=

jaclaz

P.S.:
By the way, method #4) has been in the meantime finalized and it's almost perfect, in a matter of a couple of weeks there will be a "final" tutorial, this should be the "latest" one:
http://www.msfn.org/...o...1384&st=199

i have made a script for xpsetuplauncer from the bartpe world. i have used it to install xp on several machines (unattended style). anyone interested - let me know. it requires to be able to point to the i386 folder from the xp setup disk. however - it can be copied to the local hard drive for the source files or read from a cd drive.

[TheHive]

Can you attach your script. It would help very much.

[Brito]

Well, happy that
after a few months someone is getting to the challenge:
http://www.boot-land...p?showtopic=644

What I would try first thing would be to leave the folder name \I386.

Then try with \I386\winnt32.exe /noreboot /makelocalsource

Also check this:
http://www.msfn.org/...topic=77526&hl=

jaclaz

I hadn't forgoten - but wb has only reached a good state for developing these sort of projects with version 072 which made things quite easy to get going.

Now it's only missing to boot in unattended mode - which is still failing, thanks for the links will study them and try out.

This should be fun..

P.S.:
By the way, method #4) has been in the meantime finalized and it's almost perfect, in a matter of a couple of weeks there will be a "final" tutorial, this should be the "latest" one:
http://www.msfn.org/...o...1384&st=199

Thanks!!

i have made a script for xpsetuplauncer from the bartpe world. i have used it to install xp on several machines (unattended style). anyone interested - let me know. it requires to be able to point to the i386 folder from the xp setup disk. however - it can be copied to the local hard drive for the source files or read from a cd drive.

A script has already been done to support xpsetuplauncer under the liveXP project - but it's failing and I don't know yet the reason why - I feed it with an answer file with the correct settings, but will keep trying with command line winnt32.exe until it works right..

[Brito]

...
What I would try first thing would be to leave the folder name \I386.

Then try with \I386\winnt32.exe /noreboot /makelocalsource
...

What do you mean with "leave the folder name \I386"?

I use a folder called INSTALL and these are the subfolders and files inside:

[cmpnents]
SETUP.EXE
[VALUEADD]
[DOCS]
[OEM]
[boot.images]
[SUPPORT]
[I386]
setupxp.htm
WIN51
AUTORUN.INF
spnotes.htm
WIN51IP
LEIAME.HTM
win51ip.SP1
BOOTFONT.BIN
win51ip.SP2

Will upload this project soon for testings..

[was_jaclaz]

I meant "start from the basics".

All is needed to install XP from WINNT32.EXE is in the \I386 directory, put it in the root of some drive or CD.

Don't try UNATTENDED until you are sure that "normal" ATTENDED works.

jaclaz

[Brito]

Yes, thanks for clearing this doubt - I am trying to do a "normal" install - and even using the provided switches it is still complaining that there are no partitions available to continue install..

Will keep trying!

[carfan]

Can you attach your script. It would help very much.

i'm at work now. i'll try to post tonite when i get home. i'll try to include a brief "how to".


bruno:

i'm not really sure about some of your rules. as far as i know xpsetuplauncer is free to anyone to use. should i encode into the script or do you want me to show a link to the download source??? i can do either way.

[Brito]

Edborg already uploaded it as a script some time ago: http://edborg.boot-l...Launcher.script

You are welcome to create a new topic on the tutorials sections explaining how to use it and include your script.

Also recommend placing the binary (with sources if possible) inside the download section to make it more visible: http://www.boot-land...p;showdlforum=6

It's still empty at this moment, so it would be nice to see it there..

[thunn]

Don't try UNATTENDED until you are sure that "normal" ATTENDED works.

jaclaz

Sorry jaclaz, but I disagree, assuming the user understands a little about the unattended file.

Use an unattend.txt or winnt.sif file and you stand a better chance of successfully finishing the setup.
The file contains settings that may help bypass problem areas of a windows setup, some are not even documented. It rarely causes a problem if configured correctly and you may set it to display the setup dialogues if needed.

I obsessed over this very subject for some time after discovering how difficult it really was to complete a windows setup from pe. In the end I did get it to work, but also came to the following concusions..

a.) The XP and/or Win2003 OPK (OEM Preinstallation Kit) is actually a good tool for this task.
b.) A simple batch file worked best in the end.
c.) It adds an extra phase to the setup vs. running the stock setup configuration, BUT, allows for a completely hands off setup if a disk partitioning script is made.

I don't mind hitting [enter] twice to format the setup partition, so I didn't keep the scripts on my setup discs.

I'll be back to check on the changes here though!

[was_jaclaz]

Yep, all the problems lie in these:

Use an unattend.txt or winnt.sif file and you stand a better chance of successfully finishing the setup.

It rarely causes a problem if configured correctly and you may set it to display the setup dialogues if needed.

A simple batch file worked best in the end.

(bolding is mine)

EXACTLY my opinion.

I found that to find the "correct configuration" and to write the "simple" batch files, one has to do quite a few experiments with "attended" mode.

I don't mind hitting [enter] twice to format the setup partition, so I didn't keep the scripts on my setup discs.

but then it won't be really UNATTENDED anymore.

I personally find that all the hype about "FULL UNATTENDED" is just that, if you sum the amount of time spent to find the right settings to the time testing them and all the other time taken until you have your "perfect" solution and then divide it by the number of actual installs you make, the result will very often be a larger number of minutes of your time as compared to the time a normal install will take (which you could have used reading a book).
As I see it the best compromise is a "SEMI ATTENDED" solution where one makes automatic just the easiest and more "boring" things, but keeps control on the important steps of Setup.

Of course unless you continuously re-install, I tend to never or very rarely re-install a system, I prefer to fix it, in the rare occasions when something goes wrong.

And if you have to setup a number of new machines, I find doing a sysprep and cloning to be faster and easier, as usually half of the things in the "perfect CD" you managed to assemble need to be updated, because of changes in either the software or in the new hardware...

jaclaz