For revision 476, I wrote “made PHC “do the right thing” a bit better by dropping out some config in the bat file and activating an “auto” mode; may have issues in a “-h uri” mode”

In short, there it is: the PHC becomes “Automatic-er” and allows me to be lazier. Avoiding possible user-error is merely a stretch-goal 🙂

Consider the 7 characters:

PHC.BAT

What this does is:

1. find your java.exe in a list of 12 most likely places
2. if PHC-XLSX.jar is available, use it; otherwise, use PHC.jar
3. runs it in “-A” or “–auto” mode

Auto Mode

Auto Mode simply does the smarter things for you, so that fewer choices are necessary:

1. if PHC-XLSX.jar has enabled XLSX creation, build phc.xlsx
2. if any OUIs are missing, look them up, and create phc-OUISignatureList.xml which can be used as the basis of edits to OUISignatureList.xml
3. if VMs are present, and some HBAs are not set, produce phc-vm.csv which can define HBA speeds based on having all HBAs under ProbeSW
4. pri