I need to go back and install an application that is using Installshield 3. I've tried installing it on a NT4 (VM), a windows 2000, and XP and all produce the same error on file Setup.INS. The script was created using installshield3. Recompile the script using Installshield SDK. I am not a developer. I've been trying to find an answer on google for about 12 hours. Other than finding that Installshield was sold twice in the last 8 years (I think) I have gained little else. The Setup.INS file has a date of 8/20/1999. What do I need to do to install this app? Thanks in advance for your answers.
a 6ya expert can help you resolve that issue over the phone in a minute or two.
best thing about this new service is that you are never placed on hold and get to talk to real repairmen in the US.
the service is completely free and covers almost anything you can think of (from cars to computers, handyman, and even drones).
click here to download the app (for users in the US for now) and get all the help you need. goodluck!
- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
psexec in fact does run as the user
running the command window that initiated the command. I use this
command almost daily to run either command shells, batch or vbscripts,
etc on remote computers. I've learned some about its behavior from
watching the results.
Basically, psexec copies itself to the
ADMIN$ share on the remote computer. It then installs a service on the
remote computer, and runs that service, which is the copied file. This
then executes the command that you specified in the psexec command line.
with that in mind, the user running psexec from the command line needs
to have admin rights to the remote computer. You can bypass this
requirement by using the "-u" parameter, and specifying a
domainname\username. Domainname can be the remote computer's name if
you have a local user. By putting in just the -u parameter, you'll then
be prompted to type in the hidden password.
Once running on the remote computer, psexec will function in one of three ways: 1 - If no special parameter used, will run in the same user account as the person initiating the psexec command. 2 - If the "-u" parameter is used, it will run as that user. 3 - If the "-s" parameter is used, it will run as a local system account In either of these 3 cases, you first have to have admin rights to use the ADMIN$ share and install a service.
When domain membership is broken on a computer, I'll frequently use a command line like this: psexec -u COMPUTERNAME\Administrator \\COMPUTERNAME cmd.exe
will allow me to have local admin rights by connecting to the remote
computer as the local administrator account. It will also run the
cmd.exe command as the local admin account.
LogMeIn is not officially supported within Google Chrome, but the
Mozilla Firefox version of the plugin has been verified to work in
Google Chrome with the help of the following script: <a href="http://userscripts.org/scripts/show/53796">http://userscripts.org/scripts/show/53796</a><br />
For XP put script in:<br />
"C:\Documents and Settings\YOURUSERNAME\Local Settings\Application
Data\Google\Chrome\User Data\Default\User Scripts"
For Vista and 7 put script in:<br />
To use, you must run your browser's exe with the parameter
<li>Right-Click on the Google Chrome Shortcut.</li>
<li>In the Shortcut Tab, change the Target to "C:\Users\YOURUSERNAME\AppData\Local\Google\Chrome\Application\chrome.exe --enable-user-scripts"</li></ol>
Now the LogMeIn plugin can be installed in Google Chrome from here:
Thanks for contacting Fixya Support, I am glad to assist.
What appears to be the issue, is that your .vmx (Virtual Machine File extension) which is what how your Windows XP virtual machine terminal launches and works, may possibly be corrupted. I have been using VMWare Fusion for my Macs for nearly 3 years and it is not uncommon for this type of file to become corrupted and fail to launch for no apparent reason.
The usual way to correct this inability to launch issue, is if you can use the VMWare Fusion console to revert back to a previous Snapshot (saved backups or "snapshots" of your previous Windows XP virtual terminal sessions) of that Windows Virtual Machine terminal in order to recover the functionality of the vm.
If you are not familiar with what a Snapshot in VMWare is, then that would mean chances are you have not used that function and therefore you would have no snapshots of any previous Windows XP sessions to revert back to.
If this is the case, the what I can recommend you try, is to reinstall the VMWare Fusion 3 software to overwrite the current copy you have to see if this can help repair your affected Windows XP .vmx file.
If this process does not help, then you may unfortunately have to create a new Windows XP virtual terminal if you have no back ups or Snapshots of previous sessions.
Please feel free to reply back to this post if you have further questions.
Maybe your computer is not fast enough, or does not have enough memory to run / handle a lot of programs installed at the same time, or most of the time, maybe after you installed some application / did driver updates, your sound drivers get messed up.
Most of the time, if you are using Windows Vista, you can run Windows Update, and it will find almost any type of sound drivers for your computer system. Or if you are running Windows XP compatible operating system, then you can still try to use Windows Update to either find new drivers for your computer, or you can use Windows Update to find if there is any problems with your sound drivers / sound card.
Hi, from the Desktop, (right, click) on the Taskbar, or press (CTRL+ALT+DEL) to open the Task Manager. Next in the (Tasks Man...) window, press the Services(tab), at the bottom of the window, click on the (Services...) button, the services open. Next scroll to find: SQL Server... and the InstallDriver Table...these will be services of interest to "Enable, and or "Start," also check the "Dependencies" of the services. Select "Apply and OK" once started. The next area you may want to check is the Computer Management, Type: (comp...) in the Start Search "window". Look in the Internet Info...Serv...(IIS)... "Providers category." "You may what to restart the computer, some services require ("rebooting") to "configurate" correctly." "If this helped, feedback is appreciated, thanks"