Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: dschallock on November 02, 2015, 05:36:53 PM
-
Sorry if this has been covered before but...
Is there a nifty program that lists all your libraries in one place, shows what version they are and helps you update them if they should be updated to the latest versions?
Besides wanting to have the latest and best versions of my libs, I am asking because I now have this (fairly) stable 3.9 BB1&2 install and when I install some older programs I suspect that some of them copy their older versions of libraries over my newer ones without asking. Recently I installed some software and I believe it did that as my system immediately started getting buggy and crashing. I reinstalled 3.9 and BB 1 & 2 again and the system started behaving again, but I would like to have a more organized way of knowing whats what and keeping it that way.
Ideas?
-
My friend, as someone who has been known to spend hours researching the most up-to-date Libs versions (it's part of my OCD), allow me to introduce you to this site:
http://amiga.foul.fr/index.php?p=Work%2FLibs (http://amiga.foul.fr/index.php?p=Work%2FLibs)
Also this list (http://lilliput.amiga-projects.net/TechDetails.htm) was helpful when I was first getting started.
You can get partial version info from SysInfo (http://sysinfo.d0.se/), however speaking from experience, the C:Version FULL command is going to be your new best friend. ;)
I run modified libraries from THoR, Cosmos, and Peter K., among others, and definitely recommend them (am sure someone will chime in here about "blah blah unstable, blah-blah not Commodore original, etc." however they work fine for me... your mileage may vary ;) ).
Also if you would like to compare version numbers of specific libraries, I am down for that game any day. :D
-
My friend, as someone who has been known to spend hours researching the most up-to-date Libs versions (it's part of my OCD), allow me to introduce you to this site:
http://amiga.foul.fr/index.php?p=Work%2FLibs (http://amiga.foul.fr/index.php?p=Work%2FLibs)
Also this list (http://lilliput.amiga-projects.net/TechDetails.htm) was helpful when I was first getting started.
You can get partial version info from SysInfo (http://sysinfo.d0.se/), however speaking from experience, the C:Version FULL command is going to be your new best friend. ;)
I run modified libraries from THoR, Cosmos, and Peter K., among others, and definitely recommend them (am sure someone will chime in here about "blah blah unstable, blah-blah not Commodore original, etc." however they work fine for me... your mileage may vary ;) ).
Also if you would like to compare version numbers of specific libraries, I am down for that game any day. :D
Mike you are my brother from another mother! :)
-
Sorry if this has been covered before but...
Is there a nifty program that lists all your libraries in one place, shows what version they are and helps you update them if they should be updated to the latest versions?
Besides wanting to have the latest and best versions of my libs, I am asking because I now have this (fairly) stable 3.9 BB1&2 install and when I install some older programs I suspect that some of them copy their older versions of libraries over my newer ones without asking. Recently I installed some software and I believe it did that as my system immediately started getting buggy and crashing. I reinstalled 3.9 and BB 1 & 2 again and the system started behaving again, but I would like to have a more organized way of knowing whats what and keeping it that way.
Ideas?
Castellan(anthony) keeps updated mui libs list here i think,as well as other goodies:
http://amiga.serveftp.net/downloads.html
Do a copy all clone with the current sys and BB1&2 to back up somehwere on the drive in case you blow it up, then you have a restore point.
in dopus 4.12 or better its easy to highlight the libs for version and send output to a text file.
-
there was a MOS tool also available on 68k and even on AOS4 albeit buggy that did just that, unfortunately, I cant remember the name !
I think it was done by Geit.
-
there was a MOS tool also available on 68k and even on AOS4 albeit buggy that did just that, unfortunately, I cant remember the name !
I think it was done by Geit.
Grunch
http://aminet.net/util/misc/Grunch.lha
-
Castellan(anthony) keeps updated mui libs list here i think,as well as other goodies:
http://amiga.serveftp.net/downloads.html
Thanks! There was definitely a few MUI libs here that I didn't have. Although some of them are of "dubious" use. Um, Cyberstorm? (read the screenshot) ;)
-
My friend, as someone who has been known to spend hours researching the most up-to-date Libs versions (it's part of my OCD), allow me to introduce you to this site:
http://amiga.foul.fr/index.php?p=Work%2FLibs (http://amiga.foul.fr/index.php?p=Work%2FLibs)
Also this list (http://lilliput.amiga-projects.net/TechDetails.htm) was helpful when I was first getting started.
You can get partial version info from SysInfo (http://sysinfo.d0.se/), however speaking from experience, the C:Version FULL command is going to be your new best friend. ;)
I run modified libraries from THoR, Cosmos, and Peter K., among others, and definitely recommend them (am sure someone will chime in here about "blah blah unstable, blah-blah not Commodore original, etc." however they work fine for me... your mileage may vary ;) ).
Also if you would like to compare version numbers of specific libraries, I am down for that game any day. :D
No, his new best friend will be VersionWB:
http://aminet.net/package/util/sys/VersionWB
This makes it easy-peasy to check any file version. I personally have it set up in my Tools menu on my Workbench. All I have to do to check a file is select it with the left mouse button, then go to the Tools menu and select 'VersionWB' - it then brings up the version info in a neat little dialogue box. And if I don't select a file and I go to Tools and load 'VersionWB', it brings up a file requester instead, allowing me to check any file, anywhere.
Neat little program. Yes, possible with a bit of AmigaDOS scripting, but why bother when there's this?
Try it...you might like it. :)
-
http://aminet.net/package/util/sys/VersionWB
Thanks! Configured it to a button in my file manager. Works well. Now let's see if I can remember that I put it there next time I need version info, and don't instinctively drop down to the command line. #OldHabitsAreHardToBreak #GUI'sAreMakingUsLazy :laughing:
-
Thanks! Configured it to a button in my file manager. Works well. Now let's see if I can remember that I put it there next time I need version info, and don't instinctively drop down to the command line. #OldHabitsAreHardToBreak #GUI'sAreMakingUsLazy :laughing:
I've rather made it working when double clicking library, device, gadget, datatype, handler, mcp, mcc, and mui files in the filemanager :) Why to have extra work of moving the mouse over some button and then having an click there, and having to remember that you have such a button?
-
I started writing a replacement for C:Copy that compares version strings of any file you copy with it but it's sat there 60% finished for a couple of years due to various real life issues taking up all my time.
Might try and finish it off at some point soon.
-
I started writing a replacement for C:Copy that compares version strings of any file you copy with it but it's sat there 60% finished for a couple of years due to various real life issues taking up all my time.
Might try and finish it off at some point soon.
Great idea. Is this being done in C?
-
Great idea. Is this being done in C?
Thanks, I started it because of a personal need for it when to my surprise it didn't already exist on Aminet. Yes it's written in C, the first prototype version I did was written on MorphOS and compiled with gcc4 but I rewrote it using old-fashioned style C so that it compiles with SAS/C for 68k too.
-
Thanks, I started it because of a personal need for it when to my surprise it didn't already exist on Aminet. Yes it's written in C, the first prototype version I did was written on MorphOS and compiled with gcc4 but I rewrote it using old-fashioned style C so that it compiles with SAS/C for 68k too.
That would be great! I'm sure a few of us here would use such a tool. :)
-
That would be great! I'm sure a few of us here would use such a tool. :)
That helps with motivation, I'll try make some time over the weekend to start up work on it again.
-
That would be great! I'm sure a few of us here would use such a tool. :)
I agree, it would be nice.
Back in the olden days around early 2000's? there was a website with all the updated mui libs and i seem to remember having my 4000 automated to update libs from there. cant recall for the life of me what the prog was that did it. maybe i just dreamed this?
this is not it, but hmmm... http://www.hofmann-int.de/products/amiga/mui/MCC-Install.shtml.en
-
Most recent version I could find last night is from August 28th 2013 and isn't SAS/C compilable so I must have a newer version backed up somewhere.
If I can't find anything newer at the weekend I'll use this version to carry on working with.
-
Most recent version I could find last night is from August 28th 2013 and isn't SAS/C compilable so I must have a newer version backed up somewhere.
If I can't find anything newer at the weekend I'll use this version to carry on working with.
Not to derail this thread too much, and forgive the amateur programmer question... but I seem to remember the last C compiler coming out for the Amiga as Storm C and if my memory serves SAS/C was the defacto when Amiga first began. Is there any consideration beyond personal preference when it comes to which C environment/compiler you use when writing a piece of software in C for the 68k Amiga now-a-days?
-
Not to derail this thread too much, and forgive the amateur programmer question... but I seem to remember the last C compiler coming out for the Amiga as Storm C and if my memory serves SAS/C was the defacto when Amiga first began. Is there any consideration beyond personal preference when it comes to which C environment/compiler you use when writing a piece of software in C for the 68k Amiga now-a-days?
Short answer: OCD. ;)
StormC is an IDE that uses GCC for compiling code. I like to compile it with SAS/C as it arguably creates tighter/faster binaries than GCC but also because it keeps it old school :)
VBCC is probably the best 68k compiler though.