From:	cout AT null DOT musc DOT edu (Paul Brannan)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: OpenDOS and DJGPP works but not multitasking
Date:	18 Feb 1997 01:20:55 GMT
Organization:	Medical University of South Carolina
Lines:	47
Message-ID:	<slrn5gi0ui.1it.cout@null.musc.edu>
References:	<Pine DOT LNX DOT 3 DOT 91 DOT 970210135413 DOT 13709A-100000 AT oopc49 DOT kemi DOT uu DOT se>
NNTP-Posting-Host:	null.musc.edu
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

>has to reset the computer. If one uses DPMI=OFF with EMM386 the computer 
>doesn't crash. It is possible to switch between tasks, but gcc doesn't 

I've tried with DPMI=OFF and the computer still crashes.  I allso tried
EMM386 PIC=ON (which is required in order to run DOS4GW apps), and gcc
still won't run with multitasking.

DOOM did run after PIC=ON, and DUKE3D ran without digital sfx.

Visual BASIC for DOS won't run at all.  Under DR DOS, I had to disable
the disk cache's memory lending to get vbdos to work, but this apparently
has no effect under OpenDOS.

I also cannot load my CD-ROM driver into upper memory, and I can only load
my mouse driver into upper memory when multitasking is disabled.  I have 60k
of free upper memory, so this makes no sense at all.

When multitasking is enabled, the EMM386 option USE=B000-B7FF has no effect.
In addition, nothing seems to be able to get rid of the ROM located at C000
(though I do seem to be able to move it).

I believe that all these problems must be related somehow.  Does anyone
have any ideas?  Perhaps once the source code is released we can fix these
problems.

>run in the background. At first I thought that the multitasking didn't 
>work at all but I used an old basic compiler (only 8086 code) and wrote 
>a small program that just counted up a variable and printed it's value to 
>the screen. Then I put that task in the background and it continued to 
>run (horribly slow but still...). This could be changed in 
>\OPENDOS\TASKMGR.INI so that background processes got more time and it 
>ran faster. However, gcc still doesn't run in the background.
>Has anyone succeded in getting gcc running in the background?

No, I don't seem to be able to get gcc to run in the background.  But I was
able to write a GW-BASIC program, and it did seem to run slower, but not
that much slower.

Does anyone know when the source code is going to be released?  That way we
can start fixing all these bugs.

I'm going to be setting up an OpenDOS page soon with all the bugs and bug
fixes I can find soon.  I will post the address as soon as the page is up.

Paul Brannan
brannanp AT musc DOT edu

- Raw text -