You are not logged in. Login Now
 0-24   25-49   50-74   75-99   100-124   125-149   138-162   163-187   188-212 
 213-237   238-257         
 
Author Message
25 new of 257 responses total.
raven
response 163 of 257: Mark Unseen   Oct 21 22:55 UTC 1999

I have a somewhat unusual situation. I have a computer with 3 hd windows
on c and Mandrake Linux on e.  When I originally installed Linux it
wiped out the master boot record on c Win98 so it wouldn't boot.
Scott helped me fix that by suggesting I do fdisk/mbr from the win98
boot disk which fixed the problem so win98 boots now.

My question is can I install lilo on the e drive so I can set it up as
a dual boot machine?  If so how do I do this? I have the Mandrake
6.0 cd-rom (which is esentialy red hat 6.0).

Also Linux won't recogonize my pci (non win modem) which seems to be on
com 5 for some reason, there seems to be no option for setting ttyS4
on kpppd the Kde x windows interface for pppd.

Thanks for any help rendered!
pfv
response 164 of 257: Mark Unseen   Oct 22 01:13 UTC 1999

        As I understand lilo: It still would use the MBR on C:, but if
        you have E: set up with a /boot partition, it can reach it fine.

        I myself have DOS living on the front half of C, and the rest of C
        and all of D are RedHat.. I gave myself a 2M /boot and there seems
        to be no problem at all, placing it on C or D. In my case, I stuck
        the /boot partition on the C drive with /dos and, /root (or / - I
        can't recall).

        Now, if we just had a neat way to restore OUR "mbr" after doze got
        thru mangling it ;-)
pfv
response 165 of 257: Mark Unseen   Oct 22 01:17 UTC 1999

        Don't use kpppd <shrug>.
gull
response 166 of 257: Mark Unseen   Oct 22 05:27 UTC 1999

Re #164: Yeah...I wish Linux had a DOS utility to replace a damaged lilo,
but since lilo doesn't understand the filesystem and needs the kernel
location hard-coded in, that's not really practical.

FreeBSD's 'EasyBoot' program (which is really just a partition-selector --
the actual bootstrap program is in the boot block of the FreeBSD partition)
can be installed from a DOS floppy.

FreeBSD recently changed to a new bootstrap program, and I'm not sure if I
like it or not.  It's more reminiscent of a SPARC boot ROM than the old
bootstrap was, and is probably a bit more intuitive than the old one.  It
has the same functionality; you can still boot any file in the root
filesystem, on the fly.  I've had a little trouble getting it to remember my
IRQ settings and such (FreeBSD lets you configure them at boot time), but
that's probably due to my using a 3.2-RELEASE kernel with 3.1-RELEASE rc
scripts.  For now I've been fixing it by compiling in the settings I need
when I build the kernel, but I should fix it properly one of these days.
raven
response 167 of 257: Mark Unseen   Oct 22 06:52 UTC 1999

I'm afraid this doesn't quite answer my question (go slow I'm a newbie to
Linux).  How exactly do I put lilo somewhere other than the space occupied by
windozembr?  I need windoze for apps like Pagemaker, Homepage, etc, so I can't
just trash it.  Botting Linux from a floppy would be fine as well.  My
understanding is that the bot image for linux is on my e: drive (maybe hc5). 
Is there a file I can configure on my boot floppy to int to this so I don't
have to reinstall Linux?  Again thanks for any help rendered. Ignore typos, I'm
too lazy to fix them. :-)
goose
response 168 of 257: Mark Unseen   Oct 23 20:04 UTC 1999

I need a RedHat 5.2 bootfloppy.  Is there a way to make one of these from 
DOS/Win95?  Actually what I really need is the install floppy, not just the
boot floppy.
pfv
response 169 of 257: Mark Unseen   Oct 23 22:45 UTC 1999

 re: 167..
        "Read My Lips.." Lilo lives in the MBR - there is only ONE MBR.
        It stores either the 95 bootstrap, or the the lilo bootstrap.
        The difference IS, lilo can play any field - win95 is selfish and
        self-centered.
pfv
response 170 of 257: Mark Unseen   Oct 23 22:53 UTC 1999

re 168..
        Rawwrite..

 ls -al /mnt/cdrom/images
