MagicISO has ability to create Multi-Bootable CD/DVD image file so that the user can incorporate multiple installation CD into one CD/DVD, and install multiple Operation System from one CD/DVD.
MagicDisc is freeware. It is very helpful utility designed for creating and managing virtual CD drives and CD/DVD discs. For anyone who deals with CD-based programs - it is a MUST. MagicDisc allows you to use almost all CD/DVD image without burning them onto CD or DVD in order to easily access your favorite games, music, or software programs ---- It works like a real CD/DVD-ROM: You can run programs, play games, or listen to music from your virtual CD-ROM. Allowing you to run your game images at over 200x faster than from a conventional CD/DVD-ROM.
MagicDisc is a powerful utility that uses a unique combination of options to ensure a perfect back-up every time. Partner with MagicISO, Your original games/program discs can be safely stored away, MagicISO mean that you always have your expensive media stored safely as CD/DVD image file on your hard drive, and use them with MagicDisc just like using the original discs. At the office: Program discs and many other applications generally require the original disc to be in the computer's CD-ROM drive. This restricts the amount of people in your office who can have access to the same software at the same time without the cost of additional discs. MagicDisc virtual drives resolve that problem for you. No more hunting around the offices for that elusive disc you need to run your application, everything you require is just a click away.
All supported CD/DVD image formats
BIN (CDRWin)
IMA/IMG (Generic disk images)
CIF (Easy CD Creator)
NRG (Nero - Burning ROM)
IMG/CCD (CloneCD)
MDF/MDS (Fantom CD)
VCD (Farstone Virtual Drive)
VaporCD (Noum Vapor CDROM)
P01/MD1/XA (Gear)
VC4/000 (Virtual CD)
VDI (Virtuo CD Manager)
C2D (WinOnCD)
BWI/BWT (BlinkWrite)
CDI (DiscJuggler)
TAO/DAO (Duplicator)
PDI (Instant Copy)
MagicDisc has automatically Detecting engine, so user try to open any CD/DVD image files with MagicDisc.
documented on: 2007-10-21
andregcasal May 21 2006
This is (probably) the most complete and updated guide on how to build a Multi Boot DVD. I'll be updating it as i can. Hope you like it.
Features in this guide:
Automatically create multi-boot folders and files
Install all your software directly from your CD/DVD (so it won't be copied to the HD saving time)
You'll have just one Install.cmd file to update/maintain all your software
Determine which software gets installed in which OS
Still be able to use the OEMPreInstall=Yes and [GuiRunOnce] in winnt.sif to launch some other stuff that you may need
You can slipstream drivers to every OS you want, having only one copy (BTS's DrivePacks integration being researched)
You'll still be able to use any post-install methods you like (RunOnceEx, kTool, WPI, WIHU, XPlode, etc)
This guide is compatible with the following methods and tools:
nLite
RyanVM
HFSLIT
BTS's DriverPacks (Method 2 is recomended. That way you can have only one copy of the drivers and slipstream them to all the OSs.)
Windows Post-Install Wizard (WPI)
kTool
WIHU
XPlode
This guide is compatible with the following OSs:
Windows XP SP1
Windows XP SP2
Windows Home
Windows XP Media Center
Windows 2000
Windows Server 2003 (Standard, Enterprise, Web & Data Center)
Windows 98
Before we start: Keep it simple, for boot menu use CD Shell, use simple winnt.sif files, etc. You should beautify, only after you'll successfully completed and booted from all OSs. Some beautifying options are at the end of this guide.
What you will need:
Time and patience, don't expect to get everything to work the first time
Various operating system CDs or ISOs
Sufficient drive space (5+ GB to be safe) (I used +/- 20GB for my DVD)
CDImage (GUI'ed version)
CD Shell
Hex Workshop to hex-edit files.
Optional - VMware (Shareware), Virtual PC (Freeware) or Qemu (Freeware) (for testing purposes)
Any ISO burning software, like CDBurner XP (Freeware)
Work on one operating system at a time. Test once you have that operating system added to make sure everything works right, then move onto the next OS. It will save yourself time if something goes wrong and you have no idea where to look. You can only test your DVD once you've passed the "Creating the ISO" section. Good luck!
[ ... rest ommited ...]
This post has been edited by andregcasal: Jan 29 2007.
documented on: 2007.08.07
> Now you're p***ing me off ! What do you mean integrated into the Windows > setup ? Don't drop a totally provocative hint and run away !!! smile.gif
I knew that would get you going laugh.gif .
I've used many, many different ways to run an unattened/Modded XP setup and now finally after nearly two years of p***ing around I've settled on the simplest setup going.
At present my setup consists of:
RyanVM's Update Pack, WMP10 addon and DirectX 9c addon.
Bashrat's DriverPacks (all of them except MassStorage).
Windows Post-Install Wizard to install all my apps.
To bind all this together I have my own custom addon to use with the RyanVM Integrator. It consists of files to add/update unattened setup and integrate the MediaCentre Royale theme. Included in this package is an inf I made to update reg settings at specific stages of install and to finally run RunOnceEx to finish the DriverPacks setup and execute WPI. It's clean and (even if I do say it myself) professional.
Most of this is easy to do i.e adding Ryan's updates/addons and the DriverPacks. The fun really starts when your learning how to build your own addons, write inf's and configure WPI. They're a bit more time consuming.
All-in-all the $OEM$ folders, and a batch file could do the small things I've done with my little addon, I'm just being a know-it-all whistling.gif (let the flaming commence).
The only real benefit with integration is you don't have to use oemprecopy, or what ever it's called, that messes up F6 driver installation during txtmode. You can also run an upgrade install with the /makelocalsource switch and everything works as it should ($OEM$ folders only work on a full OEM install!). Not that I ever do but you can.
If you want some help I'll be more than heppy to barrage you with links smile.gif .
documented on: Mar 21 2007, kof94
CD Shell 2.1.5 released March 1, 2005
After a long wait, a much needed maintenance release of CD Shell is coming out today. It fixes numerous bugs in the Diskemu module, and lots of other random bugs. You will also find the following new and/or improved features: an updated isolinux module (version 3.07), a new command (return here), the ability to boot Acronis ISO images using Diskemu, support for ISO level 4 (9660:1999) file systems, and finally a cool new script called the Chooser.
The chooser script is a sort of selection list menu, that allows you to scroll through up to 100 selections, complete with keyboard/mouse support, and a scroll bar. It's in the /boot/scripts/chooser directory. The example script is called runme.cds, and is full of helpful information.
To play around with the Acronis ISO booting support, just take your bootable Acronis CD, rip it to an ISO using WinISO or some such program, and then burn it onto a CD Shell disc. Then issue the command "diskemu acronis.iso", replacing acronis.iso with the name of your ISO. This is a new, experimental feature, so you might want to be careful using this on a production machine. I have done some testing, and it was working fine for me, though.
Mike
documented on: Mar 1 2005
diskemu <filename> [noboot] [segment]
The diskemu command is used to emulate floppy disk images using diskemu. The default operation is to emulate the floppy disk and boot from it.
If the noboot keyword is used, the emulated disk will not be booted. After issuing such a command, diskemu can be invoked a second time to allow emulation of two different floppy disks at once. Diskemu will always use the last disk image it was given as floppy disk A.
The optional segment parameter specifies the install segment of the diskemu emulator program.
Diskemu is an alternative to memdisk. The main differences are as follows:
memdisk caches the entire disk image in memory, and thus responds faster to disk I/O operations. Diskemu reads the disk image from the CD/DVD as the contents are requested, which requires more time.
memdisk also allows writing to the disk image exactly as if it was a real floppy disk (although the whatever is written will be lost when the machine is rebooted). Diskemu emulated floppies are read-only.
memdisk has the capability of booting hard disk images, while diskemu is limited to floppy disk images.
Diskemu does not require the emulated floppy disk to be booted.
Diskemu is able to emulate two floppy disks at once.
Although memdisk has clear advantages, there are some situations where it may not cooperate with certain programs. If you're having trouble getting your disk image to work with memdisk, try using diskemu and see if that helps.
Diskem1x.bin - CD-Rom multiboot loader and disk emulator Eltorito.sys - Hardware independent Dos CD-Rom driver...
Current version: Diskem1x.bin v1.1 BETA (11/07/01) * / Eltorito.sys v1.x
Last updated on Jul 10, 2002
Notice!
Development on diskem1x.bin has stopped!
I have some diagnostic / recovery tools in iso images. These are CD images, not floppy images. How are they to be integrated into UBCD ?
There is no straightforward method to boot ISO images from CDShell/UBCD.
You can try "diskemu image.iso", but that only works for certain types of ISO images.
For Linux-based ISOs, there are other methods for booting them. Just do a forum search.
Victor Chew
documented on: Nov 30, 2006
Thanks for this response…
But, my ISO file is about 160 Mb… I can't boot this ISO file directly with CDShell ? I search in the CDShell Help !
Edit : I have found my error… My ISO file was more than 8 character lenght… Oups…
So, I succesfull load my 160 Mb ISO file with the diskemu command !
Thanks for help !
verdesroches
documented on: Feb 28, 2007
Introduction
In my part 1 I showed how to easily reduce the source and make the cd bootable. Part 1 was meant to be as straight forward and easy as possible. In this second part I will show you how to take that bootable cd we just made and turn it into an All In One (AIO) CD. Part 2 is intended for novices, not newbies. If you already haven't, please read part 1 before continuing.
In part 1 we made a bootable cd that has XP Pro. To make an All In One (AIO) CD we're going to add XP Home to the install. You might be thinking, "why add xp home when xp pro has all the features of home?". It's true that pro has all the features of Home. The advantages of adding XP home are many - you might not want advanced features like encryption and domain support; you can use XP Home to reinstall XP Home on a friends computer; adding xp home to the cd will only add about 50 megs. Follow the steps below to add XP Home to your install.
. .
documented on: 2007-10-22
BBIE stands for Bart's Boot Image Extractor.
Version 1.0 Last updated on Sep 11, 2002
BBIE will extract all boot images from a bootable CD-Rom or ISO image file. It follows El Torito Bootable CD-ROM Format Specification v1.0. Getting boot images from a bootable CD-Rom has never been easier.
documented on: 2007-10-22