Wireless connections
Wifi works alright in AndEX Marshmallow. Just go to Settings and turn Wifi on. Unfortunately the support for Broadcom Wireless cards is not complete (in the Android-x86 project). I have experience from two different cards – BCM4311 and BCM43142. The first mentioned one works.
VirtualBox installation of AndEX Marshmallow
You can run AndEX Marshmallow live in VirtualBox. I.e. the system will start up properly, and you can even install new apps. While running for example YouTube and Spotify you will, however, notice that the sound is distorted. Once installed to hard drive (virtually) in VirtualBox the system works very well. Note: My Lollipop (160215) and KitKat (160214) versions can also run very well in VirtualBox. The Lollipop and KitKat AndEX systems can also run very well live in VirtualBox.

Install the system to hard drive
Say for example that you have a laptop with Windows 10 installed as the only operating system. If you just create one extra partition of about 5 GB you can install Android Marshmallow on this extra partition and then “dual-boot”. I.e. you can turn on your computer (called “booting it up”) and decide whether you want to start Windows or Android Marshmallow. Grub will be installed as boot handler/loader during the installation of Android Marshmallow. Note: The installation will take only about one minute. And the installation to hard drive is so simple that a 10 year old child can do it.
More about Grub and “dual-boot/multi-boot”
If you already have have one or more Linux systems installed on your computer you should skip installing Grub during the installation of AndEX. If you use Grub2 (which Ubuntu and most other Linux systems use as boot loader) you should instead add these lines to /boot/grub/grub.cfg or /etc/grub.d/40_custom – for example:menuentry ‘Android-x86_64 6.0.1 Marshmallow 160922 (sda8)’ { insmod gzio insmod part_msdos insmod ext2 set root=’hd0,msdos8′ linux /android-2016-09-22/kernel quiet root=/dev/ram0 androidboot.hardware=android_x86_64 \
acpi_sleep=s3_bios,s3_mode SRC=/android-2016-09-22 DPI=140 \
UVESA_MODE=1920×1080 initrd /android-2016-09-22/initrd.img }

NOTE 1: On some computers you may have to add nomodeset to the linux boot line. If so you may also have to remove DPI=140 and UVESA_MODE=1920×1080 from the linux boot line. (AndEX won’t start otherwise).
NOTE 2: The DPI=140 entry provides a hint about the display’s pixel density in dots per inch. This is an important setting – if the Android display’s icons and text look too small and crowded, increase this number. If things seem too big, make it smaller.

NOTE 3: The UVESA_MODE=1920×1080 entry describes the display size. This is also an important setting. If you know your display’s actual dimensions, enter them here. But not all dimensions work – it sometimes happens that a display specification that’s possible in principle isn’t feasible in practice.