Re: SMS Installer cannot make right package file.

Sounds like you have some issues with your registry keys values.
If you know the target goes to the wrong place then I would change it in
your script and recompile.
Just go through the captured registry settings and edit them to be what you
need. While there clean up the reg keys you don't need.
Sounds like (since it works from the program files area) that it is mostly
right, just making a few corrections to the registry keys captured should
help.

Terry

"Ku" <Ku@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:01F1439B-9CEF-432F-8E53-01A0C8A71DD4@xxxxxxxxxxxxxxxx
> Sir/Mamm
>
> I tried to make one exe file with Software, "ATTACHMATE MyExtra8".
> It seems like SMS Installer worked well but if I install with the exe file
> to another computer, The software runs not right.
>
> The status after installation is,
> 1. If I run the software through Start-programs-attachmate-myextra",
> Nothing
> happens. I found that Target is
> "C:\WINDOWS\Installer\{8C268131-98C2-4D12-8F10-5A8C33517372}\EXTRA_Enterprise.exe"
> and Start in ""C:\Program Files\Attachmate\EXTRA!\" in the shortcut
> properties.
> The target points wrong place.
>
> 2.There is *.EDP file that must be opened by the software. I tried to
> connect the software manually but I could't. The thing weird is It's
> possible to run the software if I go to the programs folder manually but I
> cannot connect the software with "Open with" option.
>
> I think there is some comflict problem with "Windows Installer" so I tried
> to make the EXE file to MSI with ISU Command line utility but no chage.
> I fix the first problem with editing the script manually but It took so
> much
> time and
> never solve the second problem.
>
> Please give me som advice. I will appreciate it.
>
> I used SMS installer 2.0.148. 32-bit edition.
> I ran it in Windows XP.
> we will push this through sms2003 in windows server2003.


.

Relevant Pages

  • Re: office update is unable to check for updates
    ... Windows Installer version 1.0 to Windows Installer version 1.1. ... Here is another post I saw on the forums that seems to have work for other users, but it requires advanced knowledge of the OS, basically registry editing, so please be careful if you try it. ... we need to manually delete all the registry keys for Office. ...
    (microsoft.public.officeupdate)
  • Re: newbie Help: HOW to use VBSCript on clientside to detect browser type and version
    ... > number in order to stop the HP installer malfunction. ... > and check for one with "firefox" ... >>> I appreciate any script ... or is it possible to do this through reading registry keys. ...
    (microsoft.public.scripting.vbscript)
  • Re: newbie Help: HOW to use VBSCript on clientside to detect browser type and version
    ... number in order to stop the HP installer malfunction. ... Firefox is awkward because it doesn't register ... so on) on the client side using VBScript. ... or is it possible to do this through reading registry keys. ...
    (microsoft.public.scripting.vbscript)
  • Fix for Office install fails and Install popups
    ... Tried the often suggested method of using the Windows Installer Cleanup ... aware that it involves a lot of registry editing, but it did fix ALL of my ... If you use Registry Editor ... Delete the following registry keys if they exist: ...
    (microsoft.public.office.setup)
  • Error 80070003 on Windows Updates
    ... Automatic updates fail, when I force a Windows update, it fails, and when I ... Here is the bottom of the windows update log... ... Target version: 5.5.3790.2182 Required: 5.5.3790.2182 ... Installer returned 0x3 ...
    (microsoft.public.windowsupdate)