i use orcad to draw shematics and generate a netlist and import it in powerpcb 5.0, but when i edit my schematics and regenerate the netlist and import the netlist again in powerpcb 5, a segment error occured, and a dialogbox appeared, then powerpcb 5 closed itself. help me!!! 8O
I think this can be from various soruces. These're what I can think of. So you can try.
-Check the file attribute of the pcb file make sure it's archive, nor read only.
-Are you import the whole netlist again? If so, try generate the eco first and then import the eco instead.
-Try Ascii out the file and then re-import that ascii. And then re-import the eco again.
That's all I can think of.
ArmBoy said:
i use orcad to draw shematics and generate a netlist and import it in powerpcb 5.0, but when i edit my schematics and regenerate the netlist and import the netlist again in powerpcb 5, a segment error occured, and a dialogbox appeared, then powerpcb 5 closed itself. help me!!! 8O
I would like to ask you one question.....
what is the exect error or dialog BOX ,which appears while you import the netlist......
Since there are two types of errors...one the Segementation Fault Detect and the other one FATAL DATABASE ERROR.
Since editing of the orcad schematic should not effect the result.You have t generate new netlist each time you do editing in schematic and then import the netlist in powerpcb.
while importing it checks for the valid database in powerpcb.....
so can u tell whether u get fatal database error or just segmentation error.???
Great Thanks!
The message in the error messagebox is "Segmentation Fault Detected."
After i press OK, another error messagebox appeared "Fatal Data Base Error Number 2018 Unrecoverable system error"
yeah, i really import the same hole netlist twice, and then the error occured. i will try what you suggested. Do not hesitate to give suggestions to me.
PowerPCB has two internal sections, one that controls what is in the database and some sort of graphics section that shows a representation of the data. It is possible in one of the previous versions to have the graphics totally messed up with drc errors all over the place and then to create a photoplot from the same layer that is perfect. If the job is saved and Power restarted, then the graphics resets and all is well. I have had the unrecoverable database error (followed by shutdown) before and I have found that I can sometimes avoid it by merely zooming in before doing whatever it was that caused the fault. Zooming out doesn't help, but zooming in seems to shift something in the graphics part of the memory and avoids the conflict.