Openings in “Mindtree”, Bangalore for “Application packaging”

Openings in “Mindtree”, Bangalore for “Application packaging”

FROM: bhavya@logiprosoftware.com

Hi,

Warm Greetings from Logipro Software Ltd .

This is regarding openings in “Mindtree”, Bangalore for “Application packaging” Professionals.

Skills : Application packaging or Repackaging or Wise Packaging or MSI or Install shield

Exp: 2 – 5 yrs

Type of Job: Permanent

Notice period:

Location: Bangalore

If interested, please send your updated resume in word format to bhavya@logiprosoftware.com with following:

Current CTC:

Expected CTC:

Notice Period:

Present Address:

Contact Details:

or forward it to your friends who are looking for a change.

Note: If this requirement does not match your profile please ignore this mail.

Thanks & Regards,
Bhavya
HR-Executive,
Logipro Software,
Bangalore.
Phone No:+91-80-40171713/40171700
E-mail:bhavya@logiprosoftware.com
URL: www.logiprosoftware.com

Tagged :

Tarma Installer 5.8.3681 (Windows)

created the topic: Tarma Installer 5.8.3681 (Windows)
Tarma Installer creates stand-alone software installers for Microsoft Windows platforms, including 64-bit and Windows mobile, with a small distribution size, a straightforward and clean user interface, and smart install and uninstall behavior. Professional software installer in less than 100 KB. Installs and removes programs, documents, images, multi-media files, TrueType, and OpenType fonts, .Net assemblies, ActiveX controls, COM servers, type libraries, WinHelp files, device drivers, services, registry updates, INI files, environment variables, program groups, shortcuts, and third-party tools. Platform-dependent installations allow you to specify the exact Windows versions for each installation item. Single-file self-extracting packages with authenticode signatures for secure Internet downloads, CD-ROM distribution, or any other channel.

Tagged :

window installer at startup keeps coming on and I cant remove it!

created the topic: window installer at startup keeps coming on and I cant remove it!

Question:

I have windows xp . I have a HP desktop computer…at startup I have a window trying to load called “window installer” I have to keep clicking cancel until it goes away…sometimes it trys to come back and I will click cancel continousley and it goes away then I open up my internet explorer and Iam alright. I have tried different free downloads to remove it and have gone into add/change/remove and have removed it from there but it dosent go away even with reboot. I also have an icon at bottom right of my screen that says “intel (r) graphics” and have tried to remove it from add/change/remove and it comes back…this seems to be slowing down my computer and especailly my startup…thank you for any advice! I just want to get rid of these pesky tagalongs but cant seem to budge them…

Answer
I would let the installer complete the installation and ounce complete you can choose to remove what was installed if you don’t want it.
As for Intel Graphics it sounds like part of your MoBo driver pack, what makes you think it’s a pesky tag along?

Tagged :

How do you install all windows updates after a workstation rebuild?

created the topic: How do you install all windows updates after a workstation rebuild?
I’m looking for a way to have windows updates get slipstreamed or auto installed so that when I rebuild a workstation and it gets to the logon screen it’s fully patched and up-to-date. I’m trying to secure some funds to purchase SpecOps Deploy 4.0 (leverages WDS), but if not i’ll probably remain on Fog. I would have WSUS setup as well.

The way I see if i’ve got a few options:

* Capture an image that already has had Windows Update manually run – the problem here is i doubt i’m going to end up with one image, more likely it will be 3 or more. I don’t want to have to keep refreshing images and potentially damaging the images just to install a couple of updates.
* Manually setup each individual update and deploy it like an application – similar to how our current CC3 system operates, this appeals to me as management is more central but updates would be delayed and I would have to assume that all MS updates would be friendly to the process.
* Find a way / buy a program to mount the WIM images and inject the updates – I’ve been told this is potentially a future development for Deploy 4.0, but I haven’t found anything else that would do it.
* Buy a program called WuInstall Pro – This is actually really cheap for education, $250 for unlimited client use. It’s a command line utility that can apparenty install all Windows updates, accepting the EULAs as you go. This could be scripted into the build somewhere and appears to be exactly what I need.

Anyone know of any other way to guarantee that a newly built workstation is up to date? I don’t mind the standard WSUS to keep them up to date, but I don’t want anything being used half patched.

Tagged :

Windows Installer Module stopped working – Trustedinstaller.exe

created the topic: Windows Installer Module stopped working – Trustedinstaller.exe
Windows Installer Module stopped working while trying to install Updates

