Error

[DavidHB]

I'll leave this one to Joel.

For what it's worth, I've seen this kind of error when messing with development builds, but not with the stable release. It seems to be associated in my case with repeated uninstalling and reinstalling; doing a full uninstall then running CCleaner to be sure has always fixed it for me, though not always at the first attempt.

I've not used the Program Compatibility Assistance Service; my approach is to change the setting on the compatibility tab of the executable (or shortcut) file properties. I also have UAC set to its lowest level, and usually don't need to run Eraser elevated at all in Windows 7.

David

[Joel]

Your problem has always been the same -- that Eraser cannot determine the drive configuration of your computer (necessary to handle file system specific issues.) One of your drives are inaccessible to you, and that's probably the one causing the problem.

I don't have a workaround offhand...

[Joel]

I've looked up some documentation, and will post a fix to the Eraser 6.0 branch (get from the nightly builds page) soon.

[Joel]

Fixed in r2139.

[eraseduser]

I've not used the Program Compatibility Assistance Service; my approach is to change the setting on the compatibility tab of the executable (or shortcut) file properties. I also have UAC set to its lowest level, and usually don't need to run Eraser elevated at all in Windows 7. David

There is a setting 'run program as administrator' (Privilege level) on the compatibility tab of the executable (or shortcut) file properties that can also be checked using the Program Compatibility Assistance Service (choice: The program requires additional permissions). That is what I did.

But I learned that it is not necessary to run Eraser as an Administrator all the time (viewtopic.php?f=2&t=6240#p18310).

Your problem has always been the same -- that Eraser cannot determine the drive configuration of your computer (necessary to handle file system specific issues.) One of your drives are inaccessible to you, and that's probably the one causing the problem.

I have no drive that is inaccessible to me. It was Eraser that could not determine the drive configuration of my computer which is rather new, bought 22nd December 2009. I was stubborn but now the problem is reported to be solved.

[Joel]

Did the new build solve the crash?

[eraseduser]

Not yet tested.

[eraseduser]

Did the new build solve the crash?

Still testing.


I wanted to make Unused disk space E:\ when the following error occured:

Session: Sonntag, 16. Mai 2010 18:41:12
Sonntag, 16. Mai 2010 18:41:12 Error The program does not have the required permissions to erase the unused space on disk. Run the program as an administrator and retry the operation.

[DavidHB]

Run the program as an administrator and retry the operation.

Did you?

David

[eraseduser]

Did the new build solve the crash?

Still testing.

I believe, yes.

I wanted to make Unused disk space E:\ when the following error occured:

Session: Sonntag, 16. Mai 2010 18:41:12
Sonntag, 16. Mai 2010 18:41:12 Error The program does not have the required permissions to erase the unused space on disk. Run the program as an administrator and retry the operation.

Run the program as an administrator and retry the operation.

Did you? David

Windows 7 x64
Eraser_6.0.7.1893

Yes, even though I was told that this should not be necessary. (viewtopic.php?f=2&t=6240#p18305)
Unused disk space E:\ completed with errors.

[DavidHB]

Were the errors the customary ones (problems accessing files etc.), or were there others in the log?

David

[eraseduser]

Windows 7 x64
Eraser_6.0.7.1893

Customary ones. Running Eraser as Administrator did not solve the problems accessing files etc..