From: "L. C. Robinson" <lcr@onewest.net>
To: blinux-list@redhat.com
Subject: Re: Urgent help needed!
Date: Sun, 12 Nov 2000 04:44:28 -0700 (MST) [thread overview]
Message-ID: <Pine.LNX.4.21.0011120334490.22306-100000@rupin.localnet> (raw)
In-Reply-To: <Pine.GSO.4.21.0011102343470.29698-200000@abeel.students.cs.uu.nl>
Windoze may be finicky, but not that picky. Mine has been on
partition 4 since the win 3.1 days, and now resides on my second
(slave) hard disk (same disk, just cabled differently), on
/dev/hdb4, to be precise, and DRDOS is on hda1: with lilo they
both boot up thinking they are drive C. If you're willing to
wade through the longish lilo manual, you can do almost anything
you want (the ascii text version of the manual is found in
/usr/doc/lilo-0.21/README, on my system (RedHat)). Most setups
can be done through the /usr/doc/lilo-0.21/QuickInst script.
Here's my setup:
87% df -H
Filesystem Size Used Avail Use% Mounted on
/dev/hdb4 212M 112M 100M 53% /dos/win95
/dev/hda1 37M 14M 23M 38% /dos/c
And the M$ part of my lilo.conf:
other = /dev/hda1
table = /dev/hda
label = drdos
alias = d
other = /dev/hdb4
table = /dev/hdb
label = win95
alias = 95
# Swap drives virtually:
map-drive = 0x80
to = 0x81
map-drive = 0x81
to = 0x80
On Fri, 10 Nov 2000, Andor Demarteau wrote:
> ohe error you made, windoz always needs to be on partition 1,
> no exceptions at all! The dos-labeled lines is incorrect as
> well, have a look in the lilo-manpage there's a clear exampe
> near the bottom of it explaining exactly how to do this. I
> have attached my lilo.conf (yes I'm a poor sod still having
> windoz on hda1 I know). good luck!
> On Fri, 10 Nov 2000, Saqib Shaikh wrote:
>
> > Hi all, I urgently need help to solve this problem regarding
> > partitioning. I have written my own lilo.conf, which I have
> > included at the end of this message, and then when I select
> > windows from lilo get the error message: cannot find
> > c:\windows\system\something.vxd, i cannot remember exactly.
> > basically it is looking for the windows boot loader. i am
> > using windows millennium incase this matters. my lilo.conf
> > file is:
--
L. C. Robinson
reply to no_spam+munged_lcr@onewest.net.invalid
People buy MicroShaft for compatibility, but get incompatibility and
instability instead. This is award winning "innovation". Find
out how MS holds your data hostage with "The *Lens*"; see
"CyberSnare" at http://www.netaction.org/msoft/cybersnare.html
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
Saqib Shaikh
` Andor Demarteau
` L. C. Robinson [this message]
` Andor Demarteau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.21.0011120334490.22306-100000@rupin.localnet \
--to=lcr@onewest.net \
--cc=blinux-list@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).