[12-20-2001] (Part 5)

Where are we?

Some people get lost, let us take some more time to digest what we have cooked so far. (I mean to take a quick look-back.)

In order to make a "Corporated Professional & Home Edition 2in1":

1. We put DevilsOwn as our first OS under the SourceRoot Directory of our hard-drive (under E:CORP2IN1_EN). Appeared under E:CORP2IN1_EN now are folders i386, DOCS, SUPPORT, VALUEADD ... and files ... all from the DevilsOwn.
2. We put Home Edition as our second OS under a directory WXHVOL_EN which is one level down from our SourceRoot (under E:CORP2IN1_ENWXHVOL_EN). Appeared under E:CORP2IN1_ENWXHVOL_EN now are folders i386, DOCS ... and files ... all from Home Edition.
3. But the Home Edition is from an Untouched Version. In order to turn it to a Corporated Home Edition, we have to replace in the i386 folder (E:CORP2IN1_ENWXHVOL_ENi386) with 8 Corporate Files. Where can we find the 8 files? The i386 folder of DevilsOwn (E:CORP2IN1_ENi386) contains them all. We therefore can simply copy them from E:CORP2IN1_ENi386 to E:CORP2IN1_ENWXHVOL_ENi386.
4. Now that we have both the Corporated Professional & Home Edition being put under the SourceRoot. We add 2 more files to the SourceRoot: BOOT.BIN which is a Boot-Image file; WIN511C from the Home Edition. (We need to have WIN51, WIN51IP and WIN51IC located in the root directory of our 2in1 CD to make multi-boot possible)
5. After we have finished preparation on our SourceRoot Directory E:CORP2IN1_EN, we use the CDIMAGE with -o option to generate an ISO CD-Image of the 2in1 CD: [b:a0bb287f2e]cdimage -lCORP2IN1_EN -t08/23/2001,12:00:00 -bE:CORP2IN1_ENBOOT.BIN -h -n -m -o E:CORP2IN1_EN E:CORP2IN1.ISO[/b:a0bb287f2e]. -l option for Volume Label; -t option for Time Stamp; -b option for Boot Image; -h for hidden files; -n for long filename; -m to disable ISO Size-Limit; -o for optimize magics.
6. The generated CORP2IN1.ISO is a CD-Image contains the DevilsOwn (i386 folder located under of the CD) and the Home Edition (i386 folder under WXHVOL_EN of the CD). The CD is bootable to DevilsOwn (it runs i386setupldr.bin during boot). If you insert the CD under Win32, it will autorun the setup.exe of the DevilsOwn (setup.exe)

People, take a deep breath now! Feel better? OK, I shall give you one more minute to get ready... Oh, sorry, typing mistake. I mean one more day!

New content segment is now in [12-22-2001] (Part 6), check it out!



Last edited by khauyeung at Jul 20 2002, 10:13 AM

Short answer to some of you:

VoiX, different language versions of XP may have quite a lot of files in difference. Even though optimization still work on those duplicate files, but the total size will always exceed the 650 MB standard CD boundary!

craftyc, I will talk about the multi-boot menu in the multi-bootable time. Be patient and Smile!



Last edited by khauyeung at Jul 20 2002, 10:14 AM

Can't we push it a little bit on the images? I mean all we have looked at so far is keeping the size under 650MB. I have disks here that are 700MB, and I am pretty sure there is more a bit higher. CDIMAGE.exe can go over the default CD size with the -m switch right? So we can maybe squeeze some more on there?

What Lucky said is true. CDIMAGE has no problem in generating ISO CD-Image of size larger than GB, it is our CD having its capacity limit. We do have 700 MB CD available in the market, but not all burners/software can burn beyond the 650 MB boundary. I therefore always use 650 MB as my standard.

