tag:blogger.com,1999:blog-26049584.post4457810744040765869..comments2009-01-18T12:26:43.015-05:00Charles Robinsonhttp://www.blogger.com/profile/04606895130887441753noreply@blogger.comBlogger16125tag:blogger.com,1999:blog-26049584.post-39120834885097835952009-01-18T12:26:00.000-05:002009-01-18T12:26:00.000-05:00Solved my nic card problem after uninstalling vmware and reinstalling after rebooting with the F8 option mention above. Apparently it had been unable to load the network driver on installation. It's working now.ericnycnoreply@blogger.comtag:blogger.com,1999:blog-26049584.post-81373657910050137332009-01-17T14:37:00.000-05:002009-01-17T14:37:00.000-05:00I have a similar configuration and tried all the hacks given above. I got past the code signing problem though, yes, I still have to do the f8 runaround every time I reboot. My problem now is that vmware does not seem to recognize the nic card. It is a realtek RTL8168(P)/8111c(p). I will probably try putting in another nic to see what happens. The automatic bridging box is greyed out and no nics appear in any box where you chose the physical nic. Any thoughts are welcome. I would agree that running this on vista is silly. This is a multi use home box and I'd rather leave it that way for now.EricNYCnoreply@blogger.comtag:blogger.com,1999:blog-26049584.post-9582990016864052282009-01-07T00:37:00.000-05:002009-01-07T00:37:00.000-05:00Thanks for sharing this.<BR/><BR/>I did not press F8 before install, I only set <BR/>bcdedit -set loadoptions DDISABLE_INTEGRITY_CHECKS<BR/>not the other one. And reboot the windows. I did not change anything regarding the network. Then I installed the vmware server 1.0.8 on vista Ultimate. Meanwhile, I do need to press F8 in order to make it work every time I reboot the vista.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-26049584.post-4451852377413064762008-10-20T14:03:00.000-04:002008-10-20T14:03:00.000-04:00According to the documentation I read, Vista Home demands signed drivers regardless of whether it is 32-bit or 64-bit. Vista Ultimate and Business may be a different story, I haven't touched either of them so I can't comment. And the BIOS in this garbage PC doesn't have settings to enable virtualization extensions or I would have done that first. :-)<BR/><BR/>There are probably solutions to my other points of pain, and I don't mean to be crass or unappreciative, but I really have no intention of ever using Vista so it doesn't matter to me. Thanks for sharing, though, maybe someone else will find it helpful.Charles Robinsonhttp://www.blogger.com/profile/04606895130887441753noreply@blogger.comtag:blogger.com,1999:blog-26049584.post-6157199566867426022008-10-17T02:04:00.000-04:002008-10-17T02:04:00.000-04:00It is Vista/64-bit version demands signed, not Vista/32-bit.<BR/><BR/>I run VMware Server on Vista/64-bit as well as Vista/32-bit without making those network modifications. Not sure how you arrived in that conclusion.<BR/><BR/>Check your BIOS settings to enable/disable Virtualization options. I am running 64-bit guests on my Vista/32-bit host.<BR/><BR/>Windows Run is available as WindowsKey-R. However, Start -&gt; the empty box is more powerful than run. As you start typing the command, it automatically finds it, not just executables, but your favorites, etc. etc. Then you can even right-click on the found results and run as Administrator.<BR/><BR/>In order to show the file extensions, open up Windows Explorer (Start -&gt; Computer, or WindowsKey-E) then hold ALT to see the navigation bar. There click Tools -&gt; Folder Options. The rest is same as Windows XP, go to View then unselect &quot;Hide Extensions for known file types&quot;<BR/><BR/>There you go...Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-26049584.post-89195104638307528452008-09-12T09:38:00.000-04:002008-09-12T09:38:00.000-04:00No, I couldn't run 64-bit guests, either. That's more an issue with how VMWare is seeing your CPU, though. They have a <A HREF="http://www.vmware.com/download/ws/drivers_tools.html" REL="nofollow">VMWare Guest Check</A> application you can run that will tell you whether VMWare can run 64-bit guests on your hardware. (You'll have to scroll down a little to find it on that page.)Charles Robinsonhttp://www.blogger.com/profile/04606895130887441753noreply@blogger.comtag:blogger.com,1999:blog-26049584.post-66634335988699523392008-09-10T21:40:00.000-04:002008-09-10T21:40:00.000-04:00Thanks for the info on installing VMWare on Vista Home. Are you able to instantiate 64-bit guests? When creating a new VM I was notified that 64-bit guests are not supported on my machine? (HP Turion Ultra laptop)<BR/><BR/>With respect to Vista being slow, something's probably wrong with your installation. On my laptop, restarting takes about 50sec and opening network dialog just 5sec.<BR/><BR/>Best wishes!abinsteinhttp://www.blogger.com/profile/09589312866039619976noreply@blogger.comtag:blogger.com,1999:blog-26049584.post-44331877345849583062008-08-26T09:15:00.000-04:002008-08-26T09:15:00.000-04:00You still have to hit F8 on startup.Charles Robinsonhttp://www.blogger.com/profile/04606895130887441753noreply@blogger.comtag:blogger.com,1999:blog-26049584.post-35638860244472905492008-08-18T02:16:00.000-04:002008-08-18T02:16:00.000-04:00Would running those commands that you mention in a batch file each time on start up resolve your vmware power up issues or do you still need to disable them using the F8 option? I'm just in the process of installing 1.06 on Vista64 myself so was just curious.<BR/><BR/>bcdedit /set nointegritychecks ON<BR/>bcdedit -set loadoptions DDISABLE_INTEGRITY_CHECKSAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-26049584.post-64617314817207673942008-08-02T15:49:00.000-04:002008-08-02T15:49:00.000-04:00just in on slashdot: Foxconn is bettering its ways in supporting Linux. Maybe there is a way ahead after all.Lars Berntrop-Boshttp://www.blogger.com/profile/12080086450338712707noreply@blogger.comtag:blogger.com,1999:blog-26049584.post-35701520208056316062008-08-02T11:07:00.000-04:002008-08-02T11:07:00.000-04:00ESXi uses a specially crafted Linux kernel and Foxconn does not release any Linux drivers so I'm not going to try. Actually every Dell we just bought uses a Foxconn mobo... it should be interesting when I try loading ESXi on one of those on Monday.Charles Robinsonhttp://www.blogger.com/profile/04606895130887441753noreply@blogger.comtag:blogger.com,1999:blog-26049584.post-1209537089408210672008-08-02T06:19:00.000-04:002008-08-02T06:19:00.000-04:00Would you be able to install ESXi now that is free? Would that solve your problem?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-26049584.post-36894499717802598732008-07-26T20:10:00.000-04:002008-07-26T20:10:00.000-04:00Hmmm, that must be restrictions on Vista Home edition. I'm using Vista Ultimate and my start menu has the Run option. Also the option to make file extensions is where it always was for me.Rebecca Dormannoreply@blogger.comtag:blogger.com,1999:blog-26049584.post-67629828043336890242008-07-26T15:09:00.000-04:002008-07-26T15:09:00.000-04:00Ah. How unfortunate.Lars Berntrop-Boshttp://www.blogger.com/profile/12080086450338712707noreply@blogger.comtag:blogger.com,1999:blog-26049584.post-60614128383891145052008-07-26T09:06:00.000-04:002008-07-26T09:06:00.000-04:00It is a Foxconn motherboard, unfortunately.Charles Robinsonhttp://www.blogger.com/profile/04606895130887441753noreply@blogger.comtag:blogger.com,1999:blog-26049584.post-65116145204202880452008-07-25T18:25:00.000-04:002008-07-25T18:25:00.000-04:00Why don't you install a Linux distribution your comfortable with and put VMWare server on that. No driver signing issues either. Or is there a Foxconn motherboard in that Gateway...Lars Berntrop-Boshttp://www.blogger.com/profile/12080086450338712707noreply@blogger.com