(Standalone as well as through the automatic update)

The installation starts and runs about halfway, then it stops and the message “Windows Installer Module stopped working”

Is displayed

Smaller updates still install – I have problems with these two for the moment

IE8-Windows6.0-KB978207-x86

Windows6.0-KB947821-v7-x86

The second update was posted as an update to install to get rid of the problem but it won’t install either.

I have already tried to re-register dll, delete software distribution folder and a few other things but nothing had an effect.

I run Windows Vista SP1 – 32bit version

The problem is shown below

Problem signature

Problem Event Name: APPCRASH

Application Name: TrustedInstaller.exe

Application Version: 6.0.6002.18005

Application Timestamp: 49e01af1

Fault Module Name: smiengine.dll

Fault Module Version: 6.0.6002.18005

Fault Module Timestamp: 49e0380d

Exception Code: c0000005

Exception Offset: 00039d20

OS Version: 6.0.6002.2.2.0.768.3

Locale ID: 2057

Additional Information 1: a949

Additional Information 2: ab7e38a5a24996f4fde5627a15dd846d

Additional Information 3: 6cef

Additional Information 4: 8e6c9db2ffb957e9511ebdf1317d0af3

Extra information about the problem

Bucket ID: 1673420669

Description

A Windows update did not install properly. Sending the following information to Microsoft can help improve the software.

Problem signature

Problem Event Name: WindowsUpdateFailure

ClientVersion: 7.4.7600.226

Win32HResult: 80070643

UpdateId: 577EABBB-24AF-4769-A808-3151329F1760

Scenario: Install

SourceId: 101

Environment: Unmanaged

OS Version: 6.0.6002.2.2.0.768.3

Locale ID: 2057

Extra information about the problem

Bucket ID: 940489917

msiexpert replied the topic: Re: Windows Installer Module stopped working – Trustedinstaller.exe
What anti-virus application or security suite is installed and is your subscription current? What anti-spyware applications (other than Defender)? What third-party firewall (if any)?

Has a(another) Norton or McAfee application ever been installed on the computer (e.g., a free-trial version that came preinstalled when you bought it)?

See the “How to obtain help” section of support.microsoft.com/kb/978207

For home users, no-charge support is available by calling 1-866-PCSAFETY (and/or 1-866-234-6020 and/or 1-800-936-5700) in the United States and in Canada or by contacting your local Microsoft subsidiary. There is no-charge for support calls that are associated with security updates. When you call, clearly state that your problem is related to a Security Update and cite the update’s KB number (e.g., KB978207).

Or you can…

Start a free Windows Update support incident request:
support.microsoft.com/oas/default.aspx?gprid=6527

The Consumer Security Support home page & Microsoft Update Solution Center also offer support options
consumersecuritysupport.microsoft.com/
support.microsoft.com/ph/6527#tab3

replied the topic: Re: Windows Installer Module stopped working – Trustedinstaller.exe
I use Comodo Internet Security as well as Avira AntiVir. I already tried to install the update with both disabled from start up & UAC turned off. That had no effect.

I think there was Norton 360 internet security installed when I bought the computer. I uninstalled it and replaced it by Comodo. That is about 2 years ago and I never had any problems until last week.

I don’t know if it is just running for to long and files got corrupted somehow.

I run SFC which came back with the reply “corrupted files were found but windows was not able to repair them”

msiexpert replied the topic: Re: Windows Installer Module stopped working – Trustedinstaller.exe
1. You should only have one (1) anti-virus application installed and loading at boot. Assuming you’ve purchased Comodo Internet Security, uninstall Avira AntiVir & reboot.

Moving on, Norton (and McAfee) applications are notorious for not uninstalling (or upgrading) cleanly:

2. Download the Norton Removal Tool, saving it to your desktop: ftp://ftp.symantec.com/public/english_us…ton_Removal_Tool.exe

3. Close all open applications (i.e., anything with an icon on the taskbar).

4. Right-click on the file you saved in #1 above and select Run as Administrator to run the utility. Don’t TOUCH your keyboard until the run completes, then reboot once more.

5. See if the updates will install now. If not, open a free support incident ASAP.

Tagged :

Wise Package Studio

created the topic: Wise Package Studio
Important Configuration Information

