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

wardog wrote: Windows 7 you need to use: http://www.asrock.com/microsite/win7install/

Clarification:

To enable USB mice and KBs you need to use the above patcher on Windows 7.



Too, I wonder, on one of your attempts , use the SATA Floppy Image available on your MB's dl pages. RAID or otherwise.

I unzip it right to the 10 USB install stick and F6 it where it asks what drive you want to use to install to. It'll present 3 dirs, with the top one being RAID drivers pre-install.

I dl/'d the media tool last night. 1703.15063.0

MisterJ wrote: Thanks, Wardog.  I am sorry I mentioned W7.  I have no interest in installing W7 on my system, I only used the disk to see if it would function and it does.  Enjoy, John.

NP John.

I only pointed it out as your issue with 7 there on x399 system.

hehe, No. Not unless you ha(d)(ve) an important program that the programmers left at 7.

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.

                                                                 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

[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