total 4343
dr-xr-xr-x   3 root     root         2048 Jan 13  1999 .
dr-xr-xr-x  14 root     root         4096 Jan 13  1999 ..
-r--r--r--   1 root     root          235 Jan 13  1999 TRANS.TBL
-r-xr-xr-x   1 root     root         2048 Jan 13  1999 boot.catalog
-r--r--r--   1 root     root      1474560 Jan 13  1999 boot.img
dr-xr-xr-x   2 root     root         2048 Jan 10  1999 oldones
-r--r--r--   1 root     root      1474560 Oct 13  1998 rescue.img
-r--r--r--   1 root     root      1474560 Jan 13  1999 supp.img

 ls -al /mnt/cdrom/dosutils
total 411
dr-xr-xr-x   6 root     root         4096 Nov  3  1998 .
dr-xr-xr-x  14 root     root         4096 Jan 13  1999 ..
-r--r--r--   1 root     root          332 Jun  5  1997 README
-r--r--r--   1 root     root          706 Jan 13  1999 TRANS.TBL
dr-xr-xr-x   2 root     root         2048 Nov  3  1998 autoboot
-r--r--r--   1 root     root           62 Jul 15  1998 autoboot.bat
-r--r--r--   1 root     root        17982 Jun  5  1991 copying
-r--r--r--   1 root     root       172096 Oct 14  1998 fips.exe
dr-xr-xr-x   4 root     root         2048 Nov  3  1998 fips15c
dr-xr-xr-x   4 root     root         2048 Nov  3  1998 fips20
dr-xr-xr-x   2 root     root         2048 Nov  3  1998 fipsdocs
-r--r--r--   1 root     root        39910 Jul 28  1996 gzip.exe
-r--r--r--   1 root     root        32208 Aug 22  1996 loadlin.exe
-r--r--r--   1 root     root        87210 Jan 13  1997 lodlin16.tgz
-r--r--r--   1 root     root        14305 Jul 28  1996 rawrite.exe
-r--r--r--   1 root     root         2017 Jul 28  1996 rawrite3.doc
-r--r--r--   1 root     root         9480 Jul 28  1996 rdev.exe
-r--r--r--   1 root     root        13614 Aug 23  1995 restorrb.exe

raven
response 171 of 257: Mark Unseen   Oct 24 05:53 UTC 1999

re # 169 If this is the case how do I configure lilo so I can dual boot?
I thought you could use a floppy to boot linux as well.  This option probably
actually makes sense for me as I want to learn Linux slowly so I can learn
how to set up an apache web server. However my main productivity apps are in
Win98, I wish it were different, I know Micro$oft is evil, however I can't just
throw away all my desktop publishing and web development software on principle
<shrug>.  Anyway also please keep it simple i.e. tell me the name of files I
need to edit to configure lilo, the content to place in the files, the

location of the files and where they should be saved to.  The only way to
grow the Linux community and overthrow Micr0$oft in my opinion is too
make it easy enough for low level pseudo geeks like myself to install. 1/2
:-) <set micro rant="off> Thanks again for any help rendered.
pfv
response 172 of 257: Mark Unseen   Oct 24 06:49 UTC 1999

the file is /etc/lilo.conf.

you run lilo to reset it.

here's my /etc/lilo.conf:
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
verbose=1
compact
image=/boot/bzImage-2.2.12
        label=2.2.12
        root=/dev/hda7
        read-only
image=/boot/bzImage-2.0.36
        label=YESppp
        root=/dev/hda7
        read-only
image=/boot/vmlinuz-2.0.36-0.7
        label=NOppp
        root=/dev/hda7
        read-only
other=/dev/hda1
        label=dos
        table=/dev/hda
gull
response 173 of 257: Mark Unseen   Oct 25 02:28 UTC 1999

You can create a Linux boot floppy.  I believe putting in a formatted floppy
disk and executing the following command from Linux will do it:

dd if=/boot/vmlinuz of=/dev/fd0

You'll probably have to be root to do this.  I haven't done it in a long
time, but I think that should create a very basic boot floppy for you.
raven
response 174 of 257: Mark Unseen   Oct 25 06:30 UTC 1999

re #173 Ah but you see I can't boot now because I had to replace my win98
mbr, which seems to have trashed lilo. I suppose I could I could disconnect
the ide cables from my win hds and reinstall Linux on this drive?
pfv
response 175 of 257: Mark Unseen   Oct 25 13:37 UTC 1999

        This is why you created that bootdisk, right?
gull
response 176 of 257: Mark Unseen   Oct 25 19:44 UTC 1999

Re #174: Download the boot/rescue floppies for your distribution, and use
RAWRITE to write them out.  That will let you boot your linux installation. 
You'll probably still want to make a boot floppy the way I described,
though, because it should boot your system right up without having to go
through all the prompts on the boot/rescue disks.
pfv
response 177 of 257: Mark Unseen   Oct 25 19:54 UTC 1999

        Or write one when you recompile the kernel: make zdisk.

