progeCAD support, tips and troubleshooting forum. progeCAD works very similar to some versions of AutoCAD. Moderated.

Moderators: caddit, Moderators

#1177 by 10augustus
Thu Jul 15, 2010 7:19 pm
Working for some months with progecad, still have lots of problems. Not one drawing that did not crash in one way or another... many problems ; for instance ; hatching suddenly becomes unpredictable. I have a simple square to hatch, the result is some hatching inside it, som outside it as if there were invisible boundaries and the ones drawn are not respected. error message :"m_rFrequency=31.496063.m_rBaseN=0.000000.m_mFirst-2147483648,m_nLast=22842" everything stuck ! ending the program with taskmanager is the only way to get out !
Whats wrong ?
#1179 by caddit
Mon Jul 19, 2010 9:13 am
Hello 10augustus,

We are going to treat the hatching issue as separate from the crashing issue. More often now, crashes are linked to editing older legacy drawings rather than starting with new drawings.

When ever such drawing-related "stability" issues are reported, please always remember to post the following details with your problem description:

1) System configuration - OS & SP version, RAM, HD, Printer type, Anti-virus software, progeCAD Version including patch version..
2) RESULTS from AUDIT command - any errors?
3) 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?)
4) Steps to repeat the crash - if possible

Things you can try:
1) Check the system error log for details of the crash
2) Ask us to send the crash reporting tool HERE
3) What happens when you run the audit command - any errors found?
4) "Save as" DWG earlier version i.e. 2002 under different file name, close and reopen progeCAD & load the 2002-version file
5) Open a new blank file and copy-paste the entire drawing to the new file and save under a different name. Close and restart progeCAD, open new saved file and run audit for any errors.
6) The next step, after all the above has been carried out unsuccessfully, is to email the drawing to us.
#1218 by 10augustus
Fri Aug 20, 2010 3:30 pm
Thanks for your reply, could not reply earlier as I was abroad.

The audit command sometimes results in a few errors that seem to be fixed, but is does not solve the problem afterwards.

My biggest problem are at this moment the unpredictable hatchings.

Saving as an earlier version , does not change anything.
Saving it as a copy-paste new drawing does not help either.

Thanks !

