General information
Some things you should be aware of when using CDCheck
- autorun feature is disabled while CDCheck is running (if you do not like this email me why and I will make it optional)
- for ease of use most of the dialogs that popup up can be confirmed using ENTER key
- CD tray is automatically closed if necessary when process is started
- due to high speed access CDCheck can cause your system to hang (crash) if your computer is not functioning properly
- audio CDs are not supported
- under Win95,98,ME files/directories containing non-locale characters are displayed with short file/directory name
- some people have experienced error "A device attached to the system is not functioning." when checking Video CD although the CD seemed to be OK
Known limitations
- only ansi strings can be used to specify starting directory for checking etc.
- under Win95,98,ME when file/directory A containing non-locale characters has the same long name as file/directory B without
non-locale characters then A incorrectly behaves as B (this is extremly rare condition)
- wrong junction (Windows variant of Linux symbolic link) can produce endless loop (many programs share this problem - average user will not come across this)
Tips
- when you are changing path in "CRC", "Check" etc. shortcut CTRL-SPACE can be used to popup the browsing window
FAQ
1. Why do I get "file size <> bytes read" when processing (Linux) CD?
CD is usually read only media and therefore the file cannot be changed during processing. The warning is reported because
operating system probably has some problems reading volume structure. It seems it correctly reads the file size but when it
wants to read the file it reads the wrong file and therefore reads more/less than the size expected. You can observe
this yourself if you try to copy the reported file to disk. The size of file on disk will be different than the size of file on CD
and will probably match some other file.
2. Why is CDCheck so SLOW?
You probably have checked "Run process in idle priority" in Options and you are running a background application that is using
all spare CPU cycles (like SETI@home). Uncheck the option to allow CDCheck to run processes in normal priority.
If you are using Windows NT or 2000 you can check if some application is using all of the CPU by pressing CTRL-SHIFT-ESC to show
Windows Task Manager and going to performance tab. If CPU usage is at 100% for a few seconds you should uncheck the
"Run process in idle priority".
3. Why am I getting "Insufficient quota to complete the requested service."?
The problem is a consequence of too low system resources being available. There are several things you can try:
A) Try lowering the values under CDCheck-Options-Buffers ("Device read size" and "Circular buffer size").
B) Check that you have enough space on your hard drive and big enough Disk Usage Quota (Explorer - right click - Quota Management).
C) Try installing service packs for Windows
D) Check that you have enough RAM available
E) Try closing all unneccessary running applications
BACK
FRONT PAGE
NEXT
Copyright (C) 2002, Mitja Perko (CDCheck homepage)
|