Hello I've found the following description while browsing the SVN repository: dosemu > trunk > src > emu-i386 > simx86 > interp.c: Correct off-by-one error in lock prefix handling. Fixes crash in Breadbox Ensemble lite. Today, I got a copy of the SVN trunk and compiled it. Everthing went right. I've made some tests and I can now run 4 different PC/GEOS versions with all CPU modes (off, vm86, full, vm86sim and fullsim). Congratulation! The simulated CPU now works with PC/GEOS too !! Unfortunately, the only thing I still can get running, is the mentioned Breadbox Ensemble lite :( DOSEMU terminates immediately when starting BBELITE. This are the error messages I get with the different CPU settings: 1. $_cpu_emu = "off": ERROR: general protection at 0x4f3ef: 0 2. $_cpu_emu = "vm86sim" or "fullsim": ERROR: unexpected CPU exception 0x0e err=0x00000006 cr2=086f007c while in vm86 (DOS) Program=sigsegv.c, Line=193 EIP: 11e7:0000088c ESP: 0288:00001614 VFLAGS(b): 00000 01110010 01010111 EAX: 00001320 EBX: 00001e40 ECX: 000000c6 EDX: 00000f6c VFLAGS(h): 00007257 ESI: 00000000 EDI: 00000026 EBP: 00000000 DS: 0288 ES: 0288 FS: 0278 GS: c4da FLAGS: CF PF AF ZF IF NT VM VIF IOPL: 3 STACK: eb 09 7b 93 57 72 88 02 00 00 -> 40 1e e9 08 e7 11 00 00 2b 15 OPS : 8c d8 1f 5a 5b c3 e8 cf ff cb -> 55 53 1e 56 fb 8b ec c5 76 08 55 11e7:088c push bp X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 196 () Minor opcode of failed request: 0 Serial number of failed request: 214 Current serial number in output stream: 220 3. $_cpu_emu = "vm86" or "full": No output at all... Don't know, if I did something wrong. But had to mention this. If I can help with more information, please let me know. # uname -a Linux va1 2.6.30-gentoo-r6 #9 Fri Mar 12 14:29:10 CET 2010 i686 VIA Esther processor 1000MHz CentaurHauls GNU/Linux Anyway, many thanks to the developers for this great piece of software. Andreas -- To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html