Re: "The Publisher could not be verified. etc."

That's connected with the changes that Microsoft
made in SP2. If SP2 is installed then IE nags
about many downloaded files. If they don't use IE
they can avoid that.

The warning sticks because they used IE to
download *and* they have XP installed on NTFS.
SP2 uses a hidden alternate data stream (ADS) file,
named "Zone.Indentifier", to mark files with the zone
they came from when downloaded through IE.
Windows then treats those files, from then on, as though
they were running from the Internet!

Moving the EXE to a FAT32 partition (or floppy)
and back should remove the warning. Only NTFS
supports hidden ADS files.

For more on fixing the SP2 nags see here:

http://www.jsware.net/jsware/iewacky.php3

For an ADS viewer see here. (It's a property
*** handler that installs an extra tab for all
file and folder "Properties" context menus, allowing
hidden ADS files to be viewed and deleted):

http://www.jsware.net/jsware/sviewer.php3


>
> I've written and installed a VB6 application for one of my customers.
> After a while this customer requested some changes in the program and I
made
> a new exe.
> In a stroke of genius I put the exe on the web, so the customer could
> download it himself (saves me the petrol!)
> Since then they get the message "The publisher could not be verified.
etc."
> This warning could make sense if one is trying to run a program from the
> internet, but I wonder where it is logged that this new exe did not come
on
> a CD as I usually do, but through the Internet, which perhaps was not so
> smart afterall :)
> I googled the world over this but it all comes down to either hacking the
> customer's registry or paying $$$$'s every year to Verisign.
> But then I'm still curious: How does their WinXP-SP2 know where the exe
came
> from? Is it some kind of file-attribute?
> And how can I make him forget?
>
> Thanks in advance
> Kees
>
>


.

Loading