[andregcasal]

Hi all
I want to let you guys know that I'm working on 2 projects right now, a XP CD and this Multi Boot DVD Guide. The XP CD will help me test some features I want to add to this guide, but I'm not sure if they work, so... testing is needed.
The main goal is to make this an ultimate guide, covering the best methods, tools, and automations.
I'm a fan of simplicity so I'll try to make the guide so making DVDs is as simple and fast as possible.
My future updates will be: nLite, PowerPacker, XPize, WPI (and maybe others), Drivers (BTS's or not), and a FAQ. Hope you guys like it

Anything, just ask

[dunkie12]

Quote

Hello dunkie12
The problem is very simple... You have DetachedProgram="cmd.exe /c @ECHO something>%SystemDrive%\DTPR.TAG" instead of DetachedProgram="%SystemRoot%\System32\cmd.exe /c @ECHO something>%SystemDrive%\XPPRO.TAG". Hope it helps

Yup, I realise that - I should have mentioned in my original post, that I had the full path in that you described (IE %SystemRoot%\System32\cmd.exe) however it didn't work that way either - so I changed it to what I have there.
Does it make any difference what the .TAG file is called? I need four of these files in Total, which is why I went for the naming convention that I had...
It's kinda got me stumped, as I pretty much followed your instructions step by step.

This post has been edited by dunkie12: 17 January 2007 - 09:06 PM

[dunkie12]

Update:
I've managed to get around some of the missing software by installing the common applications with the RunonceEx method. I still can't get the method described in this thread to work however. I can see the batch scripts executing at the correct stages of setup, but it's still not creating the .tag file as required. I'm now sure that the rest of the setup will work as intended if the .tag file appears.

This post has been edited by dunkie12: 18 January 2007 - 12:00 AM

[andregcasal]

Hi
Hum... It didn't worked? Maybe you deleted cmd.exe with nLite...
Try again, but in the "remove components" option, go to "Advanced" and in the "[Keep Box]" of nLite add "cmd.exe" so it doesn't get deleted.
This is assuming you have used nLite, if you didn't, after installing that source, try looking for the cmd.exe file, maybe it's missing anyway.

[dunkie12]

andregcasal, on Jan 19 2007, 06:49 AM, said:

Hi
Hum... It didn't worked? Maybe you deleted cmd.exe with nLite...
Try again, but in the "remove components" option, go to "Advanced" and in the "[Keep Box]" of nLite add "cmd.exe" so it doesn't get deleted.
This is assuming you have used nLite, if you didn't, after installing that source, try looking for the cmd.exe file, maybe it's missing anyway.

Nope, CMD.exe is there... I don't use N-Lite at all - I'm using a completely un-modded windows XP SP2 source, aside from me adding my $OEM$ distribution folders for unattend...
Could there be something in the formatting of the winnt.sif document that I've inadvertantly gotten wrong?

This post has been edited by dunkie12: 18 January 2007 - 04:04 PM

[dunkie12]

Bwahahahaha if you were to call me a fool right now you'd be correct...
I've just figured out what's causing my problem -
I put the command into the [Unattended] section of winnt.sif instead of [GUIUnattended]... bwahahaha what an id*** I am! hehe
Thanks for your help anyway andregcasal, I appreciate it man!

[andregcasal]

loool You're not an id***... It happens

[maximilian3]

wow it's beatiful.
I have followed the instructions but i have a problem.
then i try to load the command: memdisk xxx.IMA appear the error: command not available in script debugger

Why?

Thank you very much
Bye
Max

[andregcasal]

Hum... Not sure, but it seems CDShell has a new version and the scripting language may have changed. Try to search for that error at the CHShell site and fórum. If you find anything, please report back

The tests i've been conducting on XP are almost over, i'll have a complete guide in 2 or 3 months

[dunkie12]

After I got my DVD working, I managed to perfect the runonceex method using the .TAG files. If you prefer to use runonceex, you can use the same method of searching for the .TAG file to call the correct runonceex script - just have your cmdlines.txt call a batch script that searches for the .TAG file as instructed, and then use the same script to call the desired runonceex batch script. I've got this working perfectly!

[andregcasal]

Yep, that's another simple way to do it I'll had it to the guide, thanks
EDIT: The only problem is RunOnceEx runs at first logon, so it requires a reboot after first logon. If the applications installed don't need reboot, then it's actually a nice method Without RunOnceEx, all aplications, are installed at the T-13, so the first logon already has everything installed "rebootless" lol

This post has been edited by andregcasal: 29 January 2007 - 04:19 PM

[NsOnLn]

How would you incorporate WPI in this process? I like the menu option to install apps after the OS is installed. I would like to have a base WPI folder for all OS's that I install. That way I only have to update one menu. I have not started to create a multiboot yet even though I am going to soon. My other question is can this include Bart PE? That way I can have 1 DVD that has utils from Bart PE and then an option to install Windows XP Pro or Home. Any ideas? thanks

[andregcasal]

Hi, about the WPI, go to the WPI webpage and take a look at the tutorial provided. I believe it's explained there

[Mortimer]

I've tried to create my own cdshell.ini based on the example, and tried to make it as simple as possible. But i've get stuck, and now I'm a little bit confused...

boot:
cls
print "\n"
print "Press Enter to boot from DVD... \n"
getkey 5 boot 0x80
if $lastKey == key[enter]; then goto time
# When no key found...
goto boot


# Printing the Interface
menu:
set textColor= color[grey on black]
set boldColor= color[cyan on black]
cls
print c "\n\cXXÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ<\c0B$time $date\cXX>ÄÄ \n\n"
print c "\cXXMicrosoft Windows XP Professional Installation Pack \n\n""
print l "\cXXPress \c0BF1 \cXXfor Help"\n"
print c "\cXXÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ \n\n"
print c " Choose language version: \n"
print "1)  Polish\n"
print "2)  English\n\n"

print "R)  Reboot \n"
print "Q)  Quit to Command Prompt \n"
print "ESC) Boot from 1st Harddisk \n"
print c "\n"

MainKey:
getkey 20 boot 0x80
if $lastKey == key[1]; then ???
if $lastKey == key[2]; then ???
if $lastKey == key[q]; then end
if $lastKey == key[r]; then reboot

if $lastKey == key[F1]; then goto Help
if $lastKey == key[esc]; then boot 0x80

Now, what should I put to these two lines, to start installation of the choosed system immedietely?

if $lastKey == key[1]; then ???
if $lastKey == key[2]; then ???

Directory structure:

\DVD\
\DVD\Setup\
\DVD\Setup\XP
\DVD\Setup\XP\PL
\DVD\Setup\XP\EL
\DVD\PRO1
\DVD\PRO2
\DVD\BOOT

(BTW what files should i keep in the 'boot' folder?)

[andregcasal]

Hum, i didn't realized the example file has "???" on it, sorry about that

You should change those ??? with PRO1.DAT according to my tutorial. Of course you can name the boot file, what ever you what

[Mortimer]

andregcasal, on Feb 25 2007, 11:38 PM, said:

Hum, i didn't realized the example file has "???" on it, sorry about that

You should change those ??? with PRO1.DAT according to my tutorial. Of course you can name the boot file, what ever you what

No, your example file is OK, but I was unsure, since I dont have "pro1.dat" file at all.

[phkninja]

PRO1.dat is just a bootfile. if you look at most of the examples it tells you how to create pro1.dat etc. in your case pro1.dat would boot polish and pro2.dat would boot english. Basically its the standard boot file with a modification to make it boot from a folder other than i386 (the default folder)

[Mortimer]

phkninja, on Feb 27 2007, 12:43 AM, said:

PRO1.dat is just a bootfile. if you look at most of the examples it tells you how to create pro1.dat etc. in your case pro1.dat would boot polish and pro2.dat would boot english. Basically its the standard boot file with a modification to make it boot from a folder other than i386 (the default folder)

I've followed all the steps in the tutorial, but all i've got, is 'pro1.bin' and 'pro2.bin' files. Shouldn't I use those names instead of 'pro1.dat'?

[andregcasal]

Well, it seems CDShell has a preference for *.dat files, i've never actually tried with the *.bin extension, it was a too-easy-to-bother detail
If you've tried it, please report back so i can simplify a little bit more the tutorial
Good luck

[Wuschmaster]

Damn, it doesn't work for me, and I've been trying this for almost 2 days now.
But everytime I get this weird manifest error.

What am I doing wrong?



I extracted my files from the TechNet ISO called "en_winxp_pro_with_sp2.iso". (CD Name: VX2PFPP_EN)
If I install with this ISO directly, Windows Setup works just fine.
I also tried with my German and Japanese files, but the same error occurs.

I'm using Virtual PC 6.0.142.0 (2007).

Please help!

This post has been edited by Wuschmaster: 13 March 2007 - 07:21 AM