virtualbox.org

I am using Ubuntu 9.04 fully updated for my host, VirtualBox 3.2.10 r.66432 as the VM, and Windows 2000 Pro as guest. In fact I have several VDIs that are essentilly the same, which I name in order 2k-1, 2k-2, 2k-3, 2k-4, 2k-5, 2k-6 and so on. These are mostly minimally configured versions of Windows 2k, but there are two exceptions. 2k-5 is my full working version, and 2k-6 is a clone of 2k-5 in case I have to fall back for some reason. Cloned, except I have found it is not that infrequent for VirtualBox to screw up a file in \WINNT\SYSTEM32\, making that VDI unbootable. But it still has all my data and programs on it. Do I want to try and repair Windows on that VDI?

Not if you value keeping what you have there, you don't. Windows 2k/XP installs with EnableBigLba missing from the registry or set to zero. That hurts with most PCs today. You can't even install Windows 2k on a drive beyond about 128 MB in size. Ah, but VirtualBox gives you Dynamic rather than Static size, so you can create as large a virtual drive as allowed, but when Windows installs, the VirtualBox steps between and Windows has no problem installing on a virtual drive that will just keep expanding until it reaches its max. But after getting that initial install to work, you have the obligation to make sure that EnableBigLba is set to 1 in the registry. There are many discussions about how to do this simply on the Internet, so I leave it to you to seek out that info on your own. Otherwise, as more and more virtual drive space is appended, you will eventually just bang your head about when you get to the max limit allowed. You won't get a warning message, you just end up scrambling files on top of other files, until you can't even boot up again. Gee, I wonder if I forgot this time and left that 800 lb gorilla hanging over my own head. No harm finding out.

But here is my real problem at present. I am using the wired eth0 connection instead of the USB-LAN connection that is included in this noteboot, for speed and security, actually I can unplug the wired connection and go over to the wireless with ease or reverse the process. I can disable the wireless instead if I wish by software or diconnecting the antenna.

But I was considering the fact that VirtualBox allows me up to four network adapters, and apparently more than one can be in use at the same time. Now this old version of Windows isn't going to work well with multiple instances of network connections, but maybe I could designate one specific adapter to it, leaving the host with its own separate connection. I decided to try for a hookup that would look like this:

The host could be left to use either etho or wlan0, yours or its choice.

The VM Identifies Adapters 1, 2, 3, and 4. You have a choice of settings for each, such as whether it is enabled or not, whether it uses a protocol like NAT, use a Bridged Adapter there, use the internal network, whether to treat it as a Host Only Adapter, or whether to regard it as Not Attached. Yes, but what tells us what it needs to be set to to work for us? And why choices like this, when the VM already knows what the Host has to say about the actual hardware and the VM already knows the guest to be used here? I mean no disrespect of any kind, but taking all that is already known and creating the most optimum configuration, THEN letting the user decide what choices to make instead, just seems to make the most sense to me. Why force users with limited experience to make unnecessary choices? That is something Ubuntu pretty has right to start with, but maybe only because Windows forced their hand.

So tell me now, how would I configure this so that the Host alone had use of the wired connection, giving me ample opportunity to test and confirm that the guest is set up to work with the wireless card? How would I reverse that process, so that the host used the wireless and the guest used the wired? What are my auto rollover options for one or the other if one of my adapters failed to respond, or the signal gets too weak? What if I had a built-n wireless g card and stuck in a temporary or permanent n card? How could all that come together in ways that benefit the user the most? Feel free to answer, I am here to learn too.

Oh,one last thing. Sometimes a chance hit of several keys at the bottom right side of the keyboard immediately puts the guest into an Aborted mode. Then everything is lost. VirtualBox and the Host are unaffected. Be nice to snapshot the virtual machine before such a drastic departure, or at least get the choice of answering the question "Are you SURE you want this Client to abort and shut down?" Choice can be good, you know

My friend,

No insult intended but can you ask a simple question or at the very least ask a few questions using numbered/bullet lines.
I do not have the time to read a novel and doubt many others here that could actually answer your question will either.

Oh, no insult taken. Kind of you to ignore my questions and focus on my manner of delivery instead. That was so helpful. Made better use of your time as well,
I am sure. I take you are of the school that hostile questions, such as "Answer Yes or No, do you still cheat on your spouse?" are best as they involve the shortest possible use of words.

As for me, I've a detailed oriented mind, and details count. While some see PCs as just another form of appliance. I admit I still find them a bit of a challenge. and when challenged, it is often best to seek out and share the best possible answers.

But I accept your NO vote, though how best to apply it with response to my questions eludes me for the moment. No offense meant of course.

Tell you what. I did not read the entire diatribe and do not intend to. Keep it up with these long and lengthy post and you will find that no one will respond. As for me I was trying to help you by stating the obvious. Unfortunately you are now in my ignore folder and will not show up again so you will not be hindered by my needless help.

I didn't refer to as unneeded, because apparently someone there finds use for you. On the other hand, you seem to have made yourself inaccessable to me, so in that regard I hope you merely prove to be unnecessary in my search for answers. I'm glad you are not in technical support as I was, as such a reply would have put a stamp on the entire company. You aren't in tech support, are you? If so, how humiliating to a profession I always took pride in.

Perry has made himself inaccessible for you, but you in return made yourself inaccessible for others with a whole Stephen King novel sized post with questions all around with no obvious direction as to where you want to go. You ask for help with network choices, start rambling about installing on large drives and whatnot for kind of issues you might get (never had those myself, so I have absolutely no idea what you're talking about), then switch to the actual issue of networking and ask a question, then ramble on again with something totally in the opposite direction.
If you want to get help, make it clear what you're asking. Also show that you've done your homework, which I see you obviously haven't. Because if you had, you wouldn't have asked this question in the first place. The homework is reading the User Manual. Chapter 6 explains what network options you have and what each option means. Other homework includes reading and following the Forum Posting Guide and the VirtualBox FAQ.

So make it clear what your problem is and what you've done yourself to find a solution to it and if that solution worked or not.

You are not forced to make any decision about your network connections in the guest. The default is to use one NIC and NAT. For beginners, that should be all they need (which is why it is the default setting). The other options are available to allow for more complex networking setups. I have used them all at one time or another and find them very useful. There was a posting in the forum in the last few days of a user running a 4 NIC firewall in a vm. He needed the ability to use 4 NICs connectd to four different networks, some virtual and some physical.

The OPs (ahem) overly complete commentary style has been remarked upon before: check this previous occurrence, where I played the Perry role of irritated volunteer.

1. About Windows 2000 -- the big LBA looks like Win2000 bug. Not sure if VirtualBox should touch it at all. Theoretically VBox Guest Additions could enable LBA, but who will test it ?

2. Network: the default is "NAT", and it is best recommended option for the inexperienced users. Users should not touch it, unless they know what they are doing.

3. "several keys at the bottom right side" -- which keys ?