THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 04/05/2005 at 13:28, xxxxxxxx wrote:
Cinema 4D Version: 8.2
Platform: Windows ; Mac OSX ;
Language(s) : C++ ;
I'm trying to profile my code. I can turn on the 'profile' option in the project settings, and create a map file, but Build->Profile remains greyed out.
My understanding is that MSVC6.0 can't directly profile a DLL from the GUI.
So, following http://support.microsoft.com/kb/179269
I'm trying to generate a profile from the command line.
I believe I've got the batch file doing the right thing, but C4D fails to startup - giving an error dialog saying:-
Internal Error: String Resource not found!
The 'resource' directory seems to be corrupt or missing.
I've discovered that I get the exact same message if I try to run cinema_4d.exe directly from the command prompt.
So, I'm guessing that there's some critical environment difference between running the exe from the command line, and running it from the icon.
Can anyone tell me what I need to do. So close, yet so far...
Cheers - Steve
On 08/05/2005 at 10:52, xxxxxxxx wrote:
On 10/05/2005 at 12:05, xxxxxxxx wrote:
I have tried and started C4d 8.2 full, c4d 85 demo and c4d 9102 demo, by clicking on the icon, double clicking on the filename in the explorer and in the run box with a command line 'c:\program files\cinemadir\cinema 4d demo.exe'
I have not tried to start c4d from dos, i don't think that will work.
All exe's run fine.
maybe t'here's an environment variable?
however i don't think so because c4d is very forgiving on moving from dir to dir.
Hope this helps,
On 10/05/2005 at 12:40, xxxxxxxx wrote:
There must be something wrong with your installation, running from the command prompt/double clicking the executable works fine here.
I've been using a batch file to run the profiler since R7 without problems.
On 10/05/2005 at 13:38, xxxxxxxx wrote:
Thanks for the responses.
I've now managed to get it working, but I still don't really know why...
It runs fine from the command line if I type:
in the C4D directory.
If instead I type:
in the same directory, it tries to startup and fails at an early stage as reported above.
So this suggests that it's finding a different binary in the path first. BUT, if I try the same command from a different directory, it claims there's no such binary, which disproves the idea that it's finding a different binary via the path.
So, I can now get it to work, but I still don't know why it doesn't work without the '.'.