From: Bill Gaughan <wgaughan@snet.net>
To: blinux-list@redhat.com
Subject: Re: Linux on a 2-Drive Machine
Date: Tue, 13 Nov 2001 17:11:29 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.40.0111131705010.476-100000@beethoven.wgaughan.net> (raw)
In-Reply-To: <000b01c16c4d$47e42460$e08caad8@tds.net>
You would need to install zipslack or bigslack. (bigslack, if you want the
entire linux). Zipslack is designed to be installed a full running copy on
linux on a zip disk, but, you can install it on to a dos partition in the
c:\linux directory. you run a batch file from dos called loadlin.bat.
Better to have a separate linux partition on the drive and boot to linux
from lilo. I have dos and win95 on my c: drive and linux on a second
drive. dos/win95 doesn't know I have a second drive for linux. It's called
a dual-boot system. lilo comes up from the master boot record and asks you
which system you want to load, dos/windows for linux.
hope this helps. Oh, from my experience you have to unzip zipslack or
bigslack archives from windows not from pkunzip from dos. the zipslack and
bigslack archives are huge files!
--
Bill Gaughan
wgaughan@snet.net
On Tue, 13 Nov 2001, John J. Boyer wrote:
> Hello,
> I have a machine with two disk drives. The C drive is now running Windows
> 98. The D drive is used for backup. The machine boots into dos, so I can run
> dos programs if Windows commits suicide. I'm thinking of puting Linux on
> what is now the D drive. Then I would have a little DOS program to start it
> up after the machine boots. How can I write such a program? How do I install
> Linux on what is now the D drive. There will be plenty of space to still use
> it for backup. Better still, there are other machines on our network which
> can be used for backup.
> Thanks a lot.
> John
>
> Computers to Help People, Inc.
> http://www.chpi.org
> 825 East Johnson; Madison, WI 53703
>
>
>
>
>
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://listman.redhat.com/mailman/listinfo/blinux-list
>
prev parent reply other threads:[~ UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
John J. Boyer
` Saqib Shaikh
` John J. Boyer
` Brent Harding
` John J. Boyer
` Brent Harding
` L. C. Robinson
` Brent Harding
` BIOS boot control (Was: Linux on a 2-Drive Machine) L. C. Robinson
` Bill Gaughan [this message]
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.40.0111131705010.476-100000@beethoven.wgaughan.net \
--to=wgaughan@snet.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).