Discussion:
Eagle 5.10.0 libraries and Win10
(too old to reply)
Dave Bullock MBE
2019-08-30 07:35:11 UTC
Permalink
Dear Sir,
Has anyone else reported issues with older versions of EAGLE when migrating to Win10?
I have been using EAGLE for over 20 years and my licence allowed me to get as far as Ver5.10.0.
I have been running it trouble free on Win7 since this version of Windows arrived. I have now migrated to a brand new installation of Windows 10 and am getting 'Data errors' in libraries as soon as I click 'add new part'.
There are maybe 6 or seven libraries that flag up this error which is really annoying.
However I have a Microsoft 'Surface' running Win10 and EAGLE 5.10.0 and this doesn't exhibit the same behaviour.
So thinking the new installation had corrupted libraries, I copied the 'suspect' libraries from the 'surface' to my new installation but the 'Data error' message persists. (so replacing the libraries doesn't cure the fault).
Any anecdotal information or advice please?
Thanks
Dave

--
To view any images and attachments in this post, visit:
https://www.element14.com/community/message/280262
Morten Leikvoll
2019-08-30 10:51:59 UTC
Permalink
Post by Dave Bullock MBE
Dear Sir,
Has anyone else reported issues with older versions of EAGLE when migrating to Win10?
I have been using EAGLE for over 20 years and my licence allowed me to get as far as Ver5.10.0.
I have been running it trouble free on Win7 since this version of Windows arrived. I have now migrated to a brand new installation of Windows 10 and am getting 'Data errors' in libraries as soon as I click 'add new part'.
There are maybe 6 or seven libraries that flag up this error which is really annoying.
However I have a Microsoft 'Surface' running Win10 and EAGLE 5.10.0 and this doesn't exhibit the same behaviour.
So thinking the new installation had corrupted libraries, I copied the 'suspect' libraries from the 'surface' to my new installation but the 'Data error' message persists. (so replacing the libraries doesn't cure the fault).
Any anecdotal information or advice please?
Thanks
Dave
I would immediately suspect some file privilege issues. Make sure the
installation is in a root folder, and make sure you have full access to
all files.
Joern Paschedag
2019-08-30 12:56:10 UTC
Permalink
Post by Morten Leikvoll
Post by Dave Bullock MBE
Dear Sir,
Has anyone else reported issues with older versions of EAGLE when migrating to Win10?
I have been using EAGLE for over 20 years and my licence allowed me to
get as far as Ver5.10.0.
I have been running it trouble free on Win7 since this version of
Windows arrived. I have now migrated to a brand new installation of
Windows 10 and am getting 'Data errors' in libraries as soon as I
click 'add new part'.
There are maybe 6 or seven libraries that flag up this error which is really annoying.
However I have a Microsoft 'Surface' running Win10 and EAGLE 5.10.0
and this doesn't exhibit the same behaviour.
So thinking the new installation had corrupted libraries, I copied the
'suspect' libraries from the 'surface' to my new installation but the
'Data error' message persists. (so replacing the libraries doesn't
cure the fault).
Any anecdotal information or advice please?
Thanks
Dave
I would immediately suspect some file privilege issues. Make sure the
installation is in a root folder, and make sure you have full access to
all files.
Besides Mortens advise upgrade to version 5.12.0. which is
the latest Vers. 5. It has some advantages and your license allows to
install it.
--
Mit freundlichen Grüßen / With best regards

Joern Paschedag
Dave Bullock MBE
2019-08-30 14:28:26 UTC
Permalink
HI thanks for your swift replies,
Would file privilege issues just affect 6 libraries out of all the EAGLE libraries?
As I said it's only libraries like (for instance) 74xx-little-us.lbr and con-avx.lbr that throw up this error message and the rest of the libraries load without problem when I click 'add new part'.
EAGLE then works fine as long as I don't try to access these faulty? libraries.
However on my Win10 laptop the same installation works faultlessly with the same version of EAGLE.
Finally deleting the faulty libraries and copying them across from the working version on my laptop delivers the same errors on the newly copied libraries.
It's as though the main EAGLE program is somehow not recognising the libraries rather than them being faulty.

I guess I could reinstall EAGLE 5.10.0 or as Morten suggests try the last release?
It's very weird :-o
Dave

--
To view any images and attachments in this post, visit:
https://www.element14.com/community/message/280278
Joern Paschedag
2019-08-31 06:31:43 UTC
Permalink
Post by Dave Bullock MBE
HI thanks for your swift replies,
Would file privilege issues just affect 6 libraries out of all the EAGLE libraries?
As I said it's only libraries like (for instance) 74xx-little-us.lbr and con-avx.lbr that throw up this error message and the rest of the libraries load without problem when I click 'add new part'.
EAGLE then works fine as long as I don't try to access these faulty? libraries.
However on my Win10 laptop the same installation works faultlessly with the same version of EAGLE.
Finally deleting the faulty libraries and copying them across from the working version on my laptop delivers the same errors on the newly copied libraries.
It's as though the main EAGLE program is somehow not recognising the libraries rather than them being faulty.
I guess I could reinstall EAGLE 5.10.0 or as Morten suggests try the last release?
It's very weird :-o
Dave
--
https://www.element14.com/community/message/280278
Could it be that those files were modified?
If you need to modify libraries don't do it in the originals, but save
them in your own libraries.

Download eagle 5.12
ftp://ftp.cadsoft.de/eagle/program/

Imho versions lower than 6.6 are not available on autodesk server.
--
Mit freundlichen Grüßen / With best regards

Joern Paschedag
BB-Sphere (Clem)
2019-09-01 04:21:48 UTC
Permalink
asdfasfas

--
To view any images and attachments in this post, visit:
https://www.element14.com/community/message/280366

Continue reading on narkive:
Loading...