🚀 go-pugleaf

In article <4639@cbmvax.UUCP> jesup@cbmvax.UUCP (Randell Jesup) writes:
>In article <39432@linus.UUCP> eachus@mitre-bedford.arpa (Robert I. Eachus) writes:
>> [ about memory protection ... ]
>
>	Not difficult??  Not difficult, he says.  Maybe HE'D like to
>make this work with all those programs that misuse/don't use MEMF_PUBLIC?
>Also, even non-MEMF_PUBLIC memory may well still have to be readable, at
>least for old programs.  Not to say it can't be done, but just that it's
>still a sizable can of worms.

I agree it's a hell-of-a job, but why not treat it the same way as the
problem of programs not allocating CHIP memory correctly ( you remember,
back in the old days when 512K was alot :-) of memory ).  Wouldn't it
be possible to have a program that worked the same way ATOM worked with
the conversion to fast memory?  And if the programs still don't work,
tough!!!!  If the companies that wrote them aren't far-sighted enough
( actually, if they are just not-near-sighted :-) they should be looking
out for something like that ...

Of course, it's the customer that suffers, but if someone buys one of these
new machines ( or the new version of AmigaDOS or whatever it takes ) they
will have to be aware of the fact that some of their older programs 
might not work.  
 
I mean, hell, I still have a 1000 and I'm all for you guys going full
ahead and making these new machines as good as possible.  I won't be 
buying another machine until it has memory protection anyway ... I'd
really rather it be a 68020/68030 Amiga with lots of amazing (not 
necessarily compatible) graphics capabilities ...

>-- 
>Randell Jesup, Commodore Engineering {uunet|rutgers|allegra}!cbmvax!jesup
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
= Mr. Blair MacIntyre (bmacintyre@watsol.waterloo.edu)                        =
= < this space closed for repairs ... >                                       =
= Opinions? What are they? Are they expensive? Where can I get one?           =