home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.linux
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!sdd.hp.com!ux1.cso.uiuc.edu!rs6000.cmp.ilstu.edu!jliddle
- From: jliddle@rs6000.cmp.ilstu.edu (Jean Liddle)
- Subject: Re: HIMEM.SYS&WINDOWS3.1&LINUX(kernel panic after run windows3.1)
- Message-ID: <1992Dec26.173510.7665@rs6000.cmp.ilstu.edu>
- Date: Sat, 26 Dec 1992 17:35:10 GMT
- References: <1992Dec26.041223.62271@cc.usu.edu>
- Organization: Illinois State University
- Lines: 40
-
- In article <1992Dec26.041223.62271@cc.usu.edu> slc4x@cc.usu.edu writes:
- >Hi:
- > The problem is that after I install SLS, I backup some of my dos
- >file and reinstall the MS WINDOWS 3.1. After I reinstall it and run the windows
- >I try to login linux again(of cause I reset the system). But there's an error
- >message come out just before linux load the kernel into the memory. The error
- >message is
-
- t is unlear in your post whether you are doing a warm-reboot from DOS to
- linux, and whether you are using LILO or BOOT.SYS to select your
- operating system, or just running bootlin from the DOS command line.
- Personally, I use boot.sys because (a) I still keep DOS around for games
- and (b) I'm too cowardly to mess around with the boot sector of my hard drive.
- If you are doing this, you can use himem.sys or other 386 memory
- management, as long as your config.sys file is organimzed something like
- this:
-
- device=boot.sys [various args]
- device=boot.a
- device=top Select Desired Operating System
- device=boot.1 Linux
- shell=c:\etc\bootlin.com c:\etc\image
- device=boot.2
- device=himem.sys
- [ ... other ms-dos drivers, BUFFERS=, FILES=, etc. ]
- device=boot.z
- device=boot.end
-
- In this case, if you want to bootup linux, you do so without starting
- any goofy memory management stuff under DOS which might interfere with
- bootlin and hence how the linux kernel gets loaded into memory.
-
- hope this helps!
-
- Jean.
- --
- Jean Liddle
- Computer Science, Illinois State University
- e-mail: jliddle@ilstu.edu
- --------------------------------------------
-