Topic: Multi-boot question

Hi,

I have a way to make multi-boot DVD, with different languages XP.

The structure is :

\  (root)
\XPEN     (some files, in particular setupldr.bin )
\XPCH     (some files, in particluar setupldr.bin)
\SETUP\XP\ENG ( the copy of the xp_eng.iso)
\SETUP\XP\CHT ( the copy of the xp_cht.iso )

I don't know how to make this DVD with driverpacks.
I have read the tutorial of Driverpacks Base, but it doesn't mention how to deal with multi-boot.

Could someone teach me ?? Thanks

Re: Multi-boot question

the multi boot platform is not well documented... but it does work give it a shot...

Hint: you need to save some DPs_BASE.ini files in advance

DPs_BASEen.ini
DPs_BASEch.ini

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

Re: Multi-boot question

16 januari
MSDN WITH RAID SUPPORT during TXTmode
first webblog article ever, here goes..

SLIPSTREAMED MSDN DVD with RAID support and other drivers integrated.

This post is about MSDN DVD versions (with the subscriber DVD's as source)

The intent was to make the DVD boot WITH RAID SUPPORT during TXTmode.

The DVD has a choice of FIVE operating systems. This is about the 32 bit versions.

XP; XP home sp2, XP pro sp2, Media Center Edition 2005  and SERVER; 2003 standard and enterprise.

I slimmed down the source.

For this DVD, The ISO files are not needed. (You can Zap them, or don't select these folders when you burn your compilation) .

For all XP versions; Migration tools folders were zapped. (or not selected.)

One needs only ONE support folder, so I moved the NTbackup folder one finds in Home into support, and called it HOME_NTbackup, then moved this support folder out of Home. I decided to keep one VALUEADD folder.
I now find support and valueadd folders in the folder where the three XP versions are in..

Another note, for MCE 2005, content of disc2 was moved to disc1. This was done because MCE setup asked for disc2 which interupted unattended.
note >>It was difficult to browse it to disc 2, so I changed that layout.
TIP, when you don't do that, and it asks for disc 2, just change the 1 to 2 in the line, that works easier than browse. smile

If you want unattended, put your WINNT.SIF files in the i386 folder.

Next came the real work.

1; N-Lite; Nlite out unused languages and keyboards in all five windows versions.

2; RVM; Slipstreamed Hotfixes and addons to MCE2005 and the XP versions. I did NOT DO server.

3; DPs_Base; Slipstream all driverpacks to each of the five versions. (method 2, select all button, KTD off, and QSC OFF.)

Then I moved one of the five OEM folder to ROOT of DVD (These folders have the same content, but after DPs_Base was used the setup process wants the OEM folder in ROOT.) I then deleted the other four unneeded copies of the OEM folders.

The tricky part was to get the textmode drivers work on all five.

Root of source has five small folders. They contain "textmode" content.

2ENL (enterprise 2003 dutch)

2SNL (standard 2003 dutch)

XHNL (home)

XMNL (MCE2005)

XPNL (pro)

COPY and OVERWRITE the most recently added/modified files from the respective i386 folders to their corresponding "textmode" folder.

Do not copy the driver.CAB.. This was done while sorted on date in detail view... (btw, RVM updated that file, not DPsBase.)

Then COPY and OVERWRITE the *.SY_ files from the i386 folders to the corresponding "textmode" folders. (sorted on TYPE in detail view) This is done so textmode will work.  Over a hundred additional mass storage devices get added to avoid F6 at boot.

4; prepare for burn.

Use isobuster to get the bootfiles off the source DVD.

Use nero to burn your compilation.

Use the bootfile from the MSDN DVD, no floppy emulation, sectors set to 4. Hex is 07C0.

No multisession, disc at once, finalise.. And burn.

Once you licked it, it sounds sooooo simple...

Last edited by Jaak (2008-06-27 08:37:24)

The answer was 42?
Kind regards, Jaak.

Re: Multi-boot question

hi
that is how I used to do this for my MSDN DVD..

I already had the bootfiles which offer me the choice of what I want to install, so this worked for me.
I hope I find the time to test the DriverPacks BASE multiboot function for real..
(Making the build offer you the choice sounds like the toughest part.)

The answer was 42?
Kind regards, Jaak.

Re: Multi-boot question

I have already slipstreamed each folder

\SETUP\XP\ENG ( the copy of the xp_eng.iso)
\SETUP\XP\CHT ( the copy of the xp_cht.iso )

by the setting = disk, method 1, Guirunonce, KTD disabled, enabled QSC

But it doesn't work.

I also put the $OEM$ folder on root, still doesn't work.

I also export the setting, and use multi-boot option, but doesn't work....

Re: Multi-boot question

OK, I make it.....

Re: Multi-boot question

how?

The answer was 42?
Kind regards, Jaak.

Re: Multi-boot question

Sorry didn't used Base multi solution.
I'm building single CD and multi boot from the same source files.
Multi boot requirements are builded temporarily.

I dislike OEM at root directory. How to support different driverpacks version?
I've \XP_INST_XHO2\OEM and \XP_INST_XPS2\OEM

Changed DP_Install_Tool.cmd part to support root OEM and non root OEM:

Color 9f

setlocal EnableExtensions

Echo.
rem support \OEM and \multi\OEM
Echo Searching home directory for the DriverPacks...
pushd "%~dp0.."
set CDDRIVE=%cd%
popd
SET last_char=%CDDRIVE:~-1%
IF "%last_char%"=="\" set CDDRIVE=%CDDRIVE:~0,-1%
IF exist %CDDRIVE%\$OEM$\$1\D echo goto M1Found
IF exist %CDDRIVE%\OEM\bin\un7zip.exe echo GoTo M2Found

M1: not  tested
M2: should work

Re: Multi-boot question

why would somone want to have more than one driverpack version supported cdob?

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

Re: Multi-boot question

@OverFlow
I'm aware of two reasons for different driverpack version:
it's nice for testing purposes
dosn't use 2000, XP and 2003 use different drivers sometimes?


And setup dosn't find $OEM$ at root at a multi boot solution.

http://flyakite.msfn.org/unattended.htm

Example:
D:\AIO-DVD\SETUP\XP\Professional\i386\
D:\AIO-DVD\SETUP\XP\Professional\$OEM$\

It would be nice, if DP_Install_Tool.cmd search OEM and $OEM$ the same manner, that's parallel to i386 folder.

Bad memory, I edited presetup.cmd too: sourcepath is read from $winnt$.inf.
Again tested at M2 solution only.