On Mon, 19 Jan 2004, James B. Hiller wrote: > autoexec.bat has: > > @echo off > echo "Welcome to dosemu 1.0.2.1!"
confusing isn't it? > SET PATH=C:\;C:\DOS;C:\DOS\COMMAND;C:\BUDGET;C:\BATCH;C:\MENU;C:\MSCMOUSE; > lredir e: linux\fs > lredir d: linux\fs\dosd > lredir c: linux\fs\dosc you can remove this last line. it happens automatically if you boot from /dosc. > C:\>cd ppm > C:\>ppm > > (App screen, "Exit" in the menu) > > ERROR: general protection at 0x242f7: 26 > SIGILL while in vm86() > ERROR: LOCK prefix not permitted! > Program=do_vm86.c, Line=348 > EIP: 23cf:00000607 ESP: 0000:0000103f VFLAGS(b): 00000 01110010 10000110 > EAX: 58034801 EBX: 0000ffff ECX: 0000000b EDX: 0044e400 VFLAGS(h): 00007286 > ESI: 00002004 EDI: 0000fcd8 EBP: 00001045 DS: 0000 ES: ffff FS: 0000 GS: 0000 > FLAGS: PF SF IF NT RF VM VIF IOPL: 3 > STACK: 00 00 00 00 00 00 00 00 00 00 -> 04 20 90 00 00 00 01 d0 cf fc > OPS : 00 c4 5e 06 26 c7 47 04 00 00 -> 26 ff 37 9a 0d 02 ac 15 83 c4 > 26ff37 23cf:0607 push word ptr es:[bx] most likely the DOS program went into zombie land, executing wrong instructions, and now executing an instruction that wraps around. Same with "arpl" being invalid the other mail. Very difficult to track this one down. Is it 100% reliable in real DOS? Can you compare debug logs for 1.0.2.1 when it did run? Or can you run it directly from an hdimage (as you might have done before)? > There seems to be an issue with the LOCK prefix, just as it says, during > boot up. # ls -ld /var/lock drwxrwxrwt 4 root root 4096 Jan 19 02:57 > /var/lock/ No, /var/lock is completely unrelated to the LOCK prefix intel x86 CPU instruction -- what's in a name? Bart - To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
