Mail Archives: djgpp/2009/01/08/21:45:59
"Rugxulo" <rugxulo AT gmail DOT com> wrote in message
news:d0ac44e3-772a-44f7-9528-2d6f3f6f1a2c AT h20g2000yqn DOT googlegroups DOT com...
>
> I don't know what changes between releases of Binutils.
From what I could tell, not much.
> I would just use stock DJGPP srcs if
> I were you.
Next attempt...
FYI, the code for MOSS falls under a bazillion licenses. If one removes the
FreeBSD directories - assuming they aren't needed - there are like four or
five or seven licenses. The reason I mention that is that it chops up the
application into many small little files. I reduced it down to just those
which license the primary parts of the DOS extender, those licensed by
Ford's software company. I was hoping that since MOSS was small, that those
files were all that were really needed. Then, I started backfilling in the
missing pieces. 51 files and counting.... No luck on the low file count.
My OS has nearly everything he uses, but it's all in a single file. One.
Since the code pieces are under different licenses, the puzzle pieces can't
be merged together in a coherent manner. I haven't decided whether I'm
going to continue the way I'm going, scrap it, or attempt to figure out how
to compile it "properly"... so I can ignore the stuff that's not needed.
:-) I haven't figured out the correct order that a few files with the same
names are referenced due to the "#include_next" preprocessor directive. I
figured out a few from the code. Otherwise, it looks like it has everything
needed for a complete DPMI host and/or DOS extender.
> Recompiling MOSS.EXE doesn't give you any examples, so in order to
> test it, I had to find a way to build.
If you manage to recompile moss.exe, let me know. I tried out the IW
application. Under Win98SE, it "threw a wrench" at my monitor... It
switched to some mode that wouldn't display. After a reboot, I manually set
my monitor to the lowest setting - which allowed it to switch properly, it
would run, halt, run, halt. It ran on DOS nicely. I'm not sure how well it
would've run on my old 500Mhz machine though.
> I understand all that, just don't know what you're experiencing.
The text is fine. The text alignment is incorrect - due to the missing
carriage return. Are you familiar with unix2dos or dos2unix utilities?
What unix2dos does for text files must be done for text output by the C
compiler so the text is correct for DOS. I can't fully demonstrate because
of the NG line wrap. But, if the decompressor's normal text screen looks
like this, with a's being the screen width:
aaaaaaaaaaaa
Normal
Text
Is
Aligned
Left
This is what it is looks like with the improper EOL:
aaaaaaaaaaaaaa
Normal
Text
Is
A
ligned
Left
It moves down a line, continues, wraps at 80.
> It works in DOSBox,
If it's correctly emulating DOS, then the text should be shifted like the
lower picture... ;-)
> > >http://www.brynosaurus.com/
> >
> > I didn't realize he worked on vx32 also... I've read the papers and
looked
> > it over a few times. It, like many other open projects, has some
features I
> > like, but it isn't as developed as much as I'd like or going in the
> > direction I'd like. In the case of vx32, they just do binary translation
to
> > implement their sandbox. But, with more development, vx32 could be used
as
> > an x86 emulator, possibly with much better performance than others.
>
> It claims security, fast speed
"fast speed" It's the first paper(s) I've read where I actually believed
the speed of emulation claims might be correct... I'm still debating. Most
are total BS.
> Yeah, I didn't know you were cross posting until I saw that. Fitting
> to cross post for a cross compiler. ;-)
I thought one of the programmers there might've been interested in a DOS
project. ;-) Actually, considering they fully implemented a game like that
in '96, I'd think a few people would be jumping at this. '87 Arcade quality
2D when PC's were just getting decent video cards, and low quality 3D DOOM.
It's too bad the source for the game isn't available.
RP
- Raw text -