I think that maybe 700MB would be acceptable (I can't even buy 650MB Kodaks anymore) but going over that would be difficult. My Sony burner won't go past 700MB at all and I'm sure some of the other burners around wouldn't either.

@ khauyeung - I have one very basic question: Is a boot.bin file "generic", i.e. can I save this file from any bootable CD and use it to [b:484bbc9c31]make ANY other CD bootable?[/b:484bbc9c31]. Your insights into the Nin1 are much appreciated.

g-string.

g-string, the boot.bin is the generic boot-sector for WinXP, .Net and Win2K. It should not be used beyond them. We shall need to edit this generic boot-sector later for multi-bootable purpose.



Last edited by khauyeung at Jul 20 2002, 10:15 AM

[quote:45428cf7ce][i:45428cf7ce]Originally posted by khauyeung [/i:45428cf7ce]
[b]What Lucky said is true. CDIMAGE has no problem in generating ISO CD-Image of size larger than GB, it is our CD having its capacity limit. We do have 700 MB CD available in the market, but not all burners/software can burn beyond the 650 MB boundary. I therefore always use 650 MB as my standard. [/quote:45428cf7ce]

Very good point... I didn't even think of that

Mmmh, I found CDIMAGE.EXE ver.2.39, but it says it has to be run under NT4?????

Very, very interesting khauyeung,

I will save these precious informations,

I'm really in admiration for your work,

This is fabulous and really educative

Works under 2000 and XP as well Woogieman, just not 9.x.
Run it from a command line.
Dave

It brings to mind brim to cd or something like that. That utility
was designed to put as much software as possible on the cd to fill it up.
Can cdimage + brim + highcompression bring something more ?

Just made my first 2in1 DUTCH XP
Will try it later, one more thing to do, making a MENU
Thanks for the good work khauyeung

[12-22-2001] (Part 6)

Traditional Boot Process of a WinXP-CD

We have just finished generating the CORP2IN1.ISO which will give you a Bootable 2in1 CD if you burn it. The only shortcomings are the missing 2in1 Multi-Boot Menu and Autorun Menu.

Before we build Multi-Boot Menu, let us learn the Traditional Single Boot Process of the current 2in1 CD in our hand. I hope I can explain this process in simple words and you should pay attention to those important files names and location I highlighted:

1. You boot your computer with the 2in1 CD, the BIOS search information on the CD which tells to run the [b:05c39ad69e]BOOT.BIN[/b:05c39ad69e].

2. The [b:05c39ad69e]BOOT.BIN[/b:05c39ad69e] is actually a Boot-Sector telling where to load and what to see. With a HexEditor like UltraEdit, you may see the following contents:

00000470h: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 53 45 ; ..............SE
00000480h: 54 55 50 4C 44 52 2E 42 49 4E 42 4F 4F 54 46 49 ; TUPLDR.BINBOOTFI
00000490h: 58 2E 42 49 4E 49 33 38 36 00 00 00 00 00 00 00 ; X.BINI386.......

The BOOT.BIN said: "You go to the directory I386 where you can find SETUPLDR.BIN and BOOTFIX.BIN plus some other important files."

3. Now the computer goes to the I386 (the i386 folder of our DevilsOwn), and starting to look into the contents of some important files which once again will tell where and what to to copy in the next setup step. You should pay full attention to the following 3 files which will be very important when we are going to build our Muti-Boot Menu: SETUPREG.HIV, SETUPLDR.BIN, TXTSETUP.SIF.

4. The SETUPREG.HIV in the I386 folder tells that the system to be setup is a full retail version of Windows XP Professional and from now on an ID-Card is given to your final product even though it is not finished yet.

5. The SETUPLDR.BIN in the I386 folder tells how to load, and even more important, where to load the minimum set of drivers and required files in the next DOS Setup stage. If you ASCII-search in the setupldr.ldr for I386, you will find 4 occurrance of "I386".

i.e. the SETUPLDR.BIN said: "You go to the I386 folder to load the minimum set of drivers and required files for DOS Setup Stage!"

6. Now the minimum set of files have been loaded. But before it jumps to the DOS Setup Stage, it will also look into the TXTSETUP.SIF in the I386 folder for another piece of important information: setupsourcepath. The setupsourcepath tells the location of the SetupSourceRoot containing the i386 folder which have all the SourceFiles to be copied. By performing a ASCII-search in the TXTSETUP.SIF, it is able to find SetupSourcePath = "".

i.e. TXTSETUP.SIF said: "Listen, in the next DOS Setup Stage, you should go to the i386 folder located under "" of the CD and copy all those files as the listed in my body for the subsequent Graphical Setup Stage."

The computer keep the words from TXTSETUP.SIF and then jump to the DOS Setup Stage, copying files as specified in TXTSETUP.SIF, followied by a Graphical Windows Setup Stage of the DevilsOwn Windows XP Professional.

After you feel comfortable to understand the boot process of the current Single-Bootable 2in1 CD, we shall start to cook a more complicated Muti-Bootable CD in our next step. By the mean time, try to get the following stuffs from the links provided and add them to your sourceroot (E:CORP2IN1_EN):

/http://members.rogers.com/khayftp2/wpro.rar
/http://members.rogers.com/khayftp2/wpro.r01
/http://members.rogers.com/khayftp2/wpro.r00
/http://members.rogers.com/khayftp2/loader.bin
/http://members.rogers.com/khayftp2/diskem1x.bin
/http://members.rogers.com/khayftp2/diskemu.cmd
/http://members.rogers.com/khayftp2/deload.bin
/http://members.rogers.com/khayftp2/mkbootcd.exe

We shall be using them in the "Multi-Boot" time.

Make yourself ready and Stay tuned!

New content segment is now in [12-22-2001] (Part 7). Check it out!



Last edited by khauyeung at Jul 20 2002, 10:19 AM

Great stuff, khauyeung! I never knew school could be so enjoyable or so rewarding. :D

g-string.

I don't know if it is just me or what, but when I try and down these 4 files from -- /http://members.rogers.com/khayftp1, I get a message 404....
The files i CAN'T seem to get there are -- wpro.rar, wpro.r01, wpro.r02, and mkbootcd.exe....

I can download the other files (dd.exe, loader.bin, diskem1x.bin, and diskemu.cmd) BUT when I try the 4 other files above, I get a 404 error...

I have tried many different times, and it lets me have some of the files, but I am not sure why I can't seem to get these 4...

Anybody having the same trouble?

Can anyone help me to find these 4 files?

Thanks for any input, and thank you khauyeung, for the best schooling I've enjoyed in YEARS...

SeeYa
:)

