Re: AGS issues issues issues

[BLuRry <brendan.robert@gmail.com>]

On Monday, November 19, 2012 2:47:23 PM UTC-6, Kevin wrote:
> On Monday, November 19, 2012 11:57:29 AM UTC-6, BLuRry wrote:
> 
> > On Sunday, November 18, 2012 5:42:33 PM UTC-6, Kevin wrote:
> 
> > 
> 
> > > Using AGS3 on my apple IIc all I can reliably do is crash any tips?
> 
> > 
> 
> > 
> 
> > 
> 
> > I recommend tracking down the author and giving him a really good piece of your mind about how little he's updated that project recently... oh wait (looks in mirror) that would be me. ;-)
> 
> > 
> 
> > 
> 
> > 
> 
> > Yes, actually I developed it with a Rev-0 //c so I know it can work. :-)  Try toggling the "debug bootstrap" parameter.  That tends to help a bit.
> 
> > 
> 
> > 
> 
> > 
> 
> > I need to scrub through the code and optimize it a bit.  To be honest there are some things in there that need to be properly exposed.  Like the test code that lets you convert JPGs and GIFs into HGR and DHGR pictures for example.  I also used this code base for some experimental video compression -- but more on that later. ;-)
> 
> > 
> 
> > 
> 
> > 
> 
> > Anyway, ping me if the debug bootstrap option doesn't work for you.
> 
> > 
> 
> > 
> 
> > 
> 
> > -B
> 
> 
> 
> lol!
> 
> 
> 
> the server side seems to be ok-ish, it will hang once in a while, but on the //c side I might be lucky to start a game, but even moving the selector down a single item will start throwing up connection errors then locks. I am using the same ADT cable I usually use and with all the tinkering around I have done on the serial port @ 115200 its pretty stable in the cable department

There is a chance that the build is buggy.  Send me an email and I'll send you a build from my local copy for comparison.  I haven't changed anything in a long while but you never know.

I remember having trouble on the //c side because of the flow control settings -- things behaved better once I used XON/XOFF flow control but I'm not 100% sure why.  The baud rate runs at a fixed 115.2 kbaud (undocumented) which may or may not be stable on some //c's.  Can you confirm what revision of //c you're using?  (e.g. I'm using a "255", aka rev 0)

-B