This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
Binary table extraction
Started by
tara
, Nov 02 2004 14:10
8 replies to this topic
Posted 02 November 2004 - 14:10
Hello,
Our applications use a serial number validation dll (VC++).
This validation program works seamlessly with our customers in Germany.
However our applications can not be installed in China, whenever setup is started the message pops up 'Datei NeueBindateil konnte nicht aus Bin_rtabelle extrahiert werden' which essentially means 'the date Neue_Bindateil' could not be extracted from the Binar_tabelle'.
We use Installshield express version3.03 German version.
Any help would be highly appreciated.
Tara
Our applications use a serial number validation dll (VC++).
This validation program works seamlessly with our customers in Germany.
However our applications can not be installed in China, whenever setup is started the message pops up 'Datei NeueBindateil konnte nicht aus Bin_rtabelle extrahiert werden' which essentially means 'the date Neue_Bindateil' could not be extracted from the Binar_tabelle'.
We use Installshield express version3.03 German version.
Any help would be highly appreciated.
Tara
Posted 02 November 2004 - 16:29
Could be a problem with their temp folder (either full, or path too long). As a test let them create a folder C:\Temp and set the TEMP environment variable to that folder (personal and global environment).
Also a log file of the install might tell you which path Windows Installer is trying to use to extract the binary file.
Also a log file of the install might tell you which path Windows Installer is trying to use to extract the binary file.
Stefan Krüger
InstallSite.org twitter facebook
Posted 23 November 2004 - 14:21
Another question-is there a way we can work around the problem so that our Chinese customers need not rename their temp folder?
Posted 24 November 2004 - 20:04
You could write your own extraction code and extract the file to somewhere else. Or isntall the file with your application and run it from INSTALLDIR.
Stefan Krüger
InstallSite.org twitter facebook
Posted 26 November 2004 - 11:27
thanks for the tip! shall try and work it out. any tips on writing the extraction code?
Posted 27 November 2004 - 17:45
Stefan Krüger
InstallSite.org twitter facebook
Posted 24 January 2005 - 16:12
An update, our Russian customers are unable to install our products, same problem 'BInary table could not be extracted'. Renaming the Temp directory and deleting prior contents of 'Temp' directory have not helped.
Any workarounds-separate extraction code has been suggested but it will be a while till it is implemented.
Thanks Tara
Any workarounds-separate extraction code has been suggested but it will be a while till it is implemented.
Thanks Tara
Posted 25 January 2005 - 16:10
Stefan,
If it has not been done already in later versions, you should suggest to InstallShield that they update their next release to locate folders in the Win namespace using the pidl instead of the folder name. PIDLs are unique binary identifiers that windows uses internally. They should be language and culture independent.
If it has not been done already in later versions, you should suggest to InstallShield that they update their next release to locate folders in the Win namespace using the pidl instead of the folder name. PIDLs are unique binary identifiers that windows uses internally. They should be language and culture independent.