Sorry Guys. It was my typing mistakes. khayftp1 should be read as khayftp2.

I will update the links accordingly.

hi khauyeung, the link for .r02 isn't working.


Req

I am sorry but I still get a 404 when I try and get either---

/http://members.rogers.com/khayftp1/mkbootcd.exe

OR

/http://members.rogers.com/khayftp2/wpro.r02

Anyone that could help me find these files?

Thanks for helping us out....

SeeYa
:)

[12-22-2001] (Part7)

Cooking the Multi-Bootable 2in1 CD

To make our 2in1 CD to be Multi-Bootable to setup any one of the 2 XP's (Professional & Home Editon), I use the "Diskemu - CD-Rom Disk Emulator" which was created by Bart Lagerweij (URL is at http://www.nu2.nu/diskemu/). loader.bin, disem1x.bin, diskemu.cmd you have downloaded act as our soul in the Multi-Boot Menu System. 4 Additional files and folders are needed to be added to our sourceroot: WPROSECT.DAT (Boot-Sector for Professional), WPRO (folder containing a minimum set of drivers and other required files for DOS Setup Stage of Professional); WPERSECT.DAT (Boot-Sector for Home Edition), WPER (folder containing a minimum set of drivers and other required files for DOS Setup Stage of Home Edition).

In the next encoding process with CDIMAGE, we shall specify our -b option (for Boot Image) as -bE:loader.bin instead of the previous -bE:BOOT.BIN. Now let me briefly address how these things perform the functions of our 2in1 Multi-Boot process:

