Path: utzoo!attcan!uunet!cs.utexas.edu!sun-barr!ames!elroy!gryphon!jdm From: jdm@gryphon.COM (John Mesiavech) Newsgroups: comp.sys.amiga Subject: Re: SinCity Blues Keywords: SimCity, ChipMem Abuse Message-ID: <16761@gryphon.COM> Date: 15 Jun 89 07:20:39 GMT References: <19289@cup.portal.com> <10249@watcgl.waterloo.edu> <1047@sactoh0> <18043@mimsy.UUCP> Reply-To: jdm@gryphon.COM (John Mesiavech) Organization: Trailing Edge Technology, Redondo Beach, CA Lines: 50 Joining into this thread a little late, just wanted to report my own personal experiences with Maxis's Sim City program. My system: A2000 A2620 w/2MB RAM Microbotics Hardframe-2000 with 2 hard drives attached. 3 (yes, 3!) floppy drives, DF0:, DF1: and DF2:. The only special setups I do in the Startup-Sequence on the hard drive is leaving OUT the FastmemFirst program (ie, I don't run it atall). SimCity works fine from the original disk, or from the hard drive if I have the original disk in any drive. The copy protection is of the key disk sort. Now, this is at variance with many of the experiences here, and I think the culprit is FastMemFirst. Back when I was running an A1000 with 1MB, if I used the FastMemFirst progra, many programs, both PD and commercial, would bomb. Without it, they worked. Now, on this A2000, not running FastMemFirst causes no problems. To all those with SimCity: Take out the call to FastMemFirst in your startup-sequence. It may work. John P.S> Having a CLI running at the same time as Sim City in the above setup shows 50K chip mem free. -- 0-=-=-=-=-=-=-=-=-> All disclaimers apply; I didn't write this <-=-=-=-=-=-0 | ----------------------|------------------- | | "I want a New Duck | John Mesiavech | | One that won't try to bite | net.soldier.of.fortune | | One that won't chew a hole in my socks | {backbone}!gryphon!jdm | | One that won't Quack all night" | Go Purdue! (by req) | | Weird Al Yankovic, "I Want a New Duck" | | 0-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-0