@pain - do you feel like posting some of the modded CMD files for a multiboot? I'll see if I can incorporate it into a next version. I never messed with multiboots cd's. May as well make hfslip more universal.....
Well, I use the method described in this siteWindows 2000 Multiboot CD
After running the script I move the SOURCESS folder to the SETUP folder described in the method, rename the folder according to the version of the OS I'm slipstreaming (PRO, SERVER, ADVANCED <<I have not have tested ADVANCED>>) and modify the HFSL???.CMD files, just the line with the FOR statements
FOR %%i IN (D E F G H I J K L M N O P Q R S T U V W X Y Z) DO IF EXIST %%i:\I386\SVCPACK SET HFSLIP=%%i:\I386
...to this (this is the case when the sources W2k pro CD it's on this path)
FOR %%i IN (D E F G H I J K L M N O P Q R S T U V W X Y Z) DO IF EXIST %%i:\SETUP\PRO\I386\SVCPACK SET HFSLIP=%%i:\SETUP\PRO\I386
Like I said before is not big deal, just change the I386\HFSLIPWU.CMD
I understand that in the FOR statement you are searching in which drive the standard I386 folder or I386\SVCPACK folder are placed...
as a suggestion maybe you could read in an enviroment variable in the begining of the script if the user running the script want to place the sources on another path, maybe like the way you read the I HAVE READ THE INSTRUCTIONS statement, if he just press ENTER the standard path could be assumen, otherwise the ENVIROMENT variable would be used... just a suggestion of course...
the only thing in SVCPACK.INF file that need to be changed is the initial backslash in this line
Oh... and you copy the TXTSETUP.INF file to the BOOTDISK directory and change the
SetupSourcePath line from this
SetupSourcePath = "\"
SetupSourcePath = "\SETUP\PRO\"
and leave the original copy in the I386 folder without any change... just copy the file in the BOOTIMAGES folder
after that all work like a charm..
Edited by pnkiller78, 17 October 2005 - 10:18 AM.