yes dreams do get you where you want to be

i have no arguments with anything you say here

the following questions are in no way a defense of prottle

what do you mean by 'assertion error' ?

i do the board copy and paste frequently
once or twice it did go to lala land on the selection stage but it works
99% for me
i think it may be problematic if layers which have polygons are turned
off during a big window selection

when you say writing it out as orcad format, what exactly do you mean?
it won't write dsn files, do you mean SDT format ?
and that save copy as of a schem then trashed the DDB ?
due to the format?
yes that is pretty bad

knock on wood but i haven't had a ddb go bad yet
i do bring in current version Orcad schematics from time to time
(can't write them out though, they don't allow that.  i complained about
that and they said they would look into it for the DXP release)

recently i brought in some very old orcad sdt files, there were some
tricks getting the parts setup right in the cache
it crashed more than once, but it didn't hose any files
all in all it's close call whether it would be easier to just redraw it

Dennis Saputelli

Phillip Stevens wrote:
> DS> dream on Phil
> Dreams are a good thing,  they get you to where you want to be.
> DS> with that caveat stated let us recall the history of Protel
> DS> every so many years (4 or 5 ?) they start all over
> DS> the first releases of the new one are totally screwed
> DS> they fix it, they fix it, they do a minor start over then they
> DS> fix it and fix it until it is pretty good stuff and cruise for
> DS> a few years
> Yes,  that behavior is the history.  And I hope it is just
> that...History.
> Look at it this way:  even _after_ the 6 service packs,  I have a
> product which:
> - Has a major crash with a corrupted user library.
> - I suspect it has caused the corruption in that user library.
> - Fails to tell me the user library is corrupted.
> - Lost me a day and a half at a critical time,  finding this problem.
> - Gives an assertion error when a board is selected,  copied and
> pasted.  (A simple 1" x .8" 4 layer board)
> - Gives an assertion error from the Board Wizard,  when one of the
> checkboxes is not checked (board outline I think it was,  but I haven't
> tried this in awhile).
> - Fails to "save copy as" overwriting (and corrupting) the original
> DDB,  when writing it out in Orcad file format.
> Some of these (at least to me) would seem to be pretty serious.
> Is it too much to ask for some additional Design Review of the Code.
> Is it too much to ask to maybe run Bounds Checker,  and fix anything
> it finds?
> Is it too much to ask for 2-3 days (or even a week) of some
> Programmer's time to clean some of these things up?  It would only
> make the product more stable,  more marketable,  crash less,  have
> fewer support issues.  I don't get it.  Why not do it?  It's dumb not
> to.
> Getting me to buy into ATS,  pay more money, go to a yearly update
> support plan,  give up the free service packs,  AND continue to live
> with these kinds of problems,  now _that's_ dreaming......
> ---Phil

___________________________________________________________________________            Integrated Controls, Inc.    
   tel: 415-647-0480                        2851 21st Street          
      fax: 415-647-3003                        San Francisco, CA 94110

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* To post a message: mailto:[EMAIL PROTECTED]
* To leave this list visit:
* Contact the list manager:
* Forum Guidelines Rules:
* Browse or Search previous postings:
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Reply via email to