[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