Hi Rob,
On Fri, 30 Jul 1999, Robert wrote:
> > .. Addition to Tom's "AmIRC 3.1 Wish List"
> >
> > On startup, having AmIRC "read" the Envarc: directory before
> > trying to make the Vapor directory that is already present.
>
> Well, I think I'm missing something here - it doesn't seem like
> an unreasonable thing to do - try to make the directory anyway.
> If it's already there, what does it matter?
.. I think it is very "UN-reasonable" to try and make a directory
that is already there, when all it has to do is 'read' it, to see.
> Certainly it has no visible side-effect on my machine, and I
> guess not on almost everyone else's machine.
>
> Why would it?
> What problem does it cause on your machine???
.. It causes problems with me, because I keep my drives locked.
.. I explained this on July 27th, with the capture from the
SnoopDOS program.
[BEGIN]------------------------------
:
: ... Backwards, yes/no??? Due to this order of writing before
: reading, I end up having to keep cancelling requestors before
: I can get going.
:
: Process Name Action Target Name Options Res.
: ------------ ------ ----------- ------- ----
: AmIRC MakeDir ENV:Vapor Fail
: AmIRC MakeDir ENVARC:Vapor Fail
: AmIRC Open ENVARC:Vapor/AmIRC_LASTUSED Read OK
: AmIRC Open ENV:Vapor/AmIRC_LASTUSEDDIR Write OK
:
[END]------------------------------
.. My suggestion still stands, and I would like to see AmIRC
programmed so that it "reads" the Envarc: directory, before
trying to write one. I'd like it to read before writing, even
if this suggestion seems totally idiotic to eveyone else but
me. :)
Thanks,
Charlene
----------------------------------------
AmTelnet / AmFTP / AmIRC Registered User
----------------------------------------
. If you ate today, thank a farmer
__________________________________________________________
AmIRC Mailing List - Info & Archive: http://www.vapor.com/
For Listserver Help: <[EMAIL PROTECTED]>, "HELP"
To Unsubscribe: <[EMAIL PROTECTED]>, "UNSUBSCRIBE"
