{"id":283,"date":"2010-01-10T16:38:06","date_gmt":"2010-01-10T14:38:06","guid":{"rendered":"http:\/\/www.ticklishtechs.net\/2010\/01\/10\/shell-lib-reloaded-another-os-another-bug\/"},"modified":"2020-08-13T20:45:26","modified_gmt":"2020-08-13T18:45:26","slug":"shell-lib-reloaded-another-os-another-bug","status":"publish","type":"post","link":"https:\/\/www.ticklishtechs.net\/2010\/01\/10\/shell-lib-reloaded-another-os-another-bug\/","title":{"rendered":"Shell-Lib reloaded: Another OS, another bug."},"content":{"rendered":"<p>Some time ago we blogged about a nifty little .net assembly that enables you to access the basic <a href=\"http:\/\/www.ticklishtechs.net\/2007\/09\/02\/windows-shell32dll-shfileoperation-marshalling-and-hnamemappings\/\">Windows shell operations<\/a> in shell32.dll . You may want to do so especially in Win7 because your file operations integrate with the fancy Win7 dialogs, the flashing progress bar etc. <\/p>\n<p>The problem we blogged about in <a href=\"http:\/\/www.ticklishtechs.net\/2007\/09\/02\/windows-shell32dll-shfileoperation-marshalling-and-hnamemappings\/\">the former post<\/a> was a missing &quot;Pack&quot;-instruction in the marshalling-description of a structure. I guess we didn&#8217;t test it with WinXP64&#8230; but some days ago we tests it with Win7\/64 and it failed. We figured out that we introduced a new bug that occurred on 64 bit machines only. After some more testing we found out that: <\/p>\n<ul>\n<li>The original code (without Pack-value) crashes on 32 bit machines (as described in the former post). <\/li>\n<li>The original code (without Pack-value) works fine on 64 bit machines (but we don&#8217;t think the original developer had 64 bits 7 years ago \ud83d\ude09 ). <\/li>\n<li>Our fixed code (with Pack=2) works fine on 32 bit machines. <\/li>\n<li>Our fixed code (with Pack=2) crashes on 64 bit machines. <\/li>\n<\/ul>\n<p>It seems that the &quot;SHFILEOPSTRUCT&quot; structure in shell32.dll has different layouts in Win7\/64 and Win7\/32. I guess the guys at MS aim for performance and tell the compiler to optimize. The compiler optimizes by assuming the optimal Pack-value, which usually is the byte-width of the processor; 4 for 32bit, 8 for 64bit. <\/p>\n<h3>What effect does the Pack-value have at all?<\/h3>\n<p>The &quot;Pack&quot;-value controls the alignment of the starting addresses of each single member of a structure (often called &quot;offset&quot;). <\/p>\n<p>Let&#8217;s say you have this struct: <\/p>\n<p> <code>   <\/p>\n<p>struct MammaMia      <br \/>{       <br \/>&#160;&#160;&#160; public int16 sweet16;       <br \/>&#160;&#160;&#160; public byte bite;       <br \/>&#160;&#160;&#160; public string tanga;       <br \/>} <\/p>\n<p> <\/code>  <\/p>\n<p>Usually you don&#8217;t care for the exact way your data is stored in memory, but when you pass it from .NET to the Win-API you have to make sure Win-API receives and returns exactly the right format. This process is called &quot;Marshalling&quot;. <\/p>\n<p>One crucial instruction for doing so is the StructLayout attribute. <\/p>\n<p> <code>   <\/p>\n<p>[StructLayout(LayoutKind.Sequential, Pack = 1)]      <br \/>struct MammaMia       <br \/>{       <br \/>&#160;&#160;&#160; public int16 sweet16;       <br \/>&#160;&#160;&#160; public byte bite;       <br \/>&#160;&#160;&#160; public string tanga;       <br \/>} <\/p>\n<p> <\/code>  <\/p>\n<p>(Note: There are a lot more options for the StructLayout attribute and a lot more attributes that help you at marshalling.) <\/p>\n<p><strong>LayoutKind.Sequential<\/strong> means that your data is represented in memory in the same order as you declared it: First &quot;sweet16&quot;, than &quot;bite&quot; and then &quot;tanga&quot;. <\/p>\n<p><strong>Pack=1<\/strong> tells .NET that every byte can be the starting point of the next member. So .NET produces this structure in memory:<\/p>\n<p><strong><\/strong><\/p>\n<table border=\"0\" cellspacing=\"0\" cellpadding=\"2\" width=\"197\">\n<tbody>\n<tr>\n<td valign=\"top\" width=\"50\"><strong>Pack=1<\/strong><\/td>\n<td valign=\"top\" width=\"145\">&#160;<\/td>\n<\/tr>\n<tr>\n<td valign=\"top\" width=\"50\">byte<\/td>\n<td valign=\"top\" width=\"145\">data<\/td>\n<\/tr>\n<tr>\n<td valign=\"top\" width=\"50\">0<\/td>\n<td valign=\"top\" width=\"145\">sweet16<\/td>\n<\/tr>\n<tr>\n<td valign=\"top\" width=\"50\">1<\/td>\n<td valign=\"top\" width=\"145\">sweet16<\/td>\n<\/tr>\n<tr>\n<td valign=\"top\" width=\"50\">2<\/td>\n<td valign=\"top\" width=\"145\">bite<\/td>\n<\/tr>\n<tr>\n<td valign=\"top\" width=\"50\">3<\/td>\n<td valign=\"top\" width=\"145\">tanga<\/td>\n<\/tr>\n<tr>\n<td valign=\"top\" width=\"50\">4<\/td>\n<td valign=\"top\" width=\"145\">tanga<\/td>\n<\/tr>\n<tr>\n<td valign=\"top\" width=\"50\">\u2026<\/td>\n<td valign=\"top\" width=\"145\">\u2026<\/td>\n<\/tr>\n<tr>\n<td valign=\"top\" width=\"50\">20<\/td>\n<td valign=\"top\" width=\"145\">last character of tanga<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>&#160;<\/p>\n<p>&#160;<\/p>\n<p>Now <strong>Pack=2<\/strong> makes sure that only every 2nd byte can be the starting point of the next member. That leads &#8211; of course &#8211; to unused bytes in memory: <\/p>\n<table border=\"0\" cellspacing=\"0\" cellpadding=\"2\" width=\"197\">\n<tbody>\n<tr>\n<td valign=\"top\" width=\"50\"><strong>Pack=2<\/strong><\/td>\n<td valign=\"top\" width=\"145\">&#160;<\/td>\n<\/tr>\n<tr>\n<td valign=\"top\" width=\"50\">byte<\/td>\n<td valign=\"top\" width=\"145\">data<\/td>\n<\/tr>\n<tr>\n<td valign=\"top\" width=\"50\">0<\/td>\n<td valign=\"top\" width=\"145\">sweet16<\/td>\n<\/tr>\n<tr>\n<td valign=\"top\" width=\"50\">1<\/td>\n<td valign=\"top\" width=\"145\">sweet16<\/td>\n<\/tr>\n<tr>\n<td valign=\"top\" width=\"50\">2<\/td>\n<td valign=\"top\" width=\"145\">bite<\/td>\n<\/tr>\n<tr>\n<td valign=\"top\" width=\"50\">3<\/td>\n<td valign=\"top\" width=\"145\">??? (unused)<\/td>\n<\/tr>\n<tr>\n<td valign=\"top\" width=\"50\">4<\/td>\n<td valign=\"top\" width=\"145\">tanga<\/td>\n<\/tr>\n<tr>\n<td valign=\"top\" width=\"50\">5<\/td>\n<td valign=\"top\" width=\"145\">tanga<\/td>\n<\/tr>\n<tr>\n<td valign=\"top\" width=\"50\">\u2026<\/td>\n<td valign=\"top\" width=\"145\">\u2026<\/td>\n<\/tr>\n<tr>\n<td valign=\"top\" width=\"50\">21<\/td>\n<td valign=\"top\" width=\"145\">last character of tanga<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>&#160;<\/p>\n<p>&#160;<\/p>\n<p>The higher the Pack-value, the more unused bytes you get:<\/p>\n<table border=\"0\" cellspacing=\"0\" cellpadding=\"2\" width=\"197\">\n<tbody>\n<tr>\n<td valign=\"top\" width=\"50\"><strong>Pack=4<\/strong><\/td>\n<td valign=\"top\" width=\"145\">&#160;<\/td>\n<\/tr>\n<tr>\n<td valign=\"top\" width=\"50\">byte<\/td>\n<td valign=\"top\" width=\"145\">data<\/td>\n<\/tr>\n<tr>\n<td valign=\"top\" width=\"50\">0<\/td>\n<td valign=\"top\" width=\"145\">sweet16<\/td>\n<\/tr>\n<tr>\n<td valign=\"top\" width=\"50\">1<\/td>\n<td valign=\"top\" width=\"145\">sweet16<\/td>\n<\/tr>\n<tr>\n<td valign=\"top\" width=\"50\">2<\/td>\n<td valign=\"top\" width=\"145\">??? (unused)<\/td>\n<\/tr>\n<tr>\n<td valign=\"top\" width=\"50\">3<\/td>\n<td valign=\"top\" width=\"145\">??? (unused)<\/td>\n<\/tr>\n<tr>\n<td valign=\"top\" width=\"50\">4<\/td>\n<td valign=\"top\" width=\"145\">bite<\/td>\n<\/tr>\n<tr>\n<td valign=\"top\" width=\"50\">5<\/td>\n<td valign=\"top\" width=\"145\">??? (unused)<\/td>\n<\/tr>\n<tr>\n<td valign=\"top\" width=\"50\">6<\/td>\n<td valign=\"top\" width=\"145\">??? (unused)<\/td>\n<\/tr>\n<tr>\n<td valign=\"top\" width=\"50\">7<\/td>\n<td valign=\"top\" width=\"145\">??? (unused)<\/td>\n<\/tr>\n<tr>\n<td valign=\"top\" width=\"50\">8<\/td>\n<td valign=\"top\" width=\"145\">tanga<\/td>\n<\/tr>\n<tr>\n<td valign=\"top\" width=\"50\">9<\/td>\n<td valign=\"top\" width=\"145\">tanga<\/td>\n<\/tr>\n<tr>\n<td valign=\"top\" width=\"50\">\u2026<\/td>\n<td valign=\"top\" width=\"145\">\u2026<\/td>\n<\/tr>\n<tr>\n<td valign=\"top\" width=\"50\">25<\/td>\n<td valign=\"top\" width=\"145\">last character of tanga<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>&#160;<\/p>\n<p>Is this a waste of memory? Sure. But processors can access those addresses a bit faster than other addresses. So it&#8217;s an performance\/memory tradeoff. <\/p>\n<p>After some more testing, I figured out that the correct Pack-value for Win7\/64 is 8, while the correct Pack-value for Win7\/32 is 2 (see former post). Why 2? I&#8217;d expect 4 here. I don&#8217;t know and Microsoft wouldn&#8217;t provide the source code I guess.    <br \/>Maybe in former Windows version they preferred a middle-course between performance and saving memory. <\/p>\n<h3>The simple solution<\/h3>\n<p>Now it was obvious how to make die ShellLib-assembly work with 32 and 64bit: Check what machine we run on and use a different marshalling. Since I had to declare different structs here, the major code is copying data back and forth, not very interesting.<\/p>\n<p>The only interesting part here is: How do you check on what kind of machine you run? I was looking for some property at System.Environment, but didn\u2019t find anything. Then <a href=\"http:\/\/blog.aheil.de\/\">Andreas<\/a> pointed me to <a href=\"http:\/\/blogs.msdn.com\/kstanton\/archive\/2004\/04\/20\/116923.aspx\">this<\/a> post and the solution is too simple to cross one\u2019s mind:<\/p>\n<p>\u201cJust do a <strong>IntPtr.Size<\/strong> (static method) and since IntPtr is designed to be an integer whose size is platform specific, it will be <strong>8 if you are on a 64-bit machine and 4 if you are on a 32-bit machine<\/strong>.\u201c<\/p>\n<p>You can find more information and our fixed code soon at the <a href=\"http:\/\/www.codeproject.com\/KB\/shell\/csdoesshell2.aspx\">codeproject.com<\/a> .<\/p>\n<h3>Epilog<\/h3>\n<p>You can also do the marshalling all by yourself, starting with memory allocation and ending with freeing memory, just like in the old times. But this is another story and will be told later. <\/p>\n<p>Maybe.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Some time ago we blogged about a nifty little .net assembly that enables you to access the basic Windows shell operations in shell32.dll . You may want to do so especially in Win7 because your file operations integrate with the fancy Win7 dialogs, the flashing progress bar etc. The problem we blogged about in the [&hellip;]<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[62,18,73,68],"_links":{"self":[{"href":"https:\/\/www.ticklishtechs.net\/wp-json\/wp\/v2\/posts\/283"}],"collection":[{"href":"https:\/\/www.ticklishtechs.net\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.ticklishtechs.net\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.ticklishtechs.net\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.ticklishtechs.net\/wp-json\/wp\/v2\/comments?post=283"}],"version-history":[{"count":5,"href":"https:\/\/www.ticklishtechs.net\/wp-json\/wp\/v2\/posts\/283\/revisions"}],"predecessor-version":[{"id":434,"href":"https:\/\/www.ticklishtechs.net\/wp-json\/wp\/v2\/posts\/283\/revisions\/434"}],"wp:attachment":[{"href":"https:\/\/www.ticklishtechs.net\/wp-json\/wp\/v2\/media?parent=283"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.ticklishtechs.net\/wp-json\/wp\/v2\/categories?post=283"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.ticklishtechs.net\/wp-json\/wp\/v2\/tags?post=283"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}