Error log

[Jammer™]

Hey all, When MC crashes during a toolpath generation, a window comes up and says an "error log" is being created. Where would I find such a log, and what kind of info would I find in this here log? Thank you for your support!

[Lathe-Mill]

That has been happenning to me lately, i will like to know that aswell

[Rekd™]

Click on details, you can copy the log and paste it into an editor to save it. Not sure if it does this automatically.

 

The data stored there is debugging information that can supposedly be used to find out why the app is crashing. Most of it will be un-readable, but will describe the process, memory address where the error occurred, and a bunch of other data.

 

HTEY

 

'Rekd

[Jammer™]

Rekd, Are you talking about a details button in the dialog box? If so, it doesn't have one. I believe it only has a cancel button.

[Bullines]

It's a Microsoft log (usually saved in file called appcompat.txt) and not a Mastercam one. Any details in it would be regarding how the Mastercam EXE was interacting with Windows and not info such as what Mastercam was doing before the crash.

[Lars Christensen]

I am getting an alarm once and awhile, sometimes it is when I try to fit a window other times when I try to do a toolpath. I normelly reboot the computer and it seems to take care of it. I found the folder last week were it is storing these error logs, offcourse now I can't remember were.

I will try to find out when I get in today.

 

Lars

[Bullines]

appcompat.txt is usually stored in the temporary directory defined in the TEMP user variable. On Windows XP/2000 systems, this defaults to X:Documents and Settings[uSERNAME]Local SettingsTemp

[Müřlıń®]

You can send this log file to Microsoft and they can tell you exactly why Windows crashed.

 

I am still using ver 9.0 at the shop and havent ran into these crashes while trying to crunch a toolpath. In fact, I can't remember ever doing so.

 

Jaws and T@[email protected] you crash on a toolpath that is using a solid in 9.1??

 

just curious......

 

one cannot be too informed

 

 

Murlin

[crazy^millman]

They may not but I just sepnt the last 30 minutes trying to wrtie this last toolpath on a part so I could get the hell out here at a decent time today. I am using 9.1 sp2 and I can hear you surfaces a coming did that still crashed. I found in I picked the flowline parameters for direction in a different order it did not crash just had to play with it.

 

Crazy Millman teh ohhhhhhhhhhhh

[cadcam]

Bullines,I am starting to wonder if we should all let them send them to Microsoft and let it bombbard them with this mail.

Fix Windblows so it works right with my software MASTERCAM.

[crazy^millman]

a million freaking percent ot that Jay I know the problems are with windows in most cases.

 

 

Crazy Millman

[crazy^millman]

Ok bulliness how you do that you got my intrested peaked.

 

Crazy Millman

[Bullines]

The Microsoft server that receives all of these error logs that people send in must do some wicked parsing and routing of the data in those logs. Errors that are caused by Windows itself or a third-party app that was calling API calls might be flagged with a high priority. If a third-party app just simply crashes or causes a serious exception, I think those would get flagged with low priorty (or maybe no priority at all). Otherwise, Microsoft would have to look at the bugs of other people. And trust me, Microsoft has a hard enough time fixing their own bugs

 

For example, if I compile/link a simple C++ program that tries to dereference a null pointer, I'll be prompted to send this in to Microsoft. You think they want to deal with my oversight?

 

code:

---

void main (void)

{

// pointer to an integer and inited to NULL

int *pMyPointer = NULL;

 

 

// derefernce time

*pMyPointer = 1; // Tick. Tick. Kablammo!

}

---

I disable the Error Reporting Service to save a few megs of RAM

[Bullines]

quote:

---

Ok bulliness how you do that you got my intrested peaked

---

First, you must be logged in with administrator privilages. Then go to the Administrative Tools (found in the Control Panel), launch the Services applet. Find the service called "Error Reporting Service" and double-click it. Then click the "Stop" button to stop the service. Finally, in the "Startup type" combo box, select "Disabled" so that it won't start up again. HTH.

[crazy^millman]

Ok Bulliness looks like I reading your mind or something. How did you flip our postings I wonder hummmm. Just kidding around I appericate the tip could have maybe found ti but never hurt too ask a pro now does it and might be a helpful tip for soemoen else.

 

 

Crazy Millman

 

[ 10-25-2003, 02:16 PM: Message edited by: Millman^Crazy ]