Re: Dosemu Slower than CMD

Eddy Setyawan
2008-03-16T02:22:27Z

Dear All,

Hello Mr. Bambang, your guess I am from Indonesia is correct :)
perhaps you recognized from my email address or my bad english :p
anyway i can't change for hogthreshold option, it will eat more cpu
resource and i will run more than one session dos in one computer, so
i think it will eat all CPU

Hello Mr. Reinhard, My machine is 64bit but i'm run Fedora 8 using 386
arch. I can't use KVM either i need to run clipper app in many session
not only one so sharing disk is imposible except using network drive.

I found information about samba mounting in dosemu is this can
increase disk access performance?

regards,
Eddy Setyawan

On 3/16/08, Reinhard Karcher <rkarcher@frey.de> wrote:
> Eddy Setyawan schrieb:
>
> > i try to run application made using clipper when run in w*nd*ws cmd
> > command, and do some process it is a little bit slower user can feel
> > it have a delay but not more that 1 secs, but when i run it in dosemu,
> > it take more than 5 secs i don't know where this problem cause,
> > because the application is made by other person
> >
>
> > NB:
> > w*nd*ws is run on Pentium 3 733 machine
> > dosemu (v. 1.4.0) is run on Linux Fedora 8 on AMD 64 3000+ machine
> >
>
>
> You probably run a 64-bit linux. In 64-bit mode, the processor can't run
> realmode or
> 16-bit dpmi applications, so dosemu has to emulate the binary programcode.
> If you have got an diskimage with an window on it, you could run that
> image in kvm.
> On my machine, clipper code with many accesses to disk is much faster
> when run with kvm
> than in dosemu.
> The other option would by to run a 32-bit linux, perhaps from a life cd.
>
> Reinhard
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>