From: "Jim C. Brown" <jma5@umd.edu>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] hardware emularion
Date: Fri, 30 Sep 2005 18:03:29 -0400 [thread overview]
Message-ID: <20050930220329.GB20094@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <433D89F8.7020800@jax-trans.com>
On Fri, Sep 30, 2005 at 02:54:48PM -0400, Matt Young wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> When I boot the install cd in
> qemu it probes the printer parallel port for a hardware plug that has the OS key
> on it.
> some reason, even tho I have the plug inserted in the parrallel port, the
> install program does not "See" the hardware key. How do I fix this? Is there a
> way to get qemu to see the plug on the parallel port?
I don't remember if host parallel port access is possible thru a patch or not.
Normal qemu doesn't support this, so it won't work.
> If not there is a USB
> version of the hardware key, would that work better?
No. Qemu's support for USB is not as good.
> - --
> Cheers,
> Matt Young
> Senior Developer /
> Network Administrator
> IT Services/Development
> Jax Trans Services, Inc.
> matty@jax-trans.com
> http://www.jax-trans.com
> GPG Key: http://www.jaxtrans.com/gpgkey.pub
> Toll Free: (888) 844-1288
> Local: (904) 725-5600
> Fax: (904) 725-5030
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2 (MingW32)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
>
> iD8DBQFDPYn4psu98AAEk+8RAltqAJ4lCIhLcxpugtBxbWrlEGbCoW/uXQCcD+2i
> jR3Gkio4U+EKkmbUhPjt4Hw=
> =dvTq
> -----END PGP SIGNATURE-----
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>
--
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.
prev parent reply other threads:[~2005-09-30 22:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-30 18:54 [Qemu-devel] hardware emularion Matt Young
2005-09-30 22:03 ` Jim C. Brown [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050930220329.GB20094@jbrown.mylinuxbox.org \
--to=jma5@umd.edu \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).