Skip to main content
M
Mani_designer10-Marble
10-Marble
March 4, 2025
Solved

Toolkit start error

  • March 4, 2025
  • 1 reply
  • 2109 views

Hi,

I have come with an issue that when I start the protoolkit.dat fie the following error has been shown. I am newbie to this toolkit process and I am learning that think right. Can any one help me with that issue. What mistake I have done?

Thank you

Mani_designer_0-1741085273056.png

 

Best answer by HannesBuxbaum

For a complete introduction see those links and the Creo Parametric included API documentation and examples:

[Knowledge Hub] Creo Parametric - Customization
https://www.ptc.com/en/support/article/CS318231

Creo Object TOOLKIT C++ Help Center
https://support.ptc.com/help/creo_toolkit/otk_cpp_pma/r11.0/usascii/

 

Shipped with every Creo Parametric (select optional API during Creo setup):
OTK:
<Creo Common Files>\otk_cpp_doc\
- "Getting started Guide" (PDF)
- "Release Notes" (PDF)
- "User's Guide" (PDF/HTML)


<Creo Common Files>\otk_cpp_doc\objecttoolkit_Creo\
- "API Wizard"


C TOOLKIT:
<Creo Common Files>\protoolkit\
- "Getting started Guide" (PDF)
- "Release Notes" (PDF)
- "User's Guide" (PDF/HTML)


<Creo Common Files>\protoolkit\protkdoc\
- "API Wizard"


"Release Notes" (RelNotes): important information for each Creo release (new/deprecated/dropped functions)
"User's Guide" (OTKUG/TKUSE): detailed description on API topics; they complement each other – use both!
"API Wizard": function/class listing with function/method details (in/out) and links to examples (if existing)


💡Examples: source code and make files:
<Creo Common Files>\protoolkit\protk_appls\
<Creo Common Files>\otk\otk_cpp\


For OTK & OTK Java & TOOLKIT: Creo UI Editor
<Creo Common Files>\applications\creouieditor\otk_cpp_doc\creo_uifc_ug.pdf
- "Creo User Interface Foundation Classes User Guide"

1 reply

M
msteffke15-Moonstone
15-Moonstone
March 4, 2025

Ive had this message for a couple different reasons.  Either it cant find the .dll  in your exec_file line, or the folder in your text_dir does not exist.

     Here are a couple long shots it could be:   Possibly your text folder may also be missing the resource and usascii folders.   (or whatever language you use)   or:     your exec_file line is quite long.    I dont know if there is a rule about how many characters you can have, but I woudnt be surprised that if the line exceeded 80 characters it would be invalid.   Try using a destination with a shorter path.   

M
Mani_designer10-MarbleAuthor
10-Marble
March 5, 2025

Hi there, Thanks for your response. After changing my location shorter I got another error tab like below,

 

"pt_inst_test; read error"

Mani_designer_0-1741150190754.png

And the protoolkit.dat contains that follows

 

NAME pt_inst_test
EXEC_FILE ./$PRO_MACHINE_TYPE/obj/pt_inst_test.dll
TEXT_DIR ./protk_appls/pt_install_test/text
STARTUP dll
REVISION 18
END

 

Correct me if I am wrong in that procedure.

Thank you

 

F
FabianWolf14-Alexandrite
14-Alexandrite
March 6, 2025

Hello,

you might verify the directory paths by opening the info window

 

img.png 

Inside this window all paths are displayed in a resolved manner (values of environment variables called out, absolute path...).

Make sure paths are correct.

 

Terms & ConditionsCookie settingsAccessibility statement