Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!usc!sdd.hp.com!spool.mu.edu!uunet!shelby!rutgers!cbmvax!daveh From: daveh@cbmvax.commodore.com (Dave Haynie) Newsgroups: comp.sys.amiga.hardware Subject: Re: 3000 Flakyness Message-ID: <19079@cbmvax.commodore.com> Date: 18 Feb 91 17:01:11 GMT References: Reply-To: daveh@cbmvax.commodore.com (Dave Haynie) Organization: Commodore, West Chester, PA Lines: 48 In article jafo@miranda.UUCP (Sean Reifschneider) writes: >I just got a 3000/25/50 a month ago, and have been having some problems with >it. It seemed to crash more than I expected it to (one reason that I moved >from a 2000 to a 3000. I figured it'd be more stable). The combination of bugs and compatibility issues in the first 2.0x releases for the A3000, and the list of bugs in some 1.3 Amiga programs, could make for a less reliable setup running the A3000 under 2.0x. It all depends on the programs you're running. My experience is that 2.0x itself is at least as dependable as 1.3, but you're going to run into far more software conflicts. I have been spared in many ways in my own use, since I had already weeded out any programs that had trouble with the 68030. That leaves those that have trouble with 2.0x, and those that have trouble with 32 bit addressing. Either of those conditions can cause crashes on an A3000 you won't see on an A2000 or A500. >No such luck. It seemed to crash when I was doing things that would never >crash the 2000 (like run my version of 'ls', mainly on the root of a disc). The version of ls I used to use, Justin McCormik's LS (3.1 or some-such), also crashed under 2.0x. Seems it was doing something wrong that didn't matter under 1.3's FFS but did under 2.0x's FFS. There is supposedly a fix out somewhere, but I just switched over the the ls that comes with Manx 3.6a, and the problem went away. >A week or so later, I moved the 1MB of RAM to the Chip section, and added >4MB of 1MBx4 Static ZIPs. I checked and rechecked the contacts to the >chips, and every thing was ok. When I booted it, it cam up with a yellow >screen during the boot, then it just kept cycling through the boot and >coming back to the yellow. I have never seen this problem. But it sounds like either [a] you have one or more page mode DRAM in there with the static column DRAM, and the OS is still setting up RAMSEY's burst mode, or [b] your expansion bus daughter board is loose. A yellow screen on power up indicates that the system is getting a bus error before graphics is set up enough to give you a guru or other system error message. >When I power cycled it, and selected kickstart 1.3, it came up Ok. The 1.3 OS won't try to turn on RAMSEY's burst mode. >From the desk of Sean Reifschneider. Isn't Amiga UUCP great? Thanks Matt. -- Dave Haynie Commodore-Amiga (Amiga 3000) "The Crew That Never Rests" {uunet|pyramid|rutgers}!cbmvax!daveh PLINK: hazy BIX: hazy "What works for me might work for you" -Jimmy Buffett