This is a known problem. Windows refuses to boot when it isn't installed on the first hard drive and shows a black/blank screen. To handle this, you will have to "fool" Windows into believing that it is installed on the first hard drive with a little tweak in your boot loader configuration. Please note that in the below example, Gentoo is installed on hda (first disk) and Windows on hdb (second one). Adjust your config as needed.

EasyBCD can hook into an existing GRUB installation without any user intervention - just point it and it'll do the rest. If you're GRUB isn't already properly configured though, take a look at this sample configuration file for just about everything you could need. Nope. EasyBCD is a very special and unique application in that it doesn't even touch your bootsector or MBR, yet it's still the most powerful bootloader on the planet! Vista installs the "BCD Bootloader" to your MBR and Bootsector.

DISCLAIMER: Messing around with boot loader issues can make your harddisks unbootable. Please make backups before doing so. Please install a new boot loader only when you really now what you do. We reject any responsibility for damages that may occur on your system. GRUB - the GRand Unified Bootloader - needs to access some files in order to run. Its best you place them on a small - 50MB is enough even for further extensions - FAT 16/32 partition.

This is a known problem with the ATI Mach 64 video card. The problem is that this card uses address 2e8, and the fourth serial port does too. Due to a bug (feature?) in the sio(4) driver it will touch this port even if you do not have the fourth serial port, and even if you disable sio3 (the fourth port) which normally uses this address. Disable sio0, sio1, sio2 and sio3 (all of them). This way the sio driver does not get activated -> no problems.

If you have FreeBSD and Linux on the same disk, just follow LILO's installation instructions for booting a non-Linux operating system. Very briefly, these are: Boot Linux, and add the following lines to /etc/lilo.conf: other=/dev/hda2 table=/dev/hda label=FreeBSD the above assumes that your FreeBSD slice is known to Linux as /dev/hda2; tailor to suit your setup). Then, run lilo as root and you should be done. If FreeBSD resides on another disk, you need to add loader=/boot/chain.

From kernel versions 1.1.80 on, the compressed kernel image, which is what LILO needs to find, is in arch/i386/boot/zImage, or arch/i386/boot/bzImage when it is built, and is normally stored in the /boot/ directory. The /etc/lilo.conf file should refer to the vmlinuz symbolic link, not the actual kernel image. This was changed to make it easier to build kernel versions for several different processors from one source tree.

You can configure your computer to start Windows 2000, Windows NT, and either Windows 95 or Windows 98. However, you cannot configure a computer to multiple boot Windows 95 and Windows 98. Both Windows 95 and Windows 98 use the same boot file. Therefore, multiple booting Windows 95 and Windows 98 at the same time is not supported. Your installations are less prone to problems if you install Windows 95 or Windows 98 before you install Windows NT and Windows 2000.

All you need to do is disable high-resolution assist. On the CLIEs if you enable hi-res assist, it causes AcidSpider to do the black-screen at startup. To fix this, go to Prefs and under the "HiRes" panel, check "AcidSpider" as one of the applications that should not have High Resolution Assist enabled.

How to change the timeout seconds for GRUB menu on boot-up? To chage the timeout from 3 to 10 seconds: How to change default Operating System boot-up for GRUB menu? To chage the default OS from the first entry in GRUB menu to the 5th (note that counting starts from 0): How to permanently disable/enable boot-up services? Kubuntu inherits the Debian policy of disregarding non-executable scripts in initialization sequences, cron jobs, etc. (system triggered tasks).

Sure, you can. Create a primary partiton BEFORE your Windows partition (e.g. with PartitionMagic) and get a boot manager (I use the german tool 'Bootmanager', you can get a free trial version at http://www.bootmanager-pro.de).

You can also use the dd command to copy the backup saved by LILO to the boot sector. Refer to the LILO documentation if you wish to do this. FDISK /MBR MBR stands for Master Boot Record. This command replaces the boot sector with a clean DOS one, without affecting the partition table. Some purists disagree with this, but even the author of LILO, Werner Almesberger, suggests it. It is easy, and it works.

Black screens on some ROMs only may indicate that there is a problem with the emulation of that ROM or that you have an old version of the emulator. Please verify if a newer version exists and, if not, please contact the author.

Add something like this to your /etc/lilo.conf file under linux and rerun /sbin/lilo. Note that Solaris *MUST* be the active partition, on either the primary or another another hard drive. To use LILO with Solaris on the primary partition, install LILO in the MBR and mark the solaris partition as active. In this example Solaris is on your second hard drive (hence the "loader" line): other = /dev/hdb1 loader = /boot/chain.

If you have a IDE Zip® or Jaz® drive installed, remove it and try again. The boot floppy can get confused by the drives. After the system is installed you can reconnect the drive. Hopefully this will be fixed in a later release.

To play the games on our server you need Macromedia ® Flashplayer 6.xx plug-in in your browser. If you have an older version installed or don't have it at all, the installation begins automatically from the Macromedia website, this lasts about 1-2 minutes. If you have a slower internet connection it can take a while for the installation to begin. We then recommend that you download the plug-in directly from our server.

The most common reason for this problem is the absence of a bootable master boot record or active partition on the target disk. When using the Copy a specific drive method to copy one drive to another, Casper Tech Edition does not replace the master boot record or change the active partition status on the target disk. In order to ensure the target disk contains a valid master boot record and the appropriate partition is marked active, it is necessary to use the Copy an entire hard disk method.

R-Studio works on Windows 95/98/ME/NT/2000/XP/2003 only. It will not work under DOS or another operative system which fits into one bootable floppy. Therefore, you should attach your hard drives to another computer which can boot to Windows, and then restore files on that computer using R-Studio. No matter how that system recognizes your drives, R-Studio should access it.