* Wise Package Studio uses the NSAdmin user to run its services. If the password or permissions for this user are changed, WPS may not function properly.
* Since WPS is a per user license, it will only work under the user who installed it. Otherwise, an error about invalid serial numbers will appear when running.
* Batmobile hosts the SQL databases needed by WPS.
o Workbench Database
o Software Manager Database
o Wise Services Database
* The Wise Share Point is located on LSAltiris at c:\Wise Share Point.
* When running the WPS Workbench it prompts for an admin password. It is currently blank.
* We have a license for the web features of the program, but they require .NET 1.1. That version is installed on LSAltiris, but so is .NET 2.0. So, the installer does not see version 1.1 without removing version 2.0 first. Since LSAltiris is already in production, I did not want to uninstall an reinstall .NET.
* If prompted for an admin password when opening up the Workbench, there is no password.

Client Information

There is a virtual machine that acts as a client for the program. This way, we do not have to log into LSAltiris when ever we need to use the software.

* The VM is called Wise Package Client, and its host name wpclient.
* The client works on a per-user base. The client software is currently installed under the NSAdmin account. See the “Notepad” in lscs.byu.edu/utilities for the password.
* The client is really just a shortcut that points to the executables on LSAltiris.

Tagged :

Error 1719 The Windows Installer Service could not be accessed.

created the topic: Error 1719 The Windows Installer Service could not be accessed.
My computer keeps giving me this error message when I try to upload updates and other programs. I need to know what to do to fix this. Here is the whole error message:

Error 1719 The Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed. Contact your support personnel for assistance.

msiexpert replied the topic: Re: Error 1719 The Windows Installer Service could not be accessed.
Hi nancywhit,

• Do you remember making any changes to the computer recently?

This may happen if the Windows Installer files that are on your hard disk are damaged or are missing.
You install or remove a program that uses the Windows Installer Microsoft Software Installation (MSI) package file (.msi). For example, this may occur when you try to install Microsoft Office on your computer.

Method 1
First I would suggest that you check if the Windows installer service is running on the computer.

1. Go to “Start” – “Run” type “services.msc” and press on “Enter” button.

2. Double-click on the service named “Windows Installer”

3. Check the value in the “Startup type” field. If it’s currently set to “Disabled”, then this is the problem. Change it by selecting “Manual” from the drop-down box.
Make sure that the service is started and set to Manual.

Method 2
If the above step fails then unregister Windows Installer, and then reregister Windows Installer

To do this, follow these steps:

1. On the “Start” menu, click “Run”

2. In the “Open” box, type “msiexec /unreg”, and then press ENTER

3. On the “Start” menu, click “Run”

4. In the “Open” box, type “msiexec /regserver” and then press ENTER

If the above steps fail then I would suggest that you install the latest version of Windows installer on the computer, refer the below link.

www.microsoft.com/downloads/details.aspx…6f9f4&displaylang=en

replied the topic: Re: Error 1719 The Windows Installer Service could not be accessed.
Hi nancywhit,

• Do you remember making any changes to the computer recently?

This may happen if the Windows Installer files that are on your hard disk are damaged or are missing.
You install or remove a program that uses the Windows Installer Microsoft Software Installation (MSI) package file (.msi). For example, this may occur when you try to install Microsoft Office on your computer.

Method 1
First I would suggest that you check if the Windows installer service is running on the computer.

1. Go to “Start” – “Run” type “services.msc” and press on “Enter” button.

2. Double-click on the service named “Windows Installer”

3. Check the value in the “Startup type” field. If it’s currently set to “Disabled”, then this is the problem. Change it by selecting “Manual” from the drop-down box.
Make sure that the service is started and set to Manual.

Method 2
If the above step fails then unregister Windows Installer, and then reregister Windows Installer

To do this, follow these steps:

1. On the “Start” menu, click “Run”

2. In the “Open” box, type “msiexec /unreg”, and then press ENTER

3. On the “Start” menu, click “Run”

4. In the “Open” box, type “msiexec /regserver” and then press ENTER

If the above steps fail then I would suggest that you install the latest version of Windows installer on the computer, refer the below link.

www.microsoft.com/downloads/details.aspx…6f9f4&displaylang=en

Tagged :

Unvise32.exe

created the topic: unvise32.exe
unvise32.exe was added to FreeFixer’s database on 22nd January 2010. The most recent search for this file was done on 22nd January 2010. unvise32.exe is located in the ‘c:\WINDOWS\’ folder and has a size of 86016 bytes.

So far there has been 1 search for unvise32.exe.