System information :
Property Value
Name Windows XP Personal Service Pack 3
Features Terminal Services in Remote Admin Mode, Multiprocessor Free, OEM-Version
Activation Status Activated
Checked Build No
Boot Device \Device\HarddiskVolume1
System Device \Device\HarddiskVolume1
Kernel Version 5.1.2600.5973
Security 128 bits, 40 bits
Product Name Microsoft Windows XP
Build Lab 2600.xpsp_sp3_gdr.100427-1636
Hardware DEP Available Yes
DEP for 32 Bits Applications Yes
DEP for Drivers Yes
DEP Policy OptIn (only Windows system binaries)
Windows Update's version number 7.4.7600.226
Automatic Updates Automatic (Recommended)
Next Detection Time 21/08/2010 4:24
Scheduled Install Every Day @ 3:00 AM
System Restore Enabled
Machine GUID af25a441-1e13-4160-8c70-9569a54ae017
DMI System UUID 80549290-BD79DE11-99CA0026-188AFCB2
UUID 90925480-79BD-11DE-99CA-0026188AFCB2
Disk Space Disk C: 117 GB Available, 464 GB Total, 117 GB Free
Disk D: 466 GB Available, 466 GB Total, 466 GB Free
Physical Memory 3328 MB Total, 2118 MB Free
Memory Load 36%
Virtual Memory 5212 MB Total, 4020 MB Free
PageFile Name C:\pagefile.sys
PageFile Size 2046 MB
In use 135 MB
Max used 136 MB
Registry Size 8 MB (current), 120 MB (maximum)
Profile GUID {0d23e9c0-aa95-11de-8f4f-806d6172696f}
The system clock interval 15 ms
Disk 0
Size 1000.2 GB
Firmware Version 1AA01118
Serial Number S13PJDWS755243
Interface Serial ATA
Standard ATA/ATAPI-7 | ATA8-ACS version 3b
Transfer Mode (Current / Max) SATA-300 / SATA-300
Features S.M.A.R.T., APM (Disabled), 48bit LBA, NCQ, AAM (Disabled)
Temperature 26 C (78 F)
Drive Letter(s) C: D:
Controller Buffer Size on Drive 32767 KB
Queue Depth 32
Removable No
Cache Enabled (Read / Write) Yes / Yes
SMART Support Yes
Attribute Name Attribute Value Worst Value Threshold Value Raw Data
Raw Read Error Rate (01) 100 100 051 000000000000
Spin Up Time (03) 067 067 011 00000000292C
Start/Stop Count (04) 099 099 000 00000000025C
Reallocated Sector Count (05) 100 100 010 000000000000
Seek Error Rate (07) 100 100 051 000000000000
Seek Time Performance (08) 100 100 015 000000000000
Power On Hours Count (09) 100 100 000 000000000973
Spin Retry Count (0A) 100 100 051 000000000000
Calibration Retry Count (0B) 100 100 000 000000000000
Power Cycle Count (0C) 099 099 000 00000000025C
Soft read error rate (0D) 100 100 000 000000000000
[unknown] (B7) 100 100 000 000000000000
[unknown] (B8) 100 100 000 000000000000
[unknown] (BB) 100 100 000 000000000000
[unknown] (BC) 100 100 000 000000000000
Airflow Temperature (BE) 081 056 000 0000130E0013
HDA Temperature (C2) 074 055 000 00001A0E001A
Hardware ECC recovered (C3) 100 100 000 0000000346D2
Reallocation event count (C4) 100 100 000 000000000000
Current pending sector count (C5) 100 100 000 000000000000
Off-line uncorrectable sector count (C6) 100 100 000 000000000000
Ultra ATA CRC Error Rate (C7) 100 100 000 000000000000
Write Error Rate (C8) 100 100 000 000000000000
Soft read error rate (C9) 253 253 000 000000000000
Memory Summary
Maximum Capacity 16384 MBytes
Memory Slots 4
Error Correction None
DRAM Frequency 401.4 MHz
Memory Timings 5-5-5-18 (CL-RCD-RP-RAS)
Device Locator Slot 1
Manufacturer Transcend Information
Part Number JM800QLU-2G
Serial Number 0007E601
Capacity 2048 MBytes
Memory Type DDR2 (PC2-6400)
Speed 400 MHz (DDR2 800)
Supported Frequencies 200.0 MHz, 266.7 MHz, 400.0 MHz
Memory Timings 3-3-3-9-12 at 200.0 MHz, at 1.8 volts (CL-RCD-RP-RAS-RC)
Memory Timings 4-4-4-12-16 at 266.7 MHz, at 1.8 volts (CL-RCD-RP-RAS-RC)
Memory Timings 5-5-5-18-23 at 400.0 MHz, at 1.8 volts (CL-RCD-RP-RAS-RC)
Data Width 64 bits
Manufacturing Date 2009, Week 2
EPP SPD Support No
XMP SPD Support No
Device Locator Slot 2
Manufacturer Transcend Information
Part Number JM800QLU-2G
Serial Number 0007E72C
Capacity 2048 MBytes
Memory Type DDR2 (PC2-6400)
Speed 400 MHz (DDR2 800)
Supported Frequencies 200.0 MHz, 266.7 MHz, 400.0 MHz
Memory Timings 3-3-3-9-12 at 200.0 MHz, at 1.8 volts (CL-RCD-RP-RAS-RC)
Memory Timings 4-4-4-12-16 at 266.7 MHz, at 1.8 volts (CL-RCD-RP-RAS-RC)
Memory Timings 5-5-5-18-23 at 400.0 MHz, at 1.8 volts (CL-RCD-RP-RAS-RC)
Data Width 64 bits
Manufacturing Date 2008, Week 0
EPP SPD Support No
XMP SPD Support No
ProgeSOFT PDF Wizard PDFCreator: Printer2
progeSOFT PDF Printer 2010 LPT1: Printer5
ProgeSOFT JPG Wizard PDFCreator: Printer3
progeSOFT JPG Printer 2010 LPT1: Printer12
PDFCreator PDFCreator: PDFCreator
Microsoft XPS Document Writer XPSPort: Printer
HP Deskjet D1600 series (Kopie 1) USB002 Printer17
Epson Stylus COLOR 3000 ESC/P 2 USB003
EPSON Stylus COLOR 3000 USB003
Brother PC-FAX v.2 USB001 Printer7
Brother MFC-5890CN Printer USB001 BrotherM
Beeld printer voor PaperPort Nuance Image Printer Writer Port Printer9
Automatisch PDFCreator op DRAAGBAAR \\DRAAGBAAR\PDFCreator
Windows Firewall
Program C:\WINDOWS\system32\firewall.cpl
Company Microsoft Corporation
Version 5.1.2600.5512
GUID {304CE942-6E39-40D8-943A-B913C40C9CD4}
Status Inactive
Outpost Firewall Pro
Company Agnitum
Version 7.0.1
GUID {8A20CA2A-9E02-4A64-923B-0A38208EB7FD}
Status Active
AntiVir Desktop
Company Avira GmbH
GUID {AD166499-45F9-482A-A743-FDD3350758C7}
Status Active, Up-To-Date
progecad 10 professional