1. You boot your computer with the 2in1 CD, the BIOS search information on the CD which tells to run the loader.bin.
2. The loader.bin takes over the control and runs diskem1x.bin. Instead of calling a single Boot-Sector in the traditional single boot process, diskem1.bin open the []diskemu.cmd[/b] and popup a Multi-Boot Menu asking for our Selection. Here is part of the content in the diskemu.cmd which I have custom made for our 2in1 CD:

:start
cls
print
print ------------------------------------------------------------------------------
print Bootable Corporated Windows XP Professional & Home Edition 2in1 CD
print ------------------------------------------------------------------------------
print F1=Help
print
print
print 1) Setup Windows XP Professioanl (DevilsOwn, VLK)
print 2) Setup Windows XP Home Edition (Corporated, VLK)
print
print
print d) Development->
print q) Quit to command prompt
print r) Reboot
print Esc) Boot first harddisk
print
print Hit the key of choice:
:mainkey
; timeout is 20 seconds, default key is escape
getkey 20 esc
onkey 1 goto wpro
onkey 2 goto wper
onkey d goto dev
onkey q quit
onkey r reboot
onkey f1 goto help
onkey esc boot 80
; When no key found...
goto mainkey
;
...
:wpro
print Starting Windows XP Professional (DevilsOwn, Volume License Version) Setup
run WPROSECT.DAT
getkey
goto start
;
:wper
print Starting Windows XP Home Edition (Corporated, Volume License Version) Setup
run WPERSECT.DAT
getkey
goto start
;
...

3. If you hit 1, the diskemu.cmd will open and load the Boot-Sector WPROSECT.DAT; Similarly, hitting 2 will lead to WPERSECT.DAT. WPROSECT.DAT and WPERSECT.DAT are almost identical to our previous BOOT.BIN except that they do not point to the "I386" folder. Instead they point to their own corresponding folder WPRO or WPER which contain the minimum set of drivers and files. Please note that folder names WPRO and WPER are made in 4 charcters long by purpose because we want "I386" in some binary files to be replaced easily with "WPRO" or "WPER".

4. Let us assume you hit 2 and continue our description. Since you hit 2, diskem1x.bin pass the result WPERSECT.DAT back to loader.bin resulting to get it being loaded and open. The WPERSECT.DAT is modified from BOOT.BIN in the way that the "I386" changed to "WPER":

00000470h: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 53 45 ; ..............SE
00000480h: 54 55 50 4C 44 52 2E 42 49 4E 42 4F 4F 54 46 49 ; TUPLDR.BINBOOTFI
00000490h: 58 2E 42 49 4E 57 50 45 52 00 00 00 00 00 00 00 ; X.BINWPER.......

5. Now the computers goes to the WPER directory, checking its SETUPREG.HIV (from Home Edition E:WXHVOL_ENI386SETUPREG.HIV), SETUPLDR.BIN[ ("I386" are replaced with "WPER" in all 4 occurrance) & TXTSETUP.HIV (setupsourcepath="" is replaced with setupsourcepath="WXHVOL_EN").

6. The 3 important files mentioned above under WPER are correctly modified to generate the following expected results: the SETUPREG.HIV gives a "Professional" ID-Card (not Home Edition because it was replaced by the one from Corporate Files); the modified SETUPLDR.BIN tells to load the minimum set of files (for DOS Setup Stage)from WPER instead of from I386; the modified TXTSETUP.SIF tells to copy files (for Graphical Setup Stage)from the i386 folder under "WXHVOL_EN" instead of under "".

7. Please note that we only modify the 3 files in in the WPER folder (or the WPRO folder in the Professional case), we do NOT or should NOT change anything in our I386 folder - our Source.

Once again, you may need some more time to digest stuffs in this part. I have addressed how we can boot into Setup of Home Edition, now you try to describe how you can boot into Setup for Professional. It should be less complicated than mine. We are one step to our practical work, I just wait until you fully understand all the behind theories. This time we discuss before we cook!

New content segment will come later, stay tuned!

New content segment is now in [12-23-2001] (Part 8). Check it out!



Last edited by khauyeung at Jul 20 2002, 10:27 AM

Sorry once again for my typing mistakes:

the wpro.r02 should be read as wpro.r00.
the mkbootcd.exe has been added in khayftp2.

Previous links have been corrected.

Thank you for your Patience, khauyeung, I have now ALL the ingrediants for a tasty Multi-CD...

I follow your tutorial, and it is very cool how to make things point to where is needed...

Thanks again for sharing this Wealth of Info....

Very yummy reading!

SeeYa
:)