If you have additional information about the file, please share it with the FreeFixer users by posting a comment at the bottom of this page.
Vendor and version information [?]

The following is the available information on unvise32.exe:
Property Value
Product name Installer VISE
Company name MindVision Software
File description Uninstall application file
Internal name Installer VISE
Original filename UNINSTAL.EXE
Legal copyright Copyright © MindVision Software 1995-2000
Product version 3.1.1
File version 3.1.1
Digital signatures [?]

unvise32.exe is not signed.
Hashes [?]
Property Value
MD5 84b4f61f59a421bd85d97b35d1******
SHA256 f241f37d423dd5c192b22ca1d4655dbf9e9b861487a6ac0f958b190e97******
What will you do with unvise32.exe?

To help other users, please let us know what you will do with unvise32.exe:

Windows Installer Errors

created the topic: Windows Installer Errors
A Windows installer error is a terribly common computer error that can pop up typically when you are putting in a program on a PC. Some of the error messages that may be written out for this error are:

· “The Windows Installer Service could not be accessed”

· “Windows Installer Service could not be started”

· “Might not begin the Windows Installer service on Native Computer. Error 5: Access is denied.”

The error usually happens in the early stages of the installation process as a result of this is when a part of Windows referred to as MSI is accessed. MSI simply means “Microsoft Installer.

The Installer/Uninstaller

The MSI is the half of the software that interfaces with the Windows operating system and actually, makes the installation possible. The MSI is additionally the half of the software that is entered when the program is uninstalled.

When a Windows installer error occurs, it will thus as a result of of a problem in the operating system’s registry. In fact, one among the old standby strategies for repairing this drawback involves coming into the registry and altering the Windows MSI to the default value. The reason for this is often as a result of a previous installation changed the value in the registry. So, changing it to the default would be changing the MRI access to where it had been before this program was installed. Using this method is nerve wracking as a result of putting in the wrong value can cause additional problems.

Cheap Straightforward and Fast

The Microsoft website shows how to unregister and re-register the MSI as a way of repairing a Windows installer error. This is done by accessing the “msiexec” area of the operating system. Yes, this method will work, but I like to use a budget, simple and quick method once I run into a Windows installer error.

The cheap, simple and fast technique is to easily run a sensible registry cleaner. The installer problem is definitely a registry problem and a smart registry cleaner will positively fix it. “Wait!” I here you exclaim. “How can this technique be low cost if I have to end up shopping for a registry cleaner?” Here’s how:

I’ve seen countless computers with huge difficult issues and even many that needed to be taken out of service altogether because someone embarked upon a procedure that started by clicking “begin” – “run” and then typing something in the Open box. I do not even want to speak about what I’ve seen happen after people, even some technicians, started tinkering around in “regedit!’ Believe me, a registry cleaner is the cheap way. Certainly, using one is the easy and fast way.

Still wondering what is the best blackberry accessories for you? All the tips you’ll ever need about blackberry accessories can be found at blackberry accessories.

Tagged :

Extending MSI command line switches

created the topic: Extending MSI command line switches
Hi there! Today I’m going to show you how to extend your InstallAware setup packages to support custom command line switches. A frequent question we get is “why don’t standard MSI command line switches work?” The answer is really simple – InstallAware has its own bootstrapper and the command line parameters it accepts are well documented under the help topic “Setup Command Line Parameters“. In a nutshell, /s makes setup run silently, /l= turns on logging, and you can pass variable values using the form “TARGETDIR=” (including the quotes, if you are specifying values with spaces in them).

Now that we’ve gotten the basics out of the way, let’s talk about how to extend this behavior. For instance, you might have some real difficult customers who have this irrational insistence on sticking to standard MSI command line parameters. Or, more legitimately, you might be wanting to define your own custom command line parameters to do whatever you feel like doing with.

The $CMDLINE$ pre-defined script variable contains the exact command line passed to your installer. You can investigate what this variable contains using the If script command together with the Contains expression. This will make it very easy for you to test for the presence of custom command line switches. For instance, take a look at the following code snippet:

if Variable CMDLINE Contains /quiet
Set Variable SILENT to TRUE
end

This snippet uses the pre-defined script variable $SILENT$ to turn on silent installation mode when /quiet, a standard MSI command line parameter, has been passed to your installer. Easy enough!

For more complex evaluations, you can assign the $CMDLINE$ pre-defined script variable to a custom variable and then use the Parse String command to extract exactly whatever you need without destroying the contents of the original command line variable.

Tagged :