Use this forum to report bugs you find in the software.
Forum rules
We have no special rules for UVK forums. Just try to be polite and clear in your posts.
Please don't post spam in this forum. Spammers will be banned by IP, e-mail and username.
We reserve the right to delete all posts and ban all users we consider not having respected these rules without warning.
Good to know, Jim. It was actually a typo bug in a function parameter.
Currently UVK displays message errors on systems that don't have a uefi bios, or the bios doesn't have the product key stored on it. I'm planning to change this, making it show the Product key from BIOS field only if the key can be retrieved, otherwise, don't show up anything. What do you think?
One thing we humans have in common is that we are all different. So, if you think you're weird because you're different from everyone else, then we are all weird.
See, I guess we could never make everybody happy, no matter how hard we try. I'll have to stick with Jim on this one. If no key is displayed, it's obviously because it could not be found.
One thing we humans have in common is that we are all different. So, if you think you're weird because you're different from everyone else, then we are all weird.
csm wrote:I rather would see a mesagge like, " no bios key detected" then see nothing.
the proper way is
It is good if we see a message instead of nothing (like No BIOS Key detected or No UEFI BIOS active/detected), in this manner we will sure that the App working fine.....
csm wrote:I rather would see a mesagge like, " no bios key detected" then see nothing.
the proper way is
It is good if we see a message instead of nothing (like No BIOS Key detected or No UEFI BIOS active/detected), in this manner we will sure that the App working fine.....
I beg to differ sir.
Currently, more often than not, the computer will not have a BIOS key. So, all this will do is make you click OK or show a line in the system info saying there is nothing to show you. If there is nothing to show me then why take up space on the report to tell me that?
It does not mean the app is working correctly if it says there is nothing. For example, if Fred had coded it that way to begin with then the last beta would have said "no BIOS key detected" or nothing at all depending where he put his logic at. It would have still been wrong but it would have given the message there wasn't one.
I think the easiest way to tell if the app is working correctly is by common sense. If it has a UEFI BIOS it probably has a BIOS key, if not then it can't have a BIOS key.
Jim
It is not "Can it be done?" but rather, "How can we do it?"