Toolkit start error
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Toolkit start error
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
Solved! Go to Solution.
- Labels:
-
Other
-
ProToolkit
-
Toolkit
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
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"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Hi there, Thanks for your response. After changing my location shorter I got another error tab like below,
"pt_inst_test; read error"
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
@Mani_designer wrote:
Hi there, Thanks for your response. After changing my location shorter I got another error tab like below,
"pt_inst_test; read error"
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
Hi,
try using absolute paths without variables in EXEC_FILE and TEXT_DIR lines.
Martin Hanák
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Still I have the same error. should I need to debug or use compile the .dll file? (FIle location is in the same)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Hello,
you might verify the directory paths by opening the info window
Inside this window all paths are displayed in a resolved manner (values of environment variables called out, absolute path...).
Make sure paths are correct.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
After Checking with that method I got the below message in that info page,
"
Auxiliary application Information
==================================================
Application 2: pt_install_test
Exec path: C:\Program Files\PTC\Creo 11.0.3.0\Common Files\protoolkit\protk_appls\pt_install_test\pt_install_test.dll
Text path: C:\Program Files\PTC\Creo 11.0.3.0\Common Files\protoolkit\protk_appls\pt_install_test
Version unknown
Application is not running.
"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Just to clarify, the file pt_install_test.dll does exist in the directory "C:\Program Files\PTC\Creo 11.0.3.0\Common Files\protoolkit\protk_appls\pt_install_test\" ?
As, at least in Creo 11.0.1.0, PTC does not provide the dll-file pt_install_test.dll out of the box, so I assume you used the PTC given file TestInstall.c to compile it on your own, correct?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Yes you are right. There is no pt_install_test.dll exists. I am trying to reinstall Creo and then Ill check. IS it ok to reinstall or is there any other method to do that?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
To learn this Creo toolkit from scratch, is there any online resources available or PTC support for this? I am beginner to this process,
Thank you..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
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"
