> So why am I putting up with my aging K6-450? Inertia. Not much else. Well,
> it's always a major interruption to install everything on a new system,
> the network talking sense, etc....

True!  This is one on-going problem the PC industry has ignored.  As long as
they continue to ignore this problem, people will delay upgrading as long as
possible.  You would think they would realize they could double their sales
if they made transferring and upgrading easier.

My policy is to buy PCs that are sufficiently powerful and reliable that I
don't have to upgrade more often than every 4 years.  So far, this strategy
has worked:

1987:  first PC, a 10MHz 286
1992:  2nd PC, a 33MHz 486DX
1996:  3rd PC, a 200MHz Dell Pentium (my first use of Protel was on this PC)
2001:  4th PC, a 1GHz dual-PIII generic white box
2005:  who knows?

Of course, I don't count that lemon Compaq Presario 4640 I bought 3 years
ago.  That was for home use, and has long since been replaced by a 466MHz
Celeron generic white box.

If upgrading were easier, I might do it every 2 or 3 years.  My latest
upgrade (Dell to white box) took 1 week out of my work schedule to configure
network settings, load all my apps, transfer data files, and verify the
installs and transfers.  This seems like a lot of time, but I wanted to make
sure everything worked before I stopped using the old workstation.
Verifying this stuff takes lots of time!

Best regards,
Ivan Baggett
Bagotronix Inc.
website:  www.bagotronix.com

----- Original Message -----
From: "Abd ul-Rahman Lomax" <[EMAIL PROTECTED]>
To: "Protel EDA Forum" <[EMAIL PROTECTED]>
Sent: Monday, November 26, 2001 10:14 PM
Subject: Re: [PEDA] Database Repair

> At 05:52 PM 11/26/01 -0500, Jeff Adolphs wrote:
> >Hello! I'm the one having Protel Crashes with the message 'Access
> >violation....  I have read the Protel Knowledge Base and found I should
> >be doing Database Repair. Maybe the Protel Crashes are related to not
> >doing Database Repair.
> >
> >On two large Database Files the Database Repair could not fix them. Does
> >Database Repair have problems repairing large designs?
> Well, obviously, the larger the database the more possibility of an
> unrepairable error. Other than that, I don't know. But if your memory is
> limited to 64K as mentioned before, perhaps this could be a problem.
> Normally it is not necessary to repair databases, but if you have been
> having frequent crashes, this could certainly corrupt a database.
> I've never seen a damaged .ddb, though.
> Ddbs should not be allowed to grow to enormous sizes, in my opinion.
> Periodically delete unnecessary files (and empty the ddb recycle bin), and
> I recommend setting automatic compact on close. (an option under the
> menu, that mysterious down-arrow in the upper left corner of the screen.
> least that is the default position, I don't know if it can be moved.
> Files are not really deleted from the .ddb until the Recycle Bin is
> emptied, and even then the space allocated to them remains, thus the .ddb
> continues to grow. Compacting the database recovers this space.
> >Still working on why I get Protel Crashes, so far I have lowered Video
> >Acceleration, used Database Repair ( the design which has been crashing
> >was able to be fixed by Database Repair (although there is no way of
> >knowing if there was anything to fix), and gotten ALL the related Protel
> >Knowledge Base pages they had. Tomorrow I will look at the Main Board
> >and make sure the processor looks seated properly (kind of doubting the
> >processor is the problem since Microsoft Outlook ran good the last two
> >days, AutoCAD 2000 ran well also (didn't do much with AutoCAD 2000 today
> >though).
> That some programs, or even all programs but one, is no proof that there
> no hardware problem. Obviously, if all crashes happen with one program
> only, we will suspect the program rather strongly, but it is possible that
> a memory problem, for example, is pattern sensitive or that some other
> obscure interaction between the program and the hardware is bringing a
> fault to the fore.
> But, once again, the most likely culprit is the video system, sorry to
> It's a shame if one can't run an $8000 piece of software because someone
> tried to save a much smaller sum of money by not using video RAM but
> instead sharing user RAM. It is a near certainty that these problems will
> go away if you install Protel on a better computer. It doesn't have to be
> an expensive one; I could probably buy something better than I am using
> for a few hundred dollars, excluding stuff like the hard drives and other
> transferable peripherals. Hmmm...
> So why am I putting up with my aging K6-450? Inertia. Not much else. Well,
> it's always a major interruption to install everything on a new system,
> the network talking sense, etc....
> Abdulrahman Lomax
> Easthampton, Massachusetts USA

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* To post a message: mailto:[EMAIL PROTECTED]
* To leave this list visit:
* http://www.techservinc.com/protelusers/leave.html
* Contact the list manager:
* Forum Guidelines Rules:
* http://www.techservinc.com/protelusers/forumrules.html
* Browse or Search previous postings:
* http://www.mail-archive.com/proteledaforum@techservinc.com
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Reply via email to