linux-msdos-digest Sunday, April 30 2000 Volume 01 : Number 172 In this issue: ---------------------------------------------------------------------- From: Chris Willis-Ford <[EMAIL PROTECTED]> Date: Fri, 14 Apr 2000 19:16:24 -0700 (PDT) Subject: Re: Dosemu segfaults at software interrupt with CPU prefix [longish] I don't know assembly very well, and I certainly don't know much about protected mode stuff, but couldn't you just put a NOP in there instead of the prefix? On Fri, 14 Apr 2000, Josef Drexler wrote: > > Hi everybody, > > I hope this one proves somewhat interesting. First, let me give you a > short bit of background history to understand what I'm trying to do. > > I'm in the process of writing a wrapper for an old game (Ultima VII). This > game uses special protected mode instructions which are incompatible with > nearly everything else, including in particular any protected mode OS, so > I'm trying to replace these instruction and make it possible to run the > game under modern hardware. I intended to use Dosemu for testing and > debugging, so that I don't have to reboot every time I make a mistake. > > The way this wrapper will work is by replacing all access beyond real-mode > memory, i.e. all those instructions which have the operand-size prefix > (0x67) by a software interrupt instruction which will then emulate the > protected mode memory. For example, instead of > 66 67 8b 1e MOV EBX,[ESI] > I would have > 66 cd a0 xx INT A0 > > This may look a bit weird, but it is necessary to do what I need to do. > The CPU will ignore all prefixes to an int call, and the interrupt handler > can then look at them and emulate the instruction accordingly. xx is a > special code for interrupt handler determining the exact instruction, and > is not executed when returning from the interrupt by manipulating the IP on > the stack. > > So far, so good. It seems to work pretty well in a Windows 95 DOS box as > well as in real DOS. However, these are a pain to develop under, and when > I try to run this in Dosemu, I get a segmentation violation for all > interrupts with a prefix. The unprefixed interrupts, for example in the > case where I replace > 67 8a 06 MOV AL,[ESI] > with > cd a0 xx INT A0 > work fine, but any time there is a prefix, dosemu crashes with a segfault. > > Now, I understand that this is a pretty unique problem, so I'm very much > willing to fix it myself and hopefully supply a patch to the dosemu team, > but I've been looking through the source code and tried to understand why > or where the crash happens, but unfortunately I didn't get very far. I'm > not even sure where exactly I'd have to look. > > So, does anybody have any idea why this is happening, and what I can do to > fix it? Why does a prefixed int xx cause a segfault when a regular one > works fine? > > Oh, and if anybody wants to look at the source code of my wrapper, it's > available here: http://publish.uwo.ca/~jdrexler/ultima/u7patch/ . It's > written in Borland C++ 3.1. (I can't use DJGPP because it has to be real > mode.) You'd also need Ultima VII to test it, though. > > I would welcome and very much appreciate any help I could get on this. > Ultima VII is considered by many to be a classic, and it's a shame that you > have to jump through hoops to make it run on today's hardware. But > developing the wrapper under Win95 is tedious. I'd much prefer if I could > use dosemu under Linux, then I wouldn't have to reboot every few minutes... > > Thanks again for reading this and for all comments you can give. > > > -- > Josef Drexler ([EMAIL PROTECTED]) > http://publish.uwo.ca/~jdrexler/ > ------------------------------ From: Josef Drexler <[EMAIL PROTECTED]> Date: Sat, 15 Apr 2000 00:10:42 -0400 Subject: Re: Dosemu segfaults at software interrupt with CPU prefix [longish] At 19:16 14/04/00 -0700, you wrote: > >I don't know assembly very well, and I certainly don't know much about >protected mode stuff, but couldn't you just put a NOP in there instead of >the prefix? No, unfortunately not, because the the prefix is necessary for the emulation. I need to now whether it's supposed to be a 16bit or 32bit operation. I can't put it after the instruction either because then it's not unique whether it belongs to this one or the next one. >On Fri, 14 Apr 2000, Josef Drexler wrote: > >> >> Hi everybody, >> >> I hope this one proves somewhat interesting. First, let me give you a >> short bit of background history to understand what I'm trying to do. >> >> I'm in the process of writing a wrapper for an old game (Ultima VII). This >> game uses special protected mode instructions which are incompatible with >> nearly everything else, including in particular any protected mode OS, so >> I'm trying to replace these instruction and make it possible to run the >> game under modern hardware. I intended to use Dosemu for testing and >> debugging, so that I don't have to reboot every time I make a mistake. >> >> The way this wrapper will work is by replacing all access beyond real-mode >> memory, i.e. all those instructions which have the operand-size prefix >> (0x67) by a software interrupt instruction which will then emulate the >> protected mode memory. For example, instead of >> 66 67 8b 1e MOV EBX,[ESI] >> I would have >> 66 cd a0 xx INT A0 >> >> This may look a bit weird, but it is necessary to do what I need to do. >> The CPU will ignore all prefixes to an int call, and the interrupt handler >> can then look at them and emulate the instruction accordingly. xx is a >> special code for interrupt handler determining the exact instruction, and >> is not executed when returning from the interrupt by manipulating the IP on >> the stack. >> >> So far, so good. It seems to work pretty well in a Windows 95 DOS box as >> well as in real DOS. However, these are a pain to develop under, and when >> I try to run this in Dosemu, I get a segmentation violation for all >> interrupts with a prefix. The unprefixed interrupts, for example in the >> case where I replace >> 67 8a 06 MOV AL,[ESI] >> with >> cd a0 xx INT A0 >> work fine, but any time there is a prefix, dosemu crashes with a segfault. >> >> Now, I understand that this is a pretty unique problem, so I'm very much >> willing to fix it myself and hopefully supply a patch to the dosemu team, >> but I've been looking through the source code and tried to understand why >> or where the crash happens, but unfortunately I didn't get very far. I'm >> not even sure where exactly I'd have to look. >> >> So, does anybody have any idea why this is happening, and what I can do to >> fix it? Why does a prefixed int xx cause a segfault when a regular one >> works fine? >> >> Oh, and if anybody wants to look at the source code of my wrapper, it's >> available here: http://publish.uwo.ca/~jdrexler/ultima/u7patch/ . It's >> written in Borland C++ 3.1. (I can't use DJGPP because it has to be real >> mode.) You'd also need Ultima VII to test it, though. >> >> I would welcome and very much appreciate any help I could get on this. >> Ultima VII is considered by many to be a classic, and it's a shame that you >> have to jump through hoops to make it run on today's hardware. But >> developing the wrapper under Win95 is tedious. I'd much prefer if I could >> use dosemu under Linux, then I wouldn't have to reboot every few minutes... >> >> Thanks again for reading this and for all comments you can give. >> >> >> -- >> Josef Drexler ([EMAIL PROTECTED]) >> http://publish.uwo.ca/~jdrexler/ >> > - -- Josef Drexler ([EMAIL PROTECTED]) http://publish.uwo.ca/~jdrexler/ ------------------------------ From: Bart Oldeman <[EMAIL PROTECTED]> Date: Sat, 15 Apr 2000 15:35:49 +0100 (BST) Subject: Re: Dosemu segfaults at software interrupt with CPU prefix [longish] On Fri, 14 Apr 2000, Josef Drexler wrote: > So, does anybody have any idea why this is happening, and what I can do to > fix it? Why does a prefixed int xx cause a segfault when a regular one > works fine? The following patch fixes this for me: (but move the line containing "esi,edi,ecx" behind "should use ") I hope I haven't looked over something in this quick patch. Bart diff -u dosemu-1.0.0-orig/src/emu-i386/do_vm86.c dosemu-1.0.0/src/emu-i386/do_vm86.c - --- dosemu-1.0.0-orig/src/emu-i386/do_vm86.c Sun Mar 5 19:41:09 2000 +++ dosemu-1.0.0/src/emu-i386/do_vm86.c Sat Apr 15 15:28:30 2000 @@ -193,6 +193,11 @@ LWORD(eip) += (csp-lina); switch (*csp) { + + case 0xcd: /* int */ + do_int(*(csp+1)); + LWORD(eip)+=2; + break; case 0x6c: /* insb */ /* NOTE: ES can't be overwritten; prefixes 66,67 should use esi,edi,ecx ------------------------------ From: Josef Drexler <[EMAIL PROTECTED]> Date: Sat, 15 Apr 2000 17:48:39 -0400 (EDT) Subject: Re: Dosemu segfaults at software interrupt with CPU prefix [longish] On Sat, 15 Apr 2000, Bart Oldeman wrote: > On Fri, 14 Apr 2000, Josef Drexler wrote: > > > So, does anybody have any idea why this is happening, and what I can do to > > fix it? Why does a prefixed int xx cause a segfault when a regular one > > works fine? > > The following patch fixes this for me: (but move the line containing > "esi,edi,ecx" behind "should use ") > > I hope I haven't looked over something in this quick patch. No, you haven't, it works perfectly. Thanks a lot! > Bart > > diff -u dosemu-1.0.0-orig/src/emu-i386/do_vm86.c > dosemu-1.0.0/src/emu-i386/do_vm86.c > --- dosemu-1.0.0-orig/src/emu-i386/do_vm86.c Sun Mar 5 19:41:09 2000 > +++ dosemu-1.0.0/src/emu-i386/do_vm86.c Sat Apr 15 15:28:30 2000 > @@ -193,6 +193,11 @@ > LWORD(eip) += (csp-lina); > > switch (*csp) { > + > + case 0xcd: /* int */ > + do_int(*(csp+1)); > + LWORD(eip)+=2; > + break; > > case 0x6c: /* insb */ > /* NOTE: ES can't be overwritten; prefixes 66,67 should use > esi,edi,ecx > - -- Josef Drexler ------------------------------ From: Bart Oldeman <[EMAIL PROTECTED]> Date: Sat, 15 Apr 2000 23:53:38 +0100 (BST) Subject: Re: Dosemu segfaults at software interrupt with CPU prefix [longish] On Sat, 15 Apr 2000, Josef Drexler wrote: > On Sat, 15 Apr 2000, Bart Oldeman wrote: > > The following patch fixes this for me: (but move the line containing > > "esi,edi,ecx" behind "should use ") > > > > I hope I haven't looked over something in this quick patch. > > No, you haven't, it works perfectly. Thanks a lot! Nice. I produced a new one which is a bit more elegant: it treats all int variations and basically lets dosemu return to vm86 mode after a 0x66 in this case, where upon the dos app invokes the int instruction which might get trapped by dosemu in turn. So it was eg (GP=general protection fault): 0x66 0xcd 0x10 -> GP -> do_int(0x10) -> next instruction and now: 0x66 0xcd 0x10 -> GP -> 0xcd 0x10 -> GP -> do_int(0x10) I'll have to let the DOSEMU team decide whether or which version of the patch they would like to have. BTW, (0xf1) int 1 is an "undocumented" instruction, but we know how nicely behaved dos application are ;-) Bart diff -u dosemu-1.0.0-orig/src/emu-i386/do_vm86.c dosemu-1.0.0/src/emu-i386/do_vm86.c - --- dosemu-1.0.0-orig/src/emu-i386/do_vm86.c Sun Mar 5 19:41:09 2000 +++ dosemu-1.0.0/src/emu-i386/do_vm86.c Sat Apr 15 23:33:25 2000 @@ -193,6 +193,13 @@ LWORD(eip) += (csp-lina); switch (*csp) { + + case 0xcc: /* int 3 */ + case 0xcd: /* int */ + case 0xce: /* into */ + case 0xcf: /* iret */ + case 0xf1: /* int 1 */ + break; case 0x6c: /* insb */ /* NOTE: ES can't be overwritten; prefixes 66,67 should use esi,edi,ecx ------------------------------ From: Alistair MacDonald <[EMAIL PROTECTED]> Date: Sun, 16 Apr 2000 00:15:40 +0100 (BST) Subject: Re: All /usr/local install? On Wed, 12 Apr 2000, Jay Rogers wrote: > www.dosemu.org lists the latest stable release as 0.98.8. Is > this correct? If not, what's the latest stable release? I'll put my hand up and say this problem is my fault. I haven't updated the page yet. My only excuse is that making changes to our www pages is not (currently) as easy as we would like it to be. Alistair ------------------------------ From: Josef Drexler <[EMAIL PROTECTED]> Date: Sat, 15 Apr 2000 21:46:22 -0400 (EDT) Subject: Re: Dosemu segfaults at software interrupt with CPU prefix [longish] On Sat, 15 Apr 2000, Bart Oldeman wrote: > On Sat, 15 Apr 2000, Josef Drexler wrote: > > > On Sat, 15 Apr 2000, Bart Oldeman wrote: > > > The following patch fixes this for me: (but move the line containing > > > "esi,edi,ecx" behind "should use ") > > > > > > I hope I haven't looked over something in this quick patch. > > > > No, you haven't, it works perfectly. Thanks a lot! > > Nice. I produced a new one which is a bit more elegant: it treats all int > variations and basically lets dosemu return to vm86 mode after a 0x66 in > this case, where upon the dos app invokes the int instruction which might > get trapped by dosemu in turn. > > So it was eg (GP=general protection fault): > 0x66 0xcd 0x10 -> GP -> do_int(0x10) -> next instruction > > and now: > > 0x66 0xcd 0x10 -> GP -> 0xcd 0x10 -> GP -> do_int(0x10) I like it even better this way, because now I can use dosdebug's bpint for my weird interrupts. That didn't work before, but it didn't bother me too much. Although there may be one thing that might need to be improved. The iret instruction (0xcf) has two different forms, depending on the operand size. So it should executed differently depending on the 0x67 prefix. However, if for example, the instruction was coded as 0x67 0x66 0xcf IRETD (where the 0x66 is again ignored), it would be executed as a simple IRET because the prefixes are ignored, if I understand your code correctly. In the case 0x66 0x67 0xcf IRETD it would be executed correctly, but the order of prefixes should not matter. I'm afraid I'll have to leave it up to you to actually fix it though, I'm not familiar enough with dosemu yet. Anyway, that code will not happen too often, I certainly don't need it for my program, so it may be best if you just leave out the 0xcf from the case list. > I'll have to let the DOSEMU team decide whether or which version of the > patch they would like to have. > > BTW, (0xf1) int 1 is an "undocumented" instruction, but we know how > nicely behaved dos application are ;-) Heh... Thanks again for your support! > Bart > > diff -u dosemu-1.0.0-orig/src/emu-i386/do_vm86.c > dosemu-1.0.0/src/emu-i386/do_vm86.c > --- dosemu-1.0.0-orig/src/emu-i386/do_vm86.c Sun Mar 5 19:41:09 2000 > +++ dosemu-1.0.0/src/emu-i386/do_vm86.c Sat Apr 15 23:33:25 2000 > @@ -193,6 +193,13 @@ > LWORD(eip) += (csp-lina); > > switch (*csp) { > + > + case 0xcc: /* int 3 */ > + case 0xcd: /* int */ > + case 0xce: /* into */ > + case 0xcf: /* iret */ ^^^^^^^^^^^ This probably needs to be fixed... > + case 0xf1: /* int 1 */ > + break; > > case 0x6c: /* insb */ > /* NOTE: ES can't be overwritten; prefixes 66,67 should use > esi,edi,ecx > - -- Josef Drexler ------------------------------ From: Jonathan Edwards <[EMAIL PROTECTED]> Date: Sun, 16 Apr 2000 10:07:16 -0400 Subject: DOSEMU with power management on laptops I would appreciate hearing from anyone who's using DOSEMU on a laptop and who does not have any trouble with DOSEMU sessions hanging upon resumption from a suspend or hibernate. Jonathan Edwards ------------------------------ From: Bart Oldeman <[EMAIL PROTECTED]> Date: Sun, 16 Apr 2000 15:05:28 +0100 (BST) Subject: Re: Dosemu segfaults at software interrupt with CPU prefix [longish] On Sat, 15 Apr 2000, Josef Drexler wrote: > On Sat, 15 Apr 2000, Bart Oldeman wrote: > > On Sat, 15 Apr 2000, Josef Drexler wrote: > > > On Sat, 15 Apr 2000, Bart Oldeman wrote: > > So it was eg (GP=general protection fault): > > 0x66 0xcd 0x10 -> GP -> do_int(0x10) -> next instruction > > > > and now: > > > > 0x66 0xcd 0x10 -> GP -> 0xcd 0x10 -> GP -> do_int(0x10) > > I like it even better this way, because now I can use dosdebug's bpint > for my weird interrupts. That didn't work before, but it didn't bother me > too much. Nice. > Although there may be one thing that might need to be improved. The iret > instruction (0xcf) has two different forms, depending on the operand size. > So it should executed differently depending on the 0x67 prefix. > > However, if for example, the instruction was coded as > 0x67 0x66 0xcf IRETD > (where the 0x66 is again ignored), it would be executed as a simple IRET > because the prefixes are ignored, if I understand your code correctly. > In the case > 0x66 0x67 0xcf IRETD > it would be executed correctly, but the order of prefixes should not > matter. Yes, of course. I suspect the IRETD instruction to be _highly_ unusual for any DOS application, even DPMI ones, so I've enabled the old behaviour (DOSEMU quits with a general protection fault) for this particular case again. > > BTW, (0xf1) int 1 is an "undocumented" instruction, but we know how > > nicely behaved dos application are ;-) > Heh... This one didn't work under DOSEMU as it did in real mode (DOSEMU gave a GP for any form, but real mode did an int 1), so I've made the behaviour similar by emulation. A new patch is below. Bart diff -u dosemu-1.0.0-orig/src/emu-i386/do_vm86.c dosemu-1.0.0/src/emu-i386/do_vm86.c - --- dosemu-1.0.0-orig/src/emu-i386/do_vm86.c Sun Mar 5 19:41:09 2000 +++ dosemu-1.0.0/src/emu-i386/do_vm86.c Sun Apr 16 14:43:56 2000 @@ -193,6 +193,18 @@ LWORD(eip) += (csp-lina); switch (*csp) { + /* interrupt calls after prefix: we go back to vm86 */ + case 0xcc: /* int 3 and let it generate an */ + case 0xcd: /* int interrupt (don't advance eip) */ + case 0xce: /* into */ + break; + case 0xcf: /* iret */ + if (prefix67) goto op0ferr; /* iretd */ + break; + case 0xf1: /* int 1 */ + LWORD(eip)++; /* emulated "undocumented" instruction */ + do_int(1); + break; case 0x6c: /* insb */ /* NOTE: ES can't be overwritten; prefixes 66,67 should use esi,edi,ecx ------------------------------ From: Jesper Anderson <[EMAIL PROTECTED]> Date: Sun, 16 Apr 2000 22:42:00 -0400 Subject: Re: DOSEMU with power management on laptops On Sun, Apr 16, 2000 at 10:07:16AM -0400, Jonathan Edwards wrote: > I would appreciate hearing from anyone who's using DOSEMU on a laptop > and who does not have any trouble with DOSEMU sessions hanging upon > resumption from a suspend or hibernate. I had some initial trouble with this as well with the precompiled version of dosemu. When I reconfigured and recompiled it worked fine, except the DOS RTC loses the time spent in suspend and doesn't catch up on resume. Very annoying when using Agenda. Jesper - -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." - -- Benjamin Franklin, 1759 ------------------------------ From: Kevin Cheng <[EMAIL PROTECTED]> Date: Mon, 17 Apr 2000 16:53:26 +0100 (BST) Subject: Dosemu-0.66.7 Dear Vger I'm having problems with dosemu with Windows 98 2nd Edition DOS. Dosemu works fine with the FreeDos example hdimage. Okay, this is what I did: Edited /etc/dosemu.conf file and changed the line for the enviromental variable hdimage = hdimage.first to hdimage = /dev/hda1 (primary active partition with Win98 DOS) I then type DOS and it boots up okay but after going through autoexec.bat it freezes and halts. I tried an empty autoexec.bat and I still get the freezed up problem. ------------------------------ From: [EMAIL PROTECTED] Date: Mon, 17 Apr 2000 22:24:57 +0200 (MET DST) Subject: Dosemu 1.0 and linux 2.3.99 (pre5) Hi! It's been quite a long time since I last used dosemu (must have been something like 0.7) and I've decided to give it a new try. Unfortunately I've been unable to build the 1.0 release with my 2.3.99pre5 kernel. The build fails with: make[1]: Entering directory `/usr2/home/alain/dosemu-1.0.0/src' Starting DOSEMU VERSION.0 compile... - -> IMPORTANT! - Please read 'QuickStart' file before compiling DOSEMU! - Location and format of DOSEMU files have changed since 0.50pl1! - -> REQUIREMENTS for DOSEMU: - gcc 2.7.2 - libc 5.4.7 - Linux >= 2.0.28, 2.1.x >= 2.1.15 - 16 megabytes total memory+swap ====> Press Enter to continue, or hit Ctrl-C to abort <==== make[2]: Entering directory `/usr2/home/alain/dosemu-1.0.0/src/tools' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/usr2/home/alain/dosemu-1.0.0/src/tools' make[2]: Entering directory `/usr2/home/alain/dosemu-1.0.0/src/commands' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/usr2/home/alain/dosemu-1.0.0/src/commands' make[2]: Entering directory `/usr2/home/alain/dosemu-1.0.0/src/tools/periph' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/usr2/home/alain/dosemu-1.0.0/src/tools/periph' make[2]: Entering directory `/usr2/home/alain/dosemu-1.0.0/src/env/video' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/usr2/home/alain/dosemu-1.0.0/src/env/video' make[2]: Entering directory `/usr2/home/alain/dosemu-1.0.0/src/base/async' make[2]: Nothing to be done for `lib'. make[2]: Leaving directory `/usr2/home/alain/dosemu-1.0.0/src/base/async' make[2]: Entering directory `/usr2/home/alain/dosemu-1.0.0/src/arch/linux/async' make[2]: Nothing to be done for `lib'. make[2]: Leaving directory `/usr2/home/alain/dosemu-1.0.0/src/arch/linux/async' make[2]: Entering directory `/usr2/home/alain/dosemu-1.0.0/src/arch/linux/mapping' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/usr2/home/alain/dosemu-1.0.0/src/arch/linux/mapping' make[2]: Entering directory `/usr2/home/alain/dosemu-1.0.0/src/base/misc' gcc -c -D_GNU_SOURCE -O2 -fomit-frame-pointer -m486 -malign-loops=2 - -malign-jumps=2 -malign-functions=2 -MD -fno-strict-aliasi ng -DGCC_VERSION_CODE=2095 -DASM_PEDANTIC -DGLIBC_VERSION_CODE=2001 - -D_XOPEN_SOURCE -pipe -DUSING_NET -Wall -I/usr2/home/alai n/dosemu-1.0.0/src/include -I/usr2/home/alain/dosemu-1.0.0/src/dosext/dpmi - -I/usr2/home/alain/dosemu-1.0.0/src/include/slang -I /usr/X11R6/include -o disks.o disks.c In file included from /usr/include/linux/fs.h:23, from disks.c:28: /usr/include/linux/string.h:12: parse error before `__extension__' /usr/include/linux/string.h:13: parse error before `__extension__' /usr/include/linux/string.h:15: parse error before `__extension__' /usr/include/linux/string.h:16: parse error before `__extension__' /usr/include/linux/string.h:18: parse error before `__extension__' /usr/include/linux/string.h:18: parse error before `&&' /usr/include/linux/string.h:20: parse error before `__extension__' /usr/include/linux/string.h:20: parse error before `(' /usr/include/linux/string.h:21: parse error before `__extension__' /usr/include/linux/string.h:24: parse error before `__extension__' /usr/include/linux/string.h:24: parse error before `&&' /usr/include/linux/string.h:25: parse error before `__extension__' /usr/include/linux/string.h:25: parse error before `&&' /usr/include/linux/string.h:25: warning: data definition has no type or storage class /usr/include/linux/string.h:25: parse error before `}' /usr/include/linux/string.h:25: conflicting declarations of `__result' /usr/include/linux/string.h:25: `__result' previously declared here <SNIP> Is there something that must be done to "port" dosemu to 2.3.99 (and the future 2.4.X), or am I doing somthing wrong? Any info will be greatly appreciated! - ---------------------------------- Date: 17-Apr-2000 Time: 22:19:36 ------------------------------ From: Bart Oldeman <[EMAIL PROTECTED]> Date: Mon, 17 Apr 2000 21:18:01 +0100 (BST) Subject: Re: Dosemu 1.0 and linux 2.3.99 (pre5) On Mon, 17 Apr 2000 [EMAIL PROTECTED] wrote: > Hi! > > It's been quite a long time since I last used dosemu (must have > been something like 0.7) and I've decided to give it a new try. > Unfortunately I've been unable to build the 1.0 release > with my 2.3.99pre5 kernel. The build fails with: > In file included from /usr/include/linux/fs.h:23, > from disks.c:28: > /usr/include/linux/string.h:12: parse error before `__extension__' Is your /usr/include/linux a symlink into the kernel tree? This is not recommended anymore, AFAIK. You could try the string.h included with your version of glibc. Or has that one been changed as well? (I'm using glibc 2.1.3). > <SNIP> > Is there something that must be done to "port" dosemu to 2.3.99 (and the > future 2.4.X), or am I doing somthing wrong? Maybe. If the string.h dosemu complains about gets included in glibc. Bart ------------------------------ From: Alistair MacDonald <[EMAIL PROTECTED]> Date: Mon, 17 Apr 2000 22:08:25 +0100 (BST) Subject: Re: Dosemu-0.66.7 On Mon, 17 Apr 2000, Kevin Cheng wrote: > I'm having problems with dosemu with Windows 98 2nd Edition DOS. Dosemu > works fine with the FreeDos example hdimage. Okay, this is what I did: [...] > I then type DOS and it boots up okay but after going through autoexec.bat > it freezes and halts. I tried an empty autoexec.bat and I still get the > freezed up problem. 1) 0.66.7 is *very* old (A quick check indicates July 3rd 1997) You would be better upgrading if at all possible. 2) Are you trying to boot a non-GUI version of Win98-2 ? You must either prevent Windows starting the GUI (from the menu), use a version which doesn't start it by default (the rescue disk) or disable the GUI. For this last one you need to make the [Options] section of msdos.sys look like: [Options] Logo=0 BootGUI=0 (This is documented in the HOWTO) Alistair ------------------------------ From: [EMAIL PROTECTED] Date: Tue, 18 Apr 2000 06:39:04 +0200 (MET DST) Subject: Re: Dosemu 1.0 and linux 2.3.99 (pre5) On 17-Apr-2000 Bart Oldeman wrote: > On Mon, 17 Apr 2000 [EMAIL PROTECTED] wrote: > >> Hi! >> >> It's been quite a long time since I last used dosemu (must have >> been something like 0.7) and I've decided to give it a new try. >> Unfortunately I've been unable to build the 1.0 release >> with my 2.3.99pre5 kernel. The build fails with: > >> In file included from /usr/include/linux/fs.h:23, >> from disks.c:28: >> /usr/include/linux/string.h:12: parse error before `__extension__' > > Is your /usr/include/linux a symlink into the kernel tree? Yes it is (with /usr/include/asm -> /usr/src/linux/include/asm as well). > This is not > recommended anymore, AFAIK. Huh? I didn't know about that! How long has this been the case? On the other hand I know that including kernel headers in an application is no longer considered a good practice since libc6 is supposed to expose all the necessary API's (how true THAT is, I don't know). > You could try the string.h included with your > version of glibc. Or has that one been changed as well? (I'm using glibc > 2.1.3). I'm using 2.1.2. However it seems to me that dosemu specifically requires header files from the kernel tree: if I remove the symlinks, the build fails with make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/usr2/home/alain/dosemu-1.0.0/src/tools/periph' make[1]: *** No rule to make target `/usr/include/linux/errno.h', needed by `emu.o'. Stop. make[1]: Leaving directory `/usr2/home/alain/dosemu-1.0.0/src' make: *** [default] Error 2 > >> <SNIP> >> Is there something that must be done to "port" dosemu to 2.3.99 (and the >> future 2.4.X), or am I doing somthing wrong? > > Maybe. If the string.h dosemu complains about gets included in glibc. > > Bart > No luck so far, but thanks anyway - ---------------------------------- Date: 18-Apr-2000 Time: 06:29:23 ------------------------------ From: [EMAIL PROTECTED] (Eric W. Biederman) Date: 18 Apr 2000 01:25:38 -0500 Subject: Re: Dosemu 1.0 and linux 2.3.99 (pre5) [EMAIL PROTECTED] writes: > On 17-Apr-2000 Bart Oldeman wrote: > > On Mon, 17 Apr 2000 [EMAIL PROTECTED] wrote: > > > >> Hi! > >> > >> It's been quite a long time since I last used dosemu (must have > >> been something like 0.7) and I've decided to give it a new try. > >> Unfortunately I've been unable to build the 1.0 release > >> with my 2.3.99pre5 kernel. The build fails with: > > > >> In file included from /usr/include/linux/fs.h:23, > >> from disks.c:28: > >> /usr/include/linux/string.h:12: parse error before `__extension__' > > > > Is your /usr/include/linux a symlink into the kernel tree? > Yes it is (with /usr/include/asm -> /usr/src/linux/include/asm as well). > > > This is not > > recommended anymore, AFAIK. > Huh? I didn't know about that! How long has this been the case? > On the other hand I know that including kernel headers in an > application is no longer considered a good practice since libc6 > is supposed to expose all the necessary API's (how true THAT is, > I don't know). I think it's a bit of both you shouldn't need to touch your kernel headers as nothing should look at them... FWIW Last time I did a manual install of glibc-2.0.x the symlinks where indeed expected to point to your real kernel headers... dosemu is much older than glibc-2.x.x and lately has been primarily in maitenance mode, so it's primarily lazyness on our part that those headers are still included. Our best supported target is still libc5 although glibc isn't too bad. Right now you can't compile a static application with glibc-2.x :( On the question of porting it looks like what needs to be done is go through and audit all of the includes from the linux, and the asm hierarchies and make them conditional on not having libc6.... However you should be able to compile with 2.2 and be fine. Eric ------------------------------ From: Bart Oldeman <[EMAIL PROTECTED]> Date: Tue, 18 Apr 2000 12:37:22 +0100 (BST) Subject: Re: Dosemu 1.0 and linux 2.3.99 (pre5) On Tue, 18 Apr 2000 [EMAIL PROTECTED] wrote: > On 17-Apr-2000 Bart Oldeman wrote: > > On Mon, 17 Apr 2000 [EMAIL PROTECTED] wrote: > > Is your /usr/include/linux a symlink into the kernel tree? > Yes it is (with /usr/include/asm -> /usr/src/linux/include/asm as well). > > > This is not > > recommended anymore, AFAIK. > Huh? I didn't know about that! How long has this been the case? > On the other hand I know that including kernel headers in an > application is no longer considered a good practice since libc6 > is supposed to expose all the necessary API's (how true THAT is, > I don't know). OK, I guess I was spoiled by Debian policy and bypassed other distributions. I think you should still be able to compile dosemu with kernel headers from 2.2 and run it under 2.3.99. Bart (see Debian documentation below) - ------> /usr/doc/libc6/README.Debian.gz <------ Q1: Why does the Debian libc6-dev package create /usr/include/linux and /usr/include/asm directories containing header files from a specific kernel, instead of using the "established" convention of making those directories into symlinks pointing to the currently installed kernel? A1: Occasionally, changes in the kernel headers cause problems with the compilation of libc and of programs that use libc. To ensure that users are not affected by these problems, we configure libc to use the headers from a kernel that is known to work with libc and the programs that depend on stable kernel headers. Q2: What if I want to compile a program that needs a feature from a later kernel than is used by libc? A2: In practice, most programs will not have this problem. However, depending on the scope of the problem you have several options available: If the situation is one like "kernel driver development", where all use of the machine for development is expected to be against a different set of kernel headers than are supplied with the "stock" libc6-dev, rebuilding the glibc packages against that particular kernel will create a full set of libc6 packages that are "compliant" with the new kernel. All development done on machines with these packages installed will be done against the new kernel. To build libc6-dev against your particular kernel, export the environment variable ksource, set to the path to that particular kernel and build the package. If you want this new glibc package to stick against further upgrades, simply use dselect and place the packages on HOLD. This will keep them from being upgraded against your wishes. If there is just one particular program/package that needs different headers, and your kernel of choice is installed in the usual place, you can use the - -I/usr/src/linux/include option on the gcc command line, when compiling that specific program. ------------------------------ From: Gabe Ycas <[EMAIL PROTECTED]> Date: Tue, 18 Apr 2000 21:09:02 -0500 Subject: VGA [game] And X11 I have been trying to get a video game working using dosemu [1.0.0]. If I wasn't hallucinating [from sleep depervation], I did succede in getting the game to work (Dark Forces, an older Star Wars game). ANyway, not I get a page fault when I start the program. The output of xdos - -D+9v -O is as follows: [00021125] VGAEmu: vga_emu_setmode: requested mode: 0x13 (40 x 25) [00021126] VGAEmu: vga_emu_setmode: mode found in first run [00021127] VGAEmu: vga_emu_setmode: mode = 0x13, (320 x 200, 40 x 25, 8 x 8) [00021128] VGAEmu: vga_emu_setmode: scan_len = 320 [00021155] VGAemu: Seq_write_value: chain4 = 0 [00021156] VGAemu: Seq_write_value: map mask = 0xf, write plane = 0 [00021158] VGAemu: Seq_write_value: map mask = 0xf, write plane = 0 [00021164] vesa: vesa_emu_fault(): Not in ROM range page= 0x8b558 adress: 0x8b61898f [00021165] VGAEmu: vga_emu_fault: not in 0xa0000 - 0xc1000 range; page = 0x8b618, address = 0x8b61898f [00021167] VID: video_close() called [00021174] VID: video_close()->Video->close() called The relevant part of dosemu.conf (to my knowledge) is: $_video = "vga" # one of: plainvga, vga, ega, mda, mga, cga $_console = (0) # use 'console' video $_graphics = (1) # use the cards BIOS to set graphics $_videoportaccess = (1) # allow videoportaccess when 'graphics' enabled $_vbios_seg = (0xc000) # set the address of your VBIOS (e.g. 0xe000) $_vbios_size = (0x10000)# set the size of your BIOS (e.g. 0x8000) $_vmemsize = (1024) # size of regen buffer $_chipset = "" # one of: plainvga, trident, et4000, diamond, avance # cirrus, matrox, wdvga, paradise Can anyone give me any help with this? Thanks in advance, Gabriel Ycas ------------------------------ From: Marijn van Galen <[EMAIL PROTECTED]> Date: Wed, 19 Apr 2000 10:38:06 +0200 (METDST) Subject: Re: DOSEMU with power management on laptops I can only say it hangs on my laptop after having been in suspend mode, maybe it is that one way or the other, the dosemu session looses the keyboard focus. But I'm not sure, it is just that when coming out of suspend, there is no cursor on the screen... Marijn van Galen On Sun, 16 Apr 2000, Jonathan Edwards wrote: > I would appreciate hearing from anyone who's using DOSEMU on a laptop > and who does not have any trouble with DOSEMU sessions hanging upon > resumption from a suspend or hibernate. > > Jonathan Edwards > ------------------------------ From: "Will Ross" <[EMAIL PROTECTED]> Date: Wed, 19 Apr 2000 15:55:33 -0500 Subject: dosemu This is a multi-part message in MIME format. - ------=_NextPart_000_001A_01BFAA17.B2112120 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I have RedHat 3.3.2 installed. I have downloaded XFre86 3.3.6 from UMin = into my C:/windows/temp dir. (18 files ) . I have a /dosc partition on = my F: drive, where the rest of the linux os is loaded. My program has = dosemu.conf and /dosc.user on it. I want to transfer the loaded files = from C:\ to F: /dosc with dosemu. But when I try to load dosemu, I get = the following: ERROR : gettype : no disc129 genl protection of 0X90414 :f ERROR : SIGSEGV protected insn....exiting The downloaded files are in C:/windows/temp. Can you give me any help?? = Will Ross - ------=_NextPart_000_001A_01BFAA17.B2112120 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META content=3D"text/html; charset=3Diso-8859-1" = http-equiv=3DContent-Type> <META content=3D"MSHTML 5.00.2614.3500" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=3D#ffffff> <DIV><FONT color=3D#000000 face=3DArial>I have RedHat 3.3.2 installed. I = have=20 downloaded XFre86 3.3.6 from UMin into my C:/windows/temp dir. (18 files = ) . I=20 have a /dosc partition on my F: drive, where the rest of the linux os is = loaded.=20 My program has dosemu.conf and /dosc.user on it. I want to transfer the = loaded=20 files from C:\ to F: /dosc with dosemu. But when I try to load dosemu, I = get the=20 following:</FONT></DIV> <DIV><FONT color=3D#000000 face=3DArial>ERROR : gettype : no = disc129</FONT></DIV> <DIV><FONT color=3D#000000 face=3DArial>genl protection of 0X90414 = :f</FONT></DIV> <DIV><FONT color=3D#000000 face=3DArial>ERROR : SIGSEGV protected=20 insn....exiting</FONT></DIV> <DIV><FONT color=3D#000000 face=3DArial>The downloaded files are in = C:/windows/temp.=20 Can you give me any help?? Will=20 Ross</FONT></DIV></BODY></HTML> - ------=_NextPart_000_001A_01BFAA17.B2112120-- ------------------------------ From: [EMAIL PROTECTED] (Eric W. Biederman) Date: 20 Apr 2000 00:32:15 -0500 Subject: Re: dosemu "Will Ross" <[EMAIL PROTECTED]> writes: > I have RedHat 3.3.2 installed. I have downloaded XFre86 3.3.6 from UMin into my > C:/windows/temp dir. (18 files ) . I have a /dosc partition on my F: drive, > where the rest of the linux os is loaded. My program has dosemu.conf and > /dosc.user on it. I want to transfer the loaded files from C:\ to F: /dosc with > dosemu. But when I try to load dosemu, I get the following: > > ERROR : gettype : no disc129 > genl protection of 0X90414 :f > ERROR : SIGSEGV protected insn....exiting > The downloaded files are in C:/windows/temp. Can you give me any help?? Will > Ross 1) We would at least need your dosemu.conf to debug this. 2) dosemu is not the right tool for this job. Linux has a perfectly good command line, you don't need to go into the inferior dos command line to do this... 3) The right way to do this is to just mount your fat filesystems under linux and run a cp command. Put something like: /dev/hda1 /C msdos defaults 0 0 into the file. /etc/fstab Where /dev/hda1 is substituted with the correct partitions/drives of your C drive. Then mkdir /C to creat the C directory then: mount /C And cp /C/windows/temp/* /dosc or whatever is appropriate. Eric ------------------------------ From: [EMAIL PROTECTED] Date: Sat, 22 Apr 2000 05:54:26 EDT Subject: (no subject) ------------------------------ From: David Jarvie <[EMAIL PROTECTED]> Date: Sun, 23 Apr 2000 21:59:51 +0100 Subject: Dosemu 1.0.0.0 mouse bug When I run dosemu 1.0.0.0 under Linux, using the command 'dos', the mouse stops working properly (in all windows) after I move the cursor between windows a few times. There is no problem provided I keep the cursor within the dos window. When it goes wrong, the symptoms are the same as when I set up the wrong mouse type in XF86Config. The mouse goes back to normal once I kill the window which dosemu is running in. I have a Logitech MouseMan Plus PS/2 mouse, with the following settings in /etc/dosemu.conf : $_mouse = "ps2" $_mouse_dev = "/dev/mouse" $_mouse_flags = "" Note that /dev/mouse is a link to /dev/psaux. My XF86Config defines the mouse as type imps/2. I tried using the command 'dos -m' but this didn't make any difference. There is no problem when I run dosemu using the command 'xdos'. I am running dosemu using a bootdir configuration, with links to DOS files in a Windows 98 system on another partition. I hope this is enough information to point you in the right direction - if you need any more, please let me know. Regards, David Jarvie. ------------------------------ From: David Jarvie <[EMAIL PROTECTED]> Date: Sun, 23 Apr 2000 22:01:37 +0100 Subject: Dosemu 1.0.0.0 mouse bug When I run dosemu 1.0.0.0 under Linux, using the command 'dos', the mouse stops working properly (in all windows) after I move the cursor between windows a few times. There is no problem provided I keep the cursor within the dos window. When it goes wrong, the symptoms are the same as when I set up the wrong mouse type in XF86Config. The mouse goes back to normal once I kill the window which dosemu is running in. I have a Logitech MouseMan Plus PS/2 mouse, with the following settings in /etc/dosemu.conf : $_mouse = "ps2" $_mouse_dev = "/dev/mouse" $_mouse_flags = "" Note that /dev/mouse is a link to /dev/psaux. My XF86Config defines the mouse as type imps/2. I tried using the command 'dos -m' but this didn't make any difference. There is no problem when I run dosemu using the command 'xdos'. I am running dosemu using a bootdir configuration, with links to DOS files in a Windows 98 system on another partition. I hope this is enough information to point you in the right direction - if you need any more, please let me know. Regards, David Jarvie. ------------------------------ From: [EMAIL PROTECTED] (Eric W. Biederman) Date: 23 Apr 2000 17:02:32 -0500 Subject: ANNOUNCE: dosemu-1.0.0.eb1.21.patchset.tar.gz An updated patchset of my ongoing work rewriting the keyboard code & various other internationalization type tweaks, is now avaiable at: http://www.dosemu.org/~eric/ http://www.users.uswest.net/~ebiederman/files/ as: dosemu-1.0.0.eb1.21.patchset.tar.gz The most common problem I have heard seems to be related to $_term_char_set not allowing people to specify which character sets they actually have configured. This release should make correct maches possible. On the todo is to figure out how to get all of this tuning right automagically but reading LC_CTYPE or other locale dependent things. Anyone have any pointers? Changes since dosemu-1.0.0.eb1.20 (a) Documentation updates (b) Added new options: $_internal_char_set & $_external_char_set that allows people with weird configurations to specify exactly what characters sets they are running instead of messing around with $_term_char_set and hoping it works... (c) Tweaked the debugging code. Now if you have a problem as well as describing the problem to me and what is not working. Please send the dos.out file from a short test run with -D+kv -o dos.out added to the command line. At last test yes. This did properly handle umlauts and other accented characters via telnet. Changes since dosemu-1.0.0.eb1.19 (a) When pasting it might I no longer attempt to use dead keys I don't have. (b) do_patch in the patch script now correctly applies patches 18 & 19 & 20 do_patch from 1.19 would only patch you to eb1.17 oops. This would certainly keep accented characters from working. (c) The announce now spells uswest correctly. (d) I now actually list the files on dosemu.org oops. Eric ------------------------------ From: <[EMAIL PROTECTED]> Date: Tue, 25 Apr 2000 18:25:46 -0400 EDT Subject: WEB DATABASES/LISTS - 30% TO 50% OFF - 10 DAYS ONLY--Adv. Good day, We wanted to share with you the latest 30%-50% OFF, 10 DAYS ONLY PRICING SPECIALS on our database of online businesses--a cutting edge business tool for the growing networked marketplace. Our databases include contacts representing millions of online business domains which have sprung into the age of the global Internet. They are compatible with Microsoft Office, Access and all database and contact management products because they are provided in comma delimited text. These searchable databases include the standard "white pages" information like company name, address, phone number, and fax number, but we have added additional fields including first and last names of the contacts, e-mail addresses and Domain names. In some editions, an additional 4 fields of business/Web information are available. January 2000 CD-ROM databases include: Company Name Address City State or Province Postal Code Country Prefix (Dr., Mr., Mrs., etc.) First Name Middle Name Last Name Suffix (Jr., II, III, IV, etc.) Phone Extension Fax E-mail Address Web Address (Domain name) ------------------------- Expanded Editions add the following fields (web info): Web Title (title of web page) META Description (description of website) META Keywords (keywords pertinent to website) BODY (first 255 characters of default web page, e.g. index.htm, index.htm, default.htm) Available data includes: **** 8.8 Million Domain Records--MASTER DATABASE on 3 CD-ROM set **** 8,841,086 Domain Records Worldwide .COM, .NET, .ORG, .EDU CALL FOR DETAILS **** 50% OFF **** US and Canadian Domain Contacts **** 50% OFF **** 1,450,397 records: WAS $2995.00 - NOW $1497.50 US AND CANADA .COM & .NET *NEW* IT Workers-reach up to 200,000 IT (Information Technology) workers. 201,603 records: WAS $1995.00 - NOW $997.50 US AND CANADA .COM & .NET 50% OFF!!! **** 30% OFF **** CANADA and METRO EDITIONS **** 30% OFF **** Canada 95,158 records: WAS $899.95 - NOW $629.97 New York City Metro Area 91,419 records: WAS $899.95 - NOW $629.97 Los Angeles Metro Area 146,571 records: WAS $1199.95 - NOW $839.97 San Francisco Bay Metro Area 01,062 records: WAS $899.95 - NOW $629.97 Washington D.C. Metro Area 59,789 records: WAS $749.95 - NOW $524.97 Boston Metro Area 46,446 records: WAS $649.95 - NOW $454.97 ADD 33% for additional 4 fields of Web info: **** 50% OFF **** Domain Name Master List **** 50% OFF **** Over 10 million .COM, .NET, .ORG & .EDU domains and growing! Was $1995.00 - Now $997.50 ALL DISCOUNTS EXPIRE APRIL 30TH, 2000. All prices are in US Dollars. ALL MAJOR CREDIT CARDS ACCEPTED. Please call or fax toll-free at 888-922-5967. This is a one time announcement. However, if you feel you need to, you can remove via e-mail by replying to this message with REMOVE in the subject or leave a remove by phone or fax at 888-922-5967. Regards, John Powers EVA, Inc. ------------------------------ From: MaxAttack <[EMAIL PROTECTED]> Date: Mon, 24 Apr 2000 15:49:35 +1000 Subject: Problem with dosemu - --------------1689E4D7E1FEC433E068797D Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Ok i have read the faq readme etc etc on dosemu and i hear dosemu is used mainly with freedos i have freedos mini installed to hardrive i want to use freedos to play some of my classic games for dos that i still love. Anyway i have all the files ina folder and the mini.bin , but when i set dosemu to boot the mini.bin it just prints mini to screen i see information on copying the msdos.sys and io,sys over i used that and worked but due to lack of svga features and i dont have a copy of dos that isnt convenient for me i looked over at freeodos aswell for information on running freedos with dosemu and couldnt find any Could u possably help me in finding information on running freedos with dosemu Or tell me how to do so Thanks in advance. - -- "Data itself isn't good nor bad, data just represents the surrounding reality. The more data we may access, the more accurate model we may create of the reality, thereby also define our actions in ways that are maximally beneficial to our aims. The net must not be restricted by moral, ethical nor legal issues prevailing in different world locations, data must flow freely." -- chip. - --------------1689E4D7E1FEC433E068797D Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit <!doctype html public "-//w3c//dtd html 4.0 transitional//en"> <html> Ok i have read the faq readme etc etc on dosemu and i hear dosemu is used mainly with freedos <br>i have freedos mini installed to hardrive i want to use freedos to play some of my classic games for dos that i still love. Anyway i have all the files ina folder and the mini.bin , but when i set dosemu to boot the mini.bin <br>it just prints mini to screen i see information on copying the msdos.sys and io,sys over i used that and worked but due to lack of svga features and i dont have a copy of dos that isnt convenient for me i looked over at freeodos aswell for information on running freedos with dosemu and couldnt find any <br>Could u possably help me in finding information on running freedos with dosemu <br>Or tell me how to do so <br>Thanks in advance. <pre>-- "Data itself isn't good nor bad, data just represents the surrounding reality. The more data we may access, the more accurate model we may create of the reality, thereby also define our actions in ways that are maximally beneficial to our aims. The net must not be restricted by moral, ethical nor legal issues prevailing in different world locations, data must flow freely." -- chip.</pre> </html> - --------------1689E4D7E1FEC433E068797D-- ------------------------------ From: [EMAIL PROTECTED] (Robert D. Hilliard) Date: Mon, 24 Apr 2000 16:01:02 -0400 (EDT) Subject: EMUfailure.txt The file EMUfailure.txt, May 30, 1997 for dosemu 0.66.5, says that programs using Virtual Control Program Interface (VCPI) have a fundamental problem, and probably won't ever work under DOS Emu. Since that was written almost three years ago, and dosemu 1.0.0 is now available, I wonder if that is still true? Bob - -- _ |_) _ |_ Robert D. Hilliard <[EMAIL PROTECTED]> |_) (_) |_) 1294 S.W. Seagull Way <[EMAIL PROTECTED]> Palm City, FL USA PGP Key ID: A8E40EB9 ------------------------------ From: [EMAIL PROTECTED] (Eric W. Biederman) Date: 24 Apr 2000 22:22:05 -0500 Subject: Re: EMUfailure.txt [EMAIL PROTECTED] (Robert D. Hilliard) writes: > The file EMUfailure.txt, May 30, 1997 for dosemu 0.66.5, says > that programs using Virtual Control Program Interface (VCPI) have a > fundamental problem, and probably won't ever work under DOS Emu. > > Since that was written almost three years ago, and dosemu 1.0.0 > is now available, I wonder if that is still true? When it's not true we will announce windows & linux running in dosemu. Eric ------------------------------ From: Isamar Maia <[EMAIL PROTECTED]> Date: Tue, 25 Apr 2000 15:39:16 -0300 (EST) Subject: Show ANSI characters.... I'm having a slow display of ANSI characters. It's worse when I use X. What can I do to make it better ? Atenciosamente, Isamar Maia Bitnet Conectividade Ilheus/Itabuna - BA ------------------------------ From: [EMAIL PROTECTED] Date: Wed, 26 Apr 2000 16:35:43 +0800 Subject: How do I use two different hdimage files? Dear Sirs: I am at my wits' end. I have two different hdimage files for different purposes, but it seems that nothing I do let me use another hdimage file than the one written in /etc/dosemu.conf dos -[fF] does not work (at least with non-root users) neither does anything else that I try. I read the man pages and the HOWTO files several times. What did I miss? HELP! Less important but still hurting -- how do I pass a ctrl-break into dosemu? I start up xdos -C, and when I run qbasic into a loop without exit condition, neither control-break nor ctrl-C cures it. No, -k did not work. Is it just me? Hexed in Taipei ------------------------------ From: [EMAIL PROTECTED] Date: Wed, 26 Apr 2000 12:57:34 +0200 Subject: ROM Extension Hi, I've got a plug-in card which has a real-mode ROM on it. How can I make this ROM visible in a dosemu session? regards, chris ------------------------------ From: Clive Nicolson <[EMAIL PROTECTED]> Date: Wed, 26 Apr 2000 23:09:35 +1200 NZST Subject: Embedded 8088 emulation, disemu config for? I would like to run some 8088 code I have (from an embedded system) under dosemu. Is it possible to configure dosemu to do this. I have some details of the h/w config of the 8088 system that the code is for, ie 3 8251A UARTS, a 8259 PICU and a number of simple port mapped io devices. Clive ------------------------------ From: Alistair MacDonald <[EMAIL PROTECTED]> Date: Wed, 26 Apr 2000 12:12:02 +0100 (BST) Subject: Re: Problem with dosemu On Mon, 24 Apr 2000, MaxAttack wrote: > Ok i have read the faq readme etc etc on dosemu and i hear dosemu is > used mainly with freedos Mainly because we couldn't distribute a bootable disk image otherwise. [...] > Could u possably help me in finding information on running freedos with > dosemu Well, I've just seen a posting on the FreeDOS list about an entry in their Install HOWTO explaining this: http://www.freedos.org/fd-doc/howto-install.html#doc3-2 (I think they've probably missed something here -- it should be possible to make the 'mini.img' a 'vbootfloppy', rather than copying it to a real floppy.) ------------------------------ From: Alistair MacDonald <[EMAIL PROTECTED]> Date: Wed, 26 Apr 2000 12:23:56 +0100 (BST) Subject: Re: ROM Extension On Wed, 26 Apr 2000 [EMAIL PROTECTED] wrote: > I've got a plug-in card which has a real-mode ROM on it. > How can I make this ROM visible in a dosemu session? You want the 'hardware_ram' option (Section 2 of the Technical Readme: http://www.dosemu.org/docs/README-tech/0.98/README-tech-2.html ) Alistair ------------------------------ From: [EMAIL PROTECTED] Date: Wed, 26 Apr 2000 19:10:44 +0200 Subject: Re: ROM Extension Thanks, I will check it out. regards, chris On 04/26/2000 11:23:56 AM GMT Alistair MacDonald wrote: > >On Wed, 26 Apr 2000 [EMAIL PROTECTED] wrote: >> I've got a plug-in card which has a real-mode ROM on it. >> How can I make this ROM visible in a dosemu session? > >You want the 'hardware_ram' option (Section 2 of the Technical Readme: >http://www.dosemu.org/docs/README-tech/0.98/README-tech-2.html ) > >Alistair > ------------------------------ From: "Dave Taggart" <[EMAIL PROTECTED]> Date: Wed, 26 Apr 2000 17:44:25 -0500 Subject: memory limitations Hi, I am just learning about my Linux and dosemu capabilities so forgive any naive questions please. I am trying to execute a DOS app in dos emu and it says "Insufficient memory". My machine has 151MG of RAM so I am sure there is some .conf setting or something I am missing in the config.sys file. Can you help? Thanks David Taggart Sakima Group [EMAIL PROTECTED] ------------------------------ From: Furball / Philipp Kaeser <[EMAIL PROTECTED]> Date: Thu, 27 Apr 2000 21:57:54 +0000 Subject: Re: memory limitations hej, > I am just learning about my Linux and dosemu capabilities so forgive any > naive questions please. I am trying to execute a DOS app in dos emu and it > says "Insufficient memory". My machine has 151MG of RAM so I am sure there > is some .conf setting or something I am missing in the config.sys file. Can > you help? this is most possibly not a problem of dosemu but of your DOS configuration within the emulator. most probably, you have loaded too many drivers or TSR programs, and they filled the base memory of which the program requires too much to get loaded. at the DOS prompt, try the command "mem /d" to collect statistics about memory usage of DOS and diverse driver programs. on how to optimize memory usage, see the DOS help (assuming you're using a MS version) to the "dos=high,umb" directive (config.sys), "himem.sys", "emm386.exe", "devicehigh=..." and "loadhigh". some DOS programs require base memory of 550K or sometimes even up to 610K. optimizing your configuration properly should allow you easily to have about 580K of free base memory. hope you're having success, bye Philipp Kaeser / [EMAIL PROTECTED] ------------------------------ From: pozyton <[EMAIL PROTECTED]> Date: Fri, 28 Apr 2000 18:38:30 +0200 Subject: ipx + foxpro if i turn ipx ON in dosemu.conf and try to run some program written with foxpro, dosemu crushes in few minutes - I can see many numbers and shell prompt. There is no problem with this program when I turn ipx_support OFF. It happens with dosemu 0.99; 1.0.0 and RH6.0; mandrake 6,1; debian 2.1 I need run this program in net enviroment so ipx_suppor is very important help please ------------------------------ From: [EMAIL PROTECTED] Date: Fri, 28 Apr 2000 22:17:06 MET_DST Subject: RE: How do I use two different hdimage files? >Date: Wed, 26 Apr 2000 16:35:43 +0800 >Message-ID: <[EMAIL PROTECTED]> >From: [EMAIL PROTECTED] > I am at my wits' end. I have two different hdimage files for > different purposes, but it seems that nothing I do let me use > another hdimage file than the one written in /etc/dosemu.conf > dos -[fF] does not work (at least with non-root users) neither > does anything else that I try. I read the man pages and the Replace the "hdimage.first" in dosemu.conf by $HDIMAGE, and use export HDIMAGE=filename (in /var/lib/dosemu directory) before dos. Also, consider using boot directory (in same way as image, except: use directory name; put file named boot.blk in it containing boot sector of a diskette; put there file like io.sys, msdos.sys,...) > Less important but still hurting -- how do I pass a ctrl-break Seems simple Ctrl-C should work. At least from terminal it works. ------------------------------ From: Philipp <[EMAIL PROTECTED]> Date: Sun, 30 Apr 2000 14:45:57 +0200 Subject: graphics mode Hi! I have installed DosEmu 1.0.0.0 DosEmu is starting well but only when I set the direct graphics access off $_graphics=(off) When turn the option on my DosEmu hangs and I automatically return to Linux Does anybody know a solution? ------------------------------ End of linux-msdos-digest V1 #172 ********************************* To subscribe to linux-msdos-digest, send the command:
