Hello,
I have updated some new packages yesterday, and today I get the lilo prompt,
but it doesn't go further than:
Loading 1.
I don't quite understand what my problem is. Do I need to fix the MBR, or do
I need to play with lilo?
(I think it's option 2, because it goes like
Boot: MBR
On Tue, May 01, 2001 at 11:04:06AM -0400, Paindavoine, Matthieu (MPAINDAV)
wrote:
Loading 1.
I don't quite understand what my problem is. Do I need to fix the MBR, or do
I need to play with lilo?
(I think it's option 2, because it goes like
Boot: MBR --- LILO --- Kernel,
so if I
is used for booting, I choose the second option in the installation
process (using the /boot partition). Also, the installation process
installed a new MBR. Now, when I reboot, I only see MBR repeated on my
screen several times, nothing else happens. I have to boot to Linux using
a boot disk, which takes
5MB
/dev/hda5: swap 50MB
/dev/hda6: / the rest
Lilo is used for booting, I choose the second option in the installation
process (using the /boot partition). Also, the installation process
installed a new MBR. Now, when I reboot, I only see MBR repeated on my
screen several times, nothing else
@lists.debian.org
Subject: Re: Infinite sevens: MBR problems
On Wed, Feb 07, 2001 at 12:18:59PM -0500, Peter Howell wrote:
On a side note, I went into the bios and altered the boot
order. Now when I boot, it just prints:
LI
and then stops. From what I've been able to find
Hi
I'm interested in comments on the pros and cons of three alternative
configurations:
1) Keeping the dos mbr and having lilo in a partition boot sector.
Changing the bootable flags will initiate lilo etc.
This seems infeasible if the partition where lilo resides starts
beyond 1024
At 03:09 PM 2/6/01 -0800, Joey Hess wrote:
Peter Howell wrote:
MBR
L 07 07 07 07 07 .
From lilo's manual:
Disk error codes
- - - - - - - -
If the BIOS signals an error when LILO is trying to load a boot image, the
respective error code is displayed. The following BIOS error codes
into the boot chain annoys LILO (and hurts
my head anyway... it's REALLY bizarre trying to convince the bios to
boot a bootable CD on a scsi drive...)
What happens on my home system if I ignore the warnings is that the BIOS
will gladly load the LILO mbr off the hard drive, but when that mbr
tries
This is interesting, let us know what works
John
-Original Message-
From: brian moore [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 07, 2001 12:38 PM
To: Debian-User@lists.debian.org
Subject: Re: Infinite sevens: MBR problems
On Wed, Feb 07, 2001 at 12:18:59PM -0500, Peter Howell wrote
with a floppy drive that I have used to install the latest stable
base distribution of debian onto a viper 260mb type III hard drive. I had
it put LILO on the MBR, but I still needed the floppy for the reboot. This
is going to be a problem as the g1200s has no floppy drive.
One question that is asked
I've almost successfully installed the debian base on a pcmcia hard drive
in a PC110. I say almost because I can't get it to boot. When I attempt
to boot off the HD, I get the following message.
MBR
L 07 07 07 07 07 .
and so on forever. If I hold down space during boot, I get
Peter Howell wrote:
MBR
L 07 07 07 07 07 .
From lilo's manual:
Disk error codes
- - - - - - - -
If the BIOS signals an error when LILO is trying to load a boot image, the
respective error code is displayed. The following BIOS error codes are
known:
...
0x07 Invalid
At home I have a laptop where win98 and linux co-exist, with lilo offering
to boot either one at startup. But at office, after linux installs lilo to
MBR,
NT won't boot. So, I went to boot floppy, ran fdisk /mbr; but now
machine won't boot linux. Boot floppy won't work for linux either
[EMAIL PROTECTED] wrote:
At home I have a laptop where win98 and linux co-exist, with lilo offering
to boot either one at startup. But at office, after linux installs lilo to
MBR,
NT won't boot. So, I went to boot floppy, ran fdisk /mbr; but now
machine won't boot linux. Boot floppy
Pending further investigation, we now allege that [EMAIL PROTECTED] wrote:
At home I have a laptop where win98 and linux co-exist, with lilo offering
to boot either one at startup. But at office, after linux installs lilo to
MBR,
NT won't boot. So, I went to boot floppy, ran fdisk /mbr
On Tue, Dec 26, 2000 at 06:25:28PM -0500, [EMAIL PROTECTED] wrote:
At home I have a laptop where win98 and linux co-exist, with lilo offering
to boot either one at startup. But at office, after linux installs lilo to
MBR,
NT won't boot. So, I went to boot floppy, ran fdisk /mbr; but now
i did this recently, and as a solution i just created a 15MB C: drive
for
the boot loader(primary partition) then Linux got a /boot partition
and NT got it's own primary partition. then i load LILO to the MBR and
tell
it to boot to C: (which then loads NT's boot loader) to load NT
or load linux
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
In Running Linux, the example lilo.conf includes the line
boot = /dev/hda
This will install LILO into the master boot record (MBR) of hda. The
explanation continues If you give a partition device name (such as
/dev/hda2), instead of a drive
In Running Linux, the example lilo.conf includes the line
boot = /dev/hda
this is used if LILO will be the controlling boot manager for the system.
The bios will read this first when the system is turned on.
This will install LILO into the master boot record (MBR) of hda
Terry Boon [EMAIL PROTECTED] writes:
TB In Running Linux, the example lilo.conf includes the line
TB
TBboot = /dev/hda
TB
TB This will install LILO into the master boot record (MBR) of hda. The
TB explanation continues If you give a partition device name (such as
TB /dev/hda2), instead
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Many thanks to David Maze and Jason Holland for their help with this
question: I now have a happily working system.
On Sat, Nov 04, 2000 at 02:48:54PM -0500, David Z Maze wrote:
I think the default setup for Debian is to use a fairly simple MBR
From DOS, try
fdisk /mbr
Also, run a virus scan of the DOS partition, MBR, and boot records. I like NAV,
personally.
Andrew Hagen
[EMAIL PROTECTED]
http://clam.rutgers.edu/~ahagen/
the Linux
partitions.
When it asked me about installing the MBR, I took all the defaults.
After it installed (or tried to install) an MBR for /dev/sda, it gave me
a screen about how the boot partition was on an extended partition, so
it needed to install into /dev/sda2, and I again took the default
Paul D Smith [EMAIL PROTECTED] writes:
PDS Now when I boot the system it prints MBR, then does a hard hang. I
PDS can't even C-A-D or use the reset button, I have to power off/on.
PDS
PDS If I hold the SHIFT key down, it prints MBR 2AF, then does the same
PDS hard hang.
PDS
PDS I can boot off
), with an optional
boot into DOS (/dev/sda1).
When I installed Debian I had it overwrite the data in all the Linux
partitions.
When it asked me about installing the MBR, I took all the defaults.
After it installed (or tried to install) an MBR for /dev/sda, it gave me
a screen about how the boot partition
%% David Z. Maze [EMAIL PROTECTED] writes:
dzm Paul D Smith [EMAIL PROTECTED] writes:
PDS Now when I boot the system it prints MBR, then does a hard hang. I
PDS can't even C-A-D or use the reset button, I have to power off/on.
PDS
PDS If I hold the SHIFT key down, it prints MBR 2AF
%% Andy Bastien [EMAIL PROTECTED] writes:
/etc/lilo.conf says:
lba32
boot=/dev/sda2
root=/dev/sda5
install=/boot/boot.b
map=/boot/map
delay=20
vga=normal
default=Linux
image=/vmlinuz
label=Linux
read-only
image=/vmlinuz.old
label=LinuxOLD
%% Andy Bastien [EMAIL PROTECTED] writes:
ab In any case, I'd set sda1 active and then set the value for root in
ab lilo.conf to /dev/sda and then go from there.
I set sda1 active and changed the boot to /dev/sda in /etc/lilo.conf,
and re-ran lilo, and now it works; thanks.
Seems like the
Oswald Buddenhagen wrote:
Can anyone explain to me the difference between install-mbr and lilo?
the layout of a (pc) hard drive:
+---+---+---+--
| partition | few | first partition | second partition
| table | wasted
-mbr only installs a master boot record, whose function is to:
1) Determine which partition to boot from (from user input or by
default)
2) Call the boot code located in the first sector of the chosen boot
partition, which then is responsible for actually booting the OS.
BIOS == install-mbr
Note: Please let me know if this comes through as HTML (and accept my
apologies) - I'm on a new email client that I'm unfamiliar with.
no html detected :-)
Can anyone explain to me the difference between install-mbr and lilo?
the layout of a (pc) hard drive
Note: Please let me know if this comes through as HTML (and accept my
apologies) - I'm on a new email client that I'm unfamiliar with.
Can anyone explain to me the difference between install-mbr and lilo?
I've never really understood the Linux bootstrap process, and although
I've read
Hello,
Is there a way to read my current MBR, or is this the file mbr.b in
/boot?
I am not sure. I did not use LILO to configure my MBR but I used an
external bootmaster (I think from Partition Magick).
This is a strange type of file. Is there a way to make it more human
readable
Use dd to copy to local_file and read with hex reader like MC.
# dd if=/dev/hda of=local_file count=20
MC is midnight commander in console.
Osamu
On Tue, Sep 19, 2000 at 05:02:06PM +, stefan goeman wrote:
Hello,
Is there a way to read my current MBR, or is this the file mbr.b
On Mon, Sep 11, 2000 at 08:37:29PM +0200, Moritz Schulte ([EMAIL PROTECTED])
wrote:
On Mon, Sep 11, 2000 at 04:39:24PM +0100, Dominik Bittl wrote:
I deleted /dev/hda as root and now i cant boot anymore (without
disc) !!
...
What can i do ??
if i am right, and you really have only
On Mon, Sep 11, 2000 at 10:26:06PM -0700, kmself@ix.netcom.com wrote:
:On Mon, Sep 11, 2000 at 08:37:29PM +0200, Moritz Schulte ([EMAIL PROTECTED])
wrote:
: On Mon, Sep 11, 2000 at 04:39:24PM +0100, Dominik Bittl wrote:
: if i am right, and you really have only deleted this device file, then
:
UUUps !!
I deleted /dev/hda as root and now i cant boot anymore (without disc) !!
I tried to mkdir /dev/hda but it doesnt work with lilo !! My NT is still
working.
What can i do ??
Yeah i know it's stupid but what should i do ??
dominik
On Mon, Sep 11, 2000 at 04:39:24PM +0100, Dominik Bittl wrote:
I deleted /dev/hda as root and now i cant boot anymore (without disc) !!
How could this happen ;)
I tried to mkdir /dev/hda but it doesnt work with lilo !! My NT is still
working.
What can i do ??
Have a look at
On Mon, Sep 11, 2000 at 04:39:24PM +0100, Dominik Bittl wrote:
I deleted /dev/hda as root and now i cant boot anymore (without
disc) !!
eh, what do you mean? have you deleted the _device file_ '/dev/hda'?
then, i could imagine, that there's no (big) data loss.
these device files are the
tried using install-mbr and this seems to have
damaged the boot record of Win98.
Booting Win98 comes up with the MBR of install-mbr. I ran DOS Fdisk /mbr
but that did not fix it. I seem to remember a similar problem some years
ago which I was able to fix with Norton Fixdisk. I won't be home
On Wed, Sep 06, 2000 at 08:09:38AM -0700, Heather wrote:
As a preference, I think the install-mbr is elegant. I like the idea that
it won't say much, but I can hit SHIFT and access everywhere.
And if you set no delay then your non-Linux-enthusiast superiors won't
notice you've slipped one past
On Wed, Sep 06, 2000 at 08:09:38AM -0700, Heather wrote:
As a preference, I think the install-mbr is elegant. I like the idea that
it won't say much, but I can hit SHIFT and access everywhere.
And if you set no delay then your non-Linux-enthusiast superiors won't
notice you've slipped
adding
Potato as DEB on HDA10. I still could only access Potato by booting off
floppy.
I decided to remove HDA10 reduce the size of HDA3 and create HDA2 as a
primary ext2 partition. This went ok and I reloaded Potato.
At this point frustration got the better of me and I used install-mbr. I
could
Tim Wood [EMAIL PROTECTED] writes:
Hi everyone,
sorry if this is a bit of a saga but please bear with me.
[snip]
Can anybody suggest a way to get back Win98 on /dev/hda1 and, more to
the point, suggest a way to be able to boot /dev/ha1, /dev/hda5 and
/dev/hda2?
Apart from `man lilo`
Hi everyone,
sorry if this is a bit of a saga but please bear with me.
[trevails of repartitioning, ellided]
A boot off RH floppy and re-install of LILO gives me the ability to boot
into RH6.2.
I can boot off floppy into potato on /dev/hda2.
I can no longer boot Windoze, no great loss I
install-mbr and this seems to have
damaged the boot record of Win98.
Booting Win98 comes up with the MBR of install-mbr. I ran DOS Fdisk /mbr
but that did not fix it. I seem to remember a similar problem some years
ago which I was able to fix with Norton Fixdisk. I won't be home for
another week so
I am having an error messages such as No operating system or, 40 40
40... on the screen after the hard disk jumpers were not set up correctly.
What is the command to redo the master boot record?
John Kerr Anderson
[EMAIL PROTECTED]
Debian
On Sun, 03 Sep 2000, John Anderson wrote:
I am having an error messages such as No operating system or, 40 40
40... on the screen after the hard disk jumpers were not set up correctly.
What is the command to redo the master boot record?
Using windows fdisk --
fdisk /MBR
is the command
just re-load lilo into the MBR just make sure your lilo.conf is
configured right
to install to the MBR use the line:
boot=/dev/hda
to install to the primary, master hd, change accordingly for other
drives.
nate
John Anderson wrote:
I am having an error messages such as No operating system
time this happens he can
just stick the floppy in and run /sbin/lilo just like normal, and
everything will be everything again.
How can I prevent something like this happening again?
Something in the bios can be set to prevent things (viruses) from
writing to the mbr. Reinstall LILO
A friend of mine is experiencing a weird situation with multy-booting.
I installed Linux for him on a second harddrive all by itself, and
installed Lilo into MBR on /dev/hda to mutli-boot Linux and Windows
(Windows off /dev/hda1, and Linux off /dev/hdc1).
This worked fine for about a month until
cause this.
Could it be that Windows repairs the MBR by removing a foreign
multy-booter and overwriting it with the native one to only boot
Windows? If so, what could have caused this behavior. I've never
heard of anything like this. Granted, I haven't used Windows much,
and know very
On Tue, Jun 06, 2000 at 04:33:03PM -0400, Arcady Genkin wrote:
I'm going over tomorrow to reinstall LILO for him.
you should dd his kernel to a floppy, then use rdev to set the root
device to is real root partition. then next time this happens he can
just stick the floppy in and run
I have to uninstall Linux and put WindowsNT on a workstation at work.
I have formated the disk with fdisk and I get
LILO
Linux Loading ..
Error 0x01
Linux Loading ..
etc
.
.
.
How do I erase the MBR?
Dan
___
To get
On Thu, May 11, 2000 at 12:23:40PM -0700, Dan Hutchinson wrote:
How do I erase the MBR?
In DOS you can do fdisk /mbr.
--
Steve Zinck [EMAIL PROTECTED]
http://nerd.halifax.ns.ca
Use dos boot floppy with fdisk on it. Then type 'fdisk /mbr'
Oliver
Dan Hutchinson wrote:
I have to uninstall Linux and put WindowsNT on a workstation at work.
I have formated the disk with fdisk and I get
LILO
Linux Loading ..
Error 0x01
Linux Loading ..
etc
.
.
.
How
the MBR?
In DOS you can do fdisk /mbr.
--
Steve Zinck [EMAIL PROTECTED]
http://nerd.halifax.ns.ca
--
Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED]
/dev/null
___
To get your own FREE ZDNet Onebox - FREE
On Thu, May 11, 2000 at 12:23:40PM -0700, Dan Hutchinson wrote:
I have to uninstall Linux and put WindowsNT on a workstation at work.
I have formated the disk with fdisk and I get
LILO
Linux Loading ..
Error 0x01
Linux Loading ..
etc
.
.
.
How do I erase the MBR?
Boot
I have a machine with two hard disks here, that other OS resides
on hda and I added the second drive (hdc) for Debian. The setup
installed a MBR on hdc, but my BIOS only supports booting from
hda. Is there a way to install lilo in the MBR on hda and have
it boot linux from hdc1?
lilo.conf
I have a machine with two hard disks here, that other OS resides
on hda and I added the second drive (hdc) for Debian. The setup
installed a MBR on hdc, but my BIOS only supports booting from
hda. Is there a way to install lilo in the MBR on hda and have
it boot linux from hdc1?
I'm familiar
I have a machine with two hard disks here, that other OS resides
on hda and I added the second drive (hdc) for Debian. The setup
installed a MBR on hdc, but my BIOS only supports booting from
hda. Is there a way to install lilo in the MBR on hda and have
it boot linux from hdc1?
lilo.conf
On Thu, 4 May 2000, Oswald Buddenhagen wrote:
I have a machine with two hard disks here, that other OS resides
on hda and I added the second drive (hdc) for Debian. The setup
installed a MBR on hdc, but my BIOS only supports booting from
hda. Is there a way to install lilo in the MBR on hda
On Thu, 04 May 2000, Philip Lehman wrote:
On Thu, 4 May 2000, Oswald Buddenhagen wrote:
I have a machine with two hard disks here, that other OS resides
on hda and I added the second drive (hdc) for Debian. The setup
installed a MBR on hdc, but my BIOS only supports booting from
hda
On Thu, 4 May 2000, matthschulz wrote:
On Thu, 04 May 2000, Philip Lehman wrote:
On Thu, 4 May 2000, Oswald Buddenhagen wrote:
I have a machine with two hard disks here, that other OS resides
on hda and I added the second drive (hdc) for Debian. The setup
installed a MBR on hdc, but my
image: /vmlinuz
Added Linux (alias lnx) *
Boot other: /dev/hda1, loader /boot/chain.b
Added Windows (alias win)
/boot/boot.0300 exists - no backup copy made.
Writing boot sector.
What does fdisk -l /dev/hda say?
Is the mbr on hda really bootable (* at the fdisk ouput)?
Matth
lilo.conf: change the boot=/dev/hdc into boot=/dev/hda
image=/dev/hdc1 should be already there and it is fine.
and an option other=/dev/hda1 is needed for booting the other os.
I tried that, but LILO hangs with LI-. I did run lilo to update
the MBR - several times. In lilo.conf I have
or Slink
one time. The /mbr is on the Windows 98 disk, Slink is on another. I read
in the mail list that sometimes if the boot sector has virus protection
enabled this type of thing happens but I checked and it is not. Has anyone
had this problem before?
Thanks,
kent
@ www.xyf.webprovider.com
It would help if you posted your /etc/lilo.conf. My first guess is it's
installing lilo on the second disk, rather than the first.
--
++
| Eric G. Milleregm2@jps.net |
| GnuPG public key: http://www.jps.net/egm2/gpg.asc
: Saturday, February 19, 2000 10:52 PM
Subject: Re: Lilo gets wiped off /mbr
It would help if you posted your /etc/lilo.conf. My first guess is it's
installing lilo on the second disk, rather than the first.
--
++
| Eric G. Miller
On Sun, Feb 20, 2000 at 01:05:57AM -0600, ktb wrote:
Here it is:
boot=/dev/hda
root=/dev/hdb1
compact
install=/boot/boot.b
delay=40
map=/boot/map
vga=4
Take it that number means something on your system...
image=/vmlinuz
label=slink
read-only
other=/dev/hda1
hello
how can i install a sort of mbr that runs before lilo ?
because after having instaled debian i need to install a dos
partition, but as hda1 is the swap, hda2 linux and hda3 is dos, lilo
can not load the last partition (far beyong the 1024 kbytes limit)
so, is possible to boot the dos
On 4/12/99 luis wrote:
how can i install a sort of mbr that runs before lilo ?
because after having instaled debian i need to install a dos
partition, but as hda1 is the swap, hda2 linux and hda3 is dos, lilo
can not load the last partition (far beyong the 1024 kbytes limit)
if LILO won't
On Tue, 6 Jul 1999, Felipe Alvarez Harnecker wrote:
Can someone send me a DOS Master Boot record so a can dd it to
/dev/hda?
No, but if you boot a DOS floppy then you can reconstitute it by running
(DOS) fdisk /mbr. Linux fdisk will not do this. This procedure will
not alter your partition
On Tue, Jul 06, 1999 at 10:55:01PM -0400, William T Wilson wrote:
On Tue, 6 Jul 1999, Felipe Alvarez Harnecker wrote:
Can someone send me a DOS Master Boot record so a can dd it to
/dev/hda?
No, but if you boot a DOS floppy then you can reconstitute it by running
(DOS) fdisk /mbr
Can someone send me a DOS Master Boot record so a can dd it to
/dev/hda?
Please answer only if you realy know what i mean because i dont want
to alter the partition table.
Send me version info as well.
Thanks.
--
__
Felipe Alvarez
*- On 6 Jul, Felipe Alvarez Harnecker wrote about DOS MBR
Can someone send me a DOS Master Boot record so a can dd it to
/dev/hda?
Please answer only if you realy know what i mean because i dont want
to alter the partition table.
Send me version info as well.
Thanks.
If you can
iOn Tue, 6 Jul 1999, Felipe Alvarez Harnecker wrote:
Can someone send me a DOS Master Boot record so a can dd it to
/dev/hda?
Please answer only if you realy know what i mean because i dont want
to alter the partition table.
I'm also interested in this, since I have a HD with the MBR
The DOS MBR will only be valid for you from a hard drive with the exact
same paramaters and exact same partition table. (i.e. no one has one you
can use).
What you can do (I have done this before with success) is: (But beware,
this is not guaranteed to work--I have also done this and failed)
1
Felipe Alvarez Harnecker [EMAIL PROTECTED] writes:
Can someone send me a DOS Master Boot record so a can dd it to
/dev/hda?
Please answer only if you realy know what i mean because i dont want
to alter the partition table.
Send me version info as well.
Unless it is a freedos mbr
try:dd man
dd is interesting, but dangerous!!
something like: dd if=/dev/hda /of=bootsec.bla bs=512 count=1
Ciao,
Kotya
Can someone send me a DOS Master Boot record so a can dd it to
/dev/hda?
Please answer only if you realy know what i mean because i dont want
to alter
El Thu, Apr 08, 1999 at 12:11:03PM +0200, Oscar Castell Marcos escribió:
Hola,
Hola
tengo un ordenador con el Linux instalado y estoy interesado en
transformarlo a Win98, ya que me han traido un ordenador nuevo mas
potente con todo para instalar, de manera que el viejo sea Win98 i el
nuevo
Hola a todos y muchas gracias,
ya esta resuelto: con el fdisk /MBR. He logrado instalar los CDs de
Win98 para una maquina nueva en una maquina vieja. Es interesante saber
que estos programas de instalacion revisan el MBR y si existe otro sistema
operativo se niegan a hacer la instalacion
equipos nuevos y al intentar hacer la instalacion no me lo permite
hacer. Entre otras cosas no se como borrar el LILO del MBR y creo que es
eso lo que hace que el programa de instalacion se pare.
Alguien puede decirme que debo hacer para que el ordenador viejo pase
a ser un equipo nuevo sin datos
equipo son licencias unicamente
para equipos nuevos y al intentar hacer la instalacion no me lo
permite hacer. Entre otras cosas no se como borrar el LILO del MBR y
creo que es eso lo que hace que el programa de instalacion se pare.
Alguien puede decirme que debo hacer para que el ordenador
de instalacion de
Win98?
gracias
Si lo que quieres es borrar el MBR prueba
'fdisk C: /mbr', siendo C una partición de MSDOS que esté en el
mismo disco que el Linux. El fdisk es el de MSDOS.
Sino tienes ninguna borra las particiones de Linux, crea una de MSDOS y
luego
equipo son licencias unicamente para
equipos nuevos y al intentar hacer la instalacion no me lo permite hacer.
Entre otras cosas no se como borrar el LILO del MBR y creo que es eso lo
que hace que el programa de instalacion se pare. Alguien puede decirme que
debo hacer para que el ordenador viejo pase
Jose Ballesteros
08/04/99 16.38
To: Oscar Castell Marcos [EMAIL PROTECTED]
cc:
Subject: Re: LILO y MBR (Document link not converted)
Hola,
Hay varias posibilidades:
1) Hay una copia del MBR original en el directorio /boot, se deberia
hacer lo siguiente:
dd
Hola,
Si tienes por ahi floppies con DOS o una version vieja de Winbugs, puedes
bootear con ellos y usar el comando:
FDISK /MBR
Esto reescribe el MBR y deja el MBR original de DOS.
La otra, claro, es bootear con un rescue floppy y darle:
dd if=/dev/zero of=/dev/hda
Con eso te va a poner
Evening all.
Small problem here: seems that Lilo screwed up my MBR for one of the hard
drives, specifically one with Win95 on it.
Here is lilo.conf:
boot = /dev/hda
root = /dev/hdb2
install = /boot/boot.b
map = /boot/map
vga = normal
delay = 50
ramdisk = 0
read-only
default = linux
image
Boot from any DOS 6.X/Win95 bootable diskette and once in the DOS prompt
type fdisk /mbr. This will reinstate your clubbered MBR.
BTW, is there anyway in this list to reply to the list instead of the
author? My problem is I have filtering of incoming emails and it doesn't
work 'coz my filter
:
-BEGIN PGP SIGNED MESSAGE-
On Tue, 24 Nov 1998, Patrick Colbeck wrote:
Following up to my prevous mail is the lilo or mbr shipped with Debian 2
faulty
? When trying to boot from hda3 (hda1 is win98, hda2 is swap) it just says
loading Linux the reboots. It never gets
Reply-To:
Hi
Following up to my prevous mail is the lilo or mbr shipped with Debian 2 faulty
? When trying to boot from hda3 (hda1 is win98, hda2 is swap) it just says
loading Linux the reboots. It never gets to vmlinuz. This is like what
happens when it cant find vmlinuz when you forget
-BEGIN PGP SIGNED MESSAGE-
On Tue, 24 Nov 1998, Patrick Colbeck wrote:
Following up to my prevous mail is the lilo or mbr shipped with Debian 2
faulty
? When trying to boot from hda3 (hda1 is win98, hda2 is swap) it just says
loading Linux the reboots. It never gets to vmlinuz
Debian doesn't install LILO as the MBR, but rather uses a program
called MBR. It is MBR that is presenting this prompt. Look in
/usr/doc/MBR for documentation.
You don't give enough of a description of your installation to
determine the problem. Here's a guess though. It sounds as if
you
in some way to Lilo and the MBR, but don't know what
to do to fix it...
Please respond to my email as well as the list, since I read the list only
through the web pages, and need an answer fairly soon (since we may need to
cancel the course...).
Cheers
-duncan
Thanx to everyone who responded to my request about removing mbr. Since
Linux is the only OS installed on the machine in question, I have
reconfigured LILO to install in the MBR. Seems to have had the intended
effect.
Thanx!
I was wondering how hard it is to remove/replace the mbr package. We have
a single system running hamm, for which we want to disable the capability
of booting from a diskette. Currently we've disabled floppy-boot in the
BIOS, and configured LILO to require a password (only if kernel-options
On Fri, 14 Aug 1998, Gregory T. Norris wrote:
: I was wondering how hard it is to remove/replace the mbr package. We have
: a single system running hamm, for which we want to disable the capability
: of booting from a diskette. Currently we've disabled floppy-boot in the
: BIOS
On Fri, 14 Aug 1998, Gregory T. Norris wrote:
I was wondering how hard it is to remove/replace the mbr package. We have
a single system running hamm, for which we want to disable the capability
of booting from a diskette. Currently we've disabled floppy-boot in the
BIOS, and configured
Please check to see that lilo has the right parameters for your harddisk
Particularly the bits about Large, LBA ...
--Jonathan
Lil- comes up on the screen and the system hangs
(Just glad I have a recent kernel boot disk =) )
/boot/boot.hda doesn't exist.
I have no WinNT installation
701 - 800 of 831 matches
Mail list logo
