[Windows 7, 64-Bit] Error-Message while adding file to task

qpqpqpqp

New Member
Hi there!

I have a problem. I can't start a task manually. Look:



The error-message:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.IO.FileNotFoundException: Das System kann die angegebene Datei nicht finden. (Exception from HRESULT: 0x80070002)
at Eraser.Util.VolumeInfo..ctor(String volumeId)
at Eraser.Util.VolumeInfo.get_Volumes()
at Eraser.TaskDataSelectionForm..ctor()
at Eraser.TaskPropertiesForm.dataAdd_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
Eraser
Assembly Version: 6.0.6.1376
Win32 Version: 6.0.6.1376
CodeBase: file:///C:/PROGRA~1/Eraser/Eraser.exe
----------------------------------------
Eraser.Manager
Assembly Version: 6.0.6.1376
Win32 Version: 6.0.6.1376
CodeBase: file:///C:/PROGRA~1/Eraser/Eraser.Manager.DLL
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
Eraser.Util
Assembly Version: 6.0.6.1376
Win32 Version: 6.0.6.1376
CodeBase: file:///C:/PROGRA~1/Eraser/Eraser.Util.DLL
----------------------------------------
Eraser.DefaultPlugins
Assembly Version: 6.0.6.1376
Win32 Version: 6.0.6.1376
CodeBase: file:///C:/Program%20Files/Eraser/Plugins/Eraser.DefaultPlugins.dll
----------------------------------------
System.Core
Assembly Version: 3.5.0.0
Win32 Version: 3.5.30729.4926 built by: NetFXw7
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Core/3.5.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
Eraser.resources
Assembly Version: 6.0.6.1376
Win32 Version: 6.0.6.1376
CodeBase: file:///C:/Program%20Files/Eraser/en/Eraser.resources.dll
----------------------------------------
BevelLine
Assembly Version: 1.0.3589.29437
Win32 Version: 1.0.0.0
CodeBase: file:///C:/PROGRA~1/Eraser/BevelLine.DLL
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Eraser.Manager.resources
Assembly Version: 6.0.6.1376
Win32 Version: 6.0.6.1376
CodeBase: file:///C:/Program%20Files/Eraser/en/Eraser.Manager.resources.dll
----------------------------------------
mscorlib.resources
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
Eraser.Util.Unlocker
Assembly Version: 6.0.6.1376
Win32 Version: 6.0.6.1376
CodeBase: file:///C:/PROGRA~1/Eraser/Eraser.Util.Unlocker.DLL
----------------------------------------
msvcm90
Assembly Version: 9.0.30729.4926
Win32 Version: 9.00.30729.4926
CodeBase: file:///C:/Windows/WinSxS/amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.4926_none_08e1a05ba83fe554/msvcm90.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
I also unistalled Eraser and installied it again as Admin / with Admin-rights, but i got the same error. What can i do? By the way: Deleting files per Shell-Extension works fine for me.
 

DavidHB

Active Member
The 'stable' build seems to have issues of various kinds with Windows 7 x64; these seem in part to be a function of precisely which build of the .NET framework you have installed on your machine, so manifest themselves in different ways, which makes life hard for the programmers! Try the latest nightly build (I'd use the 6.0 fork, as I understand that the 6.2 fork may well get into a state of flux in the near future), to see if that helps.

David
 

Joel

Active Member
I'll need the file system, attachment (SATA/IDE/SCSI), any RAID systems, virtual disk drives, hard drives, external USB/firewire drives, USB keys/thumbdrives, card readers, network shares etc etc anything that may manifest as a drive at all that exists on your computer. Yes, do try the 6.0 builds and see if that helps anything.
 

qpqpqpqp

New Member
That is my profile: http://www.sysprofile.de/id124824

No RAID, no Card Readers, no network-sharing (disabled NetBIOS, disabled local networks, blocked port 137 UDP/TCP, etc.)

Virtual Drive: I use Daemon Tools Lite, but it's not running all-time (runs only if i need it)

Later today i will try 6.0 - bye!
 

qpqpqpqp

New Member
I don't really understnad what you mean with .net Frame work. Do I have to install a newer version?

By the way: The Nightly Build "Eraser 6.0.6.1754 r1754 8/2/10 6:41am" works fine for me.
 

Joel

Active Member
Then don't worry about it, just use 6.0.6.1754. You should update to the next stable version when it is released, however.
 

qpqpqpqp

New Member
I didn't understand it, cause my english ssems to be too bad to figure out, what you mean. Howevery, i will use the nightly version and if there will be an update to the next stable, i will update it. Thanks and greets to Singapur from germany!
 

DavidHB

Active Member
Just to explain .NET framework. That is the part of Microsoft's programming languages that applications written in those languages will use. It is useful to consider it as being (almost) a part of Windows. The problem comes when different programs use different versions of these files, or when the framework itself is updated through Windows Update. A programmer like Joel cannot conceivably test every variation that might be present in any XP, Vista or Windows 7 machine on the planet. They do therefore have to wait for an OS to become widespread, as Window 7 is now doing, and then for the bugs to get reported. That is why forums like this are so important; if people don't report bugs, they very probably won't get fixed.

I hope this explains things.

David
 
Top