Once again, Der Fisherman seems to think that there is something inherently wrong with either my machine (from the other day), or the way I performed the Eagle v6 upgrade. Well, it's not like you have a lot of room to talk - being as how you are sitting on v5.4. You have not a clue of what I've gone through upgrading to v6. Why are you defending Cadsoft? Pure ethnocentrism?
You asked before - here it is: I'm running Winxp on an Athelon XP2500+ @1.8GHz with 2GB ram. Definitely not cutting edge, but not a total dinosaur.
Maybe I should have removed my v5 installation completely just so that v6 could not tamper with those files? Well, maybe I should stay at home and never go out so that I won't get hit by an out-of-control vehicle.
Unreasonable.
I wanted to be able to continue to use Eagle v5 as I was test driving v6 and I would like to make the point that I took every precaution I knew of to prevent v6 from accessing my v5 files, short of removing the v5 installation.
I suffered no irreparable damage because I did have back-ups, but I believe I exercised due diligence in configuring my machine correctly, yet v6 somehow ignored my configuration requests and acted like it was expected to access my v5 files. At the same time v6, ignored the v6 files that were explicitly specified in my Options Directories Control Panel entries. (That is another bug... Cadsoft has known about it for years and to date Cadsoft has not fixed it. Eagle may ignore your Options Directories entries and instead operate on information contained in unspecified locations.) In v511 release notes they make mention of a newly implemented -U option, (to allow different versions to work together without interacting) but Cadsoft does not explain how to use it (not that I have found, anyway). Even after I learned how to use the -U configuration option I had to repeatedly weed out remnants of the old behavior before the v5 and v6 would work side-by-side without interaction. Then I got to see the other bugs at work.
Only with this major upgrade has the aforementioned bug become apparent because of people trying to have v5 and v6 run side-by-side and still running into unexpected trouble. Before, we expected trouble but now we shouldn't have to. (If I don't speak for you the reader, then I'm speaking for myself.)
I will let anybody interested do the necessary homework and make required configuration changes and then try to run Eagle 5xx and Eagle 6xx side-by-side. See for yourself. Enjoy!
Cadsoft has handled this latest software rollout very poorly imho, not vetting the product sufficiently to weed out bugs that would have become apparent very quickly, except that they evidently weren't looking. They rely too heavily on their Beta Test group who are evidently a bunch of shmoozers. In all fairness, there was a short list of bugs submitted in the beta test forum.
Did somebody tell me to relax? Oh, right. These are the good guys.
-----------------------------------------------------
Fisherman, if this latest major upgrade rollout proceeds like the last one, you will no longer be able to purchase or download v5xx from Cadsoft. I do like some of the new features of v6, like being able to connect one device pin to multiple PCB pads, and they now allow you to copy a component and paste it into another window running in a different instance of Eagle (but that does change the way that the Cut command works). Ability to create arbitrarily shaped pads and SMDs. Text alignments have more options, increased internal resolution, and etc.
Many of the changes have to do with the User Language Program or other more advanced features that are beyond my skill. And Eagle still will not let you have multi-line text, something I would really like to see.
END RANT
You asked before - here it is: I'm running Winxp on an Athelon XP2500+ @1.8GHz with 2GB ram. Definitely not cutting edge, but not a total dinosaur.
Maybe I should have removed my v5 installation completely just so that v6 could not tamper with those files? Well, maybe I should stay at home and never go out so that I won't get hit by an out-of-control vehicle.
Unreasonable.
I wanted to be able to continue to use Eagle v5 as I was test driving v6 and I would like to make the point that I took every precaution I knew of to prevent v6 from accessing my v5 files, short of removing the v5 installation.
I suffered no irreparable damage because I did have back-ups, but I believe I exercised due diligence in configuring my machine correctly, yet v6 somehow ignored my configuration requests and acted like it was expected to access my v5 files. At the same time v6, ignored the v6 files that were explicitly specified in my Options Directories Control Panel entries. (That is another bug... Cadsoft has known about it for years and to date Cadsoft has not fixed it. Eagle may ignore your Options Directories entries and instead operate on information contained in unspecified locations.) In v511 release notes they make mention of a newly implemented -U option, (to allow different versions to work together without interacting) but Cadsoft does not explain how to use it (not that I have found, anyway). Even after I learned how to use the -U configuration option I had to repeatedly weed out remnants of the old behavior before the v5 and v6 would work side-by-side without interaction. Then I got to see the other bugs at work.
Only with this major upgrade has the aforementioned bug become apparent because of people trying to have v5 and v6 run side-by-side and still running into unexpected trouble. Before, we expected trouble but now we shouldn't have to. (If I don't speak for you the reader, then I'm speaking for myself.)
I will let anybody interested do the necessary homework and make required configuration changes and then try to run Eagle 5xx and Eagle 6xx side-by-side. See for yourself. Enjoy!
Cadsoft has handled this latest software rollout very poorly imho, not vetting the product sufficiently to weed out bugs that would have become apparent very quickly, except that they evidently weren't looking. They rely too heavily on their Beta Test group who are evidently a bunch of shmoozers. In all fairness, there was a short list of bugs submitted in the beta test forum.
Did somebody tell me to relax? Oh, right. These are the good guys.
-----------------------------------------------------
Fisherman, if this latest major upgrade rollout proceeds like the last one, you will no longer be able to purchase or download v5xx from Cadsoft. I do like some of the new features of v6, like being able to connect one device pin to multiple PCB pads, and they now allow you to copy a component and paste it into another window running in a different instance of Eagle (but that does change the way that the Cut command works). Ability to create arbitrarily shaped pads and SMDs. Text alignments have more options, increased internal resolution, and etc.
Many of the changes have to do with the User Language Program or other more advanced features that are beyond my skill. And Eagle still will not let you have multi-line text, something I would really like to see.
END RANT
Comment