??! Why don't you guys take a look at what it IS before you critize.
Jackass of the year? If you look at what it is, you'll see, that plex86
could benifiet from it, because this way the instructions could be
reduced to 'axioms', i.e. things could be more automatic. Did you even
unzip the file and compile it? Also, with this work, I have used plex86
for debugging operating systems. Hence, it is not off-topic.
But since no one seems to care... If someone DOES add floating point and
MMX support, then I will make the original work GPL. In that case, if
whoever adds that support also makes their changes GPL, the whole thing
will be GPL. Make sense? Doesn't anyone think it's neat to have the x86
instruction set, including binary encodings, contained in just 150 or so
lines? I think it is quite cool.
Something else I've done: FAT12/FAT16 disk accesses by the emulator now
get translated to native filesystem calls. This works like this: upon
plex startup, a directory is taken (including reading the file sizes)
and then when disk reads happen, the file allocation table is emulated.
Disk writes aren't yet supported; to change a file you have to use the
native OS to change the directory contents. Also it makes everything
look like it's defragmented when it isn't really.
Patrick Mauritz wrote:
>
> On Tue, Feb 06, 2001 at 05:06:59PM +0100, [EMAIL PROTECTED] wrote:
> > I suspect you think he mailed to the list by mistake, but he didn't. Look
> > at the paragraph that starts "I'll tell you what:..."
> ok :)
>
> > > I'll tell you what: if you guys (Ron Parker and anyone on the plex86
> > > list etc.) can add floating-point and MMX support, I'll commit the
> > > changes under the GPL.
> the changes - He has two options with external changes:
> 1. accept them with the license of the author
> 2. reject them
>
> but probably he just chose the wrong word...
>
> patrick mauritz
