Hi David,
Thanks for you helpful comments.
AVxCAT V2.2.2.0 FP2 update if planned to be installed over AVxCAT V2.2.0.0 FP2 WPI
AVxCAT V2.1.1.2 get upate not enabled to get V2.2.2.0 FP2 (I'm going to enable update to V2.2.0.0 wpi)
AVxCAT base WPI package includes some missing dlls you are looking for.
Priority is yellow because no more a requirement if under AOS and the color is a warning not red.
When priority.exe is missing I use default available codding
If you have installed dlls from under AVXCAT v2.2.0.0 WPI (you should have rxtnsion...) and you may missing some other elements, pdf due V2.2.0.0. is a main update.
Of course, you can run V2.2.0.0. FP2 WPI over current installation and then replace AVxCAT and Prereqs from those into AVxCAT v2.2.2.0 FP2 (that's all) to get latest update.
About incorrect path under AVxCAT, this is because the paths already set are saved into the ini file.
To check if all is found, you can rename the avxcat.ini file and start AVxCAT (a message will tell you to do setting), go into parameters and check found paths (it should be ok). To use your initial setting, copy back your original avxcat.ini file.
By default, AVxCAT doesn't use icon view, I suggest you to give a try which simplifies usage (for some specific or customised conversion settings, go back to normal view).
Starting from a fresh installation before any AVxCAT setting, all additional tools path should be found and juts 'save parameters' after verification, I'll suggest to set cdda2wav, web and tracks naming convention + set to use priority with suggested parameters which will be helpful for some king of conversion.
About priority, prereqs.exe should find it if missing (but you can ignore it under AOS if you prefer and AVxCAT will use other priority codding)
With the latest prereqs.exe 1.0 beta (only starting from this one), all install steps are done by prereqs.exe if you choice install instead of download only. The packages are identical and what prereqs does during the install:
- it goes through each downloaded packages
- If zip -> it checks archived first level name and if @unixroot found (which means you already set an @unixroot under config.sys found during pre-scan by prereqs) symlink is used and @unixroot replaced with the found @unixroot drive letter. If local if found under @unixroot and/or user set, packages will have local as destination (if local is not part of paths and libpaths under the config.sys, it should be added manually yet)
To use simlink for manually install packages: create a simlink (ln.exe), unzip package, remove (rm) the created simlink
- If zip but a wpi is included (e.g. timidity); prereqs unzip the archive and run the warpin
- If the package is an exe file (supposed warpin executable). It is run
- If the package is a wpi then warpin is run
- For missing rpm packages available through yum (AOS), yum install can be run for all missing packages or it can be run later, the command line is been saved into the yum log file (or prereqs yum log entry)
Regards
Next upgrade is expected to update config.sys if 'local' doesn't exist and is user set under prereqs and I'm looking (may be later...) to make prereqs usable for other programs needing many additional tools (using external customized file to identify packages and links)
After run AVxCAT V2.2.2.0 FP2, you'll find a created avxcath.py (a basic python2 script usable to check hash code of files) used to check MD5 when downloading future updates though AVxCAT.
e.g. python if base python under AOS or python2.7 avxcath.py 0 file2test (0 = MD5, 1 = SHA1, 2 = SHA256, 3 = SHA384, 4 = SHA512)