Path: utzoo!mnetor!uunet!husc6!bloom-beacon!gatech!mcnc!unccvax!mru From: mru@unccvax.UUCP (markus ruppel) Newsgroups: comp.sys.ibm.pc Subject: Re: Dos/TSR/Multitasking interaction Message-ID: <920@unccvax.UUCP> Date: 5 Mar 88 21:40:19 GMT References: <2418@umd5.umd.edu> Organization: Univ. of NC at Charlotte, Charlotte, NC Lines: 41 in article <2418@umd5.umd.edu>, phil@umd5.umd.edu (Philip Shafer) says: > Keywords: DOS TSR tasking background > > DOS/TSR/Multitasking interaction > > I have a problem with DOS. Who doesn't? Right, everybody has, mainly because DOS IS NOT DESIGNED TO MULTI- TASK !!!!! Why don't you switch to a real multitasking and multi- user system like Concurrent DOS made by Digital Research, Inc. ? It provides you with BUILD IN system calls to disconnect ( detattch ) a program ( task ) from its console ( screen, you have four virtual consoles on your main screen ) , to run in the background, to com- municate between background tasks ( queues ) and so on. The most inportant point is that it has been available for the last 3 years as an OS and became pretty much mature by now. It's so called native mode is CP/M, but it supports DOS 3.3 calls as well. That means you can run DOS AND CP/M applications. I've been designing a multitasking ( 8 background tasks and one foreground user inter- face ) device control and data aquisition system in our labs and it works great. The code is written in MS C 5.0 and I've built my own little library of Concurrent DOS system calls to manage the task spawning and queue management. With CDOS you won't have to worry about 'good and bad' int's, because the system is reentrant. ( rest deleted ) > # phil@umd5.umd.edu # University of Maryland, College Park > # shafer@umdd.bitnet # IBM@UOM, Pc/Ip project > # I tried to make a signature, but the disk was spinning > # so fast I could hardly write (my pencil kept breaking) If you have any further questions, let me know. Markus Disclaimer: Neither do I own stocks nor am I affiliated in any way to DRI, except as being a satisfied customer.