This is a known issue. This is a HyperCard limitation and cannot be fixed through Compatibility Checker itself. The program thinks that the numeric string, used as a hard-drive name, is a HyperCard button ID rather than a volume name.
The workaround is to rename the hard drive with a non-numeric name before running the Compatibility Checker.