-
When I try to install my application compiled under package and wizard into
an NT workstation, I encountered error message Please refer to attached
below the error info for referneces:. Appreciate if someone can share their
experience on this matter.
>>>>>St6unst.018
%% PLEASE DO NOT MODIFY OR DELETE THIS FILE! %%
%% This file contains information about the installation of an application.
%%
%% It will be used to automatically remove all application components from
your computer if you choose to do so. %%
NOTE: Beginning of the bootstrapper section
CONFIG: Title: "Project1"
ACTION: RegKey:
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion", "SharedDLLs"
ACTION: SystemFile: "C:\WINDOWS\SYSTEM32\VB6STKIT.DLL"
(File currently on disk was already up to date)
ACTION: SystemFile: "C:\WINDOWS\SYSTEM32\COMCAT.DLL"
(File currently on disk was already up to date)
ACTION: SystemFile: "C:\WINDOWS\SYSTEM32\STDOLE2.TLB"
(File currently on disk was already up to date)
ACTION: SystemFile: "C:\WINDOWS\SYSTEM32\ASYCFILT.DLL"
(File currently on disk was already up to date)
ACTION: SystemFile: "C:\WINDOWS\SYSTEM32\OLEPRO32.DLL"
(File currently on disk was already up to date)
ACTION: SystemFile: "C:\WINDOWS\SYSTEM32\OLEAUT32.DLL"
(File currently on disk was already up to date)
ACTION: SystemFile: "C:\WINDOWS\SYSTEM32\MSVBVM60.DLL"
(File currently on disk was already up to date)
ACTION: DllSelfRegister: "C:\WINDOWS\SYSTEM32\COMCAT.DLL"
ACTION: TLBRegister: "C:\WINDOWS\SYSTEM32\STDOLE2.TLB"
ACTION: DllSelfRegister: "C:\WINDOWS\SYSTEM32\OLEPRO32.DLL"
ACTION: DllSelfRegister: "C:\WINDOWS\SYSTEM32\OLEAUT32.DLL"
ACTION: DllSelfRegister: "C:\WINDOWS\SYSTEM32\MSVBVM60.DLL"
NOTE: End of the bootstrapper section
NOTE: Now spawning the main Setup program 'Setup1.exe'....
*** ERROR: Cannot start main setup program! (CreateProcess() returned error
code 0x000000C1H)
*** ERROR: (User Responded with 'OK')
>>>>>>Setup.lst
*******
[Bootstrap]
SetupTitle=Install
SetupText=Copying Files, please stand by.
CabFile=Pco System.CAB
Spawn=Setup1.exe
Uninstal=st6unst.exe
TmpDir=msftqws.pdw
Cabs=1
[Bootstrap Files]
[email protected],$(WinSysPathSysFile),,,6/18/98 12:00:00
AM,102912,6.0.81.69
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),,5/31/98 12:00:00
AM,22288,4.71.1460.1
[email protected],$(WinSysPathSysFile),$(TLBRegister),,4/23/99 10:22:00
PM,17920,2.40.4275.1
[email protected],$(WinSysPathSysFile),,,3/8/99 11:50:56
AM,147728,2.40.4275.1
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),,3/8/99 11:50:56
AM,164112,5.0.4275.1
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),,3/8/99 11:50:54
AM,598288,2.40.4275.1
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),,12/10/98
12:28:18 AM,1409024,6.0.82.68
[IconGroups]
Group0=Project1
PrivateGroup0=True
Parent0=$(Programs)
[Project1]
Icon1=""Pco System.EXE""
Title1=Project1
StartIn1=$(AppPath)
[Setup]
Title=Project1
DefaultDir=$(ProgramFiles)\Project1
AppExe=Pco System.EXE
AppToUninstall=Pco System.EXE
[Setup1 Files]
File1=@MDAC_TYP.EXE,$(AppPath),,$(Shared),6/26/98 12:00:00
AM,8124720,4.71.1015.0
[email protected],$(WinSysPath),$(DLLSelfRegister),$(Shared),8/9/98
6:07:32 PM,118784,6.0.81.69
[email protected],$(WinSysPath),$(DLLSelfRegister),$(Shared),6/18/98
12:00:00 AM,77824,6.0.81.69
[email protected],$(CommonFiles)\designer,$(DLLSelfRegister),$(Shared),6/9/
98 12:00:00 AM,137216,6.0.0.3005
[email protected],$(WinSysPath),$(DLLSelfRegister),$(Shared),6/18/98
12:00:00 AM,299008,6.0.81.69
[email protected],$(WinSysPath),$(TLBRegister),$(Shared),6/9/99 12:00:00
AM,48528,0.0.0.0
[email protected],$(WinSysPath),$(DLLSelfRegister),$(Shared),7/29/98
2:01:56 AM,1062704,6.0.81.77
[email protected],$(WinSysPath),$(DLLSelfRegister),$(Shared),6/24/98
12:00:00 AM,140096,6.0.81.69
[email protected],$(WinSysPath),$(DLLSelfRegister),$(Shared),8/1/00 3:25:46
PM,557328,3.60.2927.2
File10=@Pco System.exe,$(AppPath),,$(Shared),8/11/00 7:14:16
AM,151552,1.0.0.0
-
This is speculation, but I know NT can be configured so that a normal user can't run an installation (my network's set up that way). If so, they shouldn't be able to run the setup...looks like yours started but stopped as soon as it got to the main setup. Maybe try installing logged on as an admin?
-
I used the administrator login for NT. I've also compiled a small sample program using the Package n wizard and try install this into the NT. Problem is the sample program works ok.
Any other suggestions to overcome this problem is very much appreciated.
Regards
CT
-
If you used the same P&D wizard from the same machine and the sample app installed ok, I'd try rebuilding the setup. In the script you posted, it said it had trouble starting the main setup program itself which isn't specific to the particular vb app.
-
Rebuilding the setup program is a good suggestion. I try install this app into a win2000 and it works. Will it make any different if user is still using the NT3.51?
Regards
CT
-
One more thing. Below is the setup log file for the small sample program which I compiled and installed successfully into the NT.
If you observe the first line of the setup1, it is doing a directory creation.
Regards
CT
%% PLEASE DO NOT MODIFY OR DELETE THIS FILE! %%
%% This file contains information about the installation of an application. %%
%% It will be used to automatically remove all application components from your computer if you choose to do so. %%
NOTE: Beginning of the bootstrapper section
CONFIG: Title: "LoanProject"
ACTION: RegKey: "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion", "SharedDLLs"
ACTION: SystemFile: "C:\WINDOWS\SYSTEM32\VB6STKIT.DLL"
(File currently on disk was already up to date)
ACTION: SystemFile: "C:\WINDOWS\SYSTEM32\COMCAT.DLL"
(File currently on disk was already up to date)
ACTION: SystemFile: "C:\WINDOWS\SYSTEM32\STDOLE2.TLB"
(File currently on disk was already up to date)
ACTION: SystemFile: "C:\WINDOWS\SYSTEM32\ASYCFILT.DLL"
(File currently on disk was already up to date)
ACTION: SystemFile: "C:\WINDOWS\SYSTEM32\OLEPRO32.DLL"
(File currently on disk was already up to date)
ACTION: SystemFile: "C:\WINDOWS\SYSTEM32\OLEAUT32.DLL"
(File currently on disk was already up to date)
ACTION: SystemFile: "C:\WINDOWS\SYSTEM32\MSVBVM60.DLL"
(File currently on disk was already up to date)
ACTION: DllSelfRegister: "C:\WINDOWS\SYSTEM32\COMCAT.DLL"
ACTION: TLBRegister: "C:\WINDOWS\SYSTEM32\STDOLE2.TLB"
ACTION: DllSelfRegister: "C:\WINDOWS\SYSTEM32\OLEPRO32.DLL"
ACTION: DllSelfRegister: "C:\WINDOWS\SYSTEM32\OLEAUT32.DLL"
ACTION: DllSelfRegister: "C:\WINDOWS\SYSTEM32\MSVBVM60.DLL"
NOTE: End of the bootstrapper section
NOTE: Now spawning the main Setup program 'Setup1.exe'....
ACTION: CreateDir: "C:\Program Files\LoanProject"
ACTION: CreateDir: "C:\WINDOWS\Profiles\cooi5\Start Menu\Programs\LoanProject"
ACTION: SharedFile: "C:\Program Files\LoanProject\Loan.exe"
(File was not found or was an older version -- new file copied)
ACTION: ShellLink: "LoanProject", "LoanProject"
ACTION: RegKey: "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion", "App Paths\Loan.EXE"
ACTION: RegValue: "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\Loan.EXE", ""
-
Depends on what you're using...which API calls, ocx's, etc. employed, that could make a difference between the 2 systems. If it installed on 2000 and not NT, I would think it's the operating system. NT and 2000 are 2 very different creatures.
Regarding the directory creation, in the first setup, it didn't get that far.
-
WadeD,
Thank you for your help in this matter. I think i have found the root cause to this problem. Kindly refer to the attached below:
If the symptom occurred after a previous installation attempt of the same application failed (for example, the computer stopped responding during setup), follow these steps:
On the target computer, search for a copy of your application's .cab file(s) in the Windows folder (or Winnt folder on NT or Windows 2000). If found, delete the .cab file(s).
Setup places the .cab file(s) in the Windows or Winnt folder and removes them at the end of a successful Setup. However, if the installation program exits abnormally, the .cab files may be left on the system.
In the Windows\Temp folder (or the folder specified by the TEMP environment variable on NT or Windows 2000), look for a subfolder named Msftqws.pdw. If found, delete the subfolder.
On the target computer, locate the following files. If any of these files have a size of 0 bytes, delete the file:
\Windows\System\Vb6stkit.dll (or \Winnt\System32\Vb6stkit.dll)
\Windows\St6unst.exe (or \Winnt\St6unst.exe)
Run Setup again.
Again thank you very much for your help
Best wishes
CT