gull
response 178 of 257: Mark Unseen   Oct 25 23:58 UTC 1999

Yup.  Which I believe does pretty much what my command does, except with a
freshly-compiled kernel.  It's always a good idea to have a recent
boot diskette around -- it'll save you from all kinds of trouble.
raven
response 179 of 257: Mark Unseen   Oct 26 06:06 UTC 1999

Well here is my situation now.  I do have a boot floppy I made during the Linux
installation when I run it I get the following:

Lilo

Press return (or wait 10 seconds) to boot your Linux Mandrake system from
/dev/hdc5  If you want to use a rescue disc type rescue now.

boot:
Loading Linux.... (it gets through putting 4 dots on the screen) then
Error 0 x 10

I also managed to make a resue disc that seems to boot me into a stripped
down Linux with emacs and a few other applications.  The recue disc is called
something like Tom's root boot.  What should I do from here to get it to
boot from a floppy to /dev/hdc5?  If the next thing doesn't work Im going
to reclaim the hd space for windows.  How does one reformat a Linux drive
to fat16 anyway?  Thanks for all your time and paitence with a Linux
newbie.
drew
response 180 of 257: Mark Unseen   Oct 26 19:51 UTC 1999

The boot floppy will stop at a prompt for entering "extra parameters". If you
just hit Enter, you get the stripped-down Linux (and get prompted for the root
disk later). At this prompt, type in

        root=/dev/hdc5

This should get you into your system. Then log in (to an account with the
necessary permissions) and type

        lilo -C /etc/lilo.conf

Assuming your lilo.conf is good, this should restore your LILO MBR.
gull
response 181 of 257: Mark Unseen   Oct 26 22:58 UTC 1999

Where'd you get 'Tom's root/boot'?  I've seen that one recommended, but when
I went to look for it the other day, I didn't know where to look.
raven
response 182 of 257: Mark Unseen   Oct 27 07:29 UTC 1999

re #181 It came on my Linux mandrake 6.0 distribution cd room which was
included with an issue of the magazine Maximum Linux which i got at Safeway
raven
response 183 of 257: Mark Unseen   Oct 27 07:35 UTC 1999

re 180 I don't think this  root boot stops except in the very begging for
anything.  It's all on one floppy so I know it dpesn't ask for another disk.
Is there anyway to put lilo and whatever else I need to boot on floppies?
I don't want to go through wiping out my win98 mbr again.  Thanks to everyone
for paitnece with a Linux newbie. Or could I put lilo on e: and switch to that
drive with the bios when I boot up?  If so, how?
raven
response 184 of 257: Mark Unseen   Oct 27 19:13 UTC 1999

No luck with either boot floppy.  Is there some way I can reinstall again and
have lilo go onto a floppy as opposed to the mbr of the c: drive? I don't want
to go through losing my win 98 mbr again.  What would happen if I pulledc the
IDE cables from my two win98 drives when i did the reinstall would lilo go  on
e:?
gull
response 185 of 257: Mark Unseen   Oct 28 02:20 UTC 1999

Slackware used to have a 'create boot floppy' option during installation. 
Don't know if it still does.
raven
response 186 of 257: Mark Unseen   Oct 28 06:07 UTC 1999

Hmm that does me no good having mandrake 6.0.  If there is no way to install
Linux without overwriting my win98 mbr I shall have to reclaim my linux gig
drive for windows.  How do i do that?
pfv
response 187 of 257: Mark Unseen   Oct 28 16:09 UTC 1999

        Sounds like you are in the position I was a few years ago, due
        to that goddamned 95..

        At this point, yer pretty well fubar. You could *TRY* to run
        the Mandrake (semi-RH) installation again: it should give you
        access to fdisk and/or Disk Druid. And, you should be able THEN
        to muck around with the "linux partition" - if you USED one.

        For me, it was just all around less hassle to NOT fight the RH
        install and just reinstall over the old install - AND MAKE A BOOT
        DISK THIS TIME. I emphasize this because, that boot disk will be
        aware of all the partitioning, and get you into the MAIN, HDD 
        SYSTEM. Once *there* you can _always_ so "lilo<cr>" and insure
        the MBR is reset.

        (man, we *really* need an anti-terrorist tool to combat this
        win95/mbr-battle) 


 0-24   25-49   50-74   75-99   100-124   125-149   138-162   163-187   188-212 
 213-237   238-257         
Response Not Possible: You are Not Logged In
 

- Backtalk version 1.3.30 - Copyright 1996-2006, Jan Wolter and Steve Weiss