I just realized Windows 7 cannot be installed on a Kaby Lake

[Shivansps]

Wondering about re upload my easy network boot guide, once you start using network boot you will never go back.

 

[John Connor]

You should really stick to topics that you know something about.

No, you should! I just built a brand new computer last weekend and I was able to use my mouse/keyboard with my USB 2.0 port like I already mentioned.

 

[VirtualLarry]

No, you should! I just built a brand new computer last weekend and I was able to use my mouse/keyboard with my USB 2.0 port like I already mentioned.

Not exactly. If you were using native USB2.0, then the scroll wheel on your mouse would have functioned.

You were using your UEFI's built-in PS/2 / Port 60/64 emulation feature.

I don't suppose that you tried plugged in a flash drive, into the "USB2.0" port, while loading Windows 7, before installing the USB3.0 Intel drivers?

 

[John Connor]

I don't suppose that you tried plugged in a flash drive, into the "USB2.0" port, while loading Windows 7, before installing the USB3.0 Intel drivers?

No. I moved my entire HDD to the new computer using sysprep. But you mention emulation. Wouldn't that work in USB 2.0 with a new Win 7 install? I use Win 7.

 

[VirtualLarry]

Here's the thing. Intel removed the hardware backwards-compatibility with the USB ports with USB2.0/EHCI. The chipset-integrated USB ports on Skylake and Kaby Lake are all XHCI (USB3.0), even the ports that are physically USB2.0. They still need USB3.0 drivers to function. (Whacked, I know!)

Windows 7's installer, unless you inject USB3.0 drivers into the install and boot WIM images, will only support up to USB2.0/EHCI.

Now, if your motherboard uses a 3rd-party USB controller chipset, then it may well be providing USB2.0/EHCI ports. Which would in fact work with Windows 7.

One way to test if that's the case, is to plug in a USB flash drive into one of those ports, before installing the Intel USB3.0 drivers. If it works, then my theory is wrong, and you do in fact have "real" USB2.0 (EHCI) ports on your board.

Edit: And as far as I know, PS/2 port emulation works regardless of which chipset-based USB port you use to plug in your keyboard and mouse. The UEFI translates between the XHCI USB controller, and uses System Management Mode on the processor, to make it look to the OS software, like someone is using a PS/2 Keyboard and Mouse.

 

[John Connor]

Well, I can tell you that when I transferred my HDD from my Q6600 board into the new computer using sysprep, no USB drivers were there until Windows booted on the new computer. I had plugged in the USB dongle for the wireless ketboard/mouse into the back USB 2.0 IO port. It did indeed work except mouse wheel scroll. Once I installed the USB 3.0 and 3.1 drivers my mouse scroll worked. So perhaps it's due to having EHCI ports.

 

[VirtualLarry]

Looking at your sig, that's a really nice board. Might consider upgrading the GPU next? Or does that one do OK for FSX?

 

[John Connor]

Thanks. I do plan on upgrading the GPU in the near future, but it does suffice for what I use it for; FSX, BF2 and some other old games. So you can imagine it's more than enough horse power. Especially since FSX is mainly a CPU oriented game. I love the CPU so far though. I have a ton of AI aircraft installed. Somewhere in the neighborhood of 400 or more airlines and when you first launch FSX it would take a good three minutes to load on the Q6600. With this new CPU the game loads in about a minute. Very impressive and I haven't over clocked yet.

My color scheme for the case fans and the MOBO RGB is red. Thus a red sig. Even the BIOS has the ability to customize the graphic and I made that a red biohazzard image. Looks really sweet.