Tja ich habe es installiert und auch das Thandor Directory entsprechend gemounted.
Wenn ich nun das Programm Thandor starte erhalte ich die Fehlermeldung:
This is not a DOS Program!
Klappt also damit nicht.
--------------
Mit dem Windows debugger habe ich folgendes erhalten:
Microsoft ® Windows Debugger Version 6.4.0007.2
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini070208-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp.080413-2111
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Wed Jul 2 11:35:14.218 2008 (GMT+2)
System Uptime: 0 days 0:02:05.941
Loading Kernel Symbols
.............................................................................................................................
Loading unloaded module list
..........
Loading User Symbols
Unable to load image nv4_disp.dll, Win32 error 2
*** WARNING: Unable to verify timestamp for nv4_disp.dll
*** ERROR: Module load completed but symbols could not be loaded for nv4_disp.dll
************************************************************
*******************
* *
* Bugcheck Analysis *
* *
************************************************************
*******************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, bfc1dfcd, b6fbd838, 0}
Probably caused by : nv4_disp.dll ( nv4_disp+248fcd )
Followup: MachineOwner
---------
0: kd> !analyze -v
************************************************************
*******************
* *
* Bugcheck Analysis *
* *
************************************************************
*******************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: bfc1dfcd, The address that the exception occurred at
Arg3: b6fbd838, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in "0x%08lx" verweist auf Speicher in "0x%08lx". Der Vorgang "%s" konnte nicht auf dem Speicher durchgef hrt werden.
FAULTING_IP:
nv4_disp+248fcd
bfc1dfcd 0fb71a movzx ebx,word ptr [edx]
TRAP_FRAME: b6fbd838 -- (.trap ffffffffb6fbd838)
ErrCode = 00000000
eax=b66099c0 ebx=00000000 ecx=00000000 edx=08c02000 esi=00000000 edi=e1ad1808
eip=bfc1dfcd esp=b6fbd8ac ebp=e1b03fe0 iopl=0 nv up ei pl zr na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nv4_disp+0x248fcd:
bfc1dfcd 0fb71a movzx ebx,word ptr [edx] ds:0023:08c02000=????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
LAST_CONTROL_TRANSFER: from 00000000 to bfc1dfcd
STACK_TEXT:
e1b03fe0 00000000 b6fbdc50 00000000 00000000 nv4_disp+0x248fcd
FOLLOWUP_IP:
nv4_disp+248fcd
bfc1dfcd 0fb71a movzx ebx,word ptr [edx]
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nv4_disp+248fcd
MODULE_NAME: nv4_disp
IMAGE_NAME: nv4_disp.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 47e8719e
STACK_COMMAND: .trap ffffffffb6fbd838 ; kb
FAILURE_BUCKET_ID: 0x8E_nv4_disp+248fcd
BUCKET_ID: 0x8E_nv4_disp+248fcd
Followup: MachineOwner
trigger
