Re: [Freedos-devel] VME Broken on AMD Ryzen

2017-05-12 Thread Rugxulo
Hi, On Fri, May 12, 2017 at 6:36 PM, Ralf Quint wrote: > On 5/12/2017 4:33 PM, Alain Mouette wrote: >> >> On 12-05-2017 16:14, Rugxulo wrote: Should JEMMEX or the FreeDOS installer work around this? >>> Just use "NOVME", and don't worry about it. >> Could you please

Re: [Freedos-devel] VME Broken on AMD Ryzen

2017-05-12 Thread Ralf Quint
On 5/12/2017 4:33 PM, Alain Mouette wrote: > > On 12-05-2017 16:14, Rugxulo wrote: >>> Should JEMMEX or the FreeDOS installer work around this? >> Just use "NOVME", and don't worry about it. > Could you please explain that... > Use that parameter when you load JEMMEX, as per instructions

Re: [Freedos-devel] VME Broken on AMD Ryzen

2017-05-12 Thread Alain Mouette
On 12-05-2017 16:14, Rugxulo wrote: >> Should JEMMEX or the FreeDOS installer work around this? > Just use "NOVME", and don't worry about it. Could you please explain that... Alain -- Check out the vibrant tech

Re: [Freedos-devel] VME Broken on AMD Ryzen

2017-05-12 Thread Rugxulo
Hi, On Fri, May 12, 2017 at 11:29 AM, Matej Horvat wrote: > > "To be clear, the problem is not at all specific to virtualization. It has > been confirmed on a Ryzen 5 1500X running FreeDOS—which comes with the > JemmEx memory manager, which enables VME by default.

[Freedos-devel] VME Broken on AMD Ryzen

2017-05-12 Thread Matej Horvat
"To be clear, the problem is not at all specific to virtualization. It has been confirmed on a Ryzen 5 1500X running FreeDOS—which comes with the JemmEx memory manager, which enables VME by default. Until VME was disabled, any attempt to boot with JemmEx failed with invalid opcode