windows 10 IoT enterprise in virtualbox 6 (ver 6.1.16)

This took me a couple tries to get windows 10 IoT to work under virtualbox, and it is very easy.
END result:

steps:
1. download windows 10 IoT enterprise from microsoft.
evaluation copy of Windows 10 IoT Enterprise here.

Direct link: 19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_en-us.iso

At the time of this writing, the file downloaded was: 19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_en-us.iso

2. run virtualbox, Create new machine:

 -Memory, 2GB

-Disk, 30GB

3.Settings:
-change the boot order as shown:

-storage
select the evaluation ISO from microsoft

-Audio,
DISABLE (we'll enable after installation)

-Network
DISABLE (we'll enable after installation)

-Everything else, I just left default.

4. take a snapshot before installation.

5. boot up and install windows as usual. 

Select Next, then 'install windows' then next again

 Custom: Install windows only

Select the drive/NEXT

installing...

Set your keyboard, etc.

I don't have internet

Continue with Limited setup.

set your username, passwd and security questions.

select NO

 DECLINE 

No for everything here. Then Accept.

Cortana: Not now

 
windows IoT will auto login:

windows start button/ power/ Shut down.

Take another Virtualbox Snapshot

Turn on audio.

Turn on Networking, leave "Cable Connected" unchecked!

Start up

Disconnect ISO:

Connect the network adapter

NO

Wait, and wait...

SKIP for now.

Create a desktop cmd.exe icon,s
right click and 'run as administrator'
slmgr /rearm

Finally, a 90 day evaluation of Windows 10 IoT:

Go ahead and install virtualbox additions...

Root the Samsung Galaxy Tab 4 SM-T230

There are a lot of tutorials on how to root a Samsung Tab 4, and this is how I accomplished the task.

oneclickroot - although this looks like a good solution, they want $$$ to root your device.
kingroot - another solution, but it looks like this uploads your device data to a cloud storage device somewhere.  Again, this is not my first choice.

My hardware:
1. computer, windows 10 (I run xubuntu, but this is necessary for rooting)
2. samsung galaxy tab 4, SM-T230
3. white USB cable provided with galaxy tab 4

Software:
1. Kies3
2. Odin3 (ver 3.09) and TWRP 2.8.0.1


backup device:
1. install dotnetfx3.5 for windows 10
2. install kies3
3. run kies, and backup your device


root process:
1. run odin3 as admininstator.
    select AP,

 then the select the openrecovery .tar file

Your Odin3 screen should look like this:

2. Unplug all cables from your Samsung tablet
    While the Tab 4 is on, press and hold down the 3 buttons:
    HOLD down:  power + vol down + the home (center) button.

    until you see this screen:

   then select Volume up to continue to allow for downloads
   you should see this:

4. Connect your tab 4 to your computer using your white USB cable.

5. run START from odin3

    get ready for device to reboot...

6. Once you see it rebooting: (while samsung screen is rebooting)

quickly hold down:
 
Power + Volume Up + Home

You should now see the recovery screen from TWRP.
Select Reboot.

7. select System

 8. Swipe to confirm:

  device should reboot.

10. Run play store app (or visit play.google.com from your computer)

11. install

"supersu" from Chainfire





12. run and enjoy.



Extras:

Install Universal init.d from androidguide.fr

Asus chromebox CN60 easy memory upgrade to 8GB

Bought this Kingston memory pack from online and it worked perfectly.  My new server now is running 8GB instead of the original 2GB.
Manf:      Kingston
Model:    HX316LS9IBK2/8
Speed:    DDR3L 1600 (PC3L 12800)
Voltage: 1.35V

Anyone want my old 2GB???

ubuntu 15.04 / 15.10 - A start job is running for dev-disk-by (slow boot)

After I upgraded to xubuntu 15.04 vivid my computers were booting extremely slowly.  I didn't panic, just waited for them to boot and started searching for answers.

Hit      during boot to see what the error message is.


 Mine showed this:
"a start job is runnning for dev-disk-by \ x2duuid-xxxx \"

So the easy fix:
swapon -s to see which drive is really your swap disk.

sudo gedit /etc/fstab
and comment out the swap file that was used during installation. Reboot, and all should be fine.

Other notes:

• You can also run:  swapon -s   to see which one is really your swap partition.
• run:  sudo blkid  to see the UUID info of your drives.
• run:  systemd-analyze critical-chain  and  systemd-analyze blame  see what is slow during start up.
• systemd for ubuntu
• 15.04 Vivid release notes