Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!ames!vsi1!zorch!mike
From: mike@zorch.SF-Bay.ORG (Mike Smithwick)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Wattsa Matta here?
Message-ID: <1991Mar10.070931.15287@zorch.SF-Bay.ORG>
Date: 10 Mar 91 07:09:31 GMT
References: <1991Mar7.065646.16121@zorch.SF-Bay.ORG> <19607@cbmvax.commodore.com>
Organization: SF-Bay Public-Access Unix
Lines: 33

In article <19607@cbmvax.commodore.com> ken@cbmvax.commodore.com (Ken Farinsky - CATS) writes:
>In article <1991Mar7.065646.16121@zorch.SF-Bay.ORG> mike@zorch.SF-Bay.ORG (Mike Smithwick) writes:
>>
>>I am calling OpenWindow and it fails for whatever reason. On my 
>>A1000 running 1.3, I get a guru, on my A3000 OpenWindow returns a NULL
>>as it should.
>>
>>On the 3000 under 1.3, OpenWindow behaves normally.
>                   ^^^
>
>For those of you that noticed, I missed this line when I originally replied.
>I don't know why 1.3 would behave better on a 3000 under low memory conditions.
>-- 
>--
>Ken Farinsky - CATS - (215) 431-9421 - Commodore Business Machines
>uucp: ken@cbmvax.commodore.com   or  ...{uunet,rutgers}!cbmvax!ken
>bix:  kfarinsky


I think I found the problem, at least in part. I removed my CLTd SCSI interface
and OpenWindow would behave properly. My 2 meg expansion hung on the end
of the interface so perhaps there was some funky problem caused by that. At 
times my 1000 would just crash on its own. That still doesn't explain why
OpenWindow would fail when I had 100K of CHIP RAM left and all I wanted was
a 20x20 pixel window. Sheeeesh! The memory can't be that fragged can it?

mike

-- 
"outside of a dog, a book is mans best friend, inside a dog, it's
 too dark to read"-Groucho

Mike Smithwick - ames!zorch!mike