Package upgrade 4.2 -> 4.5. 16bit app issue

• Question

• 

  

  0

  Sign in to vote

  Hi There,
  
  I have been going through the process of upgrading my 4.2 Packages to 4.5 packages (as well as updating the deployment hostname as they were previously hardcoded to a servername) and have come across one app that is causing a few issues.
  
  The application uses 16bit DLLs to access a database, which are in the VFS in the %windows%\system directory.  Under 4.2 they worked fine.  Upon upgrading the package I keep getting an application error which the software documentation points to wrong DLL versions or a missing DLL.
  
  I have tried to resequence the installation ensuring the DLLs and ini files are included in the VFS.
  
  I have tried setting the <VM VALUE="Win32">  and <VM VALUE="Win16">  however this does not seem to make any difference.
  
  Within the 4.5 package OSD i have used the "Application Virtualization SFTInfo" tool to export the XLM of the SFT package.  I have been able to locate the 2 files that it needs:
  
  

      <IndexEntryV1>
        <EntryVersion>0x1</EntryVersion>
        <FileID>{EE7E31D7-AAF0-4B68-8D6B-D4CEDD32564C}</FileID>
        <ParentID>{6D806E03-40F2-497A-908F-40FC77EC3985}</ParentID>
        <FileNameLength>0x7</FileNameLength>
        <ShortFileNameLength>0x7</ShortFileNameLength>
        <FileName>win.ini</FileName>
        <ShortName>WIN.INI</ShortName>
        <FattrV1>
          <FileType>1 : READONLY</FileType>
          <FileSize>0x1EB</FileSize>
          <FileAttributes>0x20</FileAttributes>
          <SoftricityFileType>0x8</SoftricityFileType>
          <OwnerID>0x108004E</OwnerID>
          <PrimaryGroupID>0x3E0248</PrimaryGroupID>
          <DateCreated>09/24/09 08:58:36</DateCreated>
          <DateModified>01/27/09 17:12:03</DateModified>
          <DateAccessed>09/24/09 08:58:36</DateAccessed>
          <SecurityDescriptorIndex>0x74E</SecurityDescriptorIndex>
        </FattrV1>
      </IndexEntryV1>

  
  
  

    <IndexEntryV1>
        <EntryVersion>0x1</EntryVersion>
        <FileID>{08AA7B63-6CF8-4EAE-AE10-8701766B0900}</FileID>
        <ParentID>{B1C54982-70A7-442A-970B-88CF664E1BDB}</ParentID>
        <FileNameLength>0xB</FileNameLength>
        <ShortFileNameLength>0xB</ShortFileNameLength>
        <FileName>COMPOBJ.DLL</FileName>
        <ShortName>COMPOBJ.DLL</ShortName>
        <FattrV1>
          <FileType>1 : READONLY</FileType>
          <FileSize>0x1AA00</FileSize>
          <FileAttributes>0x20</FileAttributes>
          <SoftricityFileType>0x1</SoftricityFileType>
          <OwnerID>0x73005C</OwnerID>
          <PrimaryGroupID>0x730079</PrimaryGroupID>
          <DateCreated>09/24/09 08:55:30</DateCreated>
          <DateModified>01/12/96 01:00:00</DateModified>
          <DateAccessed>09/24/09 08:58:36</DateAccessed>
          <SecurityDescriptorIndex>0x65B</SecurityDescriptorIndex>
        </FattrV1>
      </IndexEntryV1>

  
  
  Doing a manual install of the same application (not via APPV), the 16bit DLLs work fine.  I want to avoid this if i can.
  
  I've been working on this for the past couple days and its been driving me loopy!  I have not been able to find too many other solutions through this forums or google etc.
  
  any help or other suggestions would be awesome.
  
  Thanks in advanced
  
  
  

  • Edited by PeterGGG Thursday, September 24, 2009 1:46 AM formating

  Thursday, September 24, 2009 1:43 AM