Reply to thread

Message

<blockquote data-quote="unalterable" data-source="post: 628490" data-attributes="member: 82868">Rebel Maedhros, i have the same problem... using MP 1.1 RC2... this is my last error... they're all pretty much identical:[CODE]Problem signature:Description:&nbsp; Stopped workingProblem signature:&nbsp; Problem Event Name:&nbsp; &nbsp; CLR20r3&nbsp; Problem Signature 01:&nbsp; &nbsp; mediaportal.exe&nbsp; Problem Signature 02:&nbsp; &nbsp; 1.0.6.27718&nbsp; Problem Signature 03:&nbsp; &nbsp; 4bc47e7c&nbsp; Problem Signature 04:&nbsp; &nbsp; DokanDrive&nbsp; Problem Signature 05:&nbsp; &nbsp; 1.0.0.0&nbsp; Problem Signature 06:&nbsp; &nbsp; 4a226e3a&nbsp; Problem Signature 07:&nbsp; &nbsp; 66&nbsp; Problem Signature 08:&nbsp; &nbsp; 36&nbsp; Problem Signature 09:&nbsp; &nbsp; System.AccessViolationException&nbsp; OS Version:&nbsp; &nbsp; 6.1.7600.2.0.0.256.1&nbsp; Locale ID:&nbsp; &nbsp; 2057[/CODE]Rebel, You seem to suggest you have solved the problem:I'm afraid the &quot;dokanctl /r a - dokanctl /i a - reboot&quot; passes the extent of my knowledge... Could someone explain this to me?... or offer an alternative solution? These errors are driving me mad!Or are we all just waiting for another (more stable) dokan/rarmount update?</blockquote>

[QUOTE="unalterable, post: 628490, member: 82868"] Rebel Maedhros, i have the same problem... using MP 1.1 RC2... this is my last error... they're all pretty much identical: [CODE]Problem signature: Description: Stopped working Problem signature: Problem Event Name: CLR20r3 Problem Signature 01: mediaportal.exe Problem Signature 02: 1.0.6.27718 Problem Signature 03: 4bc47e7c Problem Signature 04: DokanDrive Problem Signature 05: 1.0.0.0 Problem Signature 06: 4a226e3a Problem Signature 07: 66 Problem Signature 08: 36 Problem Signature 09: System.AccessViolationException OS Version: 6.1.7600.2.0.0.256.1 Locale ID: 2057 [/CODE] Rebel, You seem to suggest you have solved the problem: I'm afraid the "dokanctl /r a - dokanctl /i a - reboot" passes the extent of my knowledge... Could someone explain this to me?... or offer an alternative solution? These errors are driving me mad! Or are we all just waiting for another (more stable) dokan/rarmount update? [/QUOTE]

Verification