URL: http://www.plop.at/en/bootmanager.htmlThe Plop Boot Manager is a small program to boot different operating systems. The boot manager has a builtin ide cdrom and usb driver to access those hardware without the help/need of a bios. You can boot the operating systems from harddisk, floppy, CD/DVD or from USB. You can start the boot manager from floppy, CD, network and there are many more ways to start the boot manager. You can install the boot manager on your harddisk. There is no extra partition required for the boot manager.
The Plop Boot Manager was written by Elmar Hanlhofer. If you need help, post it to the forum or send me a message with the contact form.The current version is plpbt-5.0.10.zip.
| Hard disk installation | The boot manager will be installed as primary boot manager to your hard disk. No extra partition and required. The boot manager will be in the first sectors of your hard disk before the first partition begins. |
| Start from external media Floppy CDROM/DVD USB drive |
Its not required to install the boot manager to your hard disk. You can start it from those media and use the boot manager with some limitations. |
| Start from other boot managers LiLo Syslinux Grub Grub4Dos Grub2 Windows boot.ini Windows BCD |
You can still use your prefered boot manager and additionally use features
from the Plop Boot Manager (like boot the usb drive,...). The boot manager can run in hidden mode, so you have for example an entry in your prefered boot manager to boot the usb drive and when you use this entry then it starts immediately without any additional menu. This can be useful for the usb boot function. |
| Start from network | With help of pxelinux its possible to start the boot manager from the network. |
| Start from your bios as option rom | You can store the boot manager as option rom in your bios. There is no need for any hard disk or anything else to start the boot manager. It can be used as PNP part of your bios or the boot manager can hook the INT19 to take control as first boot device. |
|
Main menu ![]() zoom |
Main menu (textmode) ![]() zoom |
Profile partitions ![]() zoom |
MBR partition edit ![]() zoom |
You can download all files here.
The Plop Boot Manager is freeware.
This software is provided 'as-is', without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this software.
There are many ways to install the boot manager to the harddisk. If you want run the boot manager without harddisk installation then see Running from Windows boot menu, LILO, GRUB, Syslinux, Floppy, CD.
Warning Linux users: Install LILO or GRUB to the boot sector of your Linux instead of the Master Boot Record (MBR). The Plop Boot Manager is not a Linux loader and cannot start Linux without LILO, GRUB, Syslinux and similar!
There are 2 versions of the install program. Basically both versions do the same. The only difference is that plpinst.com creates a backup file plpback.bin to restore harddisk sectors for a complete boot manager uninstall. The second version plpinstc.com skips the backup part. You have to use the second version for installation from write protected media like CD's or if you install from network or any other boot manager.
The install programs are installing the boot manager always on the first harddisk of your computer.
With this option you install the boot manager to your harddisk. If you have an installed operating system, then the install program creates a profile for you to boot this operating system.
With the installation from floppy, the install program makes a backup of the sectors where the boot manager will be installed. The install program writes the backup to the floppy disk. With this backup it's possible to remove the boot manager completely from your harddisk. If you use the CD installation, then it's not possible to restore the sectors. In this case the uninstall routine creates a new MBR to boot the current operating system. The partition table data won't be changed.
A small program (the loader) is required in the MBR to start the boot manager. Operating systems like Windows XP are writing during the installation their own small program into the MBR. If you install Windows XP after the boot manager, then Windows XP will start instead of the boot manager, because the loader is overwritten with the program from Windows XP. To setup that the boot manager starts before Windows XP you have to use Write mbr loader only.
With this, you can update the boot manager. But only updates with boot manager v5 are working.
Warning, this option is only available with the installation from floppy.
The install program takes the backup that was saved on the floppy disk and writes it back to the harddisk.
Warning, if you changed anything with the partition table, then do not use this option!
With this option, the program writes a new MBR to start the current operating system. The partition table will be unchanged.
Configures the Boot Manager to start in textmode.
Set destination harddisk to install the boot manager.
See Hotkeys.
The computer will be restarted.
A floppy disk image is a file that contains every sector of the floppy disk. You cannot copy the image file on a floppy disk like a common file. It's required to use a special program that writes sector per sector of the image file to the floppy disk sectors. There are many programs available to do this.
Download the current boot manager plpbt-5.0.10.zip. Extract it to get the floppy disk image. You find the disk image in the install directory. The name of the file is plpbtin.img
How to create the floppy:
DOS: You can use diskimg.com with diskimg -d a -w plpbtin.img
Windows: Write the disk image with the program rawwritewin to the floppy disk
Linux: dd if=plpbtin.img of=/dev/fd0
Download the current boot manager plpbt-5.0.10.zip. Extract it to get the iso file. You find the iso file in the install directory. The name of the file is plpbtin.iso
Notice: The CD installer makes no backup for a complete uninstall. See The install program.
Windows:
You can use Nero, or the free program CDBurnerXP, or any other program that can burn ISO images.
Use the option like burn ISO on CD or burn ISO Image. Then choose the boot manager ISO and burn it.
Linux:
cdrecord is the linux program to burn ISO images to a CD.
Burn the ISO with cdrecord: cdrecord -v dev=<devicename> <iso image>
Example:
If you access your CD burner with /dev/hdd
cdrecord -v dev=/dev/hdd plpbtin.iso
Download the current boot manager plpbt-5.0.10.zip. Extract it to get the install program. In the install directory there are 2 install programs (plpinst.com and plpinstc.com) for using under DOS.
plpinst.com creates a backup file plpback.bin for a complete boot manager uninstall. plpinstc.bin makes no backup. Use plpinstc.com for write protected media like CD's.
Download the file plpgenbtldr-0.7.zip and extract it.
Create a directory like c:\plop. You can use any directory you want.
Copy plpinstc.com and plpgenbtldr.exe to your c:\plop directory.
Rename plpinstc.com to plpbt.bin.
As administrator/with administrator rights open a command shell and change to c:\plop
Then start plpgenbtldr
This program searches for the file plpbt.bin In the current directory.
plpgenbtldr generates the file plpbtldr.bin.
Adding to the boot menu. Windows 2K and XP is different to Windows VISTA and Windows 7
Windows 2K, XP
add the line below to your c:\boot.ini
Windows VISTA
open notepad as administrator and create a file c:\boot.ini
add those lines
[boot loader] [operating systems] c:\plop\plpbtldr.bin="Install Plop Boot Manager"
Thanks to tri_zet for this info
Windows 7
Open the command prompt as administrator.
Use bcdedit to create the boot menu entry.
This prints a long number with { }.
This long number is called "id".
Replace the "id" with your number in the following commands.
bcdedit /set {id} device partition=C:
bcdedit /set {id} path \plop\plpbtldr.bin
bcdedit /displayorder {id} /addlast
Additional links: Forum entry, Gord's blog
Now you should be able to install the Plop Boot Manager from your Windows boot menu to your harddisk.
plpbt.bin must not be fragmeted! Use Wincontig or contig to take care, that plpbt.bin is not fragmented.
Download the current boot manager plpbt-5.0.10.zip. Extract it to get the boot manager install program. You find the install program plpinstc in the install directory.
Add plpinstc.com to the config file
Add the following lines to the config file
label plpinst linux plpinstc.com
Copy plpinstc to the same directory where the config file is.
You start the install program when you enter plpinst at the Syslinux command prompt.
Download the current boot manager plpbt-5.0.10.zip. Extract it to get the boot manager install program. You find the install program plpinstc.com in the install directory.
Copy plpinstc.com to /boot.
Add to your /etc/lilo.conf the following
image=/boot/plpinstc.com label=plop-install
Run lilo to update lilo.
Download the current boot manager plpbt-5.0.10.zip. Extract it to get the boot manager install program. You find the install program plpinstc.com in the install directory.
Copy plpinstc.com to /boot.
You have to choose the correct root settings in menu.lst for your system.
The following is an example
title Plop Boot Manager Install root (hd0,0) kernel /boot/plpinstc.com
When you reboot, you should be able to choose the install program from your grub menu.
You can use the Plop Boot Manager without harddisk installation with the boot manager binary file plpbt.bin. It's possible to configure the binary with plpcfgbt.
Warning: If you start the Boot Manager in the following ways, then the Boot Manager DOES NOT save the changes you made in the profile/partitions menu! Use this Boot Manager features only when you installed the Boot Manager with the install program. See Harddisk installation.
A floppy disk image is a file that contains every sector of the floppy disk. You cannot copy the image file on a floppy disk like a common file. It's required to use a special program that writes sector per sector of the image file to the floppy disk sectors. There are many programs available to do this.
Download the current boot manager plpbt-5.0.10.zip. Extract it to get the floppy disk image plpbt.img.
How to create the floppy:
DOS: You can use diskimg.com with diskimg -d a -w plpbt.img
Windows: Write the disk image with the program rawwritewin to the floppy disk
Linux: dd if=plpbt.img of=/dev/fd0
You can configure the plpbt.bin on the floppy with plpcfgbt.
Download the current boot manager plpbt-5.0.10.zip. Extract it to get the iso file plpbt.iso.
Windows:
You can use Nero, or the free program CDBurnerXP, or any other program that can burn ISO images.
Use the option like burn ISO on CD or burn ISO Image. Then choose the boot manager ISO and burn it.
Linux:
cdrecord is the linux program to burn ISO images to a CD.
Burn the ISO with cdrecord: cdrecord -v dev=<devicename> <iso image>
Example:
If you access your CD burner with /dev/hdd
cdrecord -v dev=/dev/hdd plpbt.iso
Download the file plpgenbtldr-0.7.zip and extract it.
Create a directory like c:\plop. You can use any directory you want.
Copy plpbt.bin and plpgenbtldr.exe to your c:\plop directory.
As administrator/with administrator rights open a command shell and change to c:\plop
Then start plpgenbtldr
This program searches for the file plpbt.bin in the currrent directory.
plpgenbtldr generates the file plpbtldr.bin.
Adding to the boot menu. Windows 2K and XP is different to Windows VISTA
Windows 2K, XP
add the line below to your c:\boot.ini
Windows VISTA
open notepad as administrator and create a file c:\boot.ini
add those lines
[boot loader] [operating systems] c:\plop\plpbtldr.bin="Plop Boot Manager"
Thanks to tri_zet for this info
Windows 7
Open the command prompt as administrator.
Use bcdedit to create the boot menu entry.
This prints a long number with { }.
This long number is called "id".
Replace the "id" with your number in the following commands.
bcdedit /set {id} device partition=C:
bcdedit /set {id} path \plop\plpbtldr.bin
bcdedit /displayorder {id} /addlast
Additional links: Forum entry, Gord's blog
Now you should be able to start the Plop Boot Manager from your Windows boot menu.
You can configure the file plpbt.bin with plpcfgbt.
plpbt.bin must not be fragmeted! Use Wincontig or contig to take care, that plpbt.bin is not fragmented.
Download the current boot manager plpbt-5.0.10.zip. Extract it to get the boot manager binary program plpbt.bin.
Add plpbt to the config file
Add the following lines to your config file
label plp linux plpbt.bin
Copy plpbt.bin to the same directory where the config file is.
You start the boot manager when you enter plp at the Syslinux command prompt.
You can configure the file plpbt.bin with plpcfgbt.
Download the current boot manager plpbt-5.0.10.zip. Extract it to get the boot manager binary program plpbt.bin.
Copy the plpbt.bin file to /boot.
Add to your /etc/lilo.conf the following
image=/boot/plpbt.bin label=Plop
Run lilo to update lilo.
You can configure the file plpbt.bin with plpcfgbt.
Download the current boot manager plpbt-5.0.10.zip. Extract it to get the boot manager binary program plpbt.bin.
Copy the plpbt.bin file to /boot.
You have to choose the correct root settings in menu.lst for your system.
The following is an example
title Plop Boot Manager root (hd0,0) kernel /boot/plpbt.bin
Download the current boot manager plpbt-5.0.10.zip. Extract it to get the boot manager binary program plpbt.bin.
Copy the plpbt.bin file to /boot.
You have to choose the correct root settings in grub.cfg for your system.
The following is an example
menuentry "Plop Boot Manager" {
set root=(hd0,1)
linux16 /boot/plpbt.bin
}
When you reboot, you should be able to start the boot manager from your grub menu.
You can configure the file plpbt.bin with plpcfgbt.
Cursor up/down Move the bar Enter Choose selection ESC Close window CTRL - ESC Switch to textmode CTRL - PAGE UP Switch to higher screen resolution CTRL - PAGE DOWN Switch to lower screen resolution z Enable/Disable window zoom animation
In the main menu you see all visible profiles to boot an operating system. You can start an operating system from floppy, cd/dvd or usb. You can go to the setup of the boot manager, partitions and profiles. If your bios supports APM, you can shutdown your computer.
Special additional keys for USB boot:
- press SHIFT to force USB 1.1
- press CTRL to wait for a keypress before starting the operating system. You have here the option to press "n" (next) and continue the search for mass storage devices to boot from another usb device.
1-9 Boot profile q Quick boot, open a list of all possible hardcoded partitions to boot w Write MBR with the profile settings, but do not boot f Boot floppy c Boot CD/DVD u Boot USB
press SHIFT to force USB 1.1
press CTRL to wait for a keypress before starting the operating system. You have here the option to press "n" (next) and continue the search for mass storage devices to boot from another usb device
You can manage your partitions here. The install program creates an entry for all primary partitions it finds. The names are from HDA1 up to HDD4. HD means harddisk. HDA stands for harddisk A and is the first harddisk. The numbers 1-4 are the numbers of the primary partitions.
Notice for linux users: HDA has nothing to do with the devices in linux like /dev/hda.
You can change the label for the partition. This label is used in the boot manager. The maximum length is 16 chars.
Here, you choose the harddisk of the partition.
HDA = Harddisk 1
HDB = Harddisk 2
HDC = Harddisk 3
HDD = Harddisk 4
There are 2 ways to set the ID of a partition.
You can enter the hexadecimal value for the partition.
This list has the mostly used partition ID's. If the requested ID is not in the list, then use Enter partition ID.
This is used to change the values of partitions in the MBR.
BP means boot manager partition. This values are stored in the boot manager.
P1-P4 this are the current values of the primary partitions in the MBR.
You can edit the hexadecimal values in the partition table. You can select a row with s (select) and paste the values to the row where the cursor is with p. With this function, you can import partition values to the boot manager or change values in the MBR. This can be very useful in emergency cases.
Clearing the data means clearing of the partition data in the boot manager. The data on the partition itself is unchanged.
Use it if you changed something and you want to restore the whole values of the partition in the boot manager. This is possible until you close the partition edit window.
Profiles are used to start different operating systems from different harddisks and partitions. It's also possible to detect changes in the MBR made by other software and import or forget the changes.
If you have an operating system installed and you install the boot manager, the installer creates a profile to boot the current operating system.
You can edit the label of the profile. This label is shown in the main menu. It's useful to use a label to see what operating system is going to boot. The maximum length is 16 chars.
With this option you select if the profile is shown in the main menu or not. Only visible profiles can be booted. It also has effects on the default profile in the boot manager setup.
You select from which harddisk, partition and bios device number you want to boot with this profile. You can also select what partitions or cleared partitions should be used for the MBR.
There are 3 states for a partition entry
1. a selected partition
Press enter to choose a partition from a list with all partition of this harddisk available from Partitions.
If another software change this entry in the MBR, the boot manager detects this change at the next startup. You can choose if you want to import the new values or forget them.
2. don't touch
The partition entry in the MBR will not be changed from the boot manager. That is the default setting.
If a software changes this entry in the MBR the boot manager cannot detect this change.
3. cleared
The boot manager set's this entry to 0 in the MBR. An operating system cannot detect that there is/was a partition.
WARNING: if the boot manager has not stored the values of the partition in "Partitions" then you lose the partition values in the MBR and you cannot access the data on the partition. It's possible to restore those values, but it's better, easier and safe to store the values in Partitions.
Partition programs will say this is unallocated space! Do not partition this space! You can lose data if you do it wrong.
b set boot partition. You select, what partition you want to boot with this profile. The boot manager set a bios drive number automatically. It's possible to change it with another key.
c clear partition. You set this entry to "cleared" and the boot manager cleares this entry in the MBR when you boot this profile.
d don't touch. You set the entry to don't touch and the boot manager does not change this entry when you boot this profile.
e edit boot flag. The boot flag has the bios drive number used by the boot sector routine. In some cases it's required to change this value.
r remove boot flag. Here, you remove the boot flag from the profile.
l set logial partition. You can set to boot from a logical partition 1-4 of an extended partition. Change the logical number by pressing "l". L1 = first logical, L2 = second, ...
You can clear the profile data in the boot manager. The data in Partitions are not changed.
Use it if you changed something and want to restore the whole values of the profile in the boot manager. This is possible until you close the profile edit window.
The boot manager has two modes to start. With the user interface menu and hidden.
For the hidden mode, you have to set the bootcounter and you have to select a default profile. The default profile boots after the countdown. The user can not see that there is a boot manager in the background. If you want to go into the boot manager, then press ESC.
You can enable and disable the countdown.
If the bootcounter is enabled, the boot manager waits the given time and starts after the countdown the last used profile or the default profile, depending on your settings.
Choose between 1 and 99 seconds.
At start, the boot manager set the bar to the selected option. This works for the hidden start mode too.
You have the following options
1. Last booted profile
2. Default profile
3. Floppy
4. CDROM
5. USB
You can select the default profile from a list of all visible profiles.
Show the floppy boot option in the main menu.
Show the cdrom boot option in the main menu.
Show the USB boot option in the main menu.
Use USB 1.1 controller even if there is a USB 2.0 controller.
Mode 1: Ignore the EHCI Controller
Mode 2: Setup EHCI Controller and set all ports to the companion host. Some controllers need this option to force usb 1.1.
Use Mass Storage Device. Boot the X mass storage device that was found. Other devices are ignored.
You can select the textmode during the startup of an operating system. Choose between "don't change" or 80x50.
Select the screen resolution in the boot manager. Choose between textmode 80x50 and graphicmode 640x480, 800x600, 1024x768, 1280x1024.
Enable and disable the window animation.
Select the boot manager font or the bios font.
Enable and disable the starfield animation.
Setup the master password. Disable the boot manager password protection with an empty password.
Setup the setup password. Disable the boot manager setup password protection with an empty password.
plpcfgbt-0.8.zip is a tool to configure the binary version plpbt.bin of the boot manager. This program is available for Windows and Linux. You start the program from a command shell. If you run the program without parameters then you will see the help information.
Usage: plpcfgbt [OPTIONS] file Options: ======== PARAM SET VALUES vm video mode text, 640x480, 800x600, 1024x768, 1280x1024 stm start mode menu or hidden, hidden requires cnt=on and dbt not off cnt countdown on or off cntval countdown value in seconds between 1 and 99 dbt default boot off, profile, floppy, cdrom, usb dprf default profile value between 1 and 16 stf starfield on or off zan zoom animation on or off fnt font bt or bios usb1 force usb 1.1 off or 1 or 2. 1 = Mode 1, 2 = Mode 2 usbmdev use usb massdev 1-99 int19h int19h/os boot do not boot the os and use int19h, on or off hotkey startup hotkey yes or no prf profile set 'prf' value between 1 and 16 prfname set profilename 16 chars, 'prf' must be set btdrv boot drive 80h-89h, 'prf' must be set btprt boot partition 1-4, 'prf' must be set btlog boot log part. 1-4, 'prf' must be set
Infos about int19h see here.
The hotkey option is useful with CD's or ROM's. You get the info to press CTRL-A
to start the boot manager. If you don't press it, the the booting continues
without the boot manager.
Print current settings
plpcfgbt plpbt.bin
Configure hidden boot and boot the usb device
plpcfgbt stm=hidden cnt=on cntval=1 dbt=usb plpbt.bin
plpbt-createiso.zip is a simple script to create a custom plop boot manager iso by Elmar Hanlhofer. There is one script for Windows and one script for Linux in the zip file. The scripts are using mkisofs from cdrtools.
The windows binaries of cdrtools are from http://smithii.com/cdrtools and included in the zip file. plpbt.bin and create-iso.bat must be in the same directory. You have to run create-iso.bat to create the iso file. You get a file called plpbtmycd.iso. Thats your new boot manager iso file.
You must have installed mkisofs. plpbt.bin and create-iso.bat must be in the same directory. You have to run sh create-iso.sh to create the iso file. You get a file called plpbtmycd.iso. Thats your new boot manager iso file.
You can create an option ROM file with plpbtrom-0.4-test3.zip.
Usage: plpbtrom [OPTIONS] input-file output-file Options: ======== -h this help -vendorid id hex value of the card vendor -deviceid id hex value of device -grabid grab vendor/device id from PCI ROM file -hidden disable option rom text output -nodisable do not allow option rom disable -forceINT force hook interrupt -INT18 hook int 18h input-file boot manager file (ex. plpbtrom.bin) output-file ROM file name
-forceINT: This forces the boot manager to hook the INT 19h/INT 18h. If you have a PNP bios, then the boot manager does not use the PNP bios feature of the boot device sequence. The boot manager will be started before any boot devices is tried (when INT 19h mode is used) or the boot manager is the last program that is started when all boot devices failed to boot (when INT 18h mode is used).
-INT18: Hook INT18h instead of INT19h. INT19h is the default mode.
plpbtrom - Linux executable
plpbtrom.exe - Windows executable
plpbtrom.bin - Boot Manager
The only difference is that plpbtrom.bin gives the control of the boot process back to the bios with a far return if you press esc. plpbt.bin makes a reboot with int 19h.
You can configure plpbtrom.bin like plpbt.bin with plpcfgbt. You can enable/disable a hotkey to stat the boot manager.
You can test your rom file with the free virtual machine qemu.
qemu -hda harddisk.img -option-rom plpbt.rom
If you have no harddisk image file then take one from the qemu download page or use a floppy image.
qemu -fda floppy.img -option-rom plpbt.rom
Do this at your own risk! This can damage your pc.
Download the Ami bios flash utility and save your current bios. AMI Homepage
Its a DOS program, run the following command from a DOS floppy to save your bios
Use the Windows tool MMTools to replace the network rom with the plpbt.rom.
Load the file bios.rom
Find the network option rom. It has the id 20, the name PCI Option ROM and the RunLoc number VendorID:DeviceID of your network card. Maybe there are other option roms in your bios. Take care that you choose the network option rom.
Click on it that its marked.
Click at the Replace Tab
Load as Module file the plpbt.rom file.
Press the Replace button
Press the Save ROM as and give it the name mybios.rom
Now comes the dangerous part. Flashing the bios.
I suggest to set the bios to the default settings and save it. Then boot from a dos floppy and run
Do not turn off the pc during flash. After the flash has completed, go to the bios and do again a reset to the default settings.
If all is ok, you should be able to configure the bios and start the boot manager during the boot process.
Do this at your own risk! This can damage your pc.
Download the Award bios flash utility aflash. You should find it at your Motherboard homepage in the bios section.
Run it from a DOS floppy and save your current bios to a file. Give it the name bios.rom.
Search the file cbrom in the web. There are different version, not all will work with your bios file, so you have to test it with different versions.
Run cbrom bios.rom /d
This should list all parts of the bios rom. I cannot give you the command to replace the rom. None of the cbrom programs where able to display the content of my bios rom file. You have to test it by your self.
When you updated the bios rom file, then flash it. I suggest to set the bios to the default settings and save it. Then boot from a dos floppy and run with awdflash.
If all is ok, you should be able to configure the bios and start the boot manager during the boot process.
If you run DOS and the Plop USB driver is loaded, then you can disable the USB driver with plpdisd-0.1.zip. When you disable the driver, then you are able to load other DOS usb drivers.
You can run plpdisd from config.sysDEVICE=\plpdisd.exe
It's also possible to run it from the autoexec.bat or command line.
There is a important difference between "hidden" and "cleared" partitions.
Hidden Partition: Operatings systems, backup soulutions and so on can see them but they ignore them. I would say, this is a pseudo hidden partition.
Cleared Partition: No program (except the boot manager) knows that there is/was a partition defined in the MBR. This is really hidden. It looks like unallocated space for every program. That means no other program can access the data on that partition (with some work and searching the harddisk there are still ways to access the data). There is a risk, if you repartition the harddisk, you will overwrite your invisible partition and all data on it if you do it wrong.
This is an example: A partition should be visible in one profile and hidden (and not cleared) in another profile
Lets say you want to have the second partition on HDA (HDA2) on one profile visible and on another hidden (and not cleared).
Use an empty entry in partitions. Give it the label "hidden hda2".
Select the device HDA.
Go to "VIEW/EDIT/COPY DATA".
Move the cursor to P2 and press "s". Now move up to "BP" and press "p".
Press ESC and go to "Partition ID". Choose "Select from list". Choose the hidden version of your partition.
Press ESC and save your changes.
Go to "profiles".
Now you can assign the
"visible" version of your partition to one profile and the "hidden" to another profile.
Download demoinstall.wmv (demoinstall.zip). The quality is not the best but you see all required steps. I hope its useful.
The goal is to install Windows XP on the first partition and Windows Vista on the second partition. I want that no windows has access to the partition of the other Windows. There should be a third partition that will be used as shared partition. Both Windows have access to this partition.
There are many ways to do this. I will describe one way.
It works only with the Harddisk installation!
At first install Windows XP. Create with the Windows installer a partition with the size you want. I use a 10GB partition. Install Windows XP on this partition.
When you installed your Windows, go to the Disk Management and create a second primary partition for Vista and a third primary partition for the shared data.
Now comes the boot manager part. Boot from the boot manager install floppy or CD. Install the boot manager to the harddisk and then reboot.
The boot manager created a profile called "os harddisk 1" to boot Windows XP. It also imported the 3 primary partitions. The names are HDA1, HDA2 and HDA3.
Now go to setup and profiles. Select os harddisk 1. Give it the new label windows xp.
Select linked partitions. Press enter at the first slot of HDA and select HDA1. At the second slot press c to set it to cleared. You can leave the third slot as don't touch or select HDA3. See the difference at configure partition entries.
Now leave the configuration of Windows XP and go to an empty profile in Profiles. Give it the label windows vista. Set show in main menu to yes. Now select linked partitions. Press at the first slot c to set it to cleared. At the second slot press b to set the boot flag. Press enter and select HDA2. On the third slot choose the same as for windows xp (don't touch or HDA3).
Go back to the main menu. Now you see windows xp and windows vista. Move to windows vista and press Enter. This writes the profile settings to the harddisk. The booting will fail, because Vista is not installed. Now boot the Windows Vista install DVD. In the installer you should see at the partitions screen at first an unallocated space (there is xp installed) and 2 primary partitions. Select the first primary partition to install Windows Vista. when the Windows Vista installation has been finished, it's possible, that Vista is booting immediately and the Plop Boot Manager does not come. In this case use Write mbr loader only from the Plop Boot Manager install floppy or CD.
Now you should have two bootable Windows on your harddisk and they don't know from each other. You can share data between both with the shared partition.
It's similar to the previous description, if you want to install Windows XP on the first harddisk and Windows Vista on the second harddisk. The second harddisk is HDB in the boot manager. So install Windows Vista to the first partition of the second harddisk. Set in the vista profile/linked partitions the first slot of HDB to HDB1 and press b. The boot manager will set the boot flag to 81h. This should be ok for your installation.
Here are short instructions for a complete new installation of your pc with dualbooting WinXP and Win7. It doesn't matter if you use 32 or 64 bit versions. Take care, all data on your pc will be deleted!
Boot the Win7 install DVD. Remove all partitions from the harddisk. Create a partition for Win7. The install program will create 2 partitions. One with about 80MB for the Win7 boot files and a second partition with the Win7 files. Create an additional partition for WinXP. Now you see 3 partitions. Install Win7 to the second partition. After the Win7 installation is complete, install the Plop Boot Manager. After the Boot Manager installation go to the Boot Manager Setup, then Profiles, then "OS HARDDISK 1". Change the name to "Win7". Go to linked partitions and press enter on the first position of HDA and select HDA1, on the second select HDA2 and on the third press "c" for cleared. Now leave the profile settings for Win7. Use now an empty profile to create the WinXP profile. Give it the name WinXP, visible in main menu "yes". In linked parttitions select for HDA on the first position HDA3, press "b" to set the bootflag on the first position. On the second press "c" to set it cleared. On the third press "c" to set it to cleared too. Go to the main menu and press enter on WinXP. You will be not able to boot this partition because XP is not installed currently. If you get the message about invalid boot signature, then press "n" to abort. Now boot the WinXP install CD. You should see now only one partition. Install WinXP there. After the installation completed then start the Plop Boot Manager install CD and use "Install mbr loader only". Reboot, the boot manager will tell you about partition changes. Press "y" to import the new values. Now you should be able to boot both systems.
I know this is very special. Maybe it's useful for some people. You have to configure the plpbt.bin with plpcfgbt to use int19h instead of booting the operating system.
plpcfgbt int19h=on plpbt.bin
Now you have to start plpbt.bin with a boot manager like grub, syslinux or what ever during boot time (supported boot managers see here). Choose USB and the boot manager will install the usb driver and go back to your boot manager. If you start DOS you will have access to your usb drive as last harddisk. But remember, the usbdrive is only as "read only" device available.
If it works for you then use plpcfgbt int19h=on stm=hidden cnt=on cntval=1 dbt=usb plpbt.bin
To disable the usb driver from DOS see plpdisd.
This problem was fixed but with the new NOD32 versions it's back. It's a false report.
I booted DOS from USB and I cannot write on the drive
My drivers have no write routines implemented. You want to know why? My intention was to have USB drivers for UHCI, OHCI and EHCI controllers in my tiny boot manager. The space to install the boot manager without the need of a partition is very limited. So there was no space left for write routines.
Are there plans to add write support in the future
It's in my mind, but there are no fix plans.
The boot manager detect's my usb cdrom, but booting hangs
USB CD/DVD drives are not supported.
My USB keyboard does not work when I booted from USB
USB keyboards are not supported by my drivers. When you boot Linux or Windows, then your keyboard will be available when those operating systems are taking control over the USB hardware.
Can I use my PCMCIA Card to boot from USB
No, PCMCIA is not supported.
I want to install the boot manager from my USB device, but I cannot choose my internal harddisk
The problem with installing on the internal (in this case the second) harddisk with the installer is, that the installer imports the partitions from the usb device and thinks this are the partitions of the first harddisk. When the boot manager boot's later from the real harddisk then the imported partitions are not correct. You see the problem? Sure it would be possible to add an option to handle this situation, but there are so many other ways to install the boot manager, that there are no plans to add this feature to the installer (except, many people request this feature).
I use plpbt.bin and it forgets my settings
You have to configure plpbt.bin with plpcfgbt. All changes you make within the boot manager menu are only valid until you reboot. The changes are not saved.
I can not boot from my SATA CD/DVD drive
SATA CD/DVD drives are not supported. Only IDE CD/DVD drives are working.
Special thanks goes to