New
#11
Actually it's not their fault even though it's annoying.
Until you get the actual released OS you can't really spend a lot of time and resources designing a process that might not even exist in the final released version.
A program running a Virtual Machine is extremely complex to write as it has to integrate completely with the running kernels of BOTH the HOST and GUEST OS.
A lot of programs that simply don't use a lot of "Internal Core" windows features will run essentially unchanged even on a BETA OS - for example even large programs like OFFICE will give few if any problems. Most of the "base top layer" of Windows won't have changed much if the programs "Obey the rules and use basic WINDOWS API's.
Things like the .NET interface has changed so programs using the older versions will be a problem for a while.
Also once you start interacting with the actual hardware then it gets more difficult as this stuff DOES change from release to release. This is why things like TV tuner applications, complex Video applications, and Vitrtual Machine software tend to be the hardest applications to upgrade to the new OS.
You can see from the amount of Build leaks etc et we've already had since the beta that you cant expect Microsoft to dish out fully working Windows source code to everybody -- how long before you'd see it on"The Bay" (Is there Swedish Jail Network server - judging by the comfortable conditions in most Scandanavian Prisons the'd probably get a BETTER server funded by the taxpayer ).
We'll just have to live with it -- and maybe you can find some way of getting round the ISP 1 IP address restriction you have in the dorm -- you might be able to find a way of setting your HOST machine up as a VPN and then logging on to the Internet from your XP VM machine via the host's VPN and sharing that Internet connection.
Just an Idea BTW - I wouldn't know how to do it so you'll have to ask someone else.
Cheers
jimbo
i wish there were a solution for this
or a small fix maybe
when will vmware new version out
does anybody know
because i really need nat working one
i have the same problem only i can ping a webpage from my vmware workstation.
but if I try to open it with IE I get something with connection problems ...
I'm using VMWare Workstation 6.5.2 on Win7 RC x64, and everything works really well. Internet connectivity is fine (Bridged mode for me).
Jim
Agreed, NAT doesn't work for me either.
Strange thing is, connectivity itself seems to be working - I can :
ping news.bbc.co.uk
and the address gets resolved and I get replies. But both IE7 and Google Chrome refuse to establish connectivity to a website.
So, IP connecivity seems to be "partly" working....
Hello everybody,
I was able to connect to the Internet through Bridged Networking and Microsoft Loopback Adapter in a NAT-like fashion.
Hint: From the command prompt, run "hdwwiz.exe". This should launch the "Add Hardware Wizard".
I hope this will be useful to someone.
Regards.
Rafael Lopez.