example of event log windows by crash
Type gebeurtenis: Fout
Bron van gebeurtenis: Application Error
Categorie van gebeurtenis: Geen
Gebeurtenis-ID: 1000
Datum: 30/06/2010
Tijd: 18:52:41
Gebruiker: n.v.t.
Computer: WALLABIE
Vastgelopen toepassing: icad.exe, versie:, vastgelopen module: kernel32.dll, versie: 5.1.2600.5781, vastgelopen op: 0x00012afb.

Zie Help en ondersteuning op voor meer informatie.
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 69 63 61 ure ica
0018: 64 2e 65 78 65 20 31 30 d.exe 10
0020: 2e 30 2e 38 2e 39 20 69 .0.8.9 i
0028: 6e 20 6b 65 72 6e 65 6c n kernel
0030: 33 32 2e 64 6c 6c 20 35 32.dll 5
0038: 2e 31 2e 32 36 30 30 2e .1.2600.
0040: 35 37 38 31 20 61 74 20 5781 at
0048: 6f 66 66 73 65 74 20 30 offset 0
0050: 30 30 31 32 61 66 62 0d 0012afb.
0058: 0a .
#1223 by caddit
Tue Aug 24, 2010 7:47 am
Hello 10augustus,

This sounds like a strange error we suspect it may be legacy-data related but are unsure. Please send an example file where your hatch problem may be reliably reproduced and list the steps to create the error you are getting.

You may send the DWG drawing file here:

We will try to help you.

#1267 by 10augustus
Wed Sep 29, 2010 11:19 am
I sent an erratic drawing more than three weeks ago ! no response
Starting up the program now makes it freeze ,almost all the time I hardly can work with it anymore ! I have countless problems and all of the about 60 drawings I made crashed, were inpossble to print, unhatchable or had one or more errors hat made it hardly usable !and I'm only working in 2d !! I already registred/payed two versions of this software in one year, I need drawing software for my business, I spent more than enough time trying to solve all he errors ! what's wrong with this software , are all our customers doing the tryout of it ?
#1269 by caddit
Thu Sep 30, 2010 6:16 am
Hello 10augustus,

The problem with progeCAD crash on certain system startup is known and a patch should be forthcoming.

You problem with the bhatch command in this drawing seems to be caused by implicit boundaries created via intersection of multiple lwpline entities. Simply put, if you explode the polylines into lines, the bhatch command behaves as expected.

The problem with ployline is on the list for fix, but the momentary work-around is to explode them first if they cause trouble.

#1270 by 10augustus
Thu Sep 30, 2010 7:48 am
Thanks !

I'll try it.
Another strange phenomenon:
-In drawings that apear to behave strange (2D , hatching, chamfer, fillet ...) I found that certain lines have a very small z elevation fi. 0.00038 , so they only appear to be connected but are not. Where can this elevation come from ?

-Doing an audit , it results for intance in 2 errors which are fixed. I repeat the audit and get 4 errors wich are fixed, I repeat i again and get 6 errors , fixed again .... endless.
#1271 by caddit
Thu Sep 30, 2010 8:24 am
Hello 10augustus,

