Path: utzoo!attcan!uunet!seismo!sundc!pitstop!texsun!sun-barr!rutgers!ukma!psuvm.bitnet!cunyvm!ndsuvm1!ndsuvax!ncoverby From: ncoverby@ndsuvax.UUCP (Glen Overby) Newsgroups: comp.os.minix Subject: Re: Minix 1.3 compatibility questions Summary: More than meets the eye... Message-ID: <2648@ndsuvax.UUCP> Date: 9 May 89 15:35:21 GMT References: <4163@crash.cts.com> Reply-To: ncoverby@ndsuvax.UUCP (Glen Overby) Organization: Silo Tech, Fargo ND USA Lines: 18 In article <4163@crash.cts.com> jca@pnet01.cts.com (John C. Archambeau) writes: > The sources are identical. The differences are in the distribution, the AT >version comes on 1.2 MB floppies, while the PC version comes on 360K floppies. >Also, the AT version is configured to use less memory (512K), but you can >recompile the kernel to use the full 640K base. Hu? Minix uses all memory under 640K that it can find. There is a library function called "get_tot_mem()" that is used by mm/main.c (line 5517) to determinethe number of memory clicks. "Reconfiguring" Minix to use 640K consists of installing chips (maybe flipping DIP switches, if you have a DIPpy model PC) and booting Minix. The AT kernel comes compiled with at_wini.c rather than xt_wini.c (I hope!). The RLL patch I did for the Adaptec was: change NR_SECTORS from 17 to 25, and increase the timeout value to 32767. The ROM wini apparently will require a similar hack on NR_SECTORS. -- Glen Overby uunet!ndsuvax!ncoverby (UUCP) ncoverby@ndsuvax (Bitnet)