PSF tool DynamicLibraryFixup32.dll fix issue @ config.jason file

%3CLINGO-SUB%20id%3D%22lingo-sub-2566302%22%20slang%3D%22en-US%22%3EPSF%20tool%20DynamicLibraryFixup32.dll%20fix%20issue%20%40%20config.jason%20file%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2566302%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20All%2C%3C%2FP%3E%3CP%3E%26nbsp%3BI%20created%20an%20MSIX%20package%20with%20the%20help%20of%20Timothy%20Mangan%20PSF%20Tool%20available%20in%20MS%20Store.%20Injected%20all%20required%20fixes%20like%26nbsp%3BDLL%20Fixup%20and%20File%20Redirection%20Fixup%20for%20a%2032%20Bit%20application.%3C%2FP%3E%3CP%3EAs%20the%20application%20is%2032%20bit..%20the%20PSF%20Tool%20copied%20all%20required%20PSF%20file%26nbsp%3BDynamicLibraryFixup32.dll%2C%26nbsp%3BFileRedirectionFixup32.dll%2C%20PSFLauncher32.exe%2C%20PSFRuntime32.dll%20etc..%20to%20somewhere%20in%20VFS%20folder.%20but%20my%20question%20is%20when%20I%20cross%20check%20the%20config.json%20file%20content..%20instead%20of%20seeing%20information%20of%2032%20bit%20DLLs%20like%26nbsp%3BFileRedirectionFixup32.dll%2C%26nbsp%3BDynamicLibraryFixup32.dll%2C%20I%20saw%26nbsp%3BFileRedirectionFixup.dll%2C%20DynamicLibraryFixup.dll.%3C%2FP%3E%3CP%3E1.%20Please%20suggest%20whether%20this%20will%20work%20or%20not%3F%20because%20the%20copied%20files%20were%20xxxxx32.DLLs%2C%20but%20in%20json%20file%20we%20have%20xxxxxxx.DLLs%3F%3C%2FP%3E%3CP%3E2.%20Even%20though%20I%20applied%20the%20fixes%20the%20DLL%20issues%20with%26nbsp%3BDynamicLibraryFixup32.dll%2C%20the%20application%20is%20not%20working%20as%20expected.%20My%20application%20is%20looking%20for%20NSTRC.dll%20at%20%22VFS%5CProgramFilesX86%5CIBM%5CPersonal%20Communications%22%20instead%20of%20%22VFS%5CProgramFilesX86%5CIBM%5CTrace%20Facility%22%20and%20this%20location%20was%20already%20available%20in%20json%20file.%3C%2FP%3E%3CP%3E3.%20Later%20as%20a%20part%20of%20troubleshoot%2C%20I%20placed%20one%20more%20copy%20of%20the%20required%20NSTRC.dll%20at%20%22VFS%5CProgramFilesX86%5CIBM%5CPersonal%20Communications%22%20and%20the%20application%20shortcut%20started%20working%2C%20Is%20this%20the%20only%20work%20around%20to%20resolve%20the%20issue%2C%20or%20do%20have%20any%20other%20work%20around%20to%20do%20in%20json%20file%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20suggest%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F146612%22%20target%3D%22_blank%22%3E%40TIMOTHY%20MANGAN%3C%2FA%3E%3C%2FP%3E%3CH4%20id%3D%22toc-hId-292341236%22%20id%3D%22toc-hId-292341271%22%3EThanks%20in%20Advance.%3C%2FH4%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2566302%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EDLL%20Fixup%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EDynamicLibraryFixup32.dll%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Contributor

Hi All,

 I created an MSIX package with the help of Timothy Mangan PSF Tool available in MS Store. Injected all required fixes like DLL Fixup and File Redirection Fixup for a 32 Bit application.

As the application is 32 bit.. the PSF Tool copied all required PSF file DynamicLibraryFixup32.dll, FileRedirectionFixup32.dll, PSFLauncher32.exe, PSFRuntime32.dll etc.. to somewhere in VFS folder. but my question is when I cross check the config.json file content.. instead of seeing information of 32 bit DLLs like FileRedirectionFixup32.dll, DynamicLibraryFixup32.dll, I saw FileRedirectionFixup.dll, DynamicLibraryFixup.dll.

1. Please suggest whether this will work or not? because the copied files were xxxxx32.DLLs, but in json file we have xxxxxxx.DLLs?

2. Even though I applied the fixes the DLL issues with DynamicLibraryFixup32.dll, the application is not working as expected. My application is looking for NSTRC.dll at "VFS\ProgramFilesX86\IBM\Personal Communications" instead of "VFS\ProgramFilesX86\IBM\Trace Facility" and this location was already available in json file.

3. Later as a part of troubleshoot, I placed one more copy of the required NSTRC.dll at "VFS\ProgramFilesX86\IBM\Personal Communications" and the application shortcut started working, Is this the only work around to resolve the issue, or do have any other work around to do in json file?

 

Please suggest @TIMOTHY MANGAN

Thanks in Advance.

 

 

0 Replies