Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!gatech!rutgers!ucsd!ucbvax!kepler.Berkeley.EDU!me128-aw From: me128-aw@kepler.Berkeley.EDU (me128 student) Newsgroups: comp.sys.amiga Subject: Re: Ami crashes, RAD: Message-ID: <27024@ucbvax.BERKELEY.EDU> Date: 5 Dec 88 19:52:36 GMT References: <10207@watdragon.waterloo.edu> Sender: usenet@ucbvax.BERKELEY.EDU Reply-To: me128-aw@kepler.Berkeley.EDU (me128 student) Distribution: na Organization: University of California, Berkeley Lines: 54 Help! I have been having serious problems! My Amiga has been crashing CONSTANTLY lately, starting about the time I got 1.3. When it does, I will be flipping thru screens and an interlaced screen will come up non-interlaced (so that I only see the upper half). Everything is still fine until I try flipping this screen to back, using either the gadgets or keyboard. At that point, the machine totally locks up (keyboard & mouse), responding to nothing non-vulcan. Even the GOMF button does nothing. This has occured with a variety of programs and situations, but I can always repeat it with the following: run Diga! ; Run Diga. Prefs are set to an interlaced screen MWB -i ; initialize multiple workbench MWB N n ; Open a non-interlaced workbench run Memacs file ; run an editor on a non-interlace WB [ flip this screen to back to reveal diga ] [ diga screen is non-interlaced ... click...BOOM ] Please note that I am not always running diga or mwb when this occurs, this is just one such occurance. What is causing this!!!? I am running an interlaced, overscan (671x470) workbench, if this is of any help. It seems to me that the delacing forewarns of the crash, so there ought to be a way to remedy the problem. I am also using SetAlert in my startup sequence, an boot up with either KS1.2 or KS1.3 (it has crashed with both) 2) RAD: For the life of me, I can't recover with 1.3 and RAD: EVER! Is this a slow ram problem? I use an 880k RRD. My system is as follows: Amiga 1000 with 512k Microbotics 2 Meg Expansion Ram Chris Erving's 512k memory Hack Microbotic Stardrive SCSI controller w/ 20 meg hard drive Interlaced, overscan (671x470) Workbench screen Gomf button, video hack, audio hack... (Probably irrelevent, but included for sake of completeness. My first instinct is to question the slow piggybacked ram. Does Fastmemfirst recognize non-c00000 slow ram? Shouldn't the 880k size force RAD: to be in fast ram? 3) How can I get 2 recoverable ram disks? Experimentation shows that 2 RADs don't get along at all. Even RAD: and VD0: don't like each other. BOOM! My Idea is: I want to run Rocket Ranger entirely from ram. since RR uses its own disk-fetching code, it won't work with RAM:. I found that I can diskcopy one disk to RAD: to speed it up considerably; but I want NO WAITING, PERIOD! Thanks -Vincent H. Lee