I too can confirm that Bob's method works!
Like many here, I've been getting by just fine with CA10, as I'm more of a retired user whose needs and budget, never mind the learning curve, can't justify newer versions.
Over the years I've stumbled and bumbled my way to getting CA 10 to run on Windows 7 and Windows 10 as I upgraded my hardware. When it came to moving to my new machine this summer, the HASP lock drivers I'd squirrelled away that had worked before seemed to have failed. I when so far as to compare the drivers across my collection of XP, 7 and 10 machines, file by file and version number by version number, but couldn't find a difference that stopped me this time.
For me the key was Bob's mention in passing that the newer driver packages needed to work with newer versions of Windows would not work on a fresh install of CA 10 from the original media. The key was applying the 10full08b_h.exe update to Chief - it takes changes in that package to enable good old CA 10 to speak to the more modern (?) versions of the HASP Windows drivers. Then it is just working around Windows' reaction to the signing certificate ART used 20 years ago having expired - hence the big red box.