Hi, I had a problem like this when I first started using DOS-EMU.
My CPU would jump to 99% when I opened a DOS session. However it didn't
seem to prevent any of my server processes from operating normally.
Because that was the earlier days of DOS-EMU, there were many other problems
besides this, therefore I can't say for sure what I did to fix it. I
started by lowering the HOG THRESHOLD to 1 and turning off all EMS/XMS. I
disabled ports I didn't need as well.
Setting the HOG THRESHOLD lower probably fixed my problem more than
anything. Setting it to 1 caused my programs to run like they were on a
386, but that was no big deal, they were originally designed to run on a
286.
Hopefully, that will help
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Andreas Moroder
> Sent: Monday, August 27, 2001 8:30 AM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Re: Re: Re: question on dosemu
>
>
> Hello Sreeji,
>
> Stas Sergeev did send me a patch that solve the problem.
> What is not solve is the problem that my clipper application uses
> 99% of cpu
> time.
>
> Bye and thank you very much
>
> Andreas
>
>
>
> Zitiere Sreeji K Das <[EMAIL PROTECTED]>:
>
> > Hi Andreas,
> >
> > Are you loading any drivers in your config.sys ? Can you try running
> > dosemu without parsing config.sys & autoexec.bat ? The error that you
> > reported comes from dpmi.c, while processing int 31 (Call real mode
> > procedure). I do not know the inside gory details (!), but I don't
> > think
> > this is supposed to happen in the normal course.
> >
> > Launch dos and then type F5 (if that doesn't work for u, try Ctrl ^ 5),
> > so
> > that config.sys & autoexec.bat is bypassed. I'm sure dosemu would work
> > properly. Is this problem happening when u run some particular program
> > from dosemu ? There are few programs that cannot be (yet) run from
> > within
> > dosemu.
> >
> > Sreeji
> > On Wed, 22 Aug 2001, Andreas Moroder wrote:
> >
> > > Hello Sreeji,
> > >
> > > i started the debugger and got the following output on the debugger
> > screen
> > >
> > > unable to open map file /usr/src/dosemu/bin/dosemu.map
> > > system state: stopped
> > > AX=0005 BX=0000 CX=0000 DX=0000 SI=0000 DI=0000 SP=00fc
> > BP=0000
> > > DS=0040 ES=0000 FS=0000 GS=0000 FL=0202
> > > CS:IP=f800:2004 SS:SP=0030:00fc
> > >
> > > f800:2004 B280 mov dl,80
> > > log +a
> > > g
> > >
> > > ****
> > > leavedos(99) called, at termination point of DOSEMU
> > > ****
> > >
> > > system state: stopped in DPMI-16bit
> > >
> > > EAX: 00000301 EBX: 0000000a ECX: 00000000 EDX: 000043ff eflags:
> > 00010246
> > > ESI: 0000ad7e EDI: 0000ad0a EBP: 0000ad46 DS: 01f7 ES: 01f7 FS: 0000
> > GS: 0000
> > > CS:EIP= 01d7:00001710 SS:ESP= 01f7:c344ad08
> > >
> > > #01d7:1710 8B66F6 mov sp,[bp-0A]
> > > quit
> > >
> > > the last lines in the debug output file are
> > >
> > > DPMI: calling interrupthandler 0x31 at 0x00a7:0x00003244
> > > DPMI: default protected mode interrupthandler 0x31 called
> > > DPMI: int31, ax=0301 ,ebx=000000e0 ,ecx=00000000 ,edx=000001f7
> > > edi=0000aee0 ,esi=0000af50
> > > DPMI: Interrupt vector overwritten!leavedos(99) called - shutting
> > down
> > >
> > 187678,1
> > >
> > > If necessary I can also send the full logfile.
> > >
> > > Can you tell me what is going wrong ?
> > > Thank you very much.
> > >
> > > Andreas Moroder
> > > Sant�tsbetrieb Brixen - Azienda Sanitaria di Bressanone
> > > -
> > > 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
> > >
> >
> >
> >
>
>
>
> Dr. Andreas Moroder
> Sanit�tsbetrieb Brixen - Azienda Sanitaria di Bressanone
> -
> 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
>
-
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