|
"Keyboard not found; press F1 to continue" — annals of lame error messages
xplorer˛ does a lot of things on a broad range of PC platforms and network configurations, so bugs are not out of the question. If you believe you have found a nastie, please follow this checklist. Perhaps there's a perfectly good explanation for the behaviour you observe.
Suspected bug checklist
- I want to use this command but it is disabled
Some commands are only activated when in context. Try selecting a few items first; is the command activated now? Or perhaps you are in a virtual folder and you are trying to use a command that is only applicable to filesystem folders? If you are using the free version please note that some commands are permanently disabled.
- Check your configurable options
xplorer˛ can behave quite differently depending on your preferences set in Tools | Options. Perhaps there's an option available that makes the program behave more to your liking.
- Check the minimum requirements
If you can't use a feature as advertised in the documentation, perhaps your system lacks some services necessary for xplorer˛.
- Is this a known issue?
xplorer˛ may by design operate in a way some people could find "quirky". Please browse the FAQ section for the most common sources of confusion, either in the file management or user interface departments
- Will rebooting your PC solve the problem?
It is a well known and sad fact that windows isn't the most robust operating system in the world. Many times starting afresh will make the problem go away.
|
 |
The bug checklist doesn't cover my problem
You may have found a real bug! Please submit your problem description
When reporting bugs, please keep in mind:
- Can you reproduce the bug? If you can't, neither would the development team so they couldn't help you. "Good" bugs are those that happen all the time after a fixed sequence of events.
- Think of the context when the problem occurs. Is it only for some specific files or folders? What is their common characteristic? Please include as much information as you can in your report.
- Include information on your system like Windows version, xplorer˛ version, whether you are running as an administrator or as restricted user, etc. If you really want to speed up things please send the crash log created by Dr Watson. The log file is usually found in this folder: C:\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\drwtsn32.log (please ZIP before emailing it). If you can't find the log file you may have to enable Dr Watson first according to this article.
|
|
|
