[Coco] 2 Meg memory problem

Arthur Flexser flexser at fiu.edu
Wed Jan 1 11:54:07 EST 2020


Could this be something that might be cured by reseating the 2 Meg upgrade
as well as any socketed chips it contains?  I would have thought the stress
test would catch any weird intermittent thing, but perhaps not.

Art

On Wed, Jan 1, 2020 at 11:22 AM Mark Marlette <mmarlette at frontiernet.net>
wrote:

> Chris,
> I downloaded and installed the EOU Beta4 on the CoCoSDC and tested.
> No issues all work properly here on my end.
> Regards,
> Mark Marlette
>  http://www.cloud9tech.com
> mark at cloud9tech.com
> mark at gamecamaddict.com
>
>     On Tuesday, December 31, 2019, 08:54:14 PM CST, Christopher R. Hawks <
> chawks at dls.net> wrote:
>
>  On Wed, 1 Jan 2020 02:01:02 +0000 (UTC)
> Mark Marlette <mmarlette at frontiernet.net> wrote:
>
> > Other than trying another CoCo.
> > What is the current EOU version?
> >
> >
> > Mark Marlette
> >  http://www.cloud9tech.com
> > mark at cloud9tech.com
> > mark at gamecamaddict.com
> >
> >    On Tuesday, December 31, 2019, 07:44:30 PM CST, Christopher R.
> > Hawks <chawks at dls.net> wrote:
> >  On Wed, 1 Jan 2020 01:04:50 +0000 (UTC)
> > Mark Marlette <mmarlette at frontiernet.net> wrote:
> >
> > > Thanks Henry!
> > > Mark Marlette
> > >  http://www.cloud9tech.com
> > > mark at cloud9tech.com
> > > mark at gamecamaddict.com
> > >
> > >    On Tuesday, December 31, 2019, 06:44:44 PM CST, rietveld rietveld
> > > <rietveldh at hotmail.com> wrote:
> > >  I have the cloud9 2mb test. Dsk on my desktop. I just sent you a
> > >copy
> > >
> > > Sent from my BlackBerry
> > >   Original Message
> > > From: Christopher R. Hawks
> > > Sent: Tuesday, December 31, 2019 7:37 PM
> > > To: coco at maltedmedia.com
> > > Reply To: CoCoList for Color Computer Enthusiasts
> > > Subject: Re: [Coco] 2 Meg memory problem
> > >
> > >
> > > On Wed, 1 Jan 2020 00:18:17 +0000 (UTC)
> > > Mark Marlette <mmarlette at frontiernet.net> wrote:
> > >
> > > > Chris,
> > > > Using your example, my current setup is EOU beta3.
> > > > No issues
> > > > using wcreate /w3 -s=8 0 0 40 24 1 0 0 shell i=/w3&
> > > > can clear and do a dir and it operates fine
> > > > do the above but with /w4 and -s=6
> > > > same works fine here.
> > > > Have you run stress12.bin to verify memory / mmu integrity?
> > > > Regards,
> > > > Mark Marlette
> > > >  http://www.cloud9tech.com
> > > > mark at cloud9tech.com
> > > > mark at gamecamaddict.com
> > > >
> > > >    On Tuesday, December 31, 2019, 05:50:26 PM CST, Christopher R.
> > > > Hawks <chawks at dls.net> wrote:
> > > >  On Tue, 31 Dec 2019 21:46:40 +0000 (UTC)
> > > > Mark Marlette <mmarlette at frontiernet.net> wrote:
> > > >
> > > > > Chris
> > > > > Can you please provide the exact test case and I will try and
> > > > > duplicate it here. Thanks
> > > > > Mark
> > > > >
> > > > > Sent from Frontier Yahoo Mail on Android
> > > > >
> > > > >  On Tue, Dec 31, 2019 at 3:10 PM, Christopher R.
> > > > > Hawks<chawks at dls.net> wrote: I'm seeing a strange problem with
> > > > > my CoCo3 running a Cloud9 2 Meg memory board.
> > > > >
> > > > >    When I searched online for similar problems, I found a
> > > > >message
> > > > > in the CoCo facebook group describing something similar. BUT,
> > > > > the problem I'm seeing is only with screen types 7 and 8
> > > > > running under NitrOS9 (at double speed). (NitrOS-9 updated
> > > > > yesterday) I can create and use screens up to type 6 (16k of
> > > > > memory), but screen types 7 and 8 (32k of memory) crash the
> > > > > system. Even a 'wcreate /w1 -s=8 0 0 40 24 1 0 0' from the
> > > > > command line crashes the system.
> > > > >
> > > > >    If I POKE &HFF9B,&H80 (disable 2 meg) before booting, the
> > > > >bigger
> > > > > screens work fine.
> > > > >
> > > > >    Any ideas, suggestions, or guesses? I need 320x240 in 8
> > > > >colors.
> > > > >
> > > > > Thanks!!
> > > > >
> > > > > Christopher R. Hawks
> > > > > HAWKSoft
> > > >
> > > > Mark (and all):
> > > >
> > > >    Simplest case:
> > > >
> > > > 1) boot NitrOS-9
> > > > 2) enter 'wcreate /w1 -s=8 0 0 40 24 1 0 0' at the command prompt.
> > > > 3) NitrOS-9 crashes.
> > > >
> > > >    If you use -s=6 or less for the screen type, NitrOS-9 doesn't
> > > > crash and you can start a shell (or program) in the window named
> > > > (/w1).
> > > >
> > > >    Happens with an old version of NitrOS-9 (3.3.0 beta from 2014),
> > > > the latest HG pull of NitrOS-9, and the latest EOU (use /w3, /w1
> > > > and /w2 are already in use).
> > > >
> > > >
> > > > Christopher R. Hawks
> > > > HAWKSoft
> > >
> > >     I'm reasonably sure that I did. I'd run it again if I knew where
> > > to find it. It took 2 weeks of looking in boxes to find my SDC after
> > > the move. Is it available somewhere?
> > >
> > >
> > > Christopher R. Hawks
> > > HAWKSoft
> > > --
> >
> > stress12.bin has run thru the memory 10 times
> > (2048KB RAM, 00020MB Tested, 00000 Errors)
> >
> >     Anything else to check??
> >
> >
> > Christopher R. Hawks
> > HAWKSoft
>
>     I'll have to search the barn for another CoCo3.
> Beta 4 (14 May 2019) is the latest (and the one I have).
>
>
> Christopher R. Hawks
> HAWKSoft
> --
> Local High School Dropouts Cut in Half
> Chainsaw Massacre all over again!
> ----------------------------------------
>       \  ^__^
>         \  (oo)\_______
>           (__)\      )\/\
>               ||----w |
>               ||    ||
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco
>


More information about the Coco mailing list