Jump to content

Recommended Posts

Posted

I'm trying to make a bootcd with Windows XP SP2 Home and Pro on them, with unattended installs. I made and tested all the scripts and stuff, and made i menu with easyboot, but the unattended part doesn't work with the menu. Well, it only works partly. The installation is unattended, but the scripts that SHOULD run (they should, they have been tested thoroughly) after the first boot, dont get run when i boot using the menu. I tried running the w2ksec.bin from the root, and i tried using a boot sector i extracted from my original SP2 pro cd using IsoBuster, but they both give the same problem.

can anyone help me?

thank you in advance!


Posted

Are you currently MultiBooting? I mean do you have more than 1 OS on your CD and have EX Edited w2ksect.bin and setupldr.bin

OR

You only have a Custom Boot Menu and you are launching with w2ksect.bin directly without any modifications?

Posted

I made the two options in the menu already, but i havent yet put the files on the cd-rom, so only the Pro version is on the disk, in the root. (So not in a different directory or anything yet, just <cdrom>\i386 and stuff. and because i dont have special dir's, i havent edited the setupdlr or w2ksect)

Posted

So you have everything inside

%ProgramFiles%/EasyBoot/disk1 (root with I386, $OEM$, etc.)

Inside /disk1 you have w2ksect.bin and you are calling this file with the following command in EasyBoot:

run w2ksect.bin

If so, I don't see why it won't work.

What is your method for Burning or Generating the ISO?

Posted

Yes, thats the situation (except the I have everything in C:\disk1). I make the ISO using EasyBoot itself, cause then I can pick the loader.bin as bootsector, else I won't get the menu.

Posted

Ok then what do you mean by:

The installation is unattended, but the scripts that SHOULD run after the first boot

Do you mean by that at the first LOGON?

Give me more details for theses scripts, where they are located, from where they are launched, at wich step of the setup...

If you can get pass the TextMode setup (blue background) I don't think your problem has anything to do with the boot technique. Is is probably related to the Unattended Installation itself...

Posted

the whole installation runs unattended as specified in winnt.sif, but after the first boot a script called start.cmd is supposed to run which doesn't. it is located in the folder \$oem$\$1\install. it has always worked, until I added the bootmenu thingie. And it hasn't been changed either.

Posted

Oh my mistake, you're right, after the first time Welcome screen it should run, but it doesn't run AT ALL. And it did before I added the bootmenu.

Posted
[Data]
AutoPartition=0
MsDosInitiated="0"
UnattendedInstall="Yes"
AutomaticUpdates="Yes"

[Unattended]
UnattendMode=FullUnattended
OemSkipEula=Yes
OemPreinstall=Yes
UnattendSwitch="Yes"
TargetPath=\WINDOWS
FileSystem=*
WaitForReboot="No"

[GuiUnattended]
AdminPassword=*
EncryptedAdminPassword=NO
OEMSkipRegional=1
OemSkipWelcome=1
TimeZone=110

[UserData]
ProductKey=*****-*****-*****-*****-*****
FullName="Windows"
OrgName=""
ComputerName=WinXP

[Display]
BitsPerPel=32
Xresolution=800
YResolution=600

[TapiLocation]
CountryCode=31
AreaCode=0495

[Branding]
BrandIEUsingUnattended=Yes

[Identification]
JoinWorkgroup=Werkgroep

[Networking]
InstallDefaultComponents=Yes

[Components]
msnexplr=off

[Shell]
DefaultStartPanelOff = Yes

[GuiRunOnce]
%systemdrive%\install\start.cmd

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...