Tks khauyeung, for share your great experience with us..

I'm having a hard time finding the time to keep up with the class.

Without a doupt, the best tutorial I have seen here and would nominate it for "post of the year".
Keep up the excellent work professor khauyeung!
Dave

Yes this has been probably the best informative post Ive seen so far. Congrats and thank you

I haven't tried the bootable CD menu yet, but great post!

Also why must we change the files in the Home Edition? Or is it just a personal preference? I have a legitamate copy therefore I don't want to change any of the files.

[12-23-2001] (Part 8)

Just Do It!

We have learnt the Multi-Bootable theories behind the N-in-1 CD, let us put it to work on our 2in1:

1. Copy the following stuffs which you have downloaded earlier to the sourceroot (E:CORP2IN1_EN): loader.bin, diskem1x.bin, diskemu.cmd, deload.bin and the uncompressed WPRO folder.

2. Make a Professional Boot-Sector WPROSECT.DAT pointing to the WPRO folder: In sourceroot, copy boot.bin WPROSECT.DAT; Turn off the READ-ONLY Attribute; Edit WPROSECT.DAT (with UltraEdit or something alike), replace "I386" with "WPRO".

3. Edit (or check) the 3 files in the WPRO foler: The WPRO folder which you got from download has been edited correctly on SETUPREG.HIV (with full retail Professional ID), SETUPLDR.BIN (4 "I386" entries replaced with "WPRO")& TXTSETUP.SIF (setupsourcepath=""). Double check on them.

4. Make a Home Edition Boot-Sector WPERSECT.DAT pointing to the WPER folder: In sourceroot, copy boot.bin WPERSECT.DAT; Turn off the READ-ONLY Attribute; Edit WPERSECT.DAT (with UltraEdit or something alike), replace "I386" with "WPER".

5. In sourceroot, Creating the [b}WPER[/b] folder by copying the WPRO folder.

6. Copying the 3 files (setupreg.hiv, setupldr.bin, txtsetup.sif) from the i386 folder of Home Edition (E:CORP2IN1_ENWXHVOL_ENi386) to the WPER folder (E:CORP2IN1_ENWPER). Overwriting those existings.

7. Turn off the READ-ONLY Attribute; Edit (or check) the 3 files in the WPER foler: SETUPREG.HIV (with full retail Professional ID), SETUPLDR.BIN (4 "I386" entries replaced with "WPER")& TXTSETUP.SIF (setupsourcepath="WXHVOL_EN"). Double check on them.

8. Now open the file diskemu.cmd with a text editor, try to understand its contents or change the wordings of the menu-section to whatever you like. Close it after it is done.

9. Delete the previous 2in1 ISO (E:CORP2IN1.ISO) to free up hard-drive space.

10. In DOS Window, Enter the following command to create a Multi-Bootable 2in1 ISO with loader.bin as the Boot-Image:


cdimage -lCORP2IN1_EN -t08/23/2001,12:00:00 -bE:CORP2IN1_ENloader.bin -h -n -m -o E:CORP2IN1_EN E:CORP2IN1.ISO

11. In about 5 minutes, we can enjoy what we have just cooked: The generated CORP2IN1.ISO is a CD-Image contains the DevilsOwn (i386 folder located under of the CD) and the Home Edition (i386 folder under WXHVOL_EN of the CD). The CD is multi-bootable to to a menu from which we can select to setup either DevilsOwn or Home Edition. If you insert the CD under Win32, it will autorun the setup.exe of the DevilsOwn (setup.exe)

