Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!ukma!tut.cis.ohio-state.edu!ucbvax!agate!eris.berkeley.edu!mwm
From: mwm@eris.berkeley.edu (Mike (I'll think of something yet) Meyer)
Newsgroups: comp.sys.amiga.tech
Subject: Re: problem with codeprobe
Message-ID: <24890@agate.BERKELEY.EDU>
Date: 26 May 89 08:31:21 GMT
References: <8905260346.AA05288@jade.berkeley.edu>
Sender: usenet@agate.BERKELEY.EDU
Reply-To: mwm@eris.berkeley.edu (Mike (I'll think of something yet) Meyer)
Organization: Missionaria Phonibalonica
Lines: 28

In article <8905260346.AA05288@jade.berkeley.edu> 451061@UOTTAWA.BITNET (Valentin Pepelea) writes:
<Eric Edwards <C506634@umcvmb.bitnet> writes in<Message-ID: <8905250048.AA20265@jade.
<I too have had exaclty the same problem. CodeProbe GURUed at either an
<OpenWindow() or OpenScreen() call. Even when trying out the program "lines"
<as told in the CodeProbe manual, the Guru invited me to a meditation session.
<But this happened only when I was booting off the Lattice_C disk. If I boot
<from my "ArpBench" disk, no problem. Due to the nature of my work, it took me
<3 days to discover that this was a CodeProbe bug. I was not amused.

Strange. I haven't had any problem with OpenWindow or OpenScreen
(printf, on the other hand...). Of course, I _never_ booted from the
Lattice disks.

The "lines" example documentation is known to be broken. Something
about the startup code - you either need to change the code so it uses
a real startup, or to invoke cpr telling it not to run the startup
code, I forget. If you really want to know, call the Lattice support
group (or the BBS) and ask.

Also, make sure you give cpr *lots* of stack. I habitually run with
50K. That may be why I never had any problems.

	<mike
--
Can't buy happiness no matter what you do		Mike Meyer
Can't get to heaven on roller skates			mwm@berkeley.edu
Can't take a taxicab to Timbuktu			ucbvax!mwm
Life is hard.						mwm@ucbjade.BITNET