1. Make sure "Virus protection" in your BIOS is off 2. Boot from a Win95 boot disk 3. Locate SYS.COM (I think it's in C:\WINDOWS\COMMAND) 4. run SYS.COM A: C:\ 5. run fdisk /mbr (win95 fdisk, not linux fdisk)
On Fri, Oct 29, 1999 at 01:05:08PM +0000, Martyn Pearce wrote:
>
>
> Nico De Ranter writes:
> | Nope, I've had the same problem. Can it be that lilo changes
> | something in the bootable partition and not only in the mbr? In that
> | case fdisk /mbr won't be able to help.
>
> lilo certainly can be installed at the beginnng of an ext2 partition.
> However, I've discounted this because fdisk /mbr should remove any code
> causing the jump to any other partition.
>
> Long Shot --- have you checked the bootable flags with (preferably
> linux) fdisk? The boot code that DOS fdisk installs may well observe
> these, and if set to an old Linux partition, might attempt to jump
> there, causing a lilo boot.
>
> Mx.
>
>
--
"I already have all the latest software."
-- Laura Winslow, "Family Matters"
Dwayne C. Litzenberger - [EMAIL PROTECTED]
Advertising Policy: http://DLitzPower.tripod.com/spamoff.htm
GnuPG Public Key: http://DLitzPower.tripod.com/gpgkey.asc
Fingerprint: 0535 F7CF FF5F 8547 E5A5 695E 4456 FB6C BC39 A4B0
pgpM6RvdeO4AK.pgp
Description: PGP signature
