From: "Sina Bahram" <sbahram@nc.rr.com>
To: "'Speakup is a screen review system for Linux.'"
<speakup@braille.uwo.ca>
Subject: RE: linux, windows and vmware
Date: Wed, 11 Apr 2007 11:45:12 -0400 [thread overview]
Message-ID: <004001c77c50$64bc7a10$ca01a8c0@quark> (raw)
In-Reply-To: <20070411145540.GB55783@fajrero>
We have several blades running various operating systems in VMWare and
windows as the host OS, that have been up for months now.
Think about it ... If one isn't interacting with it much, then there's
really nothing for windows to crash or get hung up on ... It's running six
to eight VMWare images.
Take care,
Sina
-----Original Message-----
From: speakup-bounces@braille.uwo.ca [mailto:speakup-bounces@braille.uwo.ca]
On Behalf Of Tyler Spivey
Sent: Wednesday, April 11, 2007 10:56 AM
To: Speakup is a screen review system for Linux.
Subject: Re: linux, windows and vmware
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Vmware with windows as the host works rather well. Serial ports just work,
since speakup isn't taking them as under linux. The disadvantage is that
windows is very unstable, to the point of needing to be rebooted every
cupple of days.
If you run vmware under linux and emulate windows, the windows at least for
me was sort of slow. Also, sharing between the two operating systems will be
an issue - either way. Samba can help with that, or windows file sharing on
the windows side.
- - Tyler
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (FreeBSD)
iD8DBQFGHPbrTsjaYASMWKQRAkkUAJ9RD5tcLtzuvZWJ1h0ueLaoD+gtaQCePMgZ
wY43UECWrvrN7gjYI/t4eyE=
=dnZt
-----END PGP SIGNATURE-----
_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
l84ad8r
` Tyler Spivey
` Sina Bahram [this message]
` Zachary Kline
` Alex Snow
` Zachary Kline
` Re[2]: " Farhan
` Tyler Spivey
` Alex Snow
` Doug Sutherland
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='004001c77c50$64bc7a10$ca01a8c0@quark' \
--to=sbahram@nc.rr.com \
--cc=speakup@braille.uwo.ca \
/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).