[RESOLVED, by TSD]1950x will not boot media comp.

ASRock TSD responded to my ticket and informs me that TR supports W10 RS1 and RS2.  RS1 requires disabling IOMMU in the BIOS.  I see no mention of this restriction in the ASRock site on the X399.  When first told, I did not even know what RS1 and RS2 were.  Here is a good reference:
https://en.wikipedia.org/wiki/Windows_10_version_history
RS1, Redstone 1, is W10.1607 and RS2 is W10.1703.  In my case the version of W10 I was installing was RS2, but I was using an older version of WinPE which obviously was not supported.  Building WinPE using the latest ADK (1703) solved my problem not the smaller size as I suspected.  I suspect this same restriction may be preventing the Server 2016 installing.  A wild guess is to try disabling IOMMU.  Here is am image sent me from an AMD document:

Enjoy, John.

Thanks, datonyb.

wardog, good grief!  I have said several times I have NO interest in W7.  How many times do I have to say I am sorry I even mentioned W7.  The SATA floopy (see the DL page for spelling) is for RAID use.  I have no RAID.  I also said I was not interested in chasing old problems. 
I have W10 x64 Professional installed on my TR.  All is well, I have no issues.  W10 installed without F6 floopy drivers.  All my special drivers are injected into the .wim files using DISM.  I have W10 x64 Pro installed.  I posted this in my first post:

Fatal1ty X399 Professional Gaming, Threadripper 1950X, 3xSamsung SSD 960 EVO, G.SKILL FlareX F4-2400CL16D-16GFXR, Windows 10 x64 Pro, Enermax Platimax 850, Enermax Liqtech TR4 CPU Cooler, Radeon RX580, BIOS 1.5

Thanks and enjoy, John.

[RESOLVED] !!!!!!!!!!

John, not for a minute can I believe a very recent from the ground up platform would not have 48-bit LBA. That would go down as a World Class blunder if this was true.

Let me read that link you provided. And go back to your original to see the components used again.





Edited by wardog - 15 Sep 2017 at 3:58am

                                                                 RESOLVED!
First, I want to apologize for even mentioning booting the W7 install DVD.  I never wanted to install W7, just see if it was possible to boot anything on this machine.  I certainly did not need old bugs to chase.  The fact that it did boot gave me a way forward.  I made a WinPE CD ROM and it booted fine.  Then I made a WinPE USB stick with no extra files like were on the old one.  It booted fine also.  I then used the USB stick to do a flat install from one one of the SSDs and all went fine.  The system is running fine.  I suspect I have a similar problem to this thread:
http://forum.asrock.com/forum_posts.asp?TID=5860&KW=2016&PN=1&title=x399-taichi-with-tr-wont-install-server-2016
I also suspect this is a BIOS problem.  Since, at least for me, it seems to be boot device size dependent, I suspect that the BIOS is using a 32 bit variable for addressing data (>4GB) on the device.  I do not know if this is an ASRock or an AMD problem, so I will open a ticket on both.  The fact that the BIOS and AGESA are so down level on Threadripper should be a shame to both.  I hope it is fixed soon.  Thanks and enjoy, John.


Edited by MisterJ - 15 Sep 2017 at 3:34am

parsec wrote: It sounds like the optical drive you are using on the X399 board does not support UEFI, while the one on your Ryzen 7 PC does. Not all optical drives support UEFI.

Lord, I haven't used an ODD to install an OS for years and years.

parsec, it seems to me it should have "installed' regardless of UEFI: <ODD> or not.