99 lines
2.5 KiB
HTML
99 lines
2.5 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
|
<HTML>
|
|
<HEAD>
|
|
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
|
|
<TITLE>The Loadlin+Win95/98/ME mini-HOWTO: Getting started:</TITLE>
|
|
<LINK HREF="Loadlin+Win95-98-ME-5.html" REL=next>
|
|
<LINK HREF="Loadlin+Win95-98-ME-3.html" REL=previous>
|
|
<LINK HREF="Loadlin+Win95-98-ME.html#toc4" REL=contents>
|
|
</HEAD>
|
|
<BODY>
|
|
<A HREF="Loadlin+Win95-98-ME-5.html">Next</A>
|
|
<A HREF="Loadlin+Win95-98-ME-3.html">Previous</A>
|
|
<A HREF="Loadlin+Win95-98-ME.html#toc4">Contents</A>
|
|
<HR>
|
|
<H2><A NAME="s4">4. Getting started:</A></H2>
|
|
|
|
<P>
|
|
<P>
|
|
<H2><A NAME="ss4.1">4.1 Step One:</A>
|
|
</H2>
|
|
|
|
<P>Edit (or create) <CODE>config.sys</CODE> on the root of Drive C. The contents should
|
|
be similar to the following:
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<HR>
|
|
<PRE>
|
|
[menu]
|
|
menuitem=Linux, Mandrake Linux 7.2
|
|
menuitem=Win98, Windows 98
|
|
menucolor=15,1
|
|
menudefault=Win98, 10
|
|
|
|
[linux]
|
|
|
|
[win98]
|
|
</PRE>
|
|
<HR>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>If your system already has a <CODE>config.sys</CODE> file, put those contents under
|
|
the <CODE>[win98]</CODE> section. The <CODE>[linux]</CODE> section is left blank
|
|
intentionally.
|
|
<P>
|
|
<P>
|
|
<H2><A NAME="ss4.2">4.2 Step Two:</A>
|
|
</H2>
|
|
|
|
<P>
|
|
<P>Edit (or create) <CODE>autoexec.bat</CODE> on the root of Drive C. The contents
|
|
should be similar to the following:
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<HR>
|
|
<PRE>
|
|
goto %config%
|
|
|
|
:linux
|
|
call c:\linux.bat
|
|
|
|
:win98
|
|
</PRE>
|
|
<HR>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>As above, if you aready have an <CODE>autoexec.bat</CODE> file, put those contents
|
|
under the <CODE>:win98</CODE> section.
|
|
<P>
|
|
<H2><A NAME="ss4.3">4.3 Step Three:</A>
|
|
</H2>
|
|
|
|
<P>Create a file called: <CODE>linux.bat</CODE>. Putting it in the root of
|
|
Drive C is as good as place as any (but it can go anywhere so long
|
|
as you reference the path or location). The contents should be
|
|
similar to the following:
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<HR>
|
|
<PRE>
|
|
@echo off
|
|
c:\loadlin c:\vmlinuz root=/dev/hda3 ro
|
|
</PRE>
|
|
<HR>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>The above example assumes that <CODE>loadlin.exe</CODE> and <CODE>vmlinuz</CODE> are
|
|
located in the root of Drive C (or C:\) and that linux is installed on the
|
|
/dev/hda3 partition. Your configuration may be different.
|
|
<P>
|
|
<P>The important thing here is to make sure that loadlin and your linux
|
|
kernel file are properly referenced. Finished!
|
|
<P>
|
|
<P>That should work for you, as that is how I have things set up on my
|
|
system, which dual boots with Win98.
|
|
<P>
|
|
<HR>
|
|
<A HREF="Loadlin+Win95-98-ME-5.html">Next</A>
|
|
<A HREF="Loadlin+Win95-98-ME-3.html">Previous</A>
|
|
<A HREF="Loadlin+Win95-98-ME.html#toc4">Contents</A>
|
|
</BODY>
|
|
</HTML>
|