You see SHARE as a problem - I see SHARE as a warning
that applications are doing something stupid! <g>
Without delving back into the various side-effects of
file sharing violations (they depend on many factors),
you seem to have missed the point about "closing
standard output" ... When standard output is not
being redirected, it matters not whether an application
specifically "closes" standard output (certainly, once
it has no further need for writing to it ...) - it is a device,
not a disk file, after all. However, when standard output
is redirected, it is no longer the 'console' device, but
an actual disk file, just as if the application itself had
explicitly opened a disk file. In that case, it is important
to close the file, to allow other applications to access
it. Normally, this is no drama for an application, because
the O/S will close it anyway when the application itself
closes. For a TSR though, the situation is different, and
the TSR needs to explicitly close the file, else it will
remain "for ever more" open by the TSR (if you look at
Ralf Brown's interrupt list about TSR's, you will see a
warning to this effect ...).
In summary, standard output is a normal disk file
when redirected, and an application needs to keep
this in mind - ie. if the application is going to "go
resident", it needs to "close" standard output when
it has finished with it ...
Joe.
> -----Original Message-----
> From: Clarence Verge [SMTP:[EMAIL PROTECTED]]
> Sent: Thursday, 22 February 2001 7:08
> To: [EMAIL PROTECTED]
> Subject: Re: DOS command line redirection for TSRs
>
> da Silva, Joe wrote:
> >
> > Anyway, I have e-mailed David Lindauer, asking that LSPPP
> > close "standard output" just before going resident. Assuming
> > he is happy to do this, we can once again redirect LSPPP's
> > output to PPP.LOG (for diagnostic purposes, I guess), without
> > the "side effects" ... :-)
>
> Remind me again. What side effects ?
> I _always_ direct LSPPP/EPPPD output to ppp.log without problem.
> I can only go back in this thread to a point where you mentioned SHARE.
> I don't use SHARE. Maybe that's the source of your problem ?
>
> Standard output can't be closed. It can only be re-directed.
>
> You CAN elect to not send anything to STDOUT, which is probably what
> happens
> when you close the file handle, but this is not the only (or original) way
> to access STDOUT.
> Or you can use another output method and do an end run around DOS, but
> I don't see why you would want to.
>
> IMHO, _if_ it WAS possible to kill STDOUT, the "cure" would be much
> worse than the perceived problem.
>
> - Clarence Verge
> --
> - Help stamp out FATWARE. As a start visit: http://home.arachne.cz/
> --
