I'm not sure what DOS you're using, but MS-DOS 5.0 and up include
AccessDOS, which slows down things for people with disabilities. One
of them lowers the keyboard rate, making you wait longer for a key
press to be registered. Perhaps you should try using this.
--
Mike
__
On Wed, Jul 06, 2005 at 10:05:51PM -0400, Jim C. Brown wrote:
> I know this. Actually that page seems out of date, as Linux's tuntap now sends
> all accesses to /dev/net/tun regardless of the type of device (tun or tap).
>
I should also add that on Linux, you can set the device name to what you w
On Thu, Jul 07, 2005 at 03:55:30AM +0200, Herbert Poetzl wrote:
> 1.1 What is the TUN ?
> The TUN is Virtual Point-to-Point network device.
> TUN driver was designed as low level kernel support for
> IP tunneling. It provides to userland application
> two interfaces:
>- /dev/tunX - characte
On 7/7/05, Jim C. Brown <[EMAIL PROTECTED]> wrote:
> This is quite clever. I don't see the sources for fsimage (the host program)
> anywhere though - it would be a lot more useful if one could tinker with both
> the host and the guest sides. This can be made to cover everything except
> resizing qc
On Wed, Jul 06, 2005 at 07:08:42PM -0400, Jim C. Brown wrote:
> When in tuntap mode, qemu creates a tap device with names like tun0, tun1,
> etc. which seems to confuse some users (the smart ones who ask why qemu uses
> IP frames instead of ethernet frames ... or something along those lines).
> The
Hi!
I have problems with keyboard on DOS as guest os on linux. When I press some
keys (in most cases those with 2 bytes scan codes like arrows) they are
interpreted twice :( So when I move a cursor in Dos Navigator (for example)
it jump 2 files down/up instead of one. Problem dosn't exists if g
On Wed, Jul 06, 2005 at 10:09:50AM +0900, Magnus Damm wrote:
> One solution for that problem would be to access the images through
> qemu. My little tool fsimage does that for you, but no bootloader is
> included for now. If there is enough interest then I would be happy to
> add new features such
When in tuntap mode, qemu creates a tap device with names like tun0, tun1,
etc. which seems to confuse some users (the smart ones who ask why qemu uses
IP frames instead of ethernet frames ... or something along those lines).
Theses should be named tap0, tap1, etc. This patch fixes qemu.
I don't t
Tilman Sauerbeck <[EMAIL PROTECTED]> [2005-06-30 20:37]:
> Next, I tried to install a real Linux distro (CRUX PPC,
> cruxppc.sunsite.dk):
>
> I created a disk image (crux-ppc-2.0.img) and started qemu like this:
>
> qemu-system-ppc -M prep -kernel zImage.prep -cdrom crux-ppc-2.0.iso
> -boot d -hd
You haven't specified:
* which OS do you use and version
* Which compiler, and what compiler version
Also, for what target do u look for? if X86 only, then you don't need
to compile all the targets. Use ./configure --help
to see the options.
Thanks,
Hetz
On 7/6/05, 황윤성 <[EMAIL PROTECTED]> wrote
make[1]: Entering directory `/home/hys545/qemu/mips-softmmu'
gcc -Wall -O2 -g -fno-strict-aliasing -fomit-frame-pointer -I. -I/home/hys545/qemu/target-mips -I/home/hys545/qemu -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -I/home/hys545/qemu/fpu -I/home/hys545/qemu/slirp -c -o op_help
11 matches
Mail list logo
