From: Don Raikes <DON.RAIKES@ORACLE.COM>
To: "Speakup is a screen review system for Linux."
<speakup@linux-speakup.org>
Subject: RE: virtualbox, was: Re: Kali Linux
Date: Fri, 1 May 2015 08:29:01 -0700 (PDT) [thread overview]
Message-ID: <7ed5350e-b5a1-41af-af3a-31025735fd2b@default> (raw)
In-Reply-To: <20150430163054.GA9356@lava-net.com>
Igor et al,
How are you getting virtualbox to work on windows? The last time I tried it (about a year ago) the gui was totally inaccessible with jaws. I would really appreciate knowing how others are getting it to work since my laptop can't handle vmware workstation maybe it will handle virtualbox instead.
-----Original Message-----
From: Igor Gueths [mailto:igueths@lava-net.com]
Sent: Thursday, April 30, 2015 9:31 AM
To: Speakup is a screen review system for Linux.
Subject: Re: virtualbox, was: Re: Kali Linux
Hey Greg, thanks for the tip! I obviously have been neglecting the RTFM time that Virtualbox requires as of late...Will definitely give that a try though.
On Wed, Apr 29, 2015 at 08:52:07PM -0700, Gregory Nowak wrote:
> Capturing/releasing the keyboard is described in I believe section
> 1.8.2 of the virtualbox manual. To capture/release the keyboard, you
> need to use the host key, which is your right control key by default.
> If you're in the guest, press your right control key to release the
> keyboard, and you should then be able to alt+tab to other windows.
> When you focus the virtualbox guest window again, it will capture your
> keyboard automatically, unless you disabled this. If you want to use
> the control key in your guest, use the left control key. So,
> ctrl+alt+f1 in the guest would be done using your left control and alt
> keys. If you're running on a gnu/linux host, then things get different
> as described in section 1.8.3 of the virtualbox manual. If you're
> running on a gnu/linux host, then pressing
> hostkey+f1 would enter ctrl+alt+f1 into the guest and so on.
>
> If this bothers you and you can't get used to it, you can remap the
> host key to something as I mentioned earlier. Alternatively, if you
> have a usb keyboard, and a place to put it, you can pass that keyboard
> through to the guest, and not have to deal with the whole host key
> thing. HTH.
>
> Greg
>
>
> On Wed, Apr 29, 2015 at 09:02:56PM -0400, Igor Gueths wrote:
> > Hey all,
> > thanks for the replies! I test booted my installation while I was at
> > work earlier today, and got what seemed to be a GDM login screen;
> > alt+f2 appeared to have no effect, but this could be due to my
> > having installed it within Virtualbox. Speaking of virtual machines,
> > presuming the installation (s) were done within Virtualbox, how did
> > you fully capture the keyboard so that you could do ctrl+alt+f1 and
> > the like? I ask because I have never gotten this to work reliably.
> > Also is there a kernel difference between the kernel that is used
> > during installation and that which is used in the installed system? Just trying to rule out the possibility of unsupported virtual audio chipsets and the like.
> > Thanks!
>
>
> --
> web site: http://www.gregn.net
> gpg public key: http://www.gregn.net/pubkey.asc
> skype: gregn1
> (authorization required, add me to your contacts list first) If we
> haven't been in touch before, e-mail me before adding me to your contacts.
>
> --
> Free domains: http://www.eu.org/ or mail dns-manager@EU.org
> _______________________________________________
> Speakup mailing list
> Speakup@linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
>
> --
> This message has been scanned for viruses and dangerous content by
> MailScanner, and is believed to be clean.
>
--
Igor
--
This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
_______________________________________________
Speakup mailing list
Speakup@linux-speakup.org
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
Igor Gueths
` Glenn / Lenny
` Don Raikes
` Don Raikes
` Igor Gueths
` Don Raikes
` Doug Smith
` Don Raikes
` Igor Gueths
` virtualbox, was: " Gregory Nowak
` Igor Gueths
` Don Raikes [this message]
` Gregory Nowak
` Don Raikes
` Igor Gueths
` Jason White
` Gregory Nowak
` Jason White
` Gregory Nowak
` Jason White
` John G Heim
` Don Raikes
` John G Heim
` Don Raikes
` Don Raikes
` Igor Gueths
` Igor Gueths
` Don Raikes
` Igor Gueths
` Doug Smith
` Jude DaShiell
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=7ed5350e-b5a1-41af-af3a-31025735fd2b@default \
--to=don.raikes@oracle.com \
--cc=speakup@linux-speakup.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 read-only IMAP folder(s) and NNTP newsgroup(s).