VB6 setup wizard

[Thomas Waenke]

Hi,

I installed the new VB6 (VB98) from the MSDN CDs. When I create a setup
package the new wizard creates a .CAB file and the setup.exe/setup.lst
files.

When I try the installation on any computer ( even the computer where I
developed the program), the following error message appears:

c:\winnt\setup.lst

invalid line in setup information file!

@COMDLG32.OCX,$(WinSysPath),$(DLLSelfRegister),$(Shared),6.24.98,12:00:00
AM,140096,6.0.81.69

The above message is shown when I try to install Microsoft's MSFlexgrid
example from the samples directory. The last line is not always the same. It
depends on the program that I try to install.

What goes wrong ??

Thanks in advance,

Thomas Waenke

[Rainer Spritzendorfer]

Thomas,

the P&D wizard can't be used on machines not configured to run the
English(US)
locale, because it formats the dates in setup.lst using the native locale
of the machine used create the package. On the other hand the setup1.exe
expects this time stamp in m/d/yyyy format.

The only workaround I know of, is to switch to English(US) locale while
generating the package (besides of manually editing the setup.lst file).

Rainer

Thomas Waenke wrote in message <35dd7...@news.munich.netsurf.de>...

[Thomas Waenke]

Rainer,

Thanks for the help. It works for 90% of the programs. But some of the
setups stop after everything has been copied and bring up the error message
that the file msftqws.pdw could not be registered because it was not found.
A strange error. This file isn't a file, but the temp directory used by the
wizard!!!

I could not find a hint in Microsoft's knowledge base. Hopefully this will
not happen to often.

Thomas

Rainer Spritzendorfer wrote in message <6rr4mi$egv$1...@news.netway.at>...

[Donnie Swafford]

Try this fix...

find a file with the
Thomas Waenke wrote in message <35e17...@news.munich.netsurf.de>...

[Donnie Swafford]

sorry about the last post ... here is the fix

Check your SETUP.LST file for the string:
c:\windows\system\$(DLLSelfRegisterEx)

If this exists, it is incorrect. It should be something like:
c:\windows\system\myocx.ocx, $(DLLSelfRegisterEx)

If that doesn't work, remove the Ex from $(DLLSelfRegisterEx) so it reads:
$(DLLSelfRegister)

This worked for me. The culprit file was the mscalendar control

Donnie

[Thomas Waenke]

It was the 'Ex' in the mscalender control. Now it works.

Thanks

Donnie Swafford wrote in message ...

[Donnie Swafford]

Please do me a favor and help me and others get the word out on this. I
found the answer on this newsgroup and am passing it along. If we all answer
this question every time we see it we can help others save time trying to
debug there setup.lst files.

Glad I was able to help

Donnie Swafford
don...@itsgroup.com

Thomas Waenke wrote in message <35e19...@news.munich.netsurf.de>...

[TGeairn...@unxpres.com]

I don't use that control, but... Can you avoid having to fix your
Setup.lst each time by modifying the MSCal.dep file and removing the Ex?

-Tom Geairn