From: Eric Gillespie Newsgroups: comp.os.msdos.djgpp Subject: Pipes and how to seek Date: Sat, 7 Mar 1998 17:05:38 +1300 Organization: Cave Rock Internet subscriber Lines: 28 Message-ID: Reply-To: viking AT caverock DOT net DOT nz NNTP-Posting-Host: 3501 AT 202 DOT 37 DOT 100 DOT 19 Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cache-Post-Path: hydrogen.caverock.co.nz!unknown AT central DOT caverock DOT co DOT nz To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Precedence: bulk Hi all - have a wee problem that I can't find anything in the FAQ about. I believe pipes under DJGPP are simulated by using temporary files in the %TEMP% directory. The problem I have is this - I wish to handle stdin with a program of mine, and I sometimes cat the output towards my program through a pipe. Only thing is, hexdump runs out of bytes way before cat has finished. I.E brick:~$ cat hexdump.o | hexdump (hexdump.o is about 27k) hexdump displays about 3.5k of file, and I can't fseek within the pipe - the program locks up when I try to do this, though I can display all bytes from the beginning to the end of what hexdump has (all 3.5k of them...) I wish this was a little clearer, but I'd have to post about 650-700 lines of code to show you what I meant...how can I get a pipe to display the ENTIRE contents of what I pass to it? Is it something to do with cat, or with my programming, or just the limitations of the OpenDOS environment? Also, does anyone know who I could write to about sorting out bugs with the LONGNAME tsr (supporting WIN'95-like long names)? I'm having strange reactions in some directories but not others... I'll let that do for the moment, and will keep on the ball at this end watching for replies, though if you want to email me, it will be faster. Cheers for the moment, The Viking, root of the Flying Brick...