Exception Processing - Windows Drive not ready
Collapse
X
-
Either solutions would work. The latter makes the most sense, as you would never want to follow file:// links for external websites, where you are sure to not have the same content accessible locally.
-
Or should I always disable indexing file:// started pages when indexing from outside websites?
Leave a comment:
-
I found out it is due to a particular page which does contain links to file://A:\contents.html ... Can I add "file://A:\" to the skip list to avoid zoom from indexing these pages?
Leave a comment:
-
It would seem like you have A:\ specified as a start point, and you're asking Zoom to index files from the floppy drive? Click on the "More" button to confirm. Another possibility is you're using Spider Mode and having it follow file:// links, and some of these links point to the floppy drive.
Leave a comment:
-
15:04:38 - [ERROR] Error: Could not open file: A:\contents.html (Error code: 21)
15:04:43 - [ERROR] Error: Could not open file: A:\G|\www\esources.html (Error code: 21)
15:05:05 - [ERROR] Error: Could not open file: A:\case.htm (Error code: 21)
15:05:11 - [ERROR] Error: Could not open file: A:\analysis.htm (Error code: 21)
15:05:17 - [ERROR] Error: Could not open file: A:\resources.htm (Error code: 21)
15:05:23 - [ERROR] Error: Could not open file: A:\country.htm (Error code: 21)
15:05:29 - [ERROR] Error: Could not open file: A:\culture.htm (Error code: 21)
15:05:35 - [ERROR] Error: Could not open file: A:\index.htm (Error code: 21)
After disabling the floppy disk in device manager, the windows error is gone.
Leave a comment:
-
It will only copy what you can see in the log and isn't filtered out. But you can filter out all the irrelevant messages, by unchecking everything but "Error" and "Warning". This will show you up to 5000 error and warning messages and retrieve any messages which scrolled by before.Originally posted by maryjili View PostCan this method copy all the log messages or just the last 5000 as said on the top of the message box? The error messages were before the last 5000 so I already closed the program and restarted with detailed log and debug mode checked and will save to the local disk.
Note that the log window in V6 is very different from V5, and things that have scrolled out of view can be moved back into view by changing the filtering options.
This will only happen if you checked the box and then left the value to "512", which is the default maximum URL length, which means it is the same as leaving this option unchecked.Originally posted by maryjili View PostAnother thing I noticed is the truncate url length option was always unchecked when I reopen a configuration file which was set to checked.
If you change this value to less than 512, and save your config and reopen it, it should retain the value.
This might be a bug, but we need to be able to reproduce this. Sometimes your configuration has changed without you knowing it - most notably if you have just opened an old V5 configuration file, in which case, V6 would have made some internal changes to adapt the configuration across - and it would consider there to be changes.Originally posted by maryjili View PostAlso sometime when closing the program it asked to save the changes to the configuration file, while I had made none.
The next time you see this, SAVE the configuration (even though you think there's no changes), quit Zoom, and then immediately re-open Zoom (with the same config) and quit it again, and see if it prompts you about changes. If it does, then it's a bug, and you should e-mail us your configuration file.
Leave a comment:
-
Can this method copy all the log messages or just the last 5000 as said on the top of the message box? The error messages were before the last 5000 so I already closed the program and restarted with detailed log and debug mode checked and will save to the local disk.
Another thing I noticed is the truncate url length option was always unchecked when I reopen a configuration file which was set to checked. Also sometime when closing the program it asked to save the changes to the configuration file, while I had made none.
Leave a comment:
-
You could just right-click on the message on the "Log" window and select "Copy current line to clipboard".
Leave a comment:
-
I did not set the option to save the indexlog to local disk, so I will rerun the indexer again now to get the message.
Leave a comment:
-
Can you give us the full message in the Zoom indexlog? The full message would tell us why it would be accessing the A:\ drive at all. Most likely you actually have something in the configuration file that points to the A drive. Like an additional start point. Or your log file location. Send us your ZCFG file if you want us to check. But please provide the index log message as needed. Abbreviating error messages just wastes time.
You can disable the floppy drive from the Control Panel, Device Manager. But this is just suppressing the issue rather than addressing it.
Leave a comment:
-
In my windows explorer, there is a floppy disk drive A: under devices with removable storage, but I already unplugged the physical floppy disk from my computer. Also when I got the exception message, I remember in the zoom indexlog, there is a message said something like "error loading A:\....". I guess it might be the problem. Would you please tell me how to remove the floppy disk configuration from the windows explorer, so that windows knows that there is no floppy disk installed?
Leave a comment:
-
We have confirmed that this is an error message from Windows, and not from our software.
As noted above, the problem appears to be related to particular system configurations. There is a mass storage device on your system, disk or otherwise, that is reporting a fault to the operating system.
Unfortunately, we can't tell you why your system has this problem. The causes can vary from faulty hardware to an incorrect or broken Windows installation.
I would recommend taking a look at the links I have given above. It is worth noting that "removable media devices" can include digital cameras, and floppy disk drives.
Here is yet another reference (vmware triggering this error due to an invalid floppy disk setup in Windows, and link to knowledge base article instructs how to disable the flag/warning):
http://communities.vmware.com/message/763566
Leave a comment:
-
And with the same hardware, software and configuration setting, I never had this message with v5 final version.
Leave a comment:
-
I just sent the screenshot jpeg file to wrensoft. The entire message box is like this:
title of the message box:
Windows - Drive not ready
content of the message box:
Exception Processing Message 0xc00000a3 Parameters
0x000007FEFD497240 0x0000000000000004
0x000007FEFD497240 0x000007FEFD497240
bottom of the message box:
cancel try again continue
I do not have any card reader or removable media devices plugged in my computer.
Leave a comment:
Leave a comment: