🚀 go-pugleaf

>        I am please to say that I am VERY happy w/ my upgrade!  I was a
>bit bummed when I realized the 68340 had no MMU, but upon doing the math,
>for what I wanted to do, the 340 could emulate an MMU faster than the 070
>could provide it.

How do you emulate an MMU?

>        Gifshow and iffshow are broken now ... probably a memory mapping
>problem?  If someone wanted to send me the source, I might be willing to
>fix them.  All of my direct screen write code still works!

What is the problem?  Does it die with a privileged instruction violation,
or do the colors just not work right?  The version of KWindows that came
with the 340 has a big bug in it when dealing with Palettes.  It seems to
only take effects if the screen having the changes made is currently
visible.

>        The new ROMS try to boot from my HD before it is ready (Maxtor
>128meg), a slight delay would help :).  Break is also broken!  Any
>explanation?

The MM/1 should fail and try again.  Mine can do this up to three times
before succeeding.  What is wrong with Break?  It works just fine for
me.

>        Gcc really zips along!  Now if only the l68 defs libraries weren't
>brain damaged, it would be as fast as our Sun!  Fix the linker, add
>hardware scrolling, and this thing would really blaze!

That it does!  G++ works really nice, too.  l68 is i/o bound (it doesn't
buffer its reads) so the 340 doesn't improve it much.  If you want to see
how fast l68 _could_ be, see how fast "collect" is (part of g++).

These opinions are all                      Brian                 _ /  __/  _ /
mine and you can't have               ( studer@bnr.ca )          / / __ / __ /
any.  So there!                 ( bcwhite@sunee.uwaterloo.ca ) ___/ ___/ ___/
-------------------------------------------------------------------------------
 The difference between theory and practice is less in theory than in practice.