Path: utzoo!mnetor!uunet!nuchat!sugar!peter
From: peter@sugar.UUCP (Peter da Silva)
Newsgroups: comp.sys.amiga
Subject: Re: The Next Generation
Message-ID: <1269@sugar.UUCP>
Date: 16 Dec 87 11:46:14 GMT
References: <2785@megaron.arizona.edu> <10001@stb.UUCP>
Organization: Sugar Land UNIX - Houston, TX
Lines: 29
Keywords: MMU paging swapping
Summary: Interesting point...

In article <10001@stb.UUCP>, michael@stb.UUCP (Michael) writes:
> In article <1217@sugar.UUCP> peter@sugar.UUCP (Peter da Silva) writes:
> >I don't see where MEMF_PUBLIC is such a problem. How much of your code
> >is public?
> All of it. It was loaded by another process by LoadSeg(), which had to
> put it into memory accessable by two different processes.

Interesting point. I don't think it's unmanagable, though. You would have
LoadSeg put the whole program into the parent's adress space until the
parent starts it up. At that point the memory would be yanked out of the
parent's adress space and stuck into the child's. The memory allocated
by LoadSeg would have to be arranged in virtual adress space so this was
possible. UnloadSeg would have to be privileged. For programs that didn't
want to do this (overlays, for example) you'd have to run some sort of
fixhunk over them.

Electronic Arts wouldn't care much for this, I suspect. They're pretty big
on protecting their badly-behaved software. Getting better, though.

Alternatively, you'd implement a NEW loadseg that loaded a protected
task, and have the new version of WorkBench and CLI use this. That way
most programs would still benefit from protection, without antagonizing EA.

> : "Copy Protection? Just say 'Off site backup'. "

There you go again, destroying your credibility.
-- 
-- Peter da Silva  `-_-'  ...!hoptoad!academ!uhnix1!sugar!peter
-- Disclaimer: These U aren't mere opinions... these are *values*.