<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi Jon,<br>
<br>
the 5.2 test builds are always "not quite next 5.2.x release"
builds, so if they have the working fix then it will automatically
end up in the next release. In this case it will be 5.2.22. Of
course the same fix will be also in 6.0, but that's further in the
future since we just started beta testing.<br>
<br>
Klaus<br>
<br>
On 08.11.2018 01:37, Jon Kunkee wrote:<br>
<blockquote type="cite"
cite="mid:DM5PR2101MB1112E39DF6AFB18CF35E5325B0C50@DM5PR2101MB1112.namprd21.prod.outlook.com">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;}
span.EmailStyle21
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal">I appreciate the pointer to testing builds;
we’re doing some internal validation using them and will post
back when we know the fix is good.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">As we’re preparing for the upcoming Windows
release, we’d like to make sure customers have more than just
test builds to use; is there any idea when this will be in an
actual release? Would it make sense to expect this to land in
a 5.2 update, or is this only going to land in 6.0?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks,<o:p></o:p></p>
<p class="MsoNormal">Jon<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Jon Kunkee <br>
<b>Sent:</b> Thursday, September 20, 2018 4:30 PM<br>
<b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:vbox-dev@virtualbox.org">vbox-dev@virtualbox.org</a><br>
<b>Cc:</b> Divya Bhat <a class="moz-txt-link-rfc2396E" href="mailto:divyabh@microsoft.com"><divyabh@microsoft.com></a><br>
<b>Subject:</b> Updating VirtualBox consumption of
IMAGE_LOAD_CONFIG_DIRECTORY*<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hi,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I’m a software engineer on in the Windows
group at Microsoft. My team recently added a pointer-sized
field to IMAGE_LOAD_CONFIG_DIRECTORY32 and
IMAGE_LOAD_CONFIG_DIRECTORY64 that is non-NULL on 32-bit x86
Windows 10 systems in the current Insider Preview.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">It seems that VirtualBox does some
extensive validation of this structure, so it now exits with
an error when it sees this field in use.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I filed a ticket about it:<o:p></o:p></p>
<p class="MsoNormal"><a
href="https://www.virtualbox.org/ticket/17977"
moz-do-not-send="true">https://www.virtualbox.org/ticket/17977</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">If I grokked the bug filing page right,
it’s proper to ask about it here too.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Adjusting the VirtualBox validation to
handle a new field in this struct has been done before, so
hopefully it’s easy to do again. (I linked two of the previous
tickets in the History section.)
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In the longer term, is there a way for the
validation to not break so easily?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks,<o:p></o:p></p>
<p class="MsoNormal">Jon<o:p></o:p></p>
<br>
</div>
</blockquote>
<br>
</body>
</html>