Disk Doctor (Bug)

[Mart]

Well today when i tested the disk doctor, it worked fine, only had an issue

i have an "usb/flash drive" that when i plug in my PC it appears 2 Removable Disks, G: and H: , g: works fine but H: not works because it looks like isn't an removable disk

 

so....

 

the that issue happened:

 

when i ask for disk doctor search in H: the program give an "message box" wifh error ("Could not make map path", something like that) and after that the disk doctor still scanning H: but it never ended,

so just asking to fix this bug in next release/up-date

 

because if the program can't make the map path it stop and u need close and open again

 

PS: the error is: DiskMapCreatorError

 

and the program go to an endless analysis

 

sorry for bad english, i have done my best

[ivy]

Hello, Mart

 

In reply to "the program give an "message box" wifh error ("Could not make map path", something like that) and after that the disk doctor still scanning H: but it never ended" mentioned in your letter, could you please send us the screenshot of this trouble you got so that we can further analyze it?

 

Thank you.

[Mart]

the error message is this: DiskMapCreatorError

 

i`m not im home now, but when i get home i post the photo here (in this same post by edit)

[Mart]

well as i promised here is the picture

 

http://img689.imageshack.us/img689/9274/diskdoctorerror.jpg

 

today i discovered the problem

 

in picture u can see in image 2 the second message dialog "Drive Not Found: H:\.", this message is running behind the Disk Doctor Windows, so i didn't saw it, only today

 

well if u guys gonna fix it, just try to put this error windows up to the disk doctor windows

[Lily2000]

Hello Mart,

 

Thanks for your taking time in providing us the pictures. But I am sorry to let you know that I can not open the link you provide.

 

However, regards to the error message " DiskMapCreatorError ", we'd like to tell you that it is indeed a bug of Disk Doctor which will be solved sooner in our next version.

 

One tip: Disk Doctor must be run under administrator privilege.

 

Thank you.

[wozofoz]

Link fixed

 

The link to the image has been fixed :smile:

 

All the best, woz of oz

[Iobiterer]

Hi,

i have the free version and used the Disc Doctor.

After the analysis there is an option to restart now and get the final analysis, or restart later and get the analysis in the next restart.

 

Well, whatever I do, nothing happens when my computer restarts.

 

Nothing pops up, nothing. What should happen in normal conditions?

Here is the report that the doctor gave me (drive C: has problems D: is okay):

 

Windows Vista

 

C:\ Volume Label: ACER, File System: NTFS

 

Volume label is ACER.

Disk Doctor is verifying files (stage 1 of 3)...

215936 file records processed.

File verification completed.

2995 large file records processed.

0 bad file records processed.

0 EA records processed.

76 reparse records processed.

Disk Doctor is verifying indexes (stage 2 of 3)...

Index entry F2C70072d01 in index $I30 of file 6077 is incorrect.

Index entry F2C700~1 in index $I30 of file 6077 is incorrect.

Index entry MSS00017.log in index $I30 of file 6763 is incorrect.

Index entry MSStmp.log in index $I30 of file 6763 is incorrect.

Index entry 00010013.ci in index $I30 of file 19549 is incorrect.

Index entry 00010013.dir in index $I30 of file 19549 is incorrect.

Index entry 00010013.wid in index $I30 of file 19549 is incorrect.

Index entry plugtmp-1 in index $I30 of file 32746 is incorrect.

Index entry PLUGTM~1 in index $I30 of file 32746 is incorrect.

Index entry sessionstore.js in index $I30 of file 86167 is incorrect.

Index entry SESSIO~1.JS in index $I30 of file 86167 is incorrect.

Index entry StreamMinerInfo.sol in index $I30 of file 115815 is incorrect.

Index entry STREAM~1.SOL in index $I30 of file 115815 is incorrect.

Index entry temp.ini in index $I30 of file 117541 is incorrect.

270366 index entries processed.

Index verification completed.

Errors found. Disk Doctor cannot continue in read-only mode.

 

 

D:\ Volume Label: DATA, File System: NTFS

 

Volume label is DATA.

Disk Doctor is verifying files (stage 1 of 3)...

68160 file records processed.

File verification completed.

0 large file records processed.

0 bad file records processed.

0 EA records processed.

0 reparse records processed.

Disk Doctor is verifying indexes (stage 2 of 3)...

79608 index entries processed.

Index verification completed.

0 unindexed files processed.

Disk Doctor is verifying security descriptors (stage 3 of 3)...

68160 security descriptors processed.

Security descriptor verification completed.

5724 data files processed.

Disk Doctor has checked the file system and found no problems.

112092159 KB total disk space.

28306836 KB in 37646 files.

16844 KB in 5726 indexes.

137559 KB in use by the system.

65536 KB occupied by the log file.

83630920 KB available on disk.

4096 bytes in each allocation unit.

28023039 total allocation units on disk.

20907730 allocation units available on disk.

 

 

What should I do? Help please, thank you!

[solbjerg]

Hi Iobiterer

I have no errors so I cannot follow your example, so there may be a bug - at least by you.

I would try a full chkdsk and see if it generated the same errors found - or repaired them.

The Disc Doctor runs without having to restart initially while a full chkdsk usually requires a restart to run.

Cheers

solbjerg

p.s. DiscDoctor is a beta application

In previous versions it was called Chkdsk, but they have added a description of the legend generated - and at least that gives one an idea of the need for a full chkdsk command in Windows. As I understand it!

 

 

 

Hi,

i have the free version and used the Disc Doctor.

After the analysis there is an option to restart now and get the final analysis, or restart later and get the analysis in the next restart.

 

Well, whatever I do, nothing happens when my computer restarts.

 

Nothing pops up, nothing. What should happen in normal conditions?

Here is the report that the doctor gave me (drive C: has problems D: is okay):

 

Windows Vista

 

C:\ Volume Label: ACER, File System: NTFS

 

Volume label is ACER.

Disk Doctor is verifying files (stage 1 of 3)...

215936 file records processed.

File verification completed.

2995 large file records processed.

0 bad file records processed.

0 EA records processed.

76 reparse records processed.

Disk Doctor is verifying indexes (stage 2 of 3)...

Index entry F2C70072d01 in index $I30 of file 6077 is incorrect.

Index entry F2C700~1 in index $I30 of file 6077 is incorrect.

Index entry MSS00017.log in index $I30 of file 6763 is incorrect.

Index entry MSStmp.log in index $I30 of file 6763 is incorrect.

Index entry 00010013.ci in index $I30 of file 19549 is incorrect.

Index entry 00010013.dir in index $I30 of file 19549 is incorrect.

Index entry 00010013.wid in index $I30 of file 19549 is incorrect.

Index entry plugtmp-1 in index $I30 of file 32746 is incorrect.

Index entry PLUGTM~1 in index $I30 of file 32746 is incorrect.

Index entry sessionstore.js in index $I30 of file 86167 is incorrect.

Index entry SESSIO~1.JS in index $I30 of file 86167 is incorrect.

Index entry StreamMinerInfo.sol in index $I30 of file 115815 is incorrect.

Index entry STREAM~1.SOL in index $I30 of file 115815 is incorrect.

Index entry temp.ini in index $I30 of file 117541 is incorrect.

270366 index entries processed.

Index verification completed.

Errors found. Disk Doctor cannot continue in read-only mode.

 

 

D:\ Volume Label: DATA, File System: NTFS

 

Volume label is DATA.

Disk Doctor is verifying files (stage 1 of 3)...

68160 file records processed.

File verification completed.

0 large file records processed.

0 bad file records processed.

0 EA records processed.

0 reparse records processed.

Disk Doctor is verifying indexes (stage 2 of 3)...

79608 index entries processed.

Index verification completed.

0 unindexed files processed.

Disk Doctor is verifying security descriptors (stage 3 of 3)...

68160 security descriptors processed.

Security descriptor verification completed.

5724 data files processed.

Disk Doctor has checked the file system and found no problems.

112092159 KB total disk space.

28306836 KB in 37646 files.

16844 KB in 5726 indexes.

137559 KB in use by the system.

65536 KB occupied by the log file.

83630920 KB available on disk.

4096 bytes in each allocation unit.

28023039 total allocation units on disk.

20907730 allocation units available on disk.

 

 

What should I do? Help please, thank you!

[detailer]

Slight problem

 

Here we go with 64bit compatibility again :shock: The GUI is "cut off" on the right side-just beyond the "t" in Next button.Seems to function properly-reporting "no problems found".

[Iobiterer]

solbjerg - i did run Disk Check (chkdsk) but no errors anymore (maybe 1 day ago therer were).

 

Here is a pic of the report attached.

 

After that did another Disk Doctor, and Drive C: is full of some errors:

 

Windows Vista

 

C:\ Volume Label: ACER, File System: NTFS

 

Volume label is ACER.

Disk Doctor is verifying files (stage 1 of 3)...

215936 file records processed.

File verification completed.

2997 large file records processed.

0 bad file records processed.

0 EA records processed.

76 reparse records processed.

Disk Doctor is verifying indexes (stage 2 of 3)...

Index entry pgstat.stat in index $I30 of file 15233 is incorrect.

Index entry PGSTAT~1.STA in index $I30 of file 15233 is incorrect.

Index entry sessionstore.js in index $I30 of file 86167 is incorrect.

Index entry SESSIO~1.JS in index $I30 of file 86167 is incorrect.

Index entry 1F275BFBd01 in index $I30 of file 119880 is incorrect.

Index entry 1F275B~1 in index $I30 of file 119880 is incorrect.

Index entry 2072CA90d01 in index $I30 of file 119880 is incorrect.

Index entry 2072CA~1 in index $I30 of file 119880 is incorrect.

Index entry 264A8471d01 in index $I30 of file 119880 is incorrect.

Index entry 264A84~1 in index $I30 of file 119880 is incorrect.

Index entry 2B091C76d01 in index $I30 of file 119880 is incorrect.

Index entry 2B091C~1 in index $I30 of file 119880 is incorrect.

Index entry 2C7CFCF2d01 in index $I30 of file 119880 is incorrect.

Index entry 2C7CFC~1 in index $I30 of file 119880 is incorrect.

Index entry 2CE29E93d01 in index $I30 of file 119880 is incorrect.

Index entry 2CE29E~1 in index $I30 of file 119880 is incorrect.

Index entry 323CBF3Ed01 in index $I30 of file 119880 is incorrect.

Index entry 323CBF~1 in index $I30 of file 119880 is incorrect.

Index entry 527F7DCEd01 in index $I30 of file 119880 is incorrect.

Index entry 527F7D~1 in index $I30 of file 119880 is incorrect.

Index entry 6065EBADd01 in index $I30 of file 119880 is incorrect.

Index entry 6065EB~1 in index $I30 of file 119880 is incorrect.

Index entry 6E532E2Fd01 in index $I30 of file 119880 is incorrect.

Index entry 6E532E~1 in index $I30 of file 119880 is incorrect.

Index entry 801F7767d01 in index $I30 of file 119880 is incorrect.

Index entry 801F77~1 in index $I30 of file 119880 is incorrect.

Index entry 8074AE8Dd01 in index $I30 of file 119880 is incorrect.

Index entry 8074AE~1 in index $I30 of file 119880 is incorrect.

Index entry 81F7E383d01 in index $I30 of file 119880 is incorrect.

Index entry 81F7E3~1 in index $I30 of file 119880 is incorrect.

Index entry 8A97E967d01 in index $I30 of file 119880 is incorrect.

Index entry 8A97E9~1 in index $I30 of file 119880 is incorrect.

Index entry 9316AE5Dd01 in index $I30 of file 119880 is incorrect.

Index entry 9316AE~1 in index $I30 of file 119880 is incorrect.

Index entry 95982405d01 in index $I30 of file 119880 is incorrect.

Index entry 959824~1 in index $I30 of file 119880 is incorrect.

Index entry BE574ED8d01 in index $I30 of file 119880 is incorrect.

Index entry BE574E~1 in index $I30 of file 119880 is incorrect.

Index entry C3A2E366d01 in index $I30 of file 119880 is incorrect.

Index entry C3A2E3~1 in index $I30 of file 119880 is incorrect.

Index entry C8416F36d01 in index $I30 of file 119880 is incorrect.

Index entry C8416F~1 in index $I30 of file 119880 is incorrect.

Index entry CC0F347Fd01 in index $I30 of file 119880 is incorrect.

Index entry CC0F34~1 in index $I30 of file 119880 is incorrect.

Index entry D25991EDd01 in index $I30 of file 119880 is incorrect.

Index entry D25991~1 in index $I30 of file 119880 is incorrect.

Index entry D3B6E68Ed01 in index $I30 of file 119880 is incorrect.

Index entry D3B6E6~1 in index $I30 of file 119880 is incorrect.

Index entry D5E29330d01 in index $I30 of file 119880 is incorrect.

Index entry D5E293~1 in index $I30 of file 119880 is incorrect.

Index entry F2C7406Ed01 in index $I30 of file 119880 is incorrect.

Index entry F2C740~1 in index $I30 of file 119880 is incorrect.

Index entry Local State in index $I30 of file 170400 is incorrect.

Index entry LOCALS~1 in index $I30 of file 170400 is incorrect.

270408 index entries processed.

Index verification completed.

Errors found. Disk Doctor cannot continue in read-only mode.

 

 

What should i do with these index errors, I am really not a computer-wizard.

 

The last 2-3 days my computer has started running more slowly, especially internet (mozilla and Chrome). Internet speed tests say that everything is okay, but my computer seems to be the issue. That is why I started using Advanced System Care, and every darn Utility it has.

Is it good to run all the utilities? i.e. Smart RAM, Turbo Boost, Internet Boost(which did not change anything), shortcut fixer and disc cleaner. I ran them all, and starting to think that my computer is even more messed up now :roll:

 

People always say that this program helped them speed up their computer a lot. I dont see any difference :???: and I am wondering what am I doing wrong.

[solbjerg]

Hi Iobiterer

Sorry it didn't work to you satisfaction, but you may have tried too many things without reading about them.

Please read Usage of IObit Products !!

 

Is your service Indexing service activated in your services? It usually isn't I think. So that is a possibility you can try - but first read about how to use the parameters in sfc in Usage of IObit Products

especially if you use it from the command prompt.

In my opinion you should not run all applications in concert.

And some of those you mention must be used with the provision that you check every recommandation and decide if you want it or not.

Please read Usage of IObit Products !!

Finally I will say that I am not familiar with Vista - I am using XP sp3

Turbo boost is an application that works much like Gamebooster- closing down some services-which will be restored by a restart of your computer..

Internet booster will often require special help in the advanced mode.

If you have sufficient RAM there is no reason to run SmartRam in my opinion.

Disc Cleaner - there you have to check each/several recommandations

Shortcut fixer - please check the items - perhaps repair those you think you need.

SmartDefrag - I always use without running anything else.

In the optimizing scan in ASC you must check every "problem" and decide if you need it or not and place those you feel you need in the Ignore list- this function mainly have the parameter to save resources - and that is not always what one wants.

Cheers

solbjerg

 

 

 

solbjerg - i did run Disk Check (chkdsk) but no errors anymore (maybe 1 day ago therer were).

 

Here is a pic of the report attached.

 

After that did another Disk Doctor, and Drive C: is full of some errors:

 

Windows Vista

 

C:\ Volume Label: ACER, File System: NTFS

 

Volume label is ACER.

Disk Doctor is verifying files (stage 1 of 3)...

215936 file records processed.

File verification completed.

2997 large file records processed.

0 bad file records processed.

0 EA records processed.

76 reparse records processed.

Disk Doctor is verifying indexes (stage 2 of 3)...

Index entry pgstat.stat in index $I30 of file 15233 is incorrect.

Index entry PGSTAT~1.STA in index $I30 of file 15233 is incorrect.

Index entry sessionstore.js in index $I30 of file 86167 is incorrect.

Index entry SESSIO~1.JS in index $I30 of file 86167 is incorrect.

Index entry 1F275BFBd01 in index $I30 of file 119880 is incorrect.

Index entry 1F275B~1 in index $I30 of file 119880 is incorrect.

Index entry 2072CA90d01 in index $I30 of file 119880 is incorrect.

Index entry 2072CA~1 in index $I30 of file 119880 is incorrect.

Index entry 264A8471d01 in index $I30 of file 119880 is incorrect.

Index entry 264A84~1 in index $I30 of file 119880 is incorrect.

Index entry 2B091C76d01 in index $I30 of file 119880 is incorrect.

Index entry 2B091C~1 in index $I30 of file 119880 is incorrect.

Index entry 2C7CFCF2d01 in index $I30 of file 119880 is incorrect.

Index entry 2C7CFC~1 in index $I30 of file 119880 is incorrect.

Index entry 2CE29E93d01 in index $I30 of file 119880 is incorrect.

Index entry 2CE29E~1 in index $I30 of file 119880 is incorrect.

Index entry 323CBF3Ed01 in index $I30 of file 119880 is incorrect.

Index entry 323CBF~1 in index $I30 of file 119880 is incorrect.

Index entry 527F7DCEd01 in index $I30 of file 119880 is incorrect.

Index entry 527F7D~1 in index $I30 of file 119880 is incorrect.

Index entry 6065EBADd01 in index $I30 of file 119880 is incorrect.

Index entry 6065EB~1 in index $I30 of file 119880 is incorrect.

Index entry 6E532E2Fd01 in index $I30 of file 119880 is incorrect.

Index entry 6E532E~1 in index $I30 of file 119880 is incorrect.

Index entry 801F7767d01 in index $I30 of file 119880 is incorrect.

Index entry 801F77~1 in index $I30 of file 119880 is incorrect.

Index entry 8074AE8Dd01 in index $I30 of file 119880 is incorrect.

Index entry 8074AE~1 in index $I30 of file 119880 is incorrect.

Index entry 81F7E383d01 in index $I30 of file 119880 is incorrect.

Index entry 81F7E3~1 in index $I30 of file 119880 is incorrect.

Index entry 8A97E967d01 in index $I30 of file 119880 is incorrect.

Index entry 8A97E9~1 in index $I30 of file 119880 is incorrect.

Index entry 9316AE5Dd01 in index $I30 of file 119880 is incorrect.

Index entry 9316AE~1 in index $I30 of file 119880 is incorrect.

Index entry 95982405d01 in index $I30 of file 119880 is incorrect.

Index entry 959824~1 in index $I30 of file 119880 is incorrect.

Index entry BE574ED8d01 in index $I30 of file 119880 is incorrect.

Index entry BE574E~1 in index $I30 of file 119880 is incorrect.

Index entry C3A2E366d01 in index $I30 of file 119880 is incorrect.

Index entry C3A2E3~1 in index $I30 of file 119880 is incorrect.

Index entry C8416F36d01 in index $I30 of file 119880 is incorrect.

Index entry C8416F~1 in index $I30 of file 119880 is incorrect.

Index entry CC0F347Fd01 in index $I30 of file 119880 is incorrect.

Index entry CC0F34~1 in index $I30 of file 119880 is incorrect.

Index entry D25991EDd01 in index $I30 of file 119880 is incorrect.

Index entry D25991~1 in index $I30 of file 119880 is incorrect.

Index entry D3B6E68Ed01 in index $I30 of file 119880 is incorrect.

Index entry D3B6E6~1 in index $I30 of file 119880 is incorrect.

Index entry D5E29330d01 in index $I30 of file 119880 is incorrect.

Index entry D5E293~1 in index $I30 of file 119880 is incorrect.

Index entry F2C7406Ed01 in index $I30 of file 119880 is incorrect.

Index entry F2C740~1 in index $I30 of file 119880 is incorrect.

Index entry Local State in index $I30 of file 170400 is incorrect.

Index entry LOCALS~1 in index $I30 of file 170400 is incorrect.

270408 index entries processed.

Index verification completed.

Errors found. Disk Doctor cannot continue in read-only mode.

 

 

What should i do with these index errors, I am really not a computer-wizard.

 

The last 2-3 days my computer has started running more slowly, especially internet (mozilla and Chrome). Internet speed tests say that everything is okay, but my computer seems to be the issue. That is why I started using Advanced System Care, and every darn Utility it has.

Is it good to run all the utilities? i.e. Smart RAM, Turbo Boost, Internet Boost(which did not change anything), shortcut fixer and disc cleaner. I ran them all, and starting to think that my computer is even more messed up now :roll:

 

People always say that this program helped them speed up their computer a lot. I dont see any difference :???: and I am wondering what am I doing wrong.

[Alicia]

Here we go with 64bit compatibility again :shock: The GUI is "cut off" on the right side-just beyond the "t" in Next button.Seems to function properly-reporting "no problems found".

 

This problem will be solved in next version V3.6.1. Thank you for your feedback!