John: I've been de-browser'd for several days because of a failed Microsoft update process. I just now read the post that says the discoverY2K website was updated. Being a curious fellow, I just had to check it out.
The sample screen on the first page shows some interesting data.
According to that screen, there are non-compliant files in the "MSWorks" directory that were manufactured by NOVELL. I find that hard to believe, unless they were manufactured by NOVELL under contract to Microsoft. Also, it looks like all of the files in that area of the directory were determined to be non-compliant. Another unlikely situation. It's possible, but unlikely.
Also according to that screen, C:\COMMAND.COM created on 5/11/98 has a compliance status of unknown. Its manufacturer is blank, which I guess means unknown. COMMAND.COM just so happens to be the system's command interpreter which exists on everybody's machine. By now, it should have been determined to be either compliant or non-compliant, and the application database should have been updated to include the status. Note that there aren't very many manufacturers of that particular module. IBM and Microsoft. Perhaps some of the OEMs.
Hopefully, CSHK's product does a better job of determining compliancy and product manufacturer than the screen shot indicates. Those guys just HAVE to realize they're displaying their wares to techies who will pick up on these goofups.
I'm still waiting for the latest and greatest version with the embedded file fix before I take the time to do an in depth evaluation.
By the way, if you click on "Software Vendors" on the discovery2k website, you get a "404 NOT FOUND" error. It's actually trying to locate /DY2K.ZIP. Ooops.
TED |
