Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!samsung!usc!rutgers!cbmvax!rsbx From: rsbx@cbmvax.commodore.com (Raymond S. Brand) Newsgroups: comp.sys.amiga Subject: Re: Amiga 3000 and poor quality control. Message-ID: <13626@cbmvax.commodore.com> Date: 5 Aug 90 21:57:33 GMT References: <9008011500.AA25318@jade.berkeley.edu> <32458@cup.portal.com> Organization: Commodore-Amiga Inc, West Chester, PA Lines: 33 In article , rick@rsami.spoami.com (Rick Schaeffer) writes: > [lots of useful info about Rick's problems and the solutions deleted for brevity] > Sorry for being so long winded with this posting. I thought it would be > worth mentioning the problems I had because, as I discovered, there ARE > solutions. Number one is RTFM! And check that you have set the > "Supports Reselection" switch to off for any added drives (both internal > and external). If you don't you might have some WEIRD problems. > > Number two is CHECK YOUR MEMORY ALLOCATIONS. I have read of several > folks having strange problems running programs under 2.0 that ran fine > under 1.3. It seems that 1.3 AllocMem maybe gave you an even multiple > of 4 bytes thus giving you a little slop but 2.0 gives you EXACTLY what > you ask for! Actually, 1.3 and 2.0 give you allocations that are a multiple of 8, the real difference is that the 3000 has memory with non-zero msb addresses. Usually when a program used one extra byte at the end, it put a zero there; if that byte was always supposed to be zero you win, otherwise.... > -- > Rick Schaeffer UUCP: uunet!isc-br.isc-br.com!ricks rsbx ------------------------------------------------------------------------ Raymond S. Brand rsbx@cbmvax.commodore.com Commodore-Amiga Engineering ...!uunet!cbmvax!rsbx 1200 Wilson Drive (215)-431-9100 West Chester PA 19380 "Looking" ------------------------------------------------------------------------