abelundercity wrote: >> fixme:ntoskrnl:KeInitializeSpinLock stub: 0x462740 >> fixme:ntoskrnl:KeInitializeSpinLock stub: 0x46273c >> fixme:ntoskrnl:KeInitializeSpinLock stub: 0x462744 >> fixme:ntoskrnl:KeInitializeSpinLock stub: 0x462748 >> fixme:ntoskrnl:KeInitializeSpinLock stub: 0x46274c >> wine: Call from 0x60398780 to unimplemented function ntoskrnl.exe.KeInitializeMutex, aborting >> wine: Unimplemented function ntoskrnl.exe.KeInitializeMutex called at address 0x60398780 (thread 0017), starting debugger... >> Unhandled exception: unimplemented function ntoskrnl.exe.KeInitializeMutex called in 32-bit code (0x603987f3). Well here's your problem! This is a bug. File one with bugzilla (http://bugs.winehq.org/ ). Be sure to include the name of the unimplemented function. >> Backtrace: ... >> 3 0x00451cc7 in cdr4_2k.sys (+0x1cc7) (0x7eda76c0) >> 4 0x004504b4 in cdr4_2k.sys (+0x4b4) (0x7eda76d8) And this is the driver that caused the problem. >> wine: Call from 0x60398780 to unimplemented function ntoskrnl.exe.KeInitializeMutex, aborting >> wine: Call from 0x6038f780 to unimplemented function ntoskrnl.exe.ExInitializeResourceLite, aborting >> wine: Unimplemented function ntoskrnl.exe.ExInitializeResourceLite called at address 0x6038f780 (thread 001e), starting debugger... >> Unhandled exception: unimplemented function ntoskrnl.exe.ExInitializeResourceLite called in 32-bit code (0x6038f7f3). And here's another bug! >> Backtrace: >> =>0 0x6038f7f3 RaiseException+0x73(code=2147483904, flags=<is not available>, nbargs=2, args=0x7edbf690) [/home/damnedyankee/wine-git/dlls/kernel32/except.c:84] in kernel32 (0x7edbf66c) >> 1 0x6053fc68 __wine_spec_unimplemented_stub+0x38(module="ntoskrnl.exe", function="ExInitializeResourceLite") [/home/damnedyankee/wine-git/dlls/winecrt0/stub.c:35] in ntoskrnl (0x7edbf69c) >> 2 0x60535428 __wine_stub_ExInitializeZone() in ntoskrnl (0x7edbf6d8) >> 3 0x604c6e67 load_driver+0x367() [/home/damnedyankee/wine-git/programs/winedevice/device.c:149] in winedevice (0x7edbf958) Now this is a weird stack. Why did load_driver() try to call ExInitializeZone()? >> PE 450000- 455560 Deferred cdralw2k.sys Looks like another driver. I'll bet this is why. What exactly do those drivers do? Do you know? Can you find out? The drivers dying is why your installer locks up. (Just be glad your whole system didn't go down. On Windows, if those drivers had failed, you would have gotten a BSOD.) Chip
