Mail Archives: djgpp/2000/11/22/04:01:01
On Wed, 22 Nov 2000, John Harrison wrote:
> 1) I've set up a RAM Disk (using MS ramdrive.sys) but I can't get bash to
> access it, ls e:/, ls e:\\ and ls e: all produce a 'no such file or
> directory' message.
What does "ls e:" print, if invoked from COMMAND.COM's prompt (not from
inside Bash!)?
> 2) I've set my put set TMPDIR=E:/ in my autoexec.bat but I'm not convinced
> that DJGPP is using this, how can I test this?
Type "SET [Enter]", and see if there's a line there which says "TMPDIR=E:/".
If there is, and if the drive E: is accessible (see above), DJGPP will
surely use that.
> 3) How should I configure my machine to get the most out of DJGPP. I've read
> the FAQ but I'm honestly none the wiser. I'm interested in having as much
> memory as possible available to my DJGPP programs when they run. I have the
> following specs, Window 98 SE, 128Mb RAM.
The FAQ advise is for plain DOS, not for Windows. For the system such as
yours, if go32-v2 reports memory that is close to 128MB, your machine is
set correctly, and you cannot do any better.
> 4) Finally one unrelated question. What should I do if I want my program to
> allocate real memory only, not virtual memory. Just a pointer to the right
> documentation would be great.
By ``real memory'' do you mean physical memory as opposed to virtual
memory, that is, memory that will never be paged out to disk?
If so, this is not really possible on Windows. About all you can do is
to lock all memory (there's a startup flag that will do that by default;
see section 18.9 of the DJGPP FAQ for more details). Of course, doing
that means that other Windows applications might be unable to run, or
your program might fail to allocate enough memory...
On plain DOS, you could disable paging done by CWSDPMI, as the FAQ
explains.
- Raw text -