Related topics

lilo - dual boot - mdk9.1 and RH8.0
I'm learning about the boot process of Windows (NT/XP) and I asked myself, where do boot sector virusses write their code??? Most boot infectors that are still around, and these are few, write their code to the MBR. Some, but not all, relocate the original uninfected MBR somewhere else, mostly to an unused sector

Two questions about boot of VxWorks!
compact # Installs the specified file as the new boot sector # install=/boot/boot-bmp.b # Specifies the location of the map file # map=/boot/map # You can set a password here, and uncomment the `restricted' lines # in the image definitions below to make it so that a password must # be typed to boot anything but a

XP will not boot without floppy boot disk
Joey Hess jo...@debian.org linux debian maint boot Update of /cvs/debian-boot/debian-installer/build/boot/powerpc In directory gluck:/tmp/cvs-serv26079/boot/powerpc Modified Files: boot.msg Log Message: - makelabel takes the build date as its second parameter. Calculating BUILD_DATE once at the start to avoid

LILO Boot Setup with Win 2000
Ruslan Ermilov r...@freebsd.org fa freebsd cvs-all ru 2004/02/09 06:11:58 PST FreeBSD src repository Modified files: sys/boot/i386 Makefile.inc sys/boot/i386/boot0 Makefile Tested on: i386, amd64 Revision Changes Path 1.9 +1 -0 src/sys/boot/i386/Makefile.inc 1.23 +7 -4 src/sys/boot/i386/boot0/Makefile 1.54 +1 -1

Bug#244100: Cobalt and Netwinder need ext2 -r0 boot partition
Rod Smith rodsm...@speaker.rodsbooks.com comp os linux setup In article <23403e52.0106250748.1b42a...@posting.google.com>, y...@pragerfenton-la.com (BkrStMuse) writes: Hello, I am having problems getting my dual boot machine to work just right. I have windows on hda and Linux on hdb with LILO on the MBR.

"disk boot failure"
"bootable floppy" means a floppy disk that has code (and associated data) in the Master Boot Record that the computer's BIOS can load and execute. What this code actually does will depend on what created the bootable floppy and for what purpose. "Bootable" in reference to CDs means essentially the same thing.

Help Dual Boot Problem
PattyL pat...@XXmvps.org microsoft public win98 setup Boot using a Win98 boot disk since it will probably recognize your CDROM drive. You can make this boot disk by double-clicking Fat32ebd.exe in the \Tools\Mtsutil\Fat32ebd folder on the Win98 installation CD. You will also have to configure your system to look

sbs 4.5 not finishing boot sequence
I have windows on hda, and indeed when I put a second windows drive on hdb, and tell bios to boot from it, it works, and windows sees it as the primary ("C:") drive and what was on hda now is the "D:" drive. I remember in the past cautiously unplugging hda where windows lives before installing Mandrake on hdb.

boot list
However I did some research I found that I must install /boot to the first 1024 cylindars of the primary drive not the extended partition. I guess what these means is that I'll have to free up space on the win98 partition which contains boot.ini. I hope fips works for this because I'm not going to run out and buy

cvs commit: src/share/mk bsd.libnames.mk src/sys/boot/i386 ...
Ruslan Ermilov r...@freebsd.org fa freebsd cvs-all ru 2004/02/06 13:58:32 PST FreeBSD src repository Modified files: share/mk bsd.libnames.mk sys/boot/i386 Makefile.inc sys/boot/i386/boot0 Makefile sys/boot/i386/boot0sio Makefile sys/boot/i386/boot2 Makefile sys/boot/i386/btx Makefile.inc sys/boot/i386/cdboot

Boot floppies
MS should have established as "policy" that the preferred way to configure an NT/W2K installation would be with a dedicated partition for boot/swap/system and an entirely separate partition for user files. Mind you, I'm not recommending that everyone start doing this......I'm saying that it's a flaw in the design

boot problem -- update
One of those is to boot from the mymlink /boot/vmlinuz or /boot/vmlinuz.old (created by the default kernel build system, and optionally kernel-package). Why you may ask. Simple. Under some circumstances, I've needed to make /boot a seperate partition. On one server I was using a software raid5 setup for the root

Seeking boot manager
H. Peter Anvin h...@zytor.com mlist linux kernel The following patch is a fairly small and fully backwards compatible change to the i386 boot protocol. It makes the maximum legal initrd address explicitly available to the boot loader, so it doesn't have to guess. To make matters worse, the current documentation

Boot from Network?
Where's the boot partition? (not root). Is it /dev/sda1? Units = cylinders of 16065 * 512 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 5 40131 83 Linux /dev/sda2 6 260 2048287+ 82 Linux swap /dev/sda3 261 515 2048287+ 83 Linux /dev/sda4 516 17785 138721275 5 Extended /dev/sda5 516 770 2048256 83 Linux

GRUB optimal dual xp boot setup
todo: updated * rescue: checker script added to source area by Edmund GRIMLEY EVANS <edmu...@rano.org>; f5.txt consistency fix Files: 316b770da6fee3b75989e906409fabf7 529 devel extra boot-floppies_2.2.7.dsc 8b18266a912c511984a43487ce7921f9 2189461 devel extra boot-floppies_2.2.7.tar.gz

Can't make boot floppy
But he really wishes to dual boot (he did not know he could), and wants both drives installed at the same time. Normally this would be easy: Install Windows on the first drive, install Linux on the second, and have LILO select which to boot. But he does not wish to re-install Linux because he has a running system

Which boot files do I need?
(Number of users seem to affect boot times as does if the welcome screen is displayed - these are guesses) What defragger do you use. XP's inbuilt one? How do you measure the 60 seconds and how is that time broken up. 9x bootlog recorded times maybe NT does too. From help Enable Boot Logging Starts while logging

Installed boot-floppies 2.2.7 (all source)
H. Peter Anvin h...@zytor.com fa linux kernel The following patch is a fairly small and fully backwards compatible change to the i386 boot protocol. It makes the maximum legal initrd address explicitly available to the boot loader, so it doesn't have to guess. To make matters worse, the current documentation

boot problem
Rod Smith rodsm...@fast9.uceprotect.net linux redhat misc [Posted and mailed] In article <71njbr$t1...@nnrp1.dejanews.com>, bear_p...@hotmail.com writes: I've read the man pages for LILO and MKBOOT but don't seem to grok how one makes a boot image on the partition for use with a 3rd party boot loader.

[Jim] Boot Times Experiment
On newer CD's the images on slice 2 and above only contain boot redirects to slice 1. To create a CD that is bootable on Sun sparc systems you need to have the boot images for the apropriate sparc architecture. A boot image file usually is a UFS filesystem image that contains the primary boot image at byte offset