Software Deployment

The sugesture i have when you use wise is to turn off registration the dll's in the package. The most time .NET application do not need dll registation.
Sometimes vendors want do discurrage with technical limitations to use the msi wrapped in there installer.
Only way is then repackaging.sometimes it can be faster then figuring it out what <CENCUUR> the vendor made this time :)

Hi folks,
@HabMan: Did you log this installation?
Does the "Error Loading Hasher DLL" message only apear on the install from the admin image or generally?
Check, if the AdminXxx tables in the MSI are well populated (compare with a working MSI or with the examples from the SDK).
Start the installation with the setup.exe and check the "Command line" entry in the resulting log file. Maybe some fancy stuff set there from the "setup.exe".

@Arco (Cybermage): Real cool medicine: If something aches, make the symptoms go away (even though, i have to admit, it's a well known and often used procedure in the "modern" society...)!
And if the problem is still there, leave it alone an create bunch of new ones! Working on the new ones is more fun, because you created them by yourself... ;-)

Regards, Nick

Habman, did you figure this out? I'm having the same problem with PrintShop22. I've created my MST using WPS and push it w/o a problem. Completes the whole install and errors out at the end with the Hasher.dll error. I can start Printshop if I don't clilck OK on the error, but as soon as I do, msiexec uninstalls the application. I did look in the Tables area of the MSI and found hasher.dll in one of the ISSetupfile tables. I don't know if I want to delete it or not. Wanted to see if you had made any progress.

They still make Printshop? I remember owning a copy of that on 5 1/4" floppy that would run on my 8088. We'd print Xmas cards on our dot matrix printer and wow the neighbours.

ORIGINAL: turbokitty

They still make Printshop? I remember owning a copy of that on 5 1/4" floppy that would run on my 8088. We'd print Xmas cards on our dot matrix printer and wow the neighbours.



LOL scary, I remember doing the same thing. Ok, not Xmas cards, but other fun stuff on dot matrix (Star Micronics if I recall correctly)

Holy crap we're old...

[blockquote]quote:

ORIGINAL: turbokitty

They still make Printshop? I remember owning a copy of that on 5 1/4" floppy that would run on my 8088. We'd print Xmas cards on our dot matrix printer and wow the neighbours.
[/blockquote]
LOL scary, I remember doing the same thing. Ok, not Xmas cards, but other fun stuff on dot matrix (Star Micronics if I recall correctly)

Holy crap we're old...

I ran it on an Apple ][e computer with the "ahead of it's time" Apple Color Imagewriter II printer.....color was a luxury at that time. But I don't think you're old unless you grew up with only a B&W Television. [:D]

I hope what this message thread turned into is ok with the moderators.....[8|]

You had a television?!?

Habman, I had to edit the Custom Action table in my transform. I removed the HashIt entry from the custom action and saved the transform. This got rid of the hasher.dll error during installation.

Although I've seen the '/t' switch documented, I stopped using it eons ago when I couldn't get it to work

For what it's worth: /t is only applicable if you are advertising a package using either /jm or /ju switches.

You have to use TRANSFORMS= if you are doing a /i install. Also - transforms doesn't have to be in uppercase - although I think did with older versions of windows installer [8|]

Cheers,
Rob.

Although I've seen the '/t' switch documented, I stopped using it eons ago when I couldn't get it to work (in my early packaging days). Instead, use the 'TRANSFORMS' keyword with an equals sign. Think of it as a special property (which must be all in upper-case, BTW):

msiexec /i "The Print Shop 21.msi" TRANSFORMS="The Print Shop 21.mst" [other_cmd_line_arguments]

May all my problems be simple ones.

Never had this issue before. Used /t switch on dozens of apps, but this time it matter.

That seems to have done the trick. Thank you.

Just wanted to all this, to share my woes, and discovery, once the install started it failed very near completion with this --> "error loading hasher dll"

Found the fix on broderbund.com --> Problem Finding Registry Keys for Hashing

http://support.broderbund.com/fix.asp?isid=42503&prog=1294820872&printer=1

Error Loading Hasher DLL - Microsoft .net framework needs installed.

With as many apps as I have seen the need for .NET, it will go as a standard app to be installed as part of the workstation image, but just wondering, Is this something a setup should look for?

I'm not sure I understand what exactly you're asking but I am a firm believer in defensive programming such that, even in the environment in which I'm currently working, where .Net F/W 2 is installed (either in the image for one site or by machine-based GP depolyment in the others), my MSIs still check for it. Remember what ASSUME did? :)

Would like to make an admin install of Print Shop 22. Run msiexec /a "The Print Shop 22.msi" and it appears to make a good admin install.

Run from admin install msiexec /i "The Print Shop 22.msi"

Goes through entire install, and at the end, hangs on "Error Loading Hasher DLL"

Research of this error shows it to be a dot.net issue.

The workstations in question have dotnet versions 1.1 and 2.0 on them, and all up to date MS updates.

I have Procmon running during the install, but need some advice on using it. I am trying to learn to use Procmon. The amount of info it gathers is overwhelming.

I went to Broderbund's web site, and filled out a technical help form, with the above issue.

I received a reply back from Broderbund, telling me for support for this product use this link, to EncoreSoftware.

I fill out the form at EncoreSoftware, with exactly the same information, as I have it stated on the previous post.

Here is the reply back from EncoreSoftware ... [font="verdana,arial"]"The program should not be installed from an msi, it should be installed D;\Setup\Setup.exe I'm not sure how it is that you are tring to install this program"

If it were up to me, I'd just use Publisher!!!