(Lee Bustin) threw this at us:
Quote:
>I currently running win 95 with VB4 I have created a program that runs
>well on my machine but not on my friends who is running win 3.1
>How can I get the disk creater make a 16 bit app or make the
>installation disk my self.
Last time this question was asked, I blamed Win95, which was wrong.
Pierre du Part corrected me, and here's what he said:
--- Begin repost ---
After stuffing around for the last four or five hours I can report
that the SETUPWIZARD VB4/16 (under Win95) works fine for creating
install sets for WIN16 systems:
The VB4 SETUP does NOT write the appropriate SWTMPL file into the
KITFILES directory. Consequently the SWDEPEND.INI file is NOT prepped
correctly. Additionally, MS neglected to include the SWDEPEND.TXT
files it refers to in the README help file. SO BE IT!!
Anyway, the cure is relatively simple. From the CDROM copy
\VB\SETUP\KITFILES\SW16TMPL.INI to the same directory on the hard
disk. Path names may need to be edited. If SWDEPEND.INI already
exists, delete it or at least remove the 16 bit references from it.
Thereafter all is well!
--- End repost ---
Jens
--
* Everything I said are the opinions of someone else. *
* I just cut-and-pasted. *
Jens Balchen jr.
Producing a 16 bit app