Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!munnari.oz.au!uniwa!vax7!nlewispn From: Lewis_P@cc.curtin.edu.au (Peter Lewis) Newsgroups: comp.os.minix Subject: Summary: How to get rmaker to work in MacMINIX Message-ID: <7206.27c8d135@cc.curtin.edu.au> Date: 25 Feb 91 00:56:20 GMT Organization: Curtin University of Technology Lines: 95 Hi All, Here is a summary of what I found out about MacMINIX, rmaker, macfile, and MultiFinder. From: IN%"ukpoit!paul%relay.EU.net@munnari.oz.au" "Paul Wood" 22-FEB-1991 01:27:48.07 >Try chmem =1000000 rmaker, thats what I use Is there a maximum on the value you can chmem? >No, not that I know of >You have applied the rmaker fix - I hope ... *** /usr/src/commands/mac/rmaker/smalloc.c~ Fri Dec 28 21:14:18 1990 --- /usr/src/commands/mac/rmaker/smalloc.c Fri Jan 4 12:55:39 1991 *************** *** 6,13 **** { char *p, *malloc(); p = sbrk(0); ! if (brk(p+size) != (char *)0) { ! fatal("Exhausted mem\n"); ! } ! return p; } --- 6,13 ---- { char *p, *malloc(); p = sbrk(0); ! if (brk(p+size+sizeof(long)) != (char *)0) { ! fatal("Exhausted mem. Requested mem=%ld\n", size); ! } ! return (p + sizeof(long) - ((long) p % sizeof(long))); } >paul@ukpoit.co.uk Paul Wood, 31 Buttermere Drive, > Dronfield Woodhouse, Sheffield, > England, S18 5PX. That was my problem! Thanks Paul. (BTW Paul, I tried to Email a reply to you but it bounced with every conceivable net address). From: IN%"smz@cs.UMD.EDU" 20-FEB-1991 21:15:14.73 >As for the unexpected eof on macwrite/macfile, it has to do with a bug in >macfile.c that assigns the output of (f)getc to a char variable. It should >have been assigned to an integer. A value of 255 assigned to a character >variable is -1 which is the value of EOF. If a new integer variable is used >for the assignment, macwrite/macread/macfile will work correctly. > >Joe Zakar >using smz@tove.cs.umd.edu Change "register char c" to "register int c", it works fine after that. From: IN%"jkain@bronze.ucs.indiana.edu" "Jeff Kain" 21-FEB-1991 09:14:26.31 >I've gotten RMAKER to work successfully after bumping up the memory >requirement by a lot. I've spent all weekend building and rebuilding >MINIX without any difficulties with RMAKER... be sure that all of your >INITs are turned of, however. Even if MINIX will run with INITs >going, I've found that many MINIX programs become more reliable when >INITS are off. This wasn't my problem, but its sound advice when testing any mac program. From: twosheds@pancake.cray.com (Jay Vollmer) >However, I have had no trouble running MacMinix 1.5 under MulFinder6.0. >I did have trouble running it under MultiFinder6.1b9. If that's what >you're doing, you might want to fall-back. >Incidentally, MacMinix runs quite nicely under 7.0b1. If you have yet to >experience 7.0... Let me tell you, it's GRRRRREAT! Other things I have done to MINIX include - Patch sh1.c of the shell to call sync() after calling onecommand(), so the filing system is always up to date. Note that this means the fsck may not be able to repair the disk structure, since it repairs it on the disk, but not in memory (and the sync will probably write it straight back). Change LEADING from 1 to 0 in Console.c so that the tty windows fit on the screen. Change keyboard.c so that the ~` key is an escape key aslong as the capslock key is not down (this matches my other terminal program). Thanks to all those who offered suggestions! Peter. Disclaimer:Curtin & I have an agreement:Neither of us listen to either of us. *-------+---------+---------+---------+---------+---------+---------+-------* Internet: Lewis_P@cc.curtin.edu.au I Peter Lewis Bitnet: Lewis_P%cc.curtin.edu.au@cunyvm.bitnet I NCRPDA, Curtin University UUCP: uunet!munnari.oz!cc.curtin.edu.au!Lewis_P I GPO Box U1987 AppleLink: Guy Kawasaki for Apple President! I Perth, WA, 6001, AUSTRALIA Brought to you by Super Global Mega Corp .com