Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!jarthur!sburke From: sburke@jarthur.Claremont.EDU (Scott Burke) Newsgroups: comp.sys.handhelds Subject: Re: Chip question Message-ID: <10031@jarthur.Claremont.EDU> Date: 8 Dec 90 16:59:08 GMT References: <1990Dec8.101737.19776@jarvis.csri.toronto.edu> Organization: Harvey Mudd College, Claremont, CA 91711 Lines: 38 In article <1990Dec8.101737.19776@jarvis.csri.toronto.edu> byu@csri.toronto.edu (Benjamin Yu) writes: >Hmm, now I know it is not just me who had this CHIP problem. But thanks to >some who give me a hint as to how to fix it,... I still don't know why it >fixes the problem. The solution is after you hit BRIX, wait for a little >while and then hit CHIP. I did this several times, and I always get any >program to be interpreted by CHIP everytime. If I hit BRIX and CHIP really >fast together, one after another, it will just give me back the menu >screen. I guess in my original post, the reason why I need to hit BRIX >CHIP 6 times to get it working is because, after 6 times, my fingers get >tired and there is enough delay between BRIX and CHIP to get the 48SX >working :-)! Interesting machine.... > I'm almost positive this isn't really what's happening. I have written a shell program using one if Jim Donnelly's browsers to provide a menu of games when I press GAME in my CST menu. Then, if I choose a CHIP game, my program turns off the clock, recalls the game string to the stack and executes CHIP. Presuming the game runs, when I quit it, I reset my flags and return to the main menu to see if another game is desired. My shell program seems to run on Tuesdays, Wednesdays, and Thursdays only. No, just kidding--it's weirder than that! Sometimes it works and sometimes it doesn't. Pressing ON-C to supposedly reset my machine to some default configuration doesn't always yield the same behavior. Single-stepping thru my code ALWAYS works, and despite MANY different kinds of tests, I have never noticed a correlation between the time between (say) BLINKY and CHIP and whether or not CHIP really runs. THe problem is, I can't FIND any correlation between the apparent state of my machine and whether or not CHIP decides to work. Oops, just ran another test. Five minutes ago, single stepping through my code worked. Now it doesn't, and I haven't even changed any of the code. I was thinking that for some reason Jim's browser left some weird status bit changed, but I get the same unpredictable resulls whether or not I use a call to TBR (his title browser). I give up. Sometimes I just don't get to play a game. :-( Scott. sburke@jarthur.claremont.edu