program SimulateError217; {$APPTYPE CONSOLE}
procedure TFakeObject.CrashMe; begin Writeln('This will not be reached'); end;
// Call virtual method -> corrupt VMT -> runtime error 217 obj.CrashMe; end. autodata runtime error 217 at 00580d29
// Windows SEH-based forced exception at 0x00580d29 #include <windows.h> void __declspec(naked) CrashAt00580d29() { __asm { mov eax, 0x00580d29 call eax // jump to invalid code -> exception } }
bcdedit.exe /set {current} nx AlwaysOn REM Then run autodata.exe If so, I can write a standalone .exe that prints that error message and terminates with the same error code for testing or documentation. Many AutoData versions store config in %APPDATA%\AutoData or
Compile with cl /LD /GS- crash.cpp — load DLL in target process → triggers error 217 at that address. Many AutoData versions store config in %APPDATA%\AutoData or C:\ProgramData\AutoData . Delete or corrupt these files, then launch:
type PFakeObject = ^TFakeObject; TFakeObject = class procedure CrashMe; virtual; end; then launch: type PFakeObject = ^TFakeObject
var obj: TFakeObject; p: Pointer; begin // Allocate memory but not as a valid object GetMem(p, SizeOf(TFakeObject)); FillChar(p^, SizeOf(TFakeObject), 0); obj := TFakeObject(p);