Hi
I have a problem with 'large' files. When my setup is greater than 450 MB, the setup does not have icon in windows explorer In file property dialog the 'version tab' is missing too.
It's a little bid curious.
On Vista is this not a problme. Vista can show the icon and the 'verion tab'. But an XP or 2000 machines the icon and the 'version tab' is missing. On FAT32 or NTFS is the same Problem.
Can anyone help me?
Martin
no file icon > 450 mb
4 posts
Search result below, you may use the search feature as well,
Are you a developer who uses NSIS to distribute your application? Are you a Winamp plug-in developer who wants to use NSIS to distribute your plug-in? Have suggestions for other people like you? This is the place.
Thank's Red Wine for your reply.
I have already used the search, but maybe my keywords not the correct one. Sorry.
In the other thread are the reason, that Windows is the bad guy. But ... the post is from 2006. When it's true Microsoft has fixed this problem long ago... ?
The 'icon problem' is negligible for me. The main problem is the missing version information, that i can set with VIAddVersionKey. I have create a .NET Apllication with C#. In this tool i would like to read this version ressource information. The .NET class named FileVersionInfo(). All properties of created instanz if this class are NULL when i read out them from a 'large' setup file.
Is this really a windows bug?
I have already used the search, but maybe my keywords not the correct one. Sorry.
In the other thread are the reason, that Windows is the bad guy. But ... the post is from 2006. When it's true Microsoft has fixed this problem long ago... ?
The 'icon problem' is negligible for me. The main problem is the missing version information, that i can set with VIAddVersionKey. I have create a .NET Apllication with C#. In this tool i would like to read this version ressource information. The .NET class named FileVersionInfo(). All properties of created instanz if this class are NULL when i read out them from a 'large' setup file.
Is this really a windows bug?
Yes, this is a Windows bug/feature/limitation.