On Wed, 26 Jul 2000, Bernie wrote:
> Michael wrote:
> >I need linear access to more memory than 640 KB !!!
>
> Ever heard of 32-bit ? ;-)
> Seriously are you trying to port Arachne to DJGPP?
DJGPP is maybe cool (although I am not used to it yet), but it is not DOS!
It is kind of operating system of its own - unfortunately runtime-only,
without 32bit kernel, 32bit shell, etc. You can have 32bit DJGPP
application with TCP/IP stack built in - but other apps wont be allowed to
access the stack. This is stupid, and it is because DOS is stupid. We need
something, which would be more lightweight then Linux (because not
everyone needs server stuff on desktop PC or thin client), but also more
robust than DOS (so all apps can access TCP/IP stack).
I really like fullscreen apps, games, Arachne ;-), and more, I think that
windowing enviroment is not really needed. But system-level graphics
drivers are needed, so any app can use the driver. Windowing enviroment
can be just one of fullscreen apps, creating virtual >>fullscreen<<
for any application which might wanted that. But the windowing enviroment
would be just optional - you would be able to run anything fullscreen, if
you would like to, and apps would be ready to run in random-sized
graphical or text window.
Having 16bit DOS running single-tasking 32bit DJGPP apps is not really an
option. In 16bit DOS, you actulay had something which was close enough to
multitasking - TSR programs. With DJGPP and DOS4GW and whatever, memory
models got confused so much, that you cannot really say DOS is still
running when 32bit app is running - 16bit code is being hibernated and
occasionaly woken up somewhere deep in memory, but it is not really DOS
any more, as it is not real operating system enviroment any more.
I also dont like the fact, that open, non-MS standards are missing for
graphics adapter drivers, printer drivers, and various device drivers,
like disks, soundcards. They cannot be forever compatible with legacy
PC-AT components like IDE drives, VGA card modes, modems as serial devices
listening to AT commands, etc. And approach of Linux is not very smart,
because I dont like all device drivers to be part of kernel - it is just
concept which sucks for noname, home-built PCs. It is maybe ok for
companies selling pre-installed Linux PC, because they can build very
custom kernel, but I would rather see some common, operating-system
independent model for drivers, so you would have eg. video card driver for
Intel architecture, which will have certain API, and will be able to be
adapted by any operating system - Windows, DOS for those who like it,
Linux (tranforming code to kernel module), and eventualy new, lightweight
system...
--
http://arachne.cz/
(Arachne WWW browser for DOS+Linux / Webhosting / MP3streaming)
