[PEDA] Netlist import choke

[Geoff Harland]

> Has any one else had problems with importing netlist into all DXP
> products. Specifically,  importing large netlist with 2000 -3000
> components.  The first time the netlist imports, DXP chokes so bad that
> it locks up.  The method I use to get around it is to extract the
> components as a separate netlist.  I import the components in first then
> reload the original netlist with nets back in.   I have seen this pretty
> consistant across DXP SP2 to AD6. and have used several different
> computers.  Is any one else using other programmed netlist?   The reason
> I have to use these netlist is because I have Cadance and Orcad
> customers.
>
> Thanks
> Mike Reagan

I have never encountered any problems of that nature myself, but then I
don't think that I've ever worked on any PCB file containing so many
components.

However your experience does indicate that there is almost certainly some
type of issue when it comes to loading really large netlist files, so if you
haven't "formally" reported your experience already, you should do so (and
if possible, also provide an example of a problematic netlist file). (Some
members of Altium's staff do monitor the messages sent to this mailing list,
but they won't necessarily act upon any defects which are reported just
here.)

As the "customary" way (since Protel 99 SE) to "effectively" load the data
within netlist files is by "synchronising" the PCB file to its associated
schematic file(s), it is likely that the code for loading netlist files is
"long in the tooth", and as such, it is not implausible that only one 65,536
byte block of memory has been provided for that particular task (harking
back to the days of earlier versions of Windows, when such memory limits
really did exist in some circumstances).

It is certainly fortunate that you are able to "load" just the components
during a first "pass" and then load the netlist information during a
subsequent pass, and I will keep that workaround in mind just in case I ever
experience similar problems myself. So while I can't really help you with
this particular matter, I still appreciate you informing everyone of that
workaround.

Regards,
Geoff Harland.