Usually when there is any change in Z elevation it means that there was something different about the UCS (axis system) it was drawn to. For example, if someone accidentally holds CTRL+MMB (middle mouse button) together while UCS=World, even momentarily, can shift the view very slightly out of orthogonal drawing view. Together with other commands, this could lead to strange deviation in Z values, etc..

Some of this can be fixed by resetting the 3d view to plan view ("top" is default) from the main progeCAD menu (View -> 3D Views -> Top) and then using the FLATTEN command. But you will need to re-check every intersection of geomtry that has been affected, as there may be minute gaps resulting from the flatten-projection.

Hard to say if this is what is causing the audit errors, but you might also consider some of the steps outlined HERE ...

#1272 by 10augustus
Thu Sep 30, 2010 8:42 am

I'll try it out !
#1273 by caddit
Thu Sep 30, 2010 10:22 am

There is another very important reason your hatching was not working in the drawing that you have sent.

There was dimensioning in the same regions but on a deactivated layer. When we turned that layer on, we immediately notice that the strange "gaps" in your hatching is exactly where the invisible dimension text was located. When we removed the dimensioning layer entirely from the drawing, and once again bhatch worked normally -even if we don't explode the polylines serving as region boundaries.

Ultimately this bug consists of two factors in combination:
1) Using implicit regions defined by multiple intersecting lwplines as bhatch boundary while...
2) The region also contains dimensioning or text - even if the dimension layer is turned off. This I think is more important.

As I said, the development team also reproduced this bug and have it on their list.

#1280 by 10augustus
Fri Oct 01, 2010 1:24 pm
Thanks again,

At least some problems I can ommit in the future !

#1376 by 10augustus
Mon Nov 29, 2010 7:13 pm
Dear friends

Eventhough progecad still is not running smoothly :? ... I'm not giving up ! Almost all my drawings show a message on ; your drawing contains invalid data... and saved with... . The log file mentions an invalid block. Even if i remove all blocks from the drawing I keep on getting that message. An audit mentions a number of errors fixed, but every time I repeat this audit the same result same errors are fixed ?.Recovering the file, opening it , solves the problem temporarely. As soon as I make a new layout , the problems begin. Every time I reopen a file I made before , the layouts are, unusable or frozen , sometimes everything in it is angled a few degrees ... or the scale mentioned is completely wrong towards my paper size. It means that until now , every time I reopen a file for printing I have to remake completely the layouts , specially for drawings with many viewports this is impossible to work with in the future. Maybe I' doing something wrong ?
Printing somewhat larger drawings sometimes results in slow printing... 6 hours for a quarter of an A3. Everything hangs ? Printing the same drawing and making a simple print preview before printing often solved this problem.

#1381 by caddit
Wed Dec 01, 2010 3:45 pm
Hi 10augustus,

You definitely get some corrupt drawings. I believe we discussed this topic together before.

If the data you get isn't clean (without audit errors) you can try saving back to a previous version DWG file (even way back to 2000 version or so) under a new filename, or else try copy and paste what you need from the corrupt drawing into a fresh new one and try AUDIT again.

Make sure you run "audit" and "purge" regularly even on new drawings to keep them error free.

If you continue to have problems with a specific file, please send it to:

Please include some information about EXACTLY what the file history is (i.e. originally drawn in AutoCAD LT 2004, modified in AutoCAD 2006 for a couple of years before editing for the last year in progeCAD 2010.. for example)
#1382 by 10augustus
Wed Dec 01, 2010 8:36 pm
Thanks for the reply.

- the copy paste trick is not working, still the same error messages. Saving to a previous version does not help either. To find out what caused the error I "undressed" the drawing layer by layer saving it each time I removed a layer. Now I have a completely empty drawing... and still the same error messages , saving an apparently empty drawing. Now I see that restarting the program, even the automatically generated drawing immediatly shows the error message trying to save it. Whitout touching even the contents of it.
The last drawing I'm working on crashed 32 times today (i started to count it) and I did not count how many times I did the audit and purge commands , mean while saving it manualy every five minutes , scared tot lose my work.!
I'm desperate ! Some drawings generated 27 files , backup , log files etc

I'll try to reinstall the software ? maybe that helps ?


#1383 by 10augustus
Wed Dec 01, 2010 8:54 pm
Reinstalling did not change anything ....