Mail Archives: djgpp/1999/01/17/05:09:38
On 14 Jan 1999, Mike Freeman wrote:
> (1) When I load JAWS high, it will not load until I remove CWSDPMI.EXE
> from upper memory. In other words, I must load JAWS high first -- then
> load CWSDPMI high. Tinytalk (TTALK.EXE) wasn't that particular. This is a
> minor annoyance.
One wonders why do you at all load CWSDPMI manually. You don't need
to: any DJGPP program will load CWSDPMI automatically at startup, and
unload it when it exits. So you shouldn't be loading CWSDPMI in the
first place.
> (2) When running a program compiled with GCC2.81 (DJGPP) and using CWSDPMI
> as the DPMI server, whenver the system() function is called, I get a "path
> not found" message spoken.
Are you sure the message reads "path not found"? There's no such text
anywhere in the code associated with the `system' library function, so
I wonder where does this message come from. Maybe JAWS changes your
PATH setting so that some directories are removed from it?
Please tell what argument do you pass to `system' in your program that
causes the "path not found" message.
> When I run a program compiled with GCC2.81 and CWSDPMI, I cannot save
> program-specific configurations -- JAWS just does nothing but goes back to
> the menu of configuration options as if it had saved but doesn't give the
> "okay" spoekn token that it did so.
>
> I must go back to the MS-DOS command prompt to save configurations.
What do you mean ``back to MS-DOS command prompt''? Didn't you just
tell that JAWS is a TSR? If so, you should be at MS-DOS command
prompt, even when JAWS is loaded, no?
Anyway, to give you meaningful help, a lot more knowledge is required
about how JAWS installs itself and how does it work. Please tell any
details you know, or, better yet, cc: your messages to the author(s)
of JAWS and ask them to join this discussion.
- Raw text -