Testies external shared Libraries, regedit, registry

[DocAElstein]

This and the next post discuses the use and results of the coding from the last post in general terms, and in particular the typical errors and crashes. The next post discusses the results and conclusions in more detail.

Coding is development aid, mainly for use in F8 step mode. ( Rem 7 section problems )
The coding is more of a development tool, and aid, but is of little use as a code to run outright. This is mainly because of section Rem 7, which frequently causes crashes and other awkward happenings, and can even cause permanent effects and even damage to a computer.
Often Excel recovers itself after a crash, and fortunately seems to often return to a state just before the crash, so this is why section Rem 7 is done towards the end of a loop, as then information obtained from the other sections is often preserved when Excel re opens after recovering itself after a crash.
Also it is much easier to see accurately where a problem occurs in F8 step mode, as a run may miss a problem occasionally or a few problems may sometimes occur in different places before the coding stops/ crashes
It is unlikely that you can do much useful with this coding in, less than a day or two. It is only of use if you are having a detailed look at the Guids.
Having said that, if you remove section Rem 7, then you may get an entire run without errors. The coding is still quite slow and inefficient, but that is much better for learning and experimenting and learning, since the less efficient spreadsheet interaction codings both allow you to see better what is going on as well as catching results before a crash/ unexpected code stop.
The problems and errors are discussed very approximately in order of most significance and highest number of occurrences.

There are 4972 Clsid entries in the registry on the old XP computer used

Main Crashes
This is both the most predominant and most consistent problem. The cause and effect is almost always the same. A crash occurs at Obj = CreateObject("New:" & [The Clsid under investigation] & ""), and usually Excel recovers itself completely and even has all data obtained up to the crash. So for example in the example screen shot, a crash occurred for the Clsid array element of indicia 168 and 183, so we have no information in cells A168 or A183, ( TypeName(Obj) ), but we have some information in the other columns for those 2 Clsid
https://i.postimg.cc/PqHtYYPd/Crash.jpg
Crash.JPG


Often in such a case we also have no information in the third column ( ProgID ), but occasional there is also information there as well
https://i.postimg.cc/C1PY32JK/Crash-2.jpg
Crash 2.JPG



When this crash occurs, (and I would typically be running in F8 step mode, so clearly I would see that the error occurs at section Rem 7 at that indicia/row number), then, on restart, I would change in the coding the lower bound in the loop to 1 above the indicia which caused the problem, ( and correspondingly change the value of the variable Rw )
For example, after the first crash shown, I would, (before running the coding in F8 step mode), change the coding to

Dim ClsInfCnt As Long, Rw As Long: Let Rw = 194 '   This keeps track of the rows - there will likely be more than there are Clsids as we need an extra row for versions at the TypeLib place
    For ClsInfCnt = 169(Clsids()) To UBound(Clsids())   ' The main Clsid Loop =======================
     Let Rw = Rw + 1 ' Every Clsid is on a new line
     Let Ws.Range("A" & Rw & "") = ClsInfCnt & "  " & Rw ' The first is a 0 and in the array is "CSID"  after that in the array you get the  { Guid thingy }  format    https://i.postimg.cc/mrHxggQD/Computer-HKEY-CLASSES-ROOT-CLSID.jpg
     Let Ws.Range("D" & Rw & "") = Clsids(ClsInfCnt) ' The main  { Clsid thingy }