🚀 go-pugleaf

In article <4j48t7$m95@viper.shadow.net>, zonum@rafs.shadow.net (Rafael
Munoz) wrote:

>I also have problems with AWeb v1.0 (I have sent all of the info
>to Yvon already, but I want to see if others are having the 
>same problem - I sent him also some Enforcer hits I was able to
>capture!).  The problem I experienced, and it is something that
>happens ALL of the times, in other words, I can make it happen
>every single time I run it, is that when I exit/quit AWeb, while
>running on an (registered) CyberGraphX v2.16 800x600x16-bit screen
>using the 24-bit picture.datatype v43.668, I ALWAYS, ALWAYS, w/o
>failure, get a System Crash #80000008 - this is w/o failure!  It
>runs flawlessly, however, while it is running - it is FAST and it
>looks GREAT w/24bit DT; just AWESOME!

>If I run AWeb either on my cgfx 800x600x256 WB screen or on its
>own cgfx 800x600x256 screen, it works fine - no problems when
>exiting/quitting!  

Yup, does the same here. I get a bunch of alerts and enforcerhits too. Guess
I had better send them off to Yvon soon. :-)

>Anyway, just want to hear from anyone that may have similar problems!
>My system is: A3000@25, 16 Meg FAST, 2 Meg CHIP, Picasso-II 
>w/registered CyberGraphX v2.16, AmiTCP, WB40.42/KS40.68.  Ok, that is
>it!

A4000/040, CV64, CyberGraphX 2.16, latest 24 bit dt.

                   T r o e l s  W a l s t e d  H a n s e n
            troels@stud.cs.uit.no - http://www.cs.uit.no/~troels