:confused:
Is it true that the setup created using Package & Deployment wizard of VB 6.0 is not run in windows 7? if not then why the setup file i ve created doesnt run in windows 7?
please help me!
regards
czns..
Printable View
:confused:
Is it true that the setup created using Package & Deployment wizard of VB 6.0 is not run in windows 7? if not then why the setup file i ve created doesnt run in windows 7?
please help me!
regards
czns..
when i tried to create setup files in 64 bit the Package & Deployment only loading doesnt show any effects. Does this Package & Deployment doesnt works in 64 bits?
please help me
regards
czns
I don't use a lot of dependencies, but I have about 5 (SGrid2, ADO, Excel Automation, VBSendmail, etc)
I do not install my programs (No setup created), but what I do just once, is create a project that has no code, just the dependencies.
I compile it, and use the P&D to create a setup.
The user runs it once, and never looks at it again.
From that day on, I can create VB6 programs and just give them to the user, to place in a folder, and they just run.
I have done the above for a user using Win7 64 bit, without problems.
but when i try to create in 64 bits it just shows loading files what is the problem?
Give us a list of all your controls and dependencies
A setup program created using package and deployment wizard should work fine under windows 7 though the user may need to right click on the setup.exe and choose run as administrator to get some system files to register properly.
So far I have not had a problem where a custom could not install my software other than if they had a user account that was restricted from adding system files. My major projects require a coupld of DLL and OCX files installed.
I ve tried to create setup files in 64 bit but the programs shows loading and i ve tried in 32 bit but it easily created the setup file. Does the vb 6 can only be used in 32bits to create setup file?
really i am confused...
I ve created setup file but at the end of setup the following message is shown:
This application has failed to start because MSDART32.dll was not found. Reinstalling the application may fix the problem.
how should i overcome that problem? Anyone here please help me!
Is the MSDart32.dll included in your package?
I ve selected all the required files while creating the setup files...
So does that mean that the MSDart32.Dll is actually in the setup package? Have you checked the cab file or setup.lst to confirm
I ve checked there(SETUP.LST) but the MSDART.DLL is not there what should i do now? BTW when i checked in my system32 i didnt find this MSDART32.DLL. what is the solution. please help me...
You need to go back and recreate the package making sure to add this file to it.
Moved to the Application Deployment forum.
Still waiting for the REPLY!
I did reply see post #13
but i ve checked for that file it is not in my C:\WINDOWS\system32 so where should i get that file. but instead of that file i ve msdart.dll.
See if there is a copy in -Quote:
Originally Posted by czns
C:\WINDOWS\system32\dllcache
there is no any files that name dllcache ...
That is not a File, it is a sub folder of System32 folderQuote:
Originally Posted by czns
In there there are tons of DLL files
PS There is a brilliant program that everyone should have, for locating files, called Everything (It is FREE) -
http://www.voidtools.com/
but there is no any subfolders name dllcache but there is subfolder cache which is empty...
You may be using a different OS from me (I am XP SP3)Quote:
Originally Posted by czns
You may have folders hidden
Download Everything and run that.
When it runs, watch the bottom left status until it finishes scanning for folders,
Then type MSDart32.dll up the top, and it will list any folders containing it.
mine also windows xp sp3.. none files are hidden..
My guess is that you are getting into trouble because you are trying to deploy bits and pieces of MDAC in your setup package. MDAC (or DAC on current versions of Windows) became part of the OS in the Win2K era and is now serviced via Windows Update. As a result you never want to try to resitribute pieces and parts of MDAC and very seldom want to try to redistribute the MDAC_TYP.EXE package (which is how you used to do this).
An exception might be a very early Windows 95 system (Win95A or Win95B, but not Win95 OSR2), though note that you also have to install DCOM95 first as well.
The reason you're having trouble is attempting to deploy the non-deployable. In this particular case the PDW seems to be being led down a primrose path based on your development system. There is probably a .DEP file somewhere deep down that says something is dependent on MSDART32.dll, but MSDART has been called MSDART.DLL (no "32") for a long, long time now. As far as I can tell the change came somewhere after MDAC 2.5, either in 2.6 or maybe 2.7.
To know for sure we'd probably have to see your SETUP.LST file's contents. If you are trying to deploy random hunks of MDAC/DAC then it is just as likely you're packaging other things that aren't deployable anymore. A lot has changed since 1997 when the PDW was built for inclusion as part of the VB/VS 6.0 product.
It is almost always helpful to see SETUP.LST when troubleshooting a PDW-related problem.
here i ve the setup.lst file that was created when i tried to make setup files. i had no problem when i learned vb6 before three years ago. all i did is same but now it is creating problem why i dont know.
setup.lst file:::
[Bootstrap]
SetupTitle=Install
SetupText=Copying Files, please stand by.
CabFile=Hydraulic Calculation v1.3.4.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),,10/30/07 3:36:02 PM,16896,5.1.2600.3244
[email protected],$(WinSysPathSysFile),,,10/31/07 12:31:36 AM,65024,5.1.2600.3244
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),,10/31/07 12:32:00 AM,83456,5.1.2600.3244
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),,10/31/07 12:32:00 AM,549888,5.1.2600.3244
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),,10/31/07 12:31:54 AM,1384479,6.0.98.2
[IconGroups]
Group0=DataProj
PrivateGroup0=True
Parent0=$(Programs)
[DataProj]
Icon1=""Hydraulic Calculation v1.3.4.exe""
Title1=DataProj
StartIn1=$(AppPath)
Icon2=""Hydraulic Calculation v1.3.4.exe""
Title2=Icon3
StartIn2=$(AppPath)
[Setup]
Title=DataProj
DefaultDir=$(ProgramFiles)\DataProj
AppExe=Hydraulic Calculation v1.3.4.exe
AppToUninstall=Hydraulic Calculation v1.3.4.exe
[Setup1 Files]
[email protected],$(WinSysPath),$(DLLSelfRegister),$(Shared),4/3/00 8:05:58 PM,118784,6.0.88.4
[email protected],$(WinSysPath),$(DLLSelfRegister),$(Shared),5/22/00 4:58:00 PM,118976,6.0.88.4
[email protected],$(WinSysPath),$(DLLSelfRegister),$(Shared),5/22/00 4:58:00 PM,140488,6.0.84.18
[email protected],$(WinSysPath),$(DLLSelfRegister),$(Shared),5/22/00 4:58:00 PM,608448,6.0.81.5
[email protected],$(WinSysPath),$(DLLSelfRegister),$(Shared),5/22/00 4:58:12 PM,438976,6.0.88.4
[email protected],$(WinSysPath),$(DLLSelfRegister),$(Shared),6/24/98 12:00:00 AM,232248,6.0.81.69
[email protected],$(WinSysPath),$(DLLSelfRegister),$(Shared),12/6/00 1:02:06 PM,262328,6.0.89.88
[email protected],$(WinSysPath),$(DLLSelfRegister),$(Shared),6/18/98 12:00:00 AM,77824,6.0.81.69
[email protected],$(WinSysPath),$(DLLSelfRegister),$(Shared),6/24/98 12:00:00 AM,187712,6.0.81.69
[email protected],$(WinSysPath),$(DLLSelfRegister),$(Shared),5/4/01 12:05:02 PM,184592,2.52.6019.1
[email protected],$(WinSysPathSysFile),,,10/31/07 12:31:54 AM,343040,7.0.2600.3244
[email protected],$(WinSysPath),$(DLLSelfRegister),$(Shared),10/31/07 12:32:00 AM,151552,5.7.0.20612
[email protected],$(WinSysPath),$(DLLSelfRegister),$(Shared),6/18/98 12:00:00 AM,299008,6.0.81.69
File14=@Hydraulic Calculation v1.3.4.exe,$(AppPath),,$(Shared),5/4/12 3:07:11 PM,368640,1.0.0.0
; The following lines may be deleted in order to obtain extra
; space for customizing this file on a full installation diskette.
;
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
I am no expert on creating setups (i do one every 2 years)
And this probably won't solve your problem.
If this -
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),,10/31/07 12:31:54
Is the VB6 runtime, then there is no need to distribute that.
Every OS since win98 SE, has them already present
I recommend that you remove that.
PS Did you get Everything ?
There is still a problem creating a setup files..
When you reply to a post, you should indicate what you are replying to.Quote:
Originally Posted by czns
You can do that in a couple of ways -
- Mention the name of the poster you are replying to, or
- Press the quote button on the post you wish to reply to.
If you were replying to my last post, I was not betting body parts, that it would solve your problem, but I still believe that one should not distribute the VB6 runtime, in 99% of install packages.
You have three files in your package that do not belong there for sure. I don't think they are the reason for the problem you are seeing but are likely enough to cause problems once you get past this specific issue:
- msadox.dll
- msvcrt.dll
- scrrun.dll
But that will leave the original problem yet to be solved. This leaves me with one more idea.
What service pack level is your VB6 software at? It sounds like you have a very old version because there isn't any MSDART32.DLL anymore.
Which version of Windows did you create this setup package on? What versions of Windows have you successfully installed it on?