1. Hello, download and install Oracle VirtualBox from their site (https://www.virtualbox.org/wiki/Downloads). You need two files: VB itself, first to be installed, and then the "extension pack" which is downloaded from the same page (look for it, the link's there). When ready with the VB, try install Ubuntu as your first VM. Definitely worth it, especially if you're new to VirtualBox. So give it a try. Don't begin to setup your new xTER virtual unless you've got some experience playing with the Ubuntu setup, ok? But if you're not new, just proceed with creating a new virtual machine as shown in Picture#1. Select Linux/RedHat 64-bit.
2. Ok. Picture#2, and you're to select the size of RAM for the xTER virtual. Select 8Gb, if you can. If not, then at least 5Gb RAM for our Home and Office editions. For xTER Router Edition, we squeezed the whole thing to fit into 2GB of RAM. You can change this value later, set it 8Gb for now if not sure.
3. Just proceed and select the VDI type as shown in Picture#3.
4. The default size of the partition is 8Gb as shown in Picture#4. Agree with the default if not sure.
5. Ok, that's it with creating the xTER VM. Now let's set up other things as shown in Pictures#5,6,7... Important - check Enable EFI to "on" as shown in Picture#5. It's "off" by default. You need EFI to boot the xTER VM.
6. Select as many CPU cores as you really have on your physical: 1,2,4..
7. Create a new "hard disk" file with .vdi extension attached to the SATA-0 controller, as shown in Picture#7. Check the "SSD" box if your comp's physical drive is a solid-state drive.
8. Now we take care of the Network. Just copy what you see in Picture#8 as your new Port Forwarding rules. Exactly as shown there in this Picture, just copy.
9. These USB settings are really important. Warning: you must have the Extension Pack installed for the working USB. If you skipped it, go back to Step 1 now. And install it. Ok, now you will add the needed USB devices one by one. Begin with the USB flash from which the EFI bootloader starts. In my case, it's named "Sundisk Cruizer" - which is the flash drive name. I also add a KYE Systems USB Camera, and I would have added another USB device, a WiFi USB pen - my old D-Link DWA125, - but it's currently connected to another computer and working. Alas. WiFi works fine with this virtual, too - so if you have a spare WiFi USB pen - go for it and plug it in now, and it will appear in the list of possibilities. Notice how I don't add a wireless keyboard or mouse, though they are in my list. Why not? Because I won't need them. xTER is a headless thing by design. So I finish this part of setup, for now with only two USB devices attached, only two - but they would still dislike each other during boot, you'll see how - a bit later in this story. After boot, all connected USB devices wouldn't conflict, but on UEFI boot - they may happen to.
10. OK, you are ready to PowerOn your xTER VM. Take a look at Picture#10 before you push the "Start" button, all right? Not explaining the sound section, just copy as you see in the picture - select ALSA and ICH AC97.
11. Come on. You pushed the "Start" - and then it all stopped. WTF? Explanation: the UEFI doesn't find this Cruizer flash, but I know why and how to make it be found. Stay cool. First - unplug the USB camera. Second - unplug the Cruizer flash. Now, plug the cruizer (flash) back. Yes, only the flash now, not the camera (later), - cool it in the air for 1-2 seconds and plug back, and now, now - type the holy "map -r" command in the Shell.
12. That's what you get - see in Picture#12. See this "FS0" up there, after "map -r"? We got it, this time. It's our flash with the bootloader, ok. Now, plug back the USB camera.
13. And then type in the Shell these commands: a) fs0: b) cd efi\boot c) bootx64.efi - and here we go.
14. Welcome to the xTER bootloader. Loading.. [ and you may have been a luckier people than us if you got the boot from the flash straight without USB conflicts, then you skipped the Steps 11-13.]
15. Finished downloading, now it's unpacking. We don't do anything but wait.
16. Finished unpacking, now starting the system. We wait a couple of minutes here.
17. And finally, the virtual machine is up and running. Congratulations. Let's get in. You'll need a browser. Of course, you are on the physical. Let's use any browser present on your physical.
18. I use a Chrome browser and type in this URL - https://192.168.88.99:8443 - that's where the admin interface begins, but. WTF? Some warnings. Because the default HTTPS certificates are not suitable for all cases (they are only good for our demo site at https://demo.xter.tech), and if you don't want these warnings - you must issue your own HTTPS certs and upload them from the Settings menu later. For now, proceed with the down link. No sweat. And the IP in my URL - it's 192.168.88.99, and it's the IP of my physical. You should know YOUR PHYSICAL MACHINE'S INTERNAL IPv4, somehow. No luck?.. really? I can't help, sorry. We can't proceed any further in this case. Thanks for your time. But ask google - How do I know my comp's internal IP? - it will help. Of course. And if you plugged a WiFi USB pen earlier - then the IP for connecting through WiFi is 192.168.56.254, and the port would still be 8443.
19. Bingo! The default admin's password is seen in the Picture#17. The first thing to do after logging in - go to Settings and change it, and a WiFi key, too. The sooner, the better. Really.
20. OK, we are in the Settings Menu. Click on the red "[!]" by the side of the labels in the second vertical submenu. The current admin password and the WiFi key ARE DISPLAYED THIS WAY. Rememeber.
21. Now, I change the WiFi key. WTF, what is "como_estas"? It's not the key, right. The corresponding key would be as shown in Picture#20. A "como_estas" is my "key phrase" from which the key shown above is auto-generated. You don't change the key directly, you change the key phrase. OK? The same way you change the admin password. Please do it now.
22. When you change these settings, you're urged to understand that it's better to WRITE DOWN THE NEW PASSWORD BEFORE IT'S TOO LATE - if you don't remember the password that you have saved, you cannot login any more and you'll have to remove the "data" folder from your EFI bootloader flash drive (FS0:\efi\data), then force stop the virtual and boot it again - to the default password and WiFi key.