From: Beso <givemesugarr@gmail.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Virtualization/WinXP
Date: Thu, 28 Jan 2010 00:30:04 +0100 [thread overview]
Message-ID: <d257c3561001271530n19acc30fpe7998fbf14dbb802@mail.gmail.com> (raw)
In-Reply-To: <5bdc1c8b1001271011j477e46e4h4070af06319f4b4f@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1782 bytes --]
2010/1/27 Mark Knecht <markknecht@gmail.com>
> On Wed, Jan 27, 2010 at 9:25 AM, The Doctor <drwho@virtadpt.net> wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Mark Knecht wrote:
> >
> >> The last time I looked at this (maybe a year ago?) I decided that the
> >> vmware-workstation would let a home user run something like two
> >> instances without charges. Not free in that I'm limited to something
> >> specific but no cost. (Is that free beer? It certainly doesn't sound
> >> like Free Speech...)
> >
> > There is also a 60-day time limit on the un-paid-for version of VMware
> > Workstation, as I recall.
> >
> > - --
> >
> > The Doctor [412/724/301/703]
>
> I got VirtualBox up and running with XP but nothing much more
> yesterday as I ran into XP licensing issues again with M$ and sort of
> backed off.
>
> I haven't figured out what's up with vmware-player networking yet. I
> can get to the web in a browser just fine, do updates through M$
> Update, do GMail. It looks perfect. However WinSCP running in
> vmware-player isn't yet finding other machines on my network. IIRC
> there were different models of networking you could set up. I have to
> go back and relearn that stuff but it's not critical to me until I
> determine if the new machine is really fast enough to run TradeStation
> and, very importantly, if the networking is stable enough and
> transparent enough to allow me to connect to their network for real
> futures trading. That will force me to dig in if it isn't OK right
> now.
>
are you sure that it isn't your routing tables that aren't ok? try
tracerouting the ip you're trying to access and see if you can reach it.
if you cannot you'd have to add the correct routing entries in windows
routing tables.
--
dott. ing. beso
[-- Attachment #2: Type: text/html, Size: 2346 bytes --]
next prev parent reply other threads:[~2010-01-28 0:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-26 19:55 [gentoo-amd64] Virtualization/WinXP Mark Knecht
2010-01-26 20:52 ` [gentoo-amd64] Virtualization/WinXP Nikos Chantziaras
2010-01-26 21:47 ` [gentoo-amd64] Virtualization/WinXP Marko Obrovac
2010-01-27 0:11 ` Mark Knecht
2010-01-27 0:23 ` Mark Knecht
2010-01-27 9:01 ` Sebastian Beßler
2010-01-27 9:55 ` Marc Joliet
2010-01-27 13:02 ` Mark Knecht
2010-01-27 14:41 ` Beso
2010-01-27 17:25 ` The Doctor
2010-01-27 18:11 ` Mark Knecht
2010-01-27 23:30 ` Beso [this message]
2010-01-28 15:05 ` Mark Knecht
2010-01-27 1:23 ` Lie Ryan
2010-01-27 2:33 ` Mark Knecht
2010-01-26 22:01 ` Paul Hartman
2010-01-27 16:43 ` The Doctor
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=d257c3561001271530n19acc30fpe7998fbf14dbb802@mail.gmail.com \
--to=givemesugarr@gmail.com \
--cc=gentoo-amd64@lists.gentoo.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