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

[David Marcus]

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?

 

[Charles Dye]

Just for fun, try this:

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

TPIPE really wants to create that directory.

 

[vefatica]

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".

 

[vefatica]

Just for fun, try this:

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!

 

[David Marcus]

Does VIEW work? I don't thing V is (necessarily) intended to work "stand-alone".

Quite right. VIEW does work. I forgot the command was VIEW, not V.

 

[vefatica]

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.

 

[thedave]

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.

Don't worry, Rex already said it's only there for the beta.
*wink*

 

[rconn]

The textpipeengine.dll developers inadvertently left in the aemail logging in the release version. They said it will be removed in their next build. (No, I don't have a date for that.)

 

[rconn]

Does VIEW work? I don't thing V is (necessarily) intended to work "stand-alone".

V.EXE cannot be used stand-alone, under any circumstances.