You don't actually 'convert' the syslog into a Macro as much as you let the system 'playback' the syslog AS IF IT WERE a Macro.
First thing to understand is that if you session truly CRASHED, then that NX session's syslog will be found in the System temp folder, usually located at something like:
C:\Temp
Now if you have not started any other sessions since the crach, it should be the LAST (i.e. newest) file in the \Temp folder with the files extension of
.syslog .
Now while the procedure to 'play' the syslog is pretty simple, there are a few caveats. For one, if during the session where NX crashed you had performed any File -> Save or File -> Save As operations, you will need to isolate that portion of the syslog which was recorded AFTER those Save operations. basicaly what we're looking for is only the stuff that came after the last Save and before whatever you were doing when the crash occured. Of course if you didn't perform a Save operation, then you will need the entire file.
Now there are a couple of ground rules. You must start a new session and open the part you were working on when the crash occured and if this part was part of an assembly and any changes in the Work or Displayed part occured (after the last File Save operation) during your session then you will need to open the complete assembly as it was when the crash occured.
OK, lets say that there were no Save or Save-As operations in your session, then start a new session, open the part you were working on and if your session originally started in Modeling go to Modeling, if it was Drafting go to Drafting. Anyway, once your where you need to be, go to...
Tools -> Macro -> Playback...
...and when the file selection dialog comes up navigate to the \Temp folder and in the 'File Name' entry box enter...
*.syslog
...which assures that only .syslog files will be shown. Select the appropriate .syslog file and hit OK and the system should replay your session up to where the crash occurred. Now you may have to be careful here since it IS possible that the system will just crash again (it's supposed to halt just before that, but...) and so if it does crash once more, you'll have to make some changes to the .syslog file.
Open the .syslog file and go to the end and try to find the entries for the command that's causing the problem and delete those lines of &MACRO code. Usually just the last few lines will be enough.
Now go back and replay the .syslog once more.
OK, now if there are any Save or Save-As operations you are going to have to remove the portion of the &MACRO section of the .syslog before you can use it. So open the .syslog life and find the LAST Save or Save-As operation (use the text editors 'find' tool looking for something like 'UG_FILE_SAVE'. So starting there look ahead a few dozens lines are so until you get to something which says something like:
Part::SaveManager saved 1 parts successfully.
Now you will need to delete that line and everything which came before it back to a line which reads:
&MACRO *****************
Now do NOT delete this line as it the actual FIRST line in that part of the .syslog file which will be played-back as a macro and the system will be looking for that line so that it knows where to start.
Anyway, that's a bit complex and remember, there is no guarantee that this will work as there are many things that could have occurred (and which was recorded) which may causet the playback to fail or to end-up giving you the incorrect results so use this with caution knowing that it's only here to cover emergencies.
That being said, good luck and if you ever have to do this let us know how it turned out, OK?
John R. Baker, P.E.
Product 'Evangelist'
Product Design Solutions
Siemens PLM Software Inc.
Industry Sector
Cypress, CA
To an Engineer, the glass is twice as big as it needs to be.
