Path: utzoo!censor!geac!maccs!cs4g6ag From: cs4g6ag@maccs.dcss.mcmaster.ca (Stephen M. Dunn) Newsgroups: comp.sys.ibm.pc.programmer Subject: Re: popen() Message-ID: <25F5D03C.5473@maccs.dcss.mcmaster.ca> Date: 8 Mar 90 03:23:39 GMT References: <1503@loria.crin.fr> <25F00B67.17161@maccs.dcss.mcmaster.ca> <21231@netnews.upenn.edu> <348@comcon.UUCP> <1990Mar7.002520.10365@calvin.spp.cornell.edu> Reply-To: cs4g6ag@maccs.dcss.mcmaster.ca (Stephen M. Dunn) Organization: McMaster University, Hamilton, Ontario Lines: 16 In article <1990Mar7.002520.10365@calvin.spp.cornell.edu> richard@calvin.spp.cornell.edu (Richard Brittain) writes: $With 4DOS, you can set variable TMP to point to a ramdisk, and all pipe $files will go there. I run mine with a 256k e: drive and this works $for most things. It is amazing how few programs check status on writes though $- very few report errors when the ramdisk fills up during a pipe operation. When using temporary files, yes, it is a very good idea to ensure that you aren't running out of room. However, for pipes implemented by DOS by playing with the file handle for STDOUT, I thought that there was no way to detect that the disk was full (I could be wrong, though). I'd check it in Duncan, but I'm not near my bookshelf right now. -- Stephen M. Dunn cs4g6ag@maccs.dcss.mcmaster.ca = "\nI'm only an undergraduate!!!\n"; **************************************************************************** "Oooh yes I need some love" - Rush