kof94

I know this is an old thread but I can't get this to work for a batch can anyone help. EDIT: Nevermind, recompiled inno setup instead.

Ok, I can register oodsh.dll for the shell extention via GUIRunOnce after install (I think) and since the windows defrager isn't going to exist anyway setting O&O as default doesn't matter. If anyones got a better way of doing this please post.

Can anyone tell me how to silently install O&O Defrag 8 with the shell extension and set as default? I'm aiming to remove windows default defrager using nite and replace it with this.

Thanks buddy, I was wondering when you were going to update this. You seem to have implemented all of my requests. Brilliant.

Thanks buddy, I'll give it a go.

I've got DOS 7.10 on the disc already so thats why I've steared away from 6.22, it's just not essential now. Thanks for the info about 311 I'll add it to my disc now. What mods do I need to make though?

Easier question, how can I make the upgrade boot folder look to the setup\..... folder on my DVD. I already have an autorun menu made with Autoplay Menu Builder it just wont execute with switches or execute batch files. If I could pre-edit the files on DVD so when the boot folder is made on the HDD it looks to the right place I wouldn't need to add a switch and the stuff in my $OEM$ folders might work aswell. Sorry, I know my requested info has changed I've just been looking at this from another angle today.

I've been having some problems upgrading Windows from my multi-boot. Every time I run XP/2K's upgrade it returns with a 'can't find the setup files' sort of message. I can understand this, as it can see the tagfiles at the root of the disc but no i386 folder. I've found a workaround using the [/makelocalsource] switch. I've also made a simple setup.bat to launch it. With five different types of installations (XP/2K) on the disc I need a simple autorun that will execute batch files or a similar program that will execute winnt32.exe with the swtich. It also needs to run under 9x (no vb6) for all the other stuff on the disc that will upgrade too. Any ideas? I'm no programmer either so it needs to be something that exists already and simple. Help, please!

Thanks to everyone for there suggestions but this has gone to the bottom of the pile for now. I still can't get it to work but I'll probably return to it. Cheers.

OK, so you want spoon feeding do you? Believe it or not this is one of the more simple things to do. Either that or I was just lucky! Follow the guide for putting XP into a multi-boot first. Work on that until you've got it right and tested it fully. If you want a simple cdshell.ini file copy this in to Notepad relable it and put it in your 'BOOT' folder: boot: cls print "\n" print "Press Enter to boot from DVD... \n" getkey 5 boot 0x80 if ($lastKey == key[enter]); goto menu # 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 "\cXXÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ\n\n" print c "\cXXXP/KNOPPIX MULTI BOOT\n\n" print c "\cXXÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ\n" print "\n" print "\n" print "\n" print "\n" print c "[F1] Windows XP Professional SP2\n" print c "[F2] Knoppix 4.0.2\n" print "\n" print "\n" print "\n" print "\n" print "\n" print "\n" print "\n" print "\n" print "\n" print "\n" print "\n" print c "\cXXÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ\n" print l "\cXX[C] Command Prompt [B] Boot Harddisk [R] Reboot\n" getkey if $lastKey == key[F1]; then chain /PRO1.DAT if $lastKey == key[F2]; then bcdw boot /KNOP.DAT if $lastKey == key[c]; then end if $lastKey == key[r]; then reboot if $lastKey == key[b]; then boot 0x80 goto menu As you may or may not be able to see if you press F1 then cdshell will try to chain boot PRO1.DAT at the root of your multi-boot disc. If you press F2 it will try to bcdw boot KNOP.DAT from the root of you multi-boot disc. These .DAT files are the boot sectors from XP and Knoppix. (PRO1 for XP and KNOP for Knoppix) To make these files download Ultra.ISO from here: ezbsystems when you've installed it do this: Open UltraISO Insert your original disc Go to 'file' (at the top) Click 'open cd/dvd' When it opens go to 'bootable' (at the top) Click 'save boot file' A box will open with the option to save the file as a .bif file. name it to the approprite name (PRO1 for XP or KNOP for Knoppix) and save it to the root of your multi-boot folder (AIO-DVD if you've followed the guide). Finally rename the files from .bif to .DAT. From here you can follow the guide for setting up XP and editing the XP boot sector. It is'nt too difficult but as you'll see it's easier to setup knoppix. Go to your Knoppix CD. Copy 'cdrom.ico' and the 'KNOPPIX' folder to the root of your multi-boot folder (where the boot sector you just made is). Rename your 'BOOT' folder for cdshell to a lowercase 'boot'. Copy the contents from the Knoppix CD 'boot' folder to your new 'boot' folder. As you can now see you have basicly made your multi-boot disc fit around Knoppix. All these Linux based installers stick to a strick Joliet standard so you must replicate the disc exactly. So it's easier to do it this way. OK, moving on. Because of this standard we need to change cdimage's parameters abit to acount for them. It wont affect anything else on your disc, just aid the linux installers. Here's an adapted command for cdimage: start cdimage.exe -lAIODVD -t08/23/2001,09:00:00 -b\AIO-DVD\BOOT\loader.bin -j1 -h -oc -o -m \AIO-DVD C:\AIODVD.iso The one fundamental to this is the -j1 parameter if you keep that your alright. Burn as normal with Nero or whatever you use. Hope that helps I'm off to get a coffee. Good luck.

First, start using cdshell I've found it alot more dynamic. Alot more work but it's worth it. Make a boot sector with UltraISO and place it on your multiboot with the rest of your boot sectors. Place all folders as you see them on the Knoppix disc to the root of your multiboot. Use the BCDW module to load the boot sector. Use the -j1 parameter with cdimage when making your iso. If you need help with cdshell look here. http://flyakite.msfnhosting.com/ Sorry this is abit rushed, if you need more help I'll check back tomorrow.

Yeah, your right, that's what I ment. I only use OEMPreinstall for BTS DP's anyway so my other option wont have it. Thanks for your post though.

A pop up box could be good so you can alt+tab between it so long as the code is selectable for copy+paste. I don't wan't to make your project overly complicated because it's simplicity of use is one of the best things about it. So anyway thats simple to implement is good for me. Afew other things: 1. Could the drop down box be wider. 2. Could the message box be afew lines larger and abit wider. 3. Source would be good I'd rather learn VB than html. Thats all.

Sorry buddy your gonna have to treat me as complete n00b. I've only been interested this for a few months. I've come a far way, my disks looking pretty phat and neer completion. I'm just stuck on this. Could you provide the string you used in cdshell and any other detailed info. I get bogged down when it comes to all the extra parameters you can add to the different modules. Thanks.

Thinks, I'll add two options to my multi-boot then (with or without BTS DP's).

how did you get it to boot?

Ok, I've got as far as having a folder with all the disks in it and an .ima to boot the setup file. but all I get is '.....insert disk 1'. I've tried making an over sized .ima but memdisk and diskemu just pup out and crash vmware. What next, has anyone actually done this on a multi-boot?

If you don't mine me asking, how easy it to make a program like this? I'd like to be able to make my own to suit my needs! I have no idea about writing programs but I'm willing to learn, it just depends on how difficult it is. At the moment I'm faced with either expanding on your menu or customising Trooperman's which means learming html. Final question, are you developing this? If so I'll shutup and be patient.

Not really but I've got it so it might aswell go on the disk! I'm trying to avoid doing just that. Thanks for your suggestion though.

I read somwhere (I can't remember where) that if using the $OEM$ folder for driver installations could cause a file corruption if you then tried to install a textmode driver via F6, is this true? Or is it only true if your trying to install the same driver twice. basicly I want to know if I use the mass storage driverpack will I still be able to install additional drivers from floppy if it's not covered in the pack? Thanks.

I thought of that a while ago but I can't find anyone with a full copy, ME wasn't really that popular. A friend of mine suggested taking files from SE but couldn't remember which ones I'd need. So I'm stuck.

Hi, I've been looking for way to make my Windows ME upgrade edition to a full version. Before anyone starts talking about warez or anything, I have a full version of Windows SE which I've always upgraded from or just put in a second drive during install of ME. I was wondering if I could take certain files from my SE disk and add to my ME disk to make it think there was already an SE installation to upgrade from. The reason I wish to do this is because I'm in the middle of making my multi-boot and I want to be able to install ME directly without installing SE first (which is also on the disc). If anyones got any ideas that be great. Cheers.

From what I gather the 'automatic' setting can cause problems on some computers (mine not being one of them though). If you set nlite's unattended settings to 'standard pc' you can press F5 during textmode setup and change the settings for the PC your using. I could be wrong with the F5 bit so if anyone wishes to correct me please do. If you read the info in nlite you can probably check for yourself though. Hope this helps.

Thanks, since I'm half way there I think I'll just add the right switch. I've downloaded Floppy creator to help with my DOS 6.22 install so it's good all round really. Thanks again.

Tried it, doesn't work! I'm using CDImage with the same parameters as flyakite's guide to make the ISO. Could you use isolinux to boot bootwiz.sys in the Recovery Manager folder instead (or am I looking in the wrong direction)? Also how do you issue a command in CDShell to look in a folder with a two word name? e.g: ...then isolinux \Recovery Manger\bootwiz.sys (or whatever would work) I only really want it on my AIO for cloneing HDD's so it's enough as it is but it would be nice to have the full CD image working.