Welcome!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

SignUp Now!

TPIPE works without being in path, but not V; aemail

Jun
768
6
In version 14.00.27, TPIPE now works without the TCM14x64 directory being in the path, but V still does not. Is that intentional?

TPIPE creates a c:\aemail directory. Is that intentional?
 
Just for fun, try this:

Code:
rd /s /q c:\aemail
> c:\aemail
attrib +shr c:\aemail
tpipe

TPIPE really wants to create that directory.
 
In version 14.00.27, TPIPE now works without the TCM14x64 directory being in the path, but V still does not. Is that intentional?

TPIPE creates a c:\aemail directory. Is that intentional?
Does VIEW work? I don't thing V is (necessarily) intended to work "stand-alone".
 
Just for fun, try this:

Code:
rd /s /q c:\aemail
> c:\aemail
attrib +shr c:\aemail
tpipe

TPIPE really wants to create that directory.
I wonder what would happen if you took away write privileges in \aemail!
 
I wonder what would happen if you took away write privileges in \aemail!
Answer: After removing the authenticated user's write-privilege on datamystic.log, TPIPE.EXE crashes and leaves the TCC from which it was started useless.
 

Similar threads

Back
Top