Subj : Re: WINDOWS 2008 62 bit Server with Win XP To : All From : GREG YOUNGBLOOD Date : Thu Jan 31 2019 07:12 pm Date: Mon, 05 Nov 2012 03:55:13 -0400 From: GREG YOUNGBLOOD To: MICHAEL PURDY Subject: Re: WINDOWS 2008 62 bit Server with Win XP Newsgroups: win.server.program Message-ID: <1352105713.32.1352082925@winserver.com> References: <1352082925.32.1352034661@winserver.com> X-WcMsg-Attr: Rcvd X-Mailer: Wildcat! Interactive Net Server v7.0.454.5 Lines: 39 Morning Mike Right now it is on a single core xeon e server IBM but I will be moving it to a Dell Quad core poweredge server with 16 gigs of ram so I should be good to go there. The last thing I did last night was move the VM to another nic card so I will be testing that today and tomorrow. Thanks for the tips though, I fell a little better knowing I'm going in the right direction. Greg -> You can run VB on a single core with 4G Memory but put simply that isn't the target platform -> -> The assumption is that you will be running on a server (not desktop) with -> max RAM and at least a Quad Core+. A dual core will work but you would be -> limited to a very small number of Virtual Machines even in headless mode. -> -> You also want to make sure your Host OS is using a physically separate -> Network Interface Card to the Virtual Machines. When you start sharing the -> host NIC with the VM's it slows things down and potentially causes odd -> Windows TCP Stack problems. -> -> When you have the server hardware in place you can then fine tune the -> Settings for each of your VM's to reduce overhead and lag. -> -> I suggest you experiment as much as possible before moving everything to a -> production environment. -> -> Mike --- Platinum Xpress/Win/WINServer v3.1 * Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013) .