TheTechGuide Forum
General Category => Software => Topic started by: tox on May 12, 2003, 10:47:40 AM
-
I have tried to construct a multi-boot disk with XP PRO and 2K PRO in it.
the directory structure looks like this:
/
iWXP (bootdisk of XP)
iW2K (bootdisk of 2K)
WXPPRO (contains the XP i386 directory) <-- this already works
W2KPRO (contains the 2K i386 directory) <-- this has the EULA error.
Win2k successfully boots from CD but upon selecting install, it prompts \"cannot find EULA\" then a reboot prompt for 15seconds.
I dont know if the CD I took this W2KPRO version is the MSDN version. It is bare, without the SP's slipstreamed yet. I'm trying if it'll work and will slipstream the SPs in it.
Any help will be appreciated.
-
I'll give you the how-to later, I need to leave to see a customer.
-
bump...
anyone?
-
From the original W2K CD, you may try copying the file used for the EULA, and reconstruct your dual boot CD.
Just a thought, that's what I would try.
-
what i changed in the W2KPRO directory is the file setupp.ini where i edited the PID=XXXXX270 (just changed the last 3 digits to 270 thats all). i did a fresh copy with the change i just mentioned. still nothing.
i saw the time stamp edit on the said file from another forum. i'll see if it does solve my dilemma.
-
the time stamp mod hasn't solved this problem. i'm trying this so that i could try slipstreamed unattended 2K installs later.
anyone? your thoughts?
-
it already has winnt.sif file in the i386 directory where it contains this line:
[unattended]
...
...
...
OemSkipEula=Yes
...
...
still it contains the error. does a slipstreamed version not contain this error? i would want to push through with the slipstream then try again.
-
well I can't remember the exact reason for this error but I made a 3 in 1 following the guide and it works no problems try perhaps making sure that you have the full retail version not a pre release or earlier beta
-
I Am having the same problem as Tox, just the other way around.
My 2K is fine but Xp sp1 is giving the EULA Error.
As far as I can tell the problem lies in the TXTSETUP.SIF file and its
position in the overall directory structure.
In other words it needs to be in the correct directory to be read by
the install routine.
Also check to see that you don't have a [color=\"red\"]txtsetup.si_[/color]
file in any of your directories.
If i figure it out I'll let you know...
Good Luck
Ralph
-
i got it!
copy the txtsetup.sif from the /i386 of the installation into the "four-letter" bootdisk. also, copy the file setupldr.bin into the "four-letter" bootdisk. edit txtsetup.sif so that the parameter "SourcePath" points to the correct directory. don't forget the trailing "\" at the end of the directory name.
after this the error will be gone.. tah dah..
/biggrin.gif\' class=\'bbc_emoticon\' alt=\':D\' />