Linux-Misc Digest #436, Volume #25 Sun, 13 Aug 00 13:13:02 EDT
Contents:
Re: masquerading (David Efflandt)
Re: Red Hat 6.2 can't detect my FAT32 partition:( (Leonard Evens)
Re: Saving and Restoring an MBR ("Torstein Pettersen")
Not Recognising eth1 (Fester)
Re: Attn: Bob M (Frank Hahn)
Re: masquerading (William W.)
Re: how and where do I get linux? (Michael Mitchell)
Re: Can not wearch website?!
Re: Accessing NTSC-partitions (Dances With Crows)
Re: Saving and Restoring an MBR (Randy Cooper)
----------------------------------------------------------------------------
From: [EMAIL PROTECTED] (David Efflandt)
Subject: Re: masquerading
Date: Sun, 13 Aug 2000 15:13:02 +0000 (UTC)
Reply-To: [EMAIL PROTECTED]
On Sun, 13 Aug 2000 15:57:26 +0200, Andy <[EMAIL PROTECTED]> wrote:
>I have a problem with the nameresolving. I have installed masquerading on my
>linux-computer. Now I'm able to ping a host in the internet from my
>win-machine, but only if I use the ip, not the name, for example:
>
>ping 194.242.164.57 works
>ping www.linux.org doesn't work
What do you have set for nameservers on your Windows box? Unless you are
running local DNS, you have to point it to your ISP's nameservers (which
requires the ever popular Windows reboot).
--
David Efflandt [EMAIL PROTECTED] http://www.de-srv.com/
http://www.autox.chicago.il.us/ http://www.berniesfloral.net/
http://hammer.prohosting.com/~cgi-wiz/ http://cgi-help.virtualave.net/
------------------------------
From: Leonard Evens <[EMAIL PROTECTED]>
Subject: Re: Red Hat 6.2 can't detect my FAT32 partition:(
Date: Sun, 13 Aug 2000 10:04:59 -0500
[EMAIL PROTECTED] wrote:
>
> The problem is that RHL doesn't show it so I can mount it . If you know
> any way so I can make it apear in my partition list . I can mount it
> myself .
> Pouria
> >
> > [EMAIL PROTECTED] wrote:
> >
> > > I have win98 and RHL 6.2 . I have a FAT16 and a FAT32 and of course
> EXT2 .
> > > I have a lot of data on my FAT32 but I can not access it with Red
> Hat . I
> > > don't know what to do . Please help me .
> > > Pouria
> > >
> > > --
RedHat 6.2 has no trouble seeing a FAT32 partition or multiple
Windows partitions of different types. Also, assuming you are
using the generic kernel (which would be the case if you didn't
try to compile and install your own kernel), you don't have to
fiddle with the kernel. I know this because I have done it many
times.
You say your Linux installation doesn't show the partition you
want to mount under Linux. Just what do you mean by that?
Can you execute
fdisk -l
and report the results? It is possible the above might not work
and you might have to specify the device as in
fdisk -l /dev/hda
for a single IDE disk on the first IDE interface. If you have
more than one disk or some exotic arrangement, let us know.
If this is what your tried (or something equivalent) then
there is something bizarre about your setup. Give us as many
details as possible.
Also, let us know how you created these partitions in the first
place.
It is possible that you never put an entry for the partition you
can't mount in /etc/fstab. There are a variety of ways of doing
this. For example, it can be done through linuxconf, but certainly
the simplest would be by editing the file directly. Let us know
what is in that file by using the command
more /etc/fstab
By comparing the results of the fdisk listing (which shows all
the partitions Linux sees) and /etc/fstab, it may be clearer to
us just what is going on.
Again, let me say there is absolutely no reason why with the
generic RH 6.2 kernel you shouldn't be able to mount any and
all FAT32 or FAT16 partitions you may have.
--
Leonard Evens [EMAIL PROTECTED] 847-491-5537
Dept. of Mathematics, Northwestern Univ., Evanston, IL 60208
------------------------------
From: "Torstein Pettersen" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: Re: Saving and Restoring an MBR
Date: Sun, 13 Aug 2000 17:45:52 +0200
It's much simpler to just boot with a win9x startup disk
and type: fdisk /MBR.
The /MBR parameter for fdisk undocumented, but it works.
(/MBR stands for Master Boot Restore).
Torstein
"Randy Cooper" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> I have noticed a lot of questions regarding recovering lost / damaged
> Master Boot Records (MBR) lately. So I thought it was about time to
> repost this.
>
> You should make a backup copy of your MBR on a bootable floppy disk
> before installing Linux and then again after installing Linux.
>
> ------------------------------------------------------------
>
> I can suggest two ways that you can back up the Master Boot Record (MBR)
>
> on an IDE drive under Windows and DOS.
>
> 1. Use the Norton Utilities.
>
> 2. Use Debug, as found in DOS, it is also available from the DOS prompt
> in Windows/95 so I assume it is also available in Windows/98.
>
> Enter the following commands to save the MBR on the C drive, ignore
> the text after the '<=' on each line as it is only a comment:
>
> DEBUG MBR.DAT <= Ignore the FILE NOT FOUND message
> A <= Assemble a program
> MOV DX,9000 <= Use segment 9000
> MOV ES,DX <= Setup the segment register
> XOR BX,BX <= Clear BX to zero
> MOV CX,0001 <= Start at track 00 sector 01, the MBR
> MOV DX,0080 <= 80=C:, 81=D:, 00=A:, 01=B:
> MOV AX,0201 <= Read 1 sector, 02=read
> INT 13 <= BIOS disk i/o call
> INT 20 <= Return to o/s
> <= Press the return key to end program entry
> G <= Execute the program
> R CX <= Display the value of CX
> :200 <= Change the value of CX to decimal 512, size of
> MBR
> W 9000:00 <= Write the sector stored at address 9000 to
> MBR.DAT
> Q <= exit DEBUG
>
> If you examine the contents of MBR.DAT using a disk file editor the last
>
> 2 bytes must be AA55.
>
> At this point you should copy the MBR to a bootable floppy along with
> DEBUG.EXE
>
> This technique may be used to recover the MBR as well, assuming you can
> boot from another device (say a floppy with DEBUG.EXE on it).
>
> Enter the following commands to restore the MBR on the C drive, ignore
> the text after the '<=' on each line as it is only a comment:
>
> DEBUG MBR.DAT <= The file containing the desired MBR, if you
> get a
> FILE NOT FOUND message type Q immediately! If
> you
> continue you will write garbage over the MBR.
> L 9000:00 <= Load the MBR into memory at this address
> A <= Assemble a program
> MOV DX,9000 <= The segment address containing the MBR
> MOV ES,DX <= Setup the segment address
> XOR BX,BX
> MOV CX,0001 <= Track 00, sector 01
> MOV DX,0080 <= 80=C:
> MOV AX,0301 <= Write one sector, 03=write
> INT 13
> INT 20
> <= Press the enter key to stop program entry
> G <= Execute the program
> Q <= Exit DEBUG
>
> The MBR should now be restored to the C drive, making it bootable.
>
> For more information on this technique for saving and restoring an MBR I
>
> refer you the book 'The Complete PC Upgrade and Maintenance Guide' by
> Mark
> Minasi, published by Sybex.
>
> Once you have Linux running you can save the boot record with the
> command:
>
> dd if=/dev/hda of=/boot/boot.MBR bs=512 count=1
>
> It can then be restored with:
>
> dd if=/boot/boot.MBR of=/dev/hda bs=512 count=1
>
> or if you do not want/need to overwrite the partition table with:
>
> dd if=/boot/boot.MBR of=/dev/hda bs=446 count=1
>
> as the partition table is kept in the last 66 bytes of the MBR.
>
> DISCLAIMER:
> Although I have double checked the above, I cannot be held responsible
>
> for any errors. I suggest you try it on a bootable floppy disk before
> using it on a hard drive. If it does not work on a floppy disk let me
> know.
>
> BTW: I find it easier to boot Linux from a floppy disk or CD-ROM than to
>
> recover an MBR from DOS. The Slackware 3.5 (or greater) CD-ROM
> makes a
> good rescue disk if you have a bios that supports bootable CDs.
>
>
>
>
> I can suggest two ways that you can back up the Master Boot Record (MBR)
> on an
> IDE drive under Windows and DOS.
>
> 1. Use the Norton Utilities.
>
> 2. Use Debug, as found in DOS, it is also available from the DOS prompt
> in
> Windows/95 so I assume it is also available in Windows/98.
>
> Enter the following commands to save the MBR on the C drive, ignore
> the text
> after the '<=' on each line as it is only a comment:
>
> DEBUG MBR.DAT <= Ignore the FILE NOT FOUND message
> A <= Assemble a program
> MOV DX,9000 <= Use segment 9000
> MOV ES,DX <= Setup the segment register
> XOR BX,BX <= Clear BX to zero
> MOV CX,0001 <= Start at track 00 sector 01, the MBR
> MOV DX,0080 <= 80=C:, 81=D:, 00=A:, 01=B:
> MOV AX,0201 <= Read 1 sector, 02=read
> INT 13 <= BIOS disk i/o call
> INT 20 <= Return to o/s
> <= Press the return key to end program entry
> G <= Execute the program
> R CX <= Display the value of CX
> :200 <= Change the value of CX to decimal 512, size of
> MBR
> W 9000:00 <= Write the sector stored at address 9000 to
> MBR.DAT
> Q <= exit DEBUG
>
> If you examine the contents of MBR.DAT using a disk file editor the last
> 2
> bytes must be AA55.
>
> At this point you should copy the MBR to a bootable floppy along with
> DEBUG.EXE
>
> This technique may be used to recover the MBR as well, assuming you can
> boot
> from another device (say a floppy with DEBUG.EXE on it).
>
> Enter the following commands to restore the MBR on the C drive, ignore
> the text
> after the '<=' on each line as it is only a comment:
>
> DEBUG MBR.DAT <= The file containing the desired MBR, if you
> get a
> FILE NOT FOUND message type Q immediately! If
> you
> continue you will write garbage over the MBR.
> L 9000:00 <= Load the MBR into memory at this address
> A <= Assemble a program
> MOV DX,9000 <= The segment address containing the MBR
> MOV ES,DX <= Setup the segment address
> XOR BX,BX
> MOV CX,0001 <= Track 00, sector 01
> MOV DX,0080 <= 80=C:
> MOV AX,0301 <= Write one sector, 03=write
> INT 13
> INT 20
> <= Press the enter key to stop program entry
> G <= Execute the program
> Q <= Exit DEBUG
>
> The MBR should now be restored to the C drive, making it bootable.
>
> For more information on this technique for saving and restoring an MBR I
> refer
> you the book 'The Complete PC Upgrade and Maintenance Guide' by Mark
> Minasi,
> published by Sybex.
>
> Once you have Linux running you can save the boot record with the
> command:
>
> dd if=/dev/hda of=/boot/boot.MBR bs=512 count=1
>
> It can then be restored with:
>
> dd if=/boot/boot.MBR of=/dev/hda bs=512 count=1
>
> or if you do not want/need to overwrite the partition table with:
>
> dd if=/boot/boot.MBR of=/dev/hda bs=446 count=1
>
> as the partition table is kept in the last 66 bytes of the MBR.
>
> DISCLAIMER:
> Although I have double checked the above, I cannot be held responsible
>
> for any errors. I suggest you try it on a bootable floppy disk before
> using it on a hard drive. If it does not work on a floppy disk let me
> know.
>
> BTW: I find it easier to boot Linux from a floppy disk or CD-ROM than to
>
> recover an MBR from DOS. The Slackware 3.5 (or greater) CD-ROM
> makes a
> good rescue disk if you have a bios that supports bootable CDs.
>
>
> --
> Reply to: [EMAIL PROTECTED] (mail checked week nights and weekends)
>
>
>
------------------------------
From: [EMAIL PROTECTED] (Fester)
Subject: Not Recognising eth1
Reply-To: [EMAIL PROTECTED]
Date: Sun, 13 Aug 2000 16:04:48 GMT
Okay, I have two identical ne2000 cards in my computer. They are both
Linksys Ether16 ISA cards. The first one, eth0, has been running fine for
6 or 7 months, it uses I/O 0x300 and IRQ 3.
I just installed eth1, and I'm having some problems. According to Linksys'
website, I need to take the card out of PnP mode. I did that by booting to
DOS with a floppy and running the Linksys setup program. PnP was telling
the second card to use I/O 0x2A0 and IRQ 11. So I switched off PnP and set
those values manually. (I kept them the same, I just turned PnP off)
I rebooted into Linux and edited /etc/conf.modules, per the "Red Hat Linux
6.X as an Internet Gateway for a Home Network" HOWTO on Linuxdoc.org. My
conf.modules reads:
alias eth0 ne
alias eth1 ne
options ne io=0x300,0x2A0 irq=3,11
ifconfig still tells me that eth1 is not found. If I reboot the machine,
eth1 fails to initialize on boot.
Can anyone provide help?
--
-- Fester
"Anyone can create 'smart' sentences
by using 'one', 'thus', or 'hence'."
-Tomo
"Thus, one is inclined to laugh at
anything Tomo says hence." -Dexter
======================================
------------------------------
From: [EMAIL PROTECTED] (Frank Hahn)
Subject: Re: Attn: Bob M
Date: Sun, 13 Aug 2000 16:09:46 GMT
Reply-To: [EMAIL PROTECTED]
On Sun, 13 Aug 2000 03:18:26 +0000, Bob Martin <[EMAIL PROTECTED]> wrote:
>If you can't get into your BIOS I would say your machine is hosed. I do
>remember something about some compaq models that stored part their BIOS
>on the HD, something like BM or PM might hose them. When you boot the
>machine you should get a message telling you what key sequence to press
>to enter setup ( BIOS ) , many use the delete key of F2
>
Some Compaqs (maybe all?) come with the BIOS stored on the harddrive
and not in a BIOS chip that most motherboards use. This data is stored
on something like the first 4MBs of the hard drive. I believe it is
the F10 key that needs to be hit. A search of http://www.deja.com
may give more specific answers.
Compaq has these BIOS files for download and there are web pages that
I have found on the Internet that give details on restoring this area
of the hard drive.
--
Frank Hahn
Government [is] an illusion the governed should not encourage.
-- John Updike, "Couples"
------------------------------
From: [EMAIL PROTECTED] (William W.)
Subject: Re: masquerading
Date: Sun, 13 Aug 2000 16:11:18 GMT
In our last episode (Sun, 13 Aug 2000 15:57:26 +0200),
the artist formerly known as Andy said:
>I have a problem with the nameresolving. I have installed masquerading on my
>linux-computer. Now I'm able to ping a host in the internet from my
>win-machine, but only if I use the ip, not the name, for example:
>
>ping 194.242.164.57 works
>ping www.linux.org doesn't work
>
Do you have a valid DNS server address or addresses in /etc/resolv.conf?
At minimum, the file should look something like:
order hosts,bind
nameserver 11.22.33.44
nameserver 11.22.33.45
With those IP addresses replaced with your DNS server addresses.
There's more info in the resolv.conf manpage.
HTH.
--
It is pitch black.
You are likely to be spammed by a grue.
------------------------------
From: Michael Mitchell <[EMAIL PROTECTED]>
Subject: Re: how and where do I get linux?
Date: Sun, 13 Aug 2000 16:12:21 GMT
I've been fiddling with Linux now for about 2 years and some of the
distributions have books that you can print off of a CD. I promise you t=
hat the
best thing is too get every little scrap of info you can. Buy yourself a=
lot of
good quality paper and print books, how-to's, etc. One of the worst thin=
gs (in
my opinion) that happens, is too be half-way through an install and be
ill-informed about the computer you are working on. If a particular piec=
e of
hardware gives you trouble, read the how-to's/ print them. Write down al=
l the
info you can on your sound card, modem/ethernet card, video card, printer=
, etc.
Check the compatibility list! Start at http://www.linux.org and if the i=
nfo you
need isn't there, you could bet good money that it links to somewhere tha=
t
covers the subject. There is a Spanish how-to and probably many sites wr=
itten
in Spanish on Linux distributions.
Stanislaw Flatto wrote:
> Noe Nieto wrote:
> >
> > hello :
> >
> > I=B4m a windows user and i want to change my system, i tried to dow=
nload
> > the caldera system open linux at their ftp server but some times my s=
ystem
> > don=B4t understand the format of the files.
> > please i really thank information about getting started on linux.
> >
> > P.D. I live in mexico, so my english is not the best sorry :-)
> >
> > --
> > Posted via CNET Help.com
> > http://www.help.com/
>
> Welcome to Linux-land!
> Your "English" is much better than that of natives where I live.
> For first time adventurer I would strongly recommend getting distro on
> CD/CD's.
> Downloading whole distribution is for someone who can recognise a
> mistake if the download misses. This comes with time.
> Have fun...
>
> --
> Stanislaw on Slak 7.1
> Slacker No.162760 on Linux counter.
> *******Are we having fun????*******
------------------------------
From: <[EMAIL PROTECTED]>
Subject: Re: Can not wearch website?!
Date: Sun, 13 Aug 2000 16:29:53 GMT
I think the file you need is /etc/resolv.conf not resolv.con. You can test
the connection by trying to ping a website. Try ping yahoo.com at the
command line and see if you get a response. Press Ctrl-C to stop the query
or it will go on for a long time.
jeff wrote:
>
>
> On Sun, 13 Aug 2000 10:47:15 +0800, sammi <[EMAIL PROTECTED]> wrote:
> >I'm a new user for Linux. Currently, I have a problem with to view the
> >wedsite. It's sound strange because my system can detect my modem but
when I
> >use Netscape to search the particular website then it will pop up a
message
> >like "Unable to locate the server nam(eg:http://www.hotmail.com) comand
> >check it and try again. Somemore like hosts are unknown and some of the
> >hosts unreachable.
> >
> >And I need to be online ASAP. Your help is much appreciated. Thanks.
> >
>
> May be that you're just not pointing to a valid DNS server. Look at
> /etc/resolv.con (that's where it is on my system, at any rate). What you
> see there should match the DNS server that your ISP makes available (or
any
> other valid nameserver).
>
> -jeff
--
Posted via CNET Help.com
http://www.help.com/
------------------------------
From: [EMAIL PROTECTED] (Dances With Crows)
Subject: Re: Accessing NTSC-partitions
Date: 13 Aug 2000 16:34:30 GMT
Reply-To: [EMAIL PROTECTED]
On 13 Aug 2000 01:37:00 +0100, Sandy Drobic wrote:
>Nothing to do, so I decided to bore you with:
>In SuSE Linux I can only access an NTSC partition in write protect mode.
>How do I get a write access?
NTSC is National Television Standards Committee, the broadcast format
used for TV in the USA. I had no idea there was a partition type dedicated
solely for storing images in that format :-]
If you mean "NTFS", write support for NTFS partitions is in the
experimental stages and trying it out can easily corrupt your
filesystem. You must either recompile the kernel or compile a couple of
modules, saying Y or M to "NTFS Read Support" and "NTFS Write Support
(DANGEROUS)" inside of "make menuconfig" or "make xconfig".
--
Matt G|There is no Darkness in Eternity/But only Light too dim for us to see
Brainbench MVP for Linux Admin / Those who do not understand Unix are
http://www.brainbench.com / condemned to reinvent it, poorly.
=============================/ ==Henry Spencer
------------------------------
From: Randy Cooper <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: Re: Saving and Restoring an MBR
Date: Sun, 13 Aug 2000 11:47:39 -0500
That will only work if you want a generic DOS MBR. What if you want to recover
the MBR after Linux has been installed and overwritten the MBR to use with
LILO?
Torstein Pettersen wrote:
> It's much simpler to just boot with a win9x startup disk
> and type: fdisk /MBR.
>
> The /MBR parameter for fdisk undocumented, but it works.
> (/MBR stands for Master Boot Restore).
>
> Torstein
>
> "Randy Cooper" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]...
> > I have noticed a lot of questions regarding recovering lost / damaged
> > Master Boot Records (MBR) lately. So I thought it was about time to
> > repost this.
> >
> > You should make a backup copy of your MBR on a bootable floppy disk
> > before installing Linux and then again after installing Linux.
> >
> > ------------------------------------------------------------
> >
> > I can suggest two ways that you can back up the Master Boot Record (MBR)
> >
> > on an IDE drive under Windows and DOS.
> >
> > 1. Use the Norton Utilities.
> >
> > 2. Use Debug, as found in DOS, it is also available from the DOS prompt
> > in Windows/95 so I assume it is also available in Windows/98.
> >
> > Enter the following commands to save the MBR on the C drive, ignore
> > the text after the '<=' on each line as it is only a comment:
> >
> > DEBUG MBR.DAT <= Ignore the FILE NOT FOUND message
> > A <= Assemble a program
> > MOV DX,9000 <= Use segment 9000
> > MOV ES,DX <= Setup the segment register
> > XOR BX,BX <= Clear BX to zero
> > MOV CX,0001 <= Start at track 00 sector 01, the MBR
> > MOV DX,0080 <= 80=C:, 81=D:, 00=A:, 01=B:
> > MOV AX,0201 <= Read 1 sector, 02=read
> > INT 13 <= BIOS disk i/o call
> > INT 20 <= Return to o/s
> > <= Press the return key to end program entry
> > G <= Execute the program
> > R CX <= Display the value of CX
> > :200 <= Change the value of CX to decimal 512, size of
> > MBR
> > W 9000:00 <= Write the sector stored at address 9000 to
> > MBR.DAT
> > Q <= exit DEBUG
> >
> > If you examine the contents of MBR.DAT using a disk file editor the last
> >
> > 2 bytes must be AA55.
> >
> > At this point you should copy the MBR to a bootable floppy along with
> > DEBUG.EXE
> >
> > This technique may be used to recover the MBR as well, assuming you can
> > boot from another device (say a floppy with DEBUG.EXE on it).
> >
> > Enter the following commands to restore the MBR on the C drive, ignore
> > the text after the '<=' on each line as it is only a comment:
> >
> > DEBUG MBR.DAT <= The file containing the desired MBR, if you
> > get a
> > FILE NOT FOUND message type Q immediately! If
> > you
> > continue you will write garbage over the MBR.
> > L 9000:00 <= Load the MBR into memory at this address
> > A <= Assemble a program
> > MOV DX,9000 <= The segment address containing the MBR
> > MOV ES,DX <= Setup the segment address
> > XOR BX,BX
> > MOV CX,0001 <= Track 00, sector 01
> > MOV DX,0080 <= 80=C:
> > MOV AX,0301 <= Write one sector, 03=write
> > INT 13
> > INT 20
> > <= Press the enter key to stop program entry
> > G <= Execute the program
> > Q <= Exit DEBUG
> >
> > The MBR should now be restored to the C drive, making it bootable.
> >
> > For more information on this technique for saving and restoring an MBR I
> >
> > refer you the book 'The Complete PC Upgrade and Maintenance Guide' by
> > Mark
> > Minasi, published by Sybex.
> >
> > Once you have Linux running you can save the boot record with the
> > command:
> >
> > dd if=/dev/hda of=/boot/boot.MBR bs=512 count=1
> >
> > It can then be restored with:
> >
> > dd if=/boot/boot.MBR of=/dev/hda bs=512 count=1
> >
> > or if you do not want/need to overwrite the partition table with:
> >
> > dd if=/boot/boot.MBR of=/dev/hda bs=446 count=1
> >
> > as the partition table is kept in the last 66 bytes of the MBR.
> >
> > DISCLAIMER:
> > Although I have double checked the above, I cannot be held responsible
> >
> > for any errors. I suggest you try it on a bootable floppy disk before
> > using it on a hard drive. If it does not work on a floppy disk let me
> > know.
> >
> > BTW: I find it easier to boot Linux from a floppy disk or CD-ROM than to
> >
> > recover an MBR from DOS. The Slackware 3.5 (or greater) CD-ROM
> > makes a
> > good rescue disk if you have a bios that supports bootable CDs.
> >
> >
> >
> >
> > I can suggest two ways that you can back up the Master Boot Record (MBR)
> > on an
> > IDE drive under Windows and DOS.
> >
> > 1. Use the Norton Utilities.
> >
> > 2. Use Debug, as found in DOS, it is also available from the DOS prompt
> > in
> > Windows/95 so I assume it is also available in Windows/98.
> >
> > Enter the following commands to save the MBR on the C drive, ignore
> > the text
> > after the '<=' on each line as it is only a comment:
> >
> > DEBUG MBR.DAT <= Ignore the FILE NOT FOUND message
> > A <= Assemble a program
> > MOV DX,9000 <= Use segment 9000
> > MOV ES,DX <= Setup the segment register
> > XOR BX,BX <= Clear BX to zero
> > MOV CX,0001 <= Start at track 00 sector 01, the MBR
> > MOV DX,0080 <= 80=C:, 81=D:, 00=A:, 01=B:
> > MOV AX,0201 <= Read 1 sector, 02=read
> > INT 13 <= BIOS disk i/o call
> > INT 20 <= Return to o/s
> > <= Press the return key to end program entry
> > G <= Execute the program
> > R CX <= Display the value of CX
> > :200 <= Change the value of CX to decimal 512, size of
> > MBR
> > W 9000:00 <= Write the sector stored at address 9000 to
> > MBR.DAT
> > Q <= exit DEBUG
> >
> > If you examine the contents of MBR.DAT using a disk file editor the last
> > 2
> > bytes must be AA55.
> >
> > At this point you should copy the MBR to a bootable floppy along with
> > DEBUG.EXE
> >
> > This technique may be used to recover the MBR as well, assuming you can
> > boot
> > from another device (say a floppy with DEBUG.EXE on it).
> >
> > Enter the following commands to restore the MBR on the C drive, ignore
> > the text
> > after the '<=' on each line as it is only a comment:
> >
> > DEBUG MBR.DAT <= The file containing the desired MBR, if you
> > get a
> > FILE NOT FOUND message type Q immediately! If
> > you
> > continue you will write garbage over the MBR.
> > L 9000:00 <= Load the MBR into memory at this address
> > A <= Assemble a program
> > MOV DX,9000 <= The segment address containing the MBR
> > MOV ES,DX <= Setup the segment address
> > XOR BX,BX
> > MOV CX,0001 <= Track 00, sector 01
> > MOV DX,0080 <= 80=C:
> > MOV AX,0301 <= Write one sector, 03=write
> > INT 13
> > INT 20
> > <= Press the enter key to stop program entry
> > G <= Execute the program
> > Q <= Exit DEBUG
> >
> > The MBR should now be restored to the C drive, making it bootable.
> >
> > For more information on this technique for saving and restoring an MBR I
> > refer
> > you the book 'The Complete PC Upgrade and Maintenance Guide' by Mark
> > Minasi,
> > published by Sybex.
> >
> > Once you have Linux running you can save the boot record with the
> > command:
> >
> > dd if=/dev/hda of=/boot/boot.MBR bs=512 count=1
> >
> > It can then be restored with:
> >
> > dd if=/boot/boot.MBR of=/dev/hda bs=512 count=1
> >
> > or if you do not want/need to overwrite the partition table with:
> >
> > dd if=/boot/boot.MBR of=/dev/hda bs=446 count=1
> >
> > as the partition table is kept in the last 66 bytes of the MBR.
> >
> > DISCLAIMER:
> > Although I have double checked the above, I cannot be held responsible
> >
> > for any errors. I suggest you try it on a bootable floppy disk before
> > using it on a hard drive. If it does not work on a floppy disk let me
> > know.
> >
> > BTW: I find it easier to boot Linux from a floppy disk or CD-ROM than to
> >
> > recover an MBR from DOS. The Slackware 3.5 (or greater) CD-ROM
> > makes a
> > good rescue disk if you have a bios that supports bootable CDs.
> >
> >
> > --
> > Reply to: [EMAIL PROTECTED] (mail checked week nights and weekends)
> >
> >
> >
--
Reply to: [EMAIL PROTECTED] (mail checked week nights and weekends)
------------------------------
** FOR YOUR REFERENCE **
The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: [EMAIL PROTECTED]
You can send mail to the entire list (and comp.os.linux.misc) via:
Internet: [EMAIL PROTECTED]
Linux may be obtained via one of these FTP sites:
ftp.funet.fi pub/Linux
tsx-11.mit.edu pub/linux
sunsite.unc.edu pub/Linux
End of Linux-Misc Digest
******************************
