<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>davesmith Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>davesmith Tracker</description>
    <pubDate>Sat, 25 Nov 2023 10:45:19 GMT</pubDate>
    <dc:date>2023-11-25T10:45:19Z</dc:date>
    <item>
      <title>Thinapp, MS Access and Vista 64 - %CommonProgramFiles(x86)% not resolved</title>
      <link>https://communities.vmware.com/t5/ThinApp/Thinapp-MS-Access-and-Vista-64-CommonProgramFiles-x86-not/m-p/2547781#M6236</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I guess this is a simple problem, but maybe not a simple solution.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have an app that creates a COM object of Access and controls an access database. Access is installed on every machine that we will run the Thinapp'd application on, so we don't need to virtualize Access. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have set VirtualizeExternalOutOfProcessCOM = 0, so that COM objects are handled in the HOST environment and this works fine for Word and Excel. However, using procmon I have seen that there is a problem with launching Access.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;From the virtualized application it is unable to load the DLL "dao.dll". Running the application "un-virtualized" does not result in an error. Investigation shows the following:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;The reg value "HKCR\Wow6432Node\TypeLib\{00025E01-0000-0000-C000-000000000046}\5.0\0\win32\(Default)" is queried and returns "%CommonProgramFiles(x86)%\Microsoft Shared\DAO\dao360.dll"&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;The UN-virtualized application then accesses file "C:\Program Files (x86)\Common Files\microsoft shared\DAO\dao360.dll" successfully&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;The virtualized app tries to access "Z:\%CommonProgramFiles(x86)%\Microsoft Shared\DAO\dao360.dll" where Z:\ is the folder that I'm running the virtualized application from.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It shows that we are not resolving %CommonProgramFiles(x86)% at all.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have seen something that may be the cause, though it is old:&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.eggheadcafe.com/software/aspnet/32819766/problems-with-createnviro.aspx" target="test_blank"&gt;http://www.eggheadcafe.com/software/aspnet/32819766/problems-with-createnviro.aspx&lt;/A&gt;&lt;/P&gt;&lt;P&gt;It talks about processes created with "CreateEnvironmentBlock" do no inherit %CommonProgramFiles(x86)% in Vista 64&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Checking that environment variable in MY application shows that it is present, however I'm not able to test the COM environment.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Has anyone seen anything like this, or could throw some light onto the solution?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Dave Smith&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 Jun 2009 19:31:37 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/Thinapp-MS-Access-and-Vista-64-CommonProgramFiles-x86-not/m-p/2547781#M6236</guid>
      <dc:creator>davesmith</dc:creator>
      <dc:date>2009-06-30T19:31:37Z</dc:date>
    </item>
    <item>
      <title>Re: Problem opening an existing VMWare machine (gnome-vfs-2.0/.../libfile.s</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Problem-opening-an-existing-VMWare-machine-gnome-vfs-2-0-libfile/m-p/1499822#M83884</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Kevin that worked...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;VMWARE_USE_SHIPPED_GTK=force vmware&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Doesn't look all nice and smooth as my current GTK, but I can click open now.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'll try swapping back in a few months, or after vmware workstation 6 comes out!!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks again&lt;/P&gt;&lt;P&gt;Dave&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Message was edited by: &lt;/P&gt;&lt;P&gt;        davesmith&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 18 Mar 2007 04:01:16 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Problem-opening-an-existing-VMWare-machine-gnome-vfs-2-0-libfile/m-p/1499822#M83884</guid>
      <dc:creator>davesmith</dc:creator>
      <dc:date>2007-03-18T04:01:16Z</dc:date>
    </item>
    <item>
      <title>Re: Problem opening an existing VMWare machine (gnome-vfs-2.0/.../libfile.s</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Problem-opening-an-existing-VMWare-machine-gnome-vfs-2-0-libfile/m-p/1499820#M83882</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Actually, no.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;gcc 4.1.1-15 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It's not been released yet, looking at the GCC homepage (http://gcc.gnu.org/)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do you think it's the debian libraries, or the vmware libraries at fault? I can't imagine it's a vmware requirement to have GCC 4.2 installed &lt;img id="smileywink" class="emoticon emoticon-smileywink" src="https://communities.vmware.com/i/smilies/16x16_smiley-wink.png" alt="Smiley Wink" title="Smiley Wink" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Shall I go chasing a debian email list??&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Dave&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 17 Mar 2007 21:37:27 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Problem-opening-an-existing-VMWare-machine-gnome-vfs-2-0-libfile/m-p/1499820#M83882</guid>
      <dc:creator>davesmith</dc:creator>
      <dc:date>2007-03-17T21:37:27Z</dc:date>
    </item>
    <item>
      <title>Problem opening an existing VMWare machine (gnome-vfs-2.0/.../libfile.so)</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Problem-opening-an-existing-VMWare-machine-gnome-vfs-2-0-libfile/m-p/1499818#M83880</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Morning!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I installed the latest VMware Workstation and every time I click File-&amp;gt;Open, the VMware workstation hangs and I get these messages in the console I started vmware from.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(vmware:7717): libgnomevfs-WARNING **: Cannot load module `/usr/lib/gnome-vfs-2.0/modules/libfile.so' (/usr/lib/vmware/lib/libgcc_s.so.1/libgcc_s.so.1: version `GCC_4.2.0' not found (required by /usr/lib/libstdc++.so.6))&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm running Debian GNU/Linux 4.0, which is 'Etch'.&lt;/P&gt;&lt;P&gt;Kernel: 2.6.18-3-k7 (not that I think that's the problem!)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anyone have any suggestions of what other information is useful??&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Dave Smith&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 17 Mar 2007 15:56:21 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Problem-opening-an-existing-VMWare-machine-gnome-vfs-2-0-libfile/m-p/1499818#M83880</guid>
      <dc:creator>davesmith</dc:creator>
      <dc:date>2007-03-17T15:56:21Z</dc:date>
    </item>
  </channel>
</rss>

