paul williamson <paul.williamson@xxxxxxxxxxxx> wrote: > No replies so far, so here's the start of the console output in the hope > someone may know where the problem lies: > > fixme:system:SystemParametersInfoW Unimplemented action: 8193 > (SPI_SETFOREGROUNDLOCKTIMEOUT) wine: Unhandled page fault on read access > to 0x00000018 at address 0x4ef87a (thread 0009), starting debugger... > Unhandled exception: page fault on read access to 0x00000018 in 32-bit > code (0x004ef87a). Register dump: > CS:0073 SS:007b DS:007b ES:007b FS:0033 GS:003b EIP:004ef87a ESP:7f22eefc > EBP:7f22ef90 EFLAGS:00210246( - 00 -RIZP1) EAX:00000000 > EBX:7f22efc8 ECX:00000470 EDX:00000114 ESI:7f22f084 EDI:00000000 > Stack dump: > 0x7f22eefc: 7f22efc8 7f22f084 7ed14ff4 0000002b 0x7f22ef0c: 00000000 > 00000000 00000006 00000000 0x7f22ef1c: 00000000 00000000 00000000 > 00000000 0x7f22ef2c: 00000000 00000000 00000000 00000000 0x7f22ef3c: > 00000000 00000000 00000000 00000000 0x7f22ef4c: 00000000 00000000 > 00000000 00000000 Backtrace: > =>1 0x004ef87a in papyrus (+0xef87a) (0x7f22ef90) > 2 0x7ecba5ea in gdi32 (+0x2a5ea) (0x7f22f0f0) 3 0x7ecca77e > WineEngEnumFonts+0x13e() in gdi32 (0x7f22f420) 4 0x7ecba907 in gdi32 This is just a guess: The crash happens after a return from WineEngNumFonts. Ideally, you would run inside the debugger (wine winedbg program.exe, set break on WineEngNumFonts) and see if the returned values differ for working vs. not working. Daniel -- Read the Wine FAQ: http://winehq.org/site/docs/wine-faq/index Read the Wine User Guide: http://winehq.org/site/docs/wineusr-guide/index When you post: Which wine version? Self compiled or prepackaged? _______________________________________________ wine-users mailing list wine-users@xxxxxxxxxx http://www.winehq.org/mailman/listinfo/wine-users