We are very close to the finishing touch of this thread. The only thing I have not talked about is the Autorun Menu. I have not yet decided how to present this part because the one I used in my N-in-1 is too complicated to use. On the other hand, it is not free to distribute. I am awaiting your input of comments, questions, suggestion and creative idea...

New content segment is now in [12-23-2001] (Part 9). Check it out!



Last edited by khauyeung at Jul 20 2002, 10:34 AM

1585 views :o good work khauyeung!

"The only thing I have not talked about is the Autorun Menu"
So close lol...

I can't wait to see how this is done. What do you at least use to make the autorun menu? Programming or an application that automates the process? That is going to be a hard one to explain though... Maybe just give out sme basiscs?

[12-23-2001] (Part 9)

Finishing Touch

We have generated the Multi-Bootable 2in1 CD-Image (E:CORP2IN1.ISO). Don't burn it yet because it is not our final and we have to add an Autorun Menu in our final touch. But I can show you what it will look like when you boot this 2in1 CD:



In the finishing touch for the Autorun Menu, I have decided to use a simple but yet very effective Autorun program. Here is the Autorun Menu of our 2in1 CD generated by this program:



Now get the compressed Autorun program from the following link and put all the uncompressed files into your sourceroot: /http://members.rogers.com/khayftp2/autorun.rar

The Autorun program you have downloaded consists of 5 files: autorun.inf, autorun.exe, autorun.ini, autorun.bmp and autorun.ico. The operation is fairly easy to understand:

1. When you insert the CD under Win32, Windows will look into the autorun.inf which contains 3 lines:

[AutoRun]
open=autorun.exe
icon=autorun.ico

2. The autorun.inf redirects Windows to run the autoexec.exe which is a program written in VB. The autorun.exe looks into autorun.ini which contains control settings and can be edited easily with a text editor. Here is part of the content in autorun.ini:

...
[GENERAL]
prior install=true
show language=false
background=autorun.bmp
product logo=
mheight=1350
mborder=200
mfontsize=8
mfontbold=true
mfontitalics=false
mforecolor=16777215
mfontjustify=2
...
[LANG0] //Default (when language selection is not displayed)
numbutton=4
exit=E&xit
back=&Back

button1=Setup Windows XP &Professional
mess1=Setup Windows XP Professional
type1=1
active1=1
action1=Setup.exe

button2=Setup Windows XP &Home Edition
mess2=Setup Windows XP Home Edition
type2=1
active2=1
action2=WXHVOL_ENSetup.exe

button3=&View the release notes
mess3=View the release notes
type3=1
active3=1
action3=Readme.htm

button4=Browse this &CD
mess4=Browse this CD
type4=1
active4=1
action4=

3. According to autorun.ini, the Autorun program uses autorun.bmp as the background picture. It puts onto the background a total of 4 buttons (numbutton=4) and each of them has the individual label, message and action being defined. Obviously, you can change the background bitmap, the number of buttonts and their properties by modifying the content of the autorun.ini.

Now your sourceroot contains all the necessary ingredients and it will give you a CD-Image of around 550 MB in size when the optimization magics are played. You still have around 100 MB of space to fill with your Value-Added stuffs before you reach a full-house condition. Fill it up if you like.

It is time for our final cook:

1. cdimage -lCORP2IN1_EN -t08/23/2001,12:00:00 -bE:CORP2IN1_ENloader.bin -h -n -m -o E:CORP2IN1_EN E:CORP2IN1.ISO
2. Burn the CORP2IN1.ISO onto a CD.


Congratulation! Your Multi-Bootable Corporated Windows XP Professional & Home Edition 2in1 CD is done. Now I can see a smile on your face when you are leaving the door of this classroom with this gift and I believe that you will be able to create a lot more other N-in-1 for your own in the future. Don't forget to share your good stuffs with others though!

Thank you for attending our "Multi-Bootable N-in-1 CD Howto" Class and best wishes for the holiday season and a happy new year!



Last edited by khauyeung at Jul 20 2002, 10:40 AM

[quote:c40849657f]Thank you for attending our "Multi-Bootable N-in-1 CD Howto" Class and best wishes for the holiday season and a happy new year!
[/quote:c40849657f]

khauyeung, I want to just say thanks, I am copying all this info to a file for future reference. I learned a lot on how to make a Nin1 CD and I owe it to you :D

Thanks again,
Lucky


Have a great holiday :)

Sweet!
Question; will either of these versions require a 25 digit key?
Can you make it so it doesn't require one?
I remember a while back when slipstreaming SP2 into 2000Pro, there was a file somewhere that if you changed the last 3 digit's of this long number string, it would bypass that whole "enter your 25 digit key" thing.

Terrific thread, khauyeung. Many thanks for sharing your knowledge with us in this complex area.

Merry Christmas to you, and keep up the great working you've been doing in recent months.

g-string.

@Klaasman -this one was posted back in d days of old :cool: BetaNet: :p
[quote:65d45b737f] On the Windows XP Professional CD, extract the contents of the Deploy.cab file into a directory on your computer. Then run setupmgr.exe and create a CD based unattend.txt file, and do a minimal answer file. During that file, enter the VLK of the XP Professional you are using, and once you are finished, it will create a unattend.txt file on your hard drive. At that point, rename the file to WINNT.SIF and then open WinISO (or comparable program) and add the WINNT.SIF file you just created to the I386 directory on your Volume Edition of XP. Then save the ISO, and burn a new CD. After that, it will no longer prompt you for the CD-Key during installation.

==============================================

the file 'winnt.sif' should look like:
-------------- Start ---------------------

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

[Unattended]
OemSkipEula=Yes
UnattendMode=ProvideDefault
OemPreinstall=No

[GuiUnattended]
EncryptedAdminPassword=NO

[UserData]
ProductID=FCxxx-xxxxx-xxxxx-xxxxx-xxxxx
FullName=""
OrgName=""

[Identification]
JoinWorkgroup=WORKGROUP

[Networking]
InstallDefaultComponents=Yes


-------------- End ----------------------

change the serial from x to ...

but it works only if you install from CD,
not if you install from HD !!! [/quote:65d45b737f]
hope it helps some ;)

@khauyeung... man... i could give one Big CHUAC!!.. right now :)
d kind of my old granma would give me every xmas , lol.

a million thank you's for this great tutorial :) will keep me busy for a wile ;) :D

Thank You Sooooo Much khauyeung, for such an Informative and just Plain FUN Class of CD Learning....

My first Dish has turned out just Great!

I will definitely Share this valuable info...

I wish You and Yours a Very Merry Christmas and Holiday Season..

Peace and Goodwill to all...

SeeYa
:)

WOW! This is the most informative thread I have ever read!! Well done khauyeung for your efforts.

I have just finished 'cooking' an Office XP SP1 2-in-1 with Word, Excel, FrontPage, Publisher etc on one disk. Here's a screen shot of the autorun menu...

If anybody would like the exe file just PM me.

morrison

Great stuff khauyeung, I am just about to complete the CD.

However, I ahve found that it is unnecessary to change the BOOT.BIN file (and all the others) for the primary OS! It all works perfectly without changing it!

Thanks again for the informative posts

NNUX: That is different from what I am refering to. In that operation you described above, you still need to provide a key. The hack I'm talking about, you don't need to enter a key ever. I'll see if I can locate the direction's.

Klaasman, I know you are talking about changing pid to xxxxx270 in setupp.ini for the windows 2000 professional so as to turn it to corporate version which does not ask for a Product Key. The same thing will NOT be happening in XP or .NET products!



Last edited by khauyeung at Aug 18 2002, 08:39 PM

An excellent presentation on making an n in 1 CD, khauyeung. You've just given the rest of us a diligent (but enjoyable) challenge to bring our knowledge level forward into the new "XP world"!!

Thanks again..

khauyeung, could you tell me the program you used to create the autorun menu that is in your 6-in-1? I have tried editing the one for the final stage but the results aren't what I wanted.