work then ... I assume you can boot from floppy. If you don't have auto
detect, you can read the disk type during floppy boot and use those ..
--Jon.
Thank you all for still taking a notice of me (this is the 4th letter
concerning the MBR!)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
On Sun, 10 May 1998, Tristan Day wrote:
Thanks to all for all the help and ideas, but it still won't work: here's
what has gone wrong:
snip
'lilo -u /dev/hda' says boot sector of /dev/hda does not have a lilo
signature
'lilo -u' runs fine and says that it has restored the original MBR
Thanks to all for all the help and ideas, but it still won't work: here's
what has gone wrong:
The DOS 'fdisk /MBR' ran with no errors, but made no difference to bootup.
'lilo -u /dev/hda' says boot sector of /dev/hda does not have a lilo
signature
'lilo -u' runs fine and says that it has
On Sun, May 10, 1998 at 01:23:48PM +0100, Tristan Day wrote:
Thanks to all for all the help and ideas, but it still won't work: here's
what has gone wrong:
Can you state the problem again? I missed your earlier posts.
The DOS 'fdisk /MBR' ran with no errors, but made no difference to bootup
/hda, 0800 is /dev/sda, etc. Those backups
can be used to restore the old MBR if no easier method is available. The
commands are
dd if=/boot/boot.0300 of=/dev/hda bs=446 count=1 or
dd if=/boot/boot.0800 of=/dev/sda bs=446 count=1
respectively.
--
You appear
Sorry, that should have been:
dd if=/boot/boot.0301 of=/dev/hda bs=446 count=1
-Ossama
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
-- that's the NTFS partition containing NT
My system _did_ work before -- honest!!
Thank you all for still taking a notice of me (this is the 4th letter
concerning the MBR!)
Tristan
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
When I load from a boot disk (created by format /s at dos prompt in
Win95), fdisk doesn't work because it doesn't exist, thus
fdisk /MBR
doesn't work. If I try this in linux, it says MBR not found tried in lower
case too
=(
Tristan -- one unhappy WinNT4 and Debian dual-booter
On Sat, May 09, 1998 at 05:54:08PM +0100, Tristan Day wrote:
When I load from a boot disk (created by format /s at dos prompt in
Win95), fdisk doesn't work because it doesn't exist, thus
fdisk /MBR
doesn't work. If I try this in linux, it says MBR not found tried in lower
case too
You may have already come across this link for
multibooting Linux and ???.
http://www.owlnet.rice.edu/~sedmison/directboot.html
--
tony mollica
[EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
. It says booting Win95, then returns to the LILO prompt.
The problem remains, I can't seem to overwrite the MBR, not with LILO, not
with fdisk. I found out that the Windows partition was FAT32, but surely
I bet FAT32 is the problem. It is not DOS-compatible, so existing disk
utilities cannot
[EMAIL PROTECTED] writes:
Where can one find information about /sbin/activate? I have it
on my system (Debian 1.2.18), but no man pages, How-To, or other
documentation. It does not give any meaningful response to activate -h
or activate --help. What does this program do?
According to
-Original Message-
From: Dale Harrison [EMAIL PROTECTED]
To: debian-user@lists.debian.org debian-user@lists.debian.org
Date: Wednesday, October 29, 1997 9:26 PM
Subject: Linux, FAT32 and a mighty odd MBR.
Hello.
I had a weird problem last night, installing Debian 1.3* on a friends PC
is removed.
Hmmm. Boot via Win95 rescue disk and fdisk /mbr. Reboot and LILO's STILL
there. Tried this more times than I can recall.. LILO won't die. System
Commander reported some wacky things about the MBR, saying things were
pretty well screwed with it.
The problem remains, I can't seem
Dale Harrison [EMAIL PROTECTED] writes:
So, I guess I'm throwing this out to you guys, is this a Windows problem?
A Debian problem? A LILO problem? A FAT32 problem?
I can't point out a solution but I can tell you that it's probably not
related specifically to Debian or to Linux, as I have had
I last installed Debian) LILO doesn't always install on
the MBR, but in my case in /dev/hda1. What does your /etc/lilo.conf
look like?
You could also try to write a new MBR with /sbin/activate /dev/hda 1
or whichever partition Win95's on.
--
Carey Evans * http://home.clear.net.nz/pages
PROTECTED] wrote:
You could also try to write a new MBR with /sbin/activate /dev/hda 1
or whichever partition Win95's on.
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
I don't have an awsome computer like that, but I experianced problems when
installing LILO on the MBR with win95. Win95 lost all its long filenames!
I'd would try installing LILO on the root partition of Linux.
-Paul
On Thu, 30 Oct 1997, Dale Harrison wrote:
Hello.
I had a weird problem
option was successful,
but when I add a section for win95 in lilo.conf and run /sbin/lilo it
complains that lilo must reside on the mbr (i assume that win95 has
taken
the mbr). How can I put lilo back on the mbr?
You need to use the 'boot' command, I believe. Something like boot = /dev
add a section for win95 in lilo.conf and run /sbin/lilo it
complains that lilo must reside on the mbr (i assume that win95 has
taken
the mbr). How can I put lilo back on the mbr?
Any help is greatly appreciated
Thanks goes out to all who responded to my plea for help.
After reading everyones mail and falling back to a phrase we use
in the Military when all else fails, read the instructions! I
have my P90 back up and going again!
I checked out my boot directory and found the following files:
boot.0300
On Sat, 22 Feb 1997, Rick Macdonald wrote:
On Sat, 22 Feb 1997, Brian Hutchinson wrote:
Here is some more information on my sad state!
Maybe I'll be the first to answer the simplest of your questions:
The dos mbr can be replaced with dos fdisk:
c:\= fdisk /mbr
...RickM...
Yeah
/mbr
to wipe out lilo on the mbr (/dev/hda) but what about lilo on /dev/hda1?
Have I trashed my DOS partiton information? What can I do now?
I did run fdisk and the partition information looked correct. It knew
the partition was all dos and it was bootable/primary.
Thanks again,
Brian
[EMAIL PROTECTED] (Brian Hutchinson) wrote:
Here is some more information on my sad state!
[All information zapped...]
From what you've written, I gather that you inadvertedly told LILO to
overwrite the boot sector (_not_ the MBR) of your DOS partition. DOS
keeps some important bookkeeping
information zapped...]
From what you've written, I gather that you inadvertedly told LILO to
overwrite the boot sector (_not_ the MBR) of your DOS partition. DOS
keeps some important bookkeeping information in it's boot sector, among
which the size of the partition, the number of sectors in a cluster
Gertjan Klein wrote:
From what you've written, I gather that you inadvertedly told LILO to
overwrite the boot sector (_not_ the MBR) of your DOS partition. DOS
keeps some important bookkeeping information in it's boot sector, among
which the size of the partition, the number of sectors
thought so. I did that once before.
Several nice people have e-mailed me and told me to do a fdisk /mbr
to wipe out lilo on the mbr (/dev/hda) but what about lilo on /dev/hda1?
Have I trashed my DOS partiton information? What can I do now?
Lilo most likely backed it up.
Boot back into your
tried using lilo to forget about my linux drive and just boot
dos but I think I ended up messing things up. I tried:
/etc/lilo.conf:
boot=/dev/hda
other=/dev/hda1
table=/dev/hda
label=dos
When I boot the machine I get LILO then unexpected EOF loading dos.
Is there any way I can rebuild my MBR so
Here is some more information on my sad state!
I thought no problem, I'll just make a dos boot floppy.
wrong. When I do a C: I can get to the drive but when
I try to do a dir or anything I get:
Invalid media type reading drive C
The machine I built the kernel for (the 386) is giving me
On Sat, 22 Feb 1997, Brian Hutchinson wrote:
Here is some more information on my sad state!
Maybe I'll be the first to answer the simplest of your questions:
The dos mbr can be replaced with dos fdisk:
c:\= fdisk /mbr
...RickM...
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word
Brian --
For a quick fix, a provided you have a backup to boot dos, reboot
under drive a: for dos, get onto the c: drive, and run fdisk /mbr. This
will restore the c: disk so that it will boot dos automatically.
For future reference, whenever you rebuild the kernel, it's a good idea
801 - 831 of 831 matches
Mail list logo