Welcome!

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

SignUp Now!

Issue running TPipe from a script in BDebugger

M

MGibs

Jun
149
13
Still seeing the issue running TPipe from within BDebugger using V36 Build 18.

Same issue described in this thread

1775519356757.webp
 
Not reproducible here. (And not the issue I marked as done in the Suggestions forum.)

And your screenshot doesn't make sense - you're not in BDEBUGGER, you're still in the TCC tab window. And you haven't run TPIPE.

What happens if you just run BDEBUGGER (with no arguments), and then load your TestTPipe.BTM in a BDEBUGGER tab, and start debugging?
 
Sorry for the confusion Rex. In the screenshot above I started with a Type of the TestTPipe.btm file so you could see the contents.

Then I ran BDebugger passing in the TestTPipe.btm file as a parameter.

I neglected to tell you what I did in the BDebugger. All I did there was click the "Start" button and then clicked the "Run to breakpoint or end" button.

When the debugger ran the BTM file, that's what generated the error message shown at the bottom of the screenshot.

I have attached a zip file containing a video of exactly what I did. (The forum wouldn't allow me to upload the .MP4 video directly.)

I did try running BDEBUGGER (with no arguments) and then loading the .BTM file. It produced exactly the same results.

Let me know if there is anything else I can do help troubleshoot this.

-Michael

P.S. I'm beginning to wonder if this is an issue with my machine. Is anyone else able to reproduce my results with Build 18?
 

Attachments

I'm also still getting (build 18) "Error - Can't access TextPipeEngine64.dll" when debugging a BTM that uses TPIPE.

Code: 
d:\tc36> d /f te*.dll
D:\tc36\textpipeengine64.dll

P.S., I also get it with v35.
 
I issue bdebugger xavtemp.btm (I posted that BTM in the beta forum), press the start button, and choose run to breakpoint from the menu. If I choose start without debugging the same thing happens. The same thing happens in v35.

Code: 
v:\> which bdebugger
bdebugger is an internal command
 
The problem remains when I remove all plugins from my Plugins directory.
 
rconn said:
I think you're not telling me what you're really doing.

List EVERY step you're taking, and what you see at each step.
Click to expand...

With all due respect, I have tried to explain every step in prior posts. I even attached a video so you could see what I was doing.

Here's a simple self-contained script to demonstrate the issue.

Code: 
@echo off

if exist "TestInput.txt" del "TestInput.txt"
if exist "TestOutput.txt" del "TestOutput.txt"

echo This is a test >TestInput.txt

tpipe /input=Testinput.txt /output=TestOutput.txt /simple=5

dir testoutput.txt

quit

Here's the steps to recreate exactly what I did
  • Save this to a file (e.g. named TestTPipe.btm)
  • Then Run BDEBUGGER TestTPipe.btm (or whatever you named it.)
  • From within the debugger click the "Start" button
  • From within the debugger click the "Run to breakpoint or end" button
  • Check the results in the TCC window
Both Vince and I are receiving the following error message in the TCC window

Code: 
TCC: (Sys) C:\batfile\testtpipe2.btm [8]  The parameter is incorrect.
 "Error - Can't access TextPipeEngine64.dll"

What result do you see when you run this script in BDebugger?
 
Try it with build 20 (already uploaded). I added more error handling so it should hopefully give more detailed information on exactly what is failing. Also added a check for someone (plugin or injected code) doing a COM initialization with a different threading model.

What result do you see when you run this script in BDebugger?
Click to expand...

It runs successfully for me.
 
rconn said:
Try it with build 20 (already uploaded). I added more error handling so it should hopefully give more detailed information on exactly what is failing. Also added a check for someone (plugin or injected code) doing a COM initialization with a different threading model.



It runs successfully for me.
Click to expand...

New error with build 20

TCC: (Sys) C:\batfile\TestTPipe2.btm [8] The parameter is incorrect.
"Error - Can't create TextPipeEngine64.dll instance (0x80040154)"
 
With build 21 I get the "instance" error.

Code: 
TCC 36.00.21 x64 (d:\tc36\tcc.exe)
Microsoft Windows 11 Pro for Workstations
10.0.26200.8037 (25H2)
WindowsTerminal 1.23.2601.21001 (1.23.211.0)

v:\> bdebugger xavtemp.btm
TCC: (Sys) V:\xavtemp.btm [14]  The parameter is incorrect.
 "Error - Can't create TextPipeEngine64.dll instance (0x80040154)"
 
rconn said:
Try it again with build 21 (already uploaded). I added a check for restrictive COM security settings, and adjusted the TextPipeEngine64.dll CreateInstance parameters accordingly.
Click to expand...

Looks like the same error for me too.

Code: 
TCC  36.00.21 x64   Windows 11 [Version 10.0.26200.8037]
Copyright 2026 JP Software Inc.  All Rights Reserved

TCC: (Sys) C:\batfile\TestTPipe2.btm [8]  The parameter is incorrect.
 "Error - Can't create TextPipeEngine64.dll instance (0x80040154)"
 
rconn said:
One more thing to try - start an elevated session (TCC or CMD), go to the TCMD36 installation directory, and run this command:

Code: 
regsvr32 textpipeengine64.dll

and let me know if regsvr32 fails or succeeds. If it succeeds, try BDEBUGGER again.
Click to expand...

Bingo! That worked. Meaning regsrvr32 succeeded...and the BDebugger session with TPipe worked as well.
 
Last edited:
You must log in or register to reply here.
Back
Top