delorie.com/archives/browse.cgi | search |
From: | cat AT animal DOT u-net DOT com |
Subject: | Re: function fork() |
Organization: | none |
References: | <Pine DOT SUN DOT 3 DOT 91 DOT 1001121102801 DOT 7635E-100000 AT is> |
Newsgroups: | comp.os.msdos.djgpp |
NNTP-Posting-Host: | host1.lowtech.org |
X-Original-NNTP-Posting-Host: | host1.lowtech.org |
Message-ID: | <3a2fe050$1@news.gemsoft.net> |
Date: | 7 Dec 2000 19:09:04 GMT |
X-Trace: | 7 Dec 2000 19:09:04 GMT, host1.lowtech.org |
Lines: | 17 |
X-Complaints-To: | abuse AT gemsoft DOT net |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
Reply-To: | djgpp AT delorie DOT com |
In the case of a program p2fork for example it might be possible to save the state of the running version of the program to a data file and then replicate the program with a line such as system("start /b p2fork --restart=data"); Here the /b flag indicates run in background. The previous reply I got on this newsgroup was extremely helpful and it bears repitition. This method does make windows look like a multitasking program. It may be necessary to modify the .pif for p2fork after it has been invoked to make it keep using CPU time when running in background mode. Users with a fast enough processor and heaps of memory should be able to get 2**n copies of their program running in no time :) Tony Goddard
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |