Mail Archives: opendos/1997/01/21/01:40:46
>> Hehe. That's not even including the tools directory with the stuff needed
>> to build it in its current form. That's another 2700 files. *grin*
>
>How much disk space does the entire subdirectory tree consume? I mean
>including all sources and things needed to compile them.
>
The build tools require 78.1MB, and the source tree requires 53MB. ;)
>>
>> To utilize the "load-high" ability of EMM386, you can use DEVICEHIGH in
>> config.sys and LH or LOADHIGH in autoexec.bat. Keep in mind that it
>> doesn't just stick things in "normal" high memory. It shoves it above the
>> 1 mb mark leaving far more of the base 640k available. With all my sound
>
>This is great!!!! Bye bye QEMM! Hmm. Does it just do all of this
>automatically or do you still need a program like Optimize or Memmaker?
>Seems to me that it should probably just do it and not need those
>programs. Am I right?
It's pretty automagic. Just specify what you want stuffed high, and EMM386
takes care of the rest.
>Well, I've got 634k with QEMM and I've got all my drivers (a lot of them)
Hmmm.... and how much was QEMM? *grin*
>loaded into UMB's and I've got the HMA reserved for DESQview so DOS loads
>into UMB's instead of high. It gives me more mem that way. But after I
>got the CD-ROM, and UniVBE, and a couple other new drivers that are
>needed, my memory has shrunk down again. I loaded into the HMA now, cause
>I don't really use DV anymore, but MSCDEX REFUSES to load HIGH!!!!!!!!
>I've got 64k of contiguous UMB memory and MSCDEX is only using 12k! It
>WONT load into UMB's! However if I unload a few other drivers, then
>MSCDEX will load HIGH. I guess it needs like a meg of startup memory or
>something before it shrinks to 12k. Also QEMM has the VIDRAM program
>which lets you get up to 730k of memory for apps if you don't use
>graphics. You can enable/disable this on the fly without rebooting. I
>don't have much use for it though.
>
OpenDOS uses NWCDEX which has the same functionality of MSCDEX. It loads
high without any problems at all, and will also allocate any buffers it
needs in high RAM.
>Regardless, it sounds like OpenDOS does ALL of this PLUS much much more!
>And it sounds like it does it better too! I can't wait to see my progs
>all loaded above 1M! Hey, I got 20Megs of RAM! I don't want to suffer
>anymore with 589k in DOS!
>
Well, you'll NEVER get 20MB TPA with a 16 bit OS, but hey, with the source
coming soon, how long do you think it will take a gang of crazed coders to
turn OpenDOS into a 32 bit pure OS? *grin*
>They said, "All good things will come to those who wait." Well, we've
>been waiting, and waiting, and waiting, and now we will reap the rewards
>of not supporting Microsloth.
>
It wouldn't surprise me to see support for ext2fs within two months of the
source release. I would _love_ a 1.7 gig disk with 1024 byte inodes...er
clusters. ;)
>
>> > True. Perhaps someday WINE will be complete. :o)
>> Or perhaps WINE will become part of GEM....*smile*
>
>There you go again with those acronyms that I've never heard of. Ok, I'll
>bite... What does GEM stand for? What does it do? Where can I get more
>info? Should I sit down and foam at the mouth over it too?
>
GEM stands for Graphical Environment Manager. If you've ever seen an Atari
ST or used an early version of Ventura Publisher, you've seen GEM.
If you're feeling like a dedicated coder, send me mail reminding me about
your interest in GEM and I'll give you more info. (I don't have the time
to deal with "wannabe" interest freaks. No offence intended. *grin*)
>Can you tell me where I can get a GIF or JPEG of the Caldera OpenDOS logo?
>I want to plaster it on my webpage. I'd like various sizes to choose
>from if possible. Also, I want to do whatever else I can to inform others
>of alternatives to M$.
>
To my knowledge, one does not exist. Feeling artistic? Submit one. ;)
>LINUX: The ONLY bulletproof 32-bit operating system that has it all.
Ahem. For Now.
g.
- Raw text -