This content has been marked as final. Show 16 replies
I can feel your pain! I have the same REALLY ANNOYING problem. I've called Mathsoft and sent a detailed bug report last December and again in January but so far I haven't received any answer.
By the way, if you go to this URL:
you will find the following statement:
"Contacting us by Email
Email support is available at firstname.lastname@example.org. A Support Representative will respond to your question within 3 business days. "
Well these have been 3 loooooooong days...
I have had this problem. It is not a problem with developer studio as I have had the message on a machine which does not have Developer installed.
The latest advice from Mathsoft is to install as Administrator. Open and initialise mathcad as administrator, before logging off. Then log off and log back on as a user. Mathcad should now accessible to users.
I may be talking about a different aspect of the same problem, from Mathsoft advice it would seem this 'unpack debugger' error is a generic problem with several affects. I attach Mathsoft's advice on it.
----- Forwarded by Jacqui Cheswick/Users/AdeptScientific on 18/02/2002 10:42 -----
One way the Unload debugger error happens is if an Administrator installs Mathcad 2001i and finishes install, logs off and does not run Mathcad and authenticate it. If a non-Admin user logs on and starts Mathcad before it has been authenticated by an admin user then the debugger error appears. This may occur in other situations where non-admin users are running Mathcad.
Can you ask your users to install Mathcad as Administrators. Launch Mathcad and authenticate and then log off and back on again as non-admins? Please let me know how this turns out.
Hope this is some help.
This is interesting. In my case however I am always logged in as a member of the Administrators group. Hence, all my software is installed with Administrator "privileges", including Dev. Studio and Mathcad.
What I find comforting though is that apparently Mathsoft has been researching this problem. I still wish they would provide more feedback to the user when a bug is reported. It's OK to tell me it will only be fixed in the next release! But at least let me know that this is not just a problem on my machine.
Of course the problem is not in Mathcad installing or so on. The problem is encounter that Mathcad 2001i check at startup is it loading under debugger or not and prevent to load if it's run under debugger. To determine it is not so complicated. The major problem that I can't see the internal variable in my USEREFI function.
For creating my USEREFI functions I use Microsoft Visual C++ 6.0. And when I set in Debug mode to run Mathcad for debugging my function I can't load it and debug. And I can only check the function result and can't check internal values in my function while it runs.
This is very big problem. The major lack in Mathcad programming from the point of view of developer is the absence of ability to view variables values while any function calculated.
I think I just discovered why we're getting the "unload your debugger" message when creating a user DLL: Mathsoft2001i actually installs along with a new piece of licensing software that causes the problem. After installing Mathcad I have a new "C:\C_DILLA\" directory sitting on my HD. This directory contains a hidden subfolder called "SafeCast Product Licences" containing what I assume is the license file itself. Then there is another directory:
C:\Documents and Settings\xavier\Local Settings\TEMP\~ef87a1\
which contains a bunch of files. One of them, a text file, reads:
SafeCast - Example Default Contact File Copyright (C) 1998, 1999 C-Dilla Ltd.
Please contact the helpdesk using one of the following methods:
Address: Mathsoft Engineering & Education, Inc.
101 Main Street
Cambridge, Massachussetts 02142.1521
More interesting is a file named "S0010409.cfg" which contains a bunch of messages related to licensing issues as well as the dreaded "You must unload your debugger before you can run this program".
In conclusion, it looks as if we are now prevented from running the debugger because this could allow somebody to break through the license protection. I really hope this is only a temporary "feature"... that will soon disappear.
Two more side notes:
C_dilla uses one (or more) sectors on the HD, so a HD clean can do some harm as well.
C_dilla can't run any machine and/or HD. On my IBM 570 I can't make any C_dilla protected program run - so far. If somebody have a trick to make it work I'll be happy to hear about it. Until then I'll stay with 2001.
The debugging issue arises from copy-protection restrictions.
Here is a workaround. To edit your project, close the Mathcad debug session and then open the project using the following steps:
1) Start Mathcad.exe.
2) Start the debugger from Visual Studio by attaching to the mathcad.exe process.
3) Open the source code file related to the DLL or OCX that you wish to debug and place breakpoints where desired. (This assumes that the user DLL or OCX was loaded as a result of launching Mathcad or inserting a component into a worksheet.)
4) Debug as you normally would have.
We will continue to search for alternative ways for people to write and debug .dlls, and we appreciate your understanding and patience while we investigate other solutions.
If you have further questions about this please contact email@example.com.