Jump to content

Welcome to eMastercam

Register now to participate in the forums, access the download area, buy Mastercam training materials, post processors and more. This message will be removed once you have signed in.

Use your display name or email address to sign in:

Chris Bell CNC Software

CNC Software
  • Posts

    567
  • Joined

  • Last visited

Everything posted by Chris Bell CNC Software

  1. Bob, what resolution and DPI are you running on that system? I've never come across this problem before, either.
  2. Mark, You have an automated backup process that is restoring tool libraries to previous states? Why is a "backup" restoring files? Seems kind of backwards. If it's really going by timestamps, any change at all to a tool library is going to change the time stamp. Try editing the diameter of a tool in MILL_INCH.TOOLS and saving it. The Date Modified will be updated. How many versions of Mastercam do you have on your machine? Is there any chance that you are opening X3 part files in X4, but the operations and custom tools are pointing back to the X3 directory structure? You might be updating the X3 tool libraries and not the X4 ones.
  3. Hi Leandro, What error message are you receiving when trying to run Engrave? Where is it failing? What OS are you running (32 or 64-bit as well)? Thank you.
  4. benk, You have to save it locally and then double-click the *.exe. Running it from our server isn't going to work.
  5. Mastercam X4 MU3 has been released to all customers. It is available for download on Mastercam.com. Mastercam X4 MU3 is a cumulative installation that contains all of the bug fixes in X4 MU1, X4 MU2 and more. All of the translators have also been updated to the 2010 versions. This must be installed on top of Mastercam X4, X4 MU1, or X4 MU2. If X4 MU1 or X4 MU2 is already installed on a system, the "Mastercam X4 MU1 / MU2" entry in Add / Remove Programs (Programs and Features in Windows™ Vista and 7) will be replaced with the MU3 entry. If MU3 is uninstalled, your Mastercam version will be rolled back to X4. Your maintenance date must be 12-31-09 or later to run X4 MU3. The Mastercam.exe version number is 13.3.0.22. Remember, all X4, X4 MU1, and X4 MU2 third-party add-ons or CHooks need to be rebuilt with the Mastercam X4 MU3 SDK. Please contact your vendor for updated versions of these applications. To install: 1. Click on the mastercamx4-mu3-web.exe link and save it to your computer. 2. After the download is complete, double click on the *.exe to begin the installation. 3. Follow the installation instructions. If you have any problems or suggestions, do not hesitate to contact [email protected]. Thank you.
  6. quote: Chris.. I have to take issue with this.. If you are accessing the nethasp via a VPN tunnel, you are running the app on the computer at home. Only license inquiries travel back and forth over the internet.. everything else is running on the home computer. I've never tried this with Mastercam, but Vericut rocks on my Win7x64 workstation at home. Ahh but we're talking about a HASP, not a NetHASP This has been done by customers with NetHASPs doing exactly what Tom stated, but it is not a supported method.
  7. Accessing a HASP over VPN / Remote Desktop / GoToMyPC isn't ideal, as graphics rendering is painfully slow (these programs all disable hardware acceleration at the Windows level, not a Mastercam issue ). Your best bet would be DesignLT, but that doesn't have any toolpathing functionality. Demo HLE is okay if you are just using it to learn the software, but HLE parts are not compatible with an Industrial SIM. Just be careful with the SIM... don't lose that little guy.
  8. For the record, Mastercam is not supported on a Mac.
  9. Hi Everyone, Mastercam X4 MU2 has been released to all customers. It is available for download on Mastercam.com. Mastercam X4 MU2 is a cumulative installation that contains all of the bug fixes in X4 MU1 and more. All of the translators have also been updated to the 2010 versions. This must be installed on top of Mastercam X4 or X4 MU1. If X4 MU1 is already installed on a system, the "Mastercam X4 MU1" entry in Add / Remove Programs (Programs and Features in Windows™ Vista and 7) will be replaced with the MU2 entry. If MU2 is uninstalled, your Mastercam version will be rolled back to X4. You must have maintenance through 09-30-09 to run X4 MU2. The Mastercam.exe version number is 13.2.0.10. Remember, all X4 or X4 MU1 third-party add-ons or CHooks need to be rebuilt with the Mastercam X4 MU2 SDK. Please contact your vendor for updated versions of these applications. To install: 1. Click on the mastercamx4-mu2-pc2.exe link and save it to your computer. 2. After the download is complete, double click on the *.exe to begin the installation. 3. Follow the installation instructions. If you have any problems or suggestions, do not hesitate to contact [email protected]. Thank you.
  10. Kevin, thanks for the files. All of them are producing error code 32... so at least that is consistent. And I'll go with the Friday the 13th theory. That, or me slamming my head into my desk cause seismic activity which disrupted toolpath generation Thanks for the help guys, send in those reports if you are crashing.
  11. Verndog, You mentioned on Saturday or Sunday that you crashed several times when running the mccore.dll that I gave you. Could you go into your temp directory and send me the XML files that the crashes created? You already sent me one, but there should be a few more. Remember, they start with the date that they were created, followed by the time, and end with log.xml (something like 11242009083000log.xml it it crashed today at 8:30:00 in the morning). If they were the last crashes you experienced, they will be the top ones in chronological order.
  12. Verndog, send in the crash reports for any instance of the crash. The MORE common problem is the tmpmmx.tmp (x being the number of the temp file written) problem, the error log you sent me was not that one. I'm guessing the error code will be the same, but let's make sure Anyone else who wants the debug build please email me.
  13. Verndog - I looked at your first crash that you sent in today, it gave me a lot of information thanks to the build you are using. Keep sending them in, and thanks for the help. The first error he sent in was caused by a sharing violation. The temp file was created, but we could not read it back in. Something was holding it in memory and was not allowing anything else to read it. Now to keep digging and figure out what is holding it.
  14. Verndog, I sent you another email, but it was bounced for whatever reason (no files attached at all).
  15. quote: 6)It is something new written into Version X4 and X4MU1 that has a trickle down effect with all version X Mastercams. Post hoc ergo propter hoc This very likely is not true (I'm at about 98% certainty with this one) as MCCore.dll is not shared amongst versions, and that is where the crash is coming from. We also have a few users reporting the crash that have never installed X4 or X4 MU1. I have a debug version of X4 MU2 that I would like to try on a few of the affected computers. If anyone is interested, please email me at [email protected]. I can send you a link to the build. Thanks again, everyone.
  16. Hi Peon, I don't think that is related, but it is definitely something I want to look into. You are importing the toolpath using Import Operations in the Operations Manager? Will this occur if you create a new 3D HST operation? Feel free to send me a sample part and email address and I can look at your crash reports. Tom, I like the way you think and wish to subscribe to your newsletter. Those are all possibilities.
  17. Rickster, I'm looking for information and not an attack. Let's keep this professional. Keep the information coming, guys. So far we know 1) It's not OS-specific. 2) It occurs on small and large files, so page file size / "full" temp directory is not likely an issue. 3) Mastercam 3rd party applications are likely not to blame (some people have them installed, others do not) 4) AVG seems to be common amongst the affected computer, but it is not unanimous. Could there be shared definitions in other AV software? 5) Could there be multiple causes to the problem? Rickster uninstalled AV, but still had the problem. Or was there something left behind by the previously-installed software that caused the problem? One other thing to try (anyone who is affected by the the problem), is Windows Firewall or Defender enabled? If so, disable it and see if the problem goes away. We're hoping to have a build with some special code that will help debug the problem. If anyone is interested in participating in some testing who has the crashing problem, please let me know (email me at [email protected]). I'll notify you this weekend when the build is complete. Thank you all for your help and patience with this issue.
  18. As Mastercam Guru stated, get HLE from your reseller. It's free and will do exactly what you're looking for.
  19. To anyone who is having this problem (or who had it in the last few weeks), what AntiVirus software are you running?
  20. Hi guys, We just came up with a solution that may solve the Engrave issue on the x64 systems, but it has NOT been thoroughly tested yet. I am not confident in releasing this yet, and Salahuddin and I have been working on this issue for a few years, so I wanted him to have the opportunity to give this a quick test. I will let all of you know when this is ready for release. Thank you for your patience.
  21. "The demo uses some form of hasp emulation to run in its special "save disabled" mode." This is not true. They can be run side-by-side, but Demo DOES check for HASP Emulators, so you can get the *.exe not valid warning from just running Demo.
  22. If you're not experiencing the problem, then you don't have to change the *.dll. Just know that it will likely be the official Verify *.dll in the next release (unless we make other Verify changes). I'm glad to hear that it is working.
  23. There is a bug in X4 MU1 which causes the stock and tool in Verify to display with no lighting, giving it a black appearance. We have a fix for this issue, and it has been posted on Mastercam.com. To use the fix: 1) Download the file mcverify-fix.zip from the above link. 2) Open your Mastercam X4 MU1 installation directory. 3) Close X4 MU1 if it is open. 4) Rename “MCVerify.dll”. This will prevent the file from being overwritten by the new *.dll. 5) Extract mcverify-fix.zip into the root of your X4 MU1 installation. The new Verify *.dll will be incorporated into the next service pack or maintenance release for X4. Thank you for your patience with this issue, we sincerely apologize for any inconvenience it may have caused. If you encounter any problems with this, please contact [email protected].
  24. Hi guys, We have a fix! Go to Mastercam.com to download it. Below are the installation instructions: 1) Download the file mcverify-fix.zip from the above link. 2) Open your Mastercam X4 MU1 installation directory. 3) Close X4 MU1 if it is open. 4) Rename “MCVerify.dll”. This will prevent the file from being overwritten by the new *.dll. 5) Extract mcverify-fix.zip into the root of your X4 MU1 installation. I'd like to sincerely thank all of you for your help with this issue. The graphics card and driver information helped us track down the problem. I would also like to apologize for any inconvenience this may have caused. If there are any problems, please respond here or send an email to [email protected]. Thanks again.
  25. Hi guys, I logged this as bug number cnc00065718. Thank you.

Join us!

eMastercam - your online source for all things Mastercam.

Together, we are the strongest Mastercam community on the web with over 56,000 members, and our online store offers a wide selection of training materials for all applications and skill levels.

Follow us

×
×
  • Create New...