![]() Saving it as a copy-paste new drawing does not help either.įeatures Terminal Services in Remote Admin Mode, Multiprocessor Free, OEM-VersionĭEP Policy OptIn (only Windows system binaries)Īutomatic UpdatesĚutomatic (Recommended) Saving as an earlier version, does not change anything. My biggest problem are at this moment the unpredictable hatchings. The audit command sometimes results in a few errors that seem to be fixed, but is does not solve the problem afterwards. Thanks for your reply, could not reply earlier as I was abroad. Close and restart progeCAD, open new saved file and run audit for any errors.Ħ) The next step, after all the above has been carried out unsuccessfully, is to email the drawing to us. ![]() 2002 under different file name, close and reopen progeCAD & load the 2002-version fileĥ) Open a new blank file and copy-paste the entire drawing to the new file and save under a different name. When ever such drawing-related "stability" issues are reported, please always remember to post the following details with your problem description:ġ) System configuration - OS & SP version, RAM, HD, Printer type, Anti-virus software, progeCAD Version including patch version.Ģ) RESULTS from AUDIT command - any errors?ģ) Background of drawing being edited - where does it come from, how big (MB), any blocks or XREFs including layout border blocks (how old are the block or xref files?)Ĥ) Steps to repeat the crash - if possibleġ) Check the system error log for details of the crashĢ) Ask us to send the crash reporting tool HEREģ) What happens when you run the audit command - any errors found?Ĥ) "Save as" DWG earlier version i.e. ![]() ![]() More often now, crashes are linked to editing older legacy drawings rather than starting with new drawings. ![]() We are going to treat the hatching issue as separate from the crashing issue. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |