PDA

View Full Version : Making a install for a network



NewsArchive
11-13-1997, 01:00 AM
I have ISE2, and want to make a install for my VB4 & VB5 apps.
I've made simple installs for standalone PC's but, have no idea on
how to make a install for a 20 user Novell network..

My program uses lots of OCX's, and DLL's.. If I'm right in thinking all
of these files
will have to put on all workstations by my install?

I'm totallly lost, your help will be greatly apppreciated..

Len

NewsArchive
01-14-1998, 01:00 AM
What I've done is take the stand alone install and just change the final
icon/shortcut it creates to point to the netwok drive
It installs the OCX's and DLL's on the local machine (good for speed
reasons) and then the EXE is on the network so it can be updated more
easily
Yes, the users have the EXE taking up disk space, but you can write a quick
VB program to erase the junk files

Leonard H. Erickson <lenny@rapidstudy.com> wrote in article
<346BD3A4.7F054EF1@rapidstudy.com>...
> I have ISE2, and want to make a install for my VB4 & VB5 apps.
> I've made simple installs for standalone PC's but, have no idea on
> how to make a install for a 20 user Novell network..
>
> My program uses lots of OCX's, and DLL's.. If I'm right in thinking all
> of these files
> will have to put on all workstations by my install?
>
> I'm totallly lost, your help will be greatly apppreciated..
>
> Len
>
>

NewsArchive
01-14-1998, 01:00 AM
On 14 Jan 98 20:06:20 GMT, "PC User"
<CoreyLapka@Martin-Associates.com.no.sp.am> wrote:
>What I've done is take the stand alone install and just change the final
>icon/shortcut it creates to point to the netwok drive

You can also try this... Write an extension (in VC++ preferably) that will
bring up a dialog box asking if this is a network install. If so, let the
user point to the network drive, create the shortcuts and cancel the
installation. The uninstall removes all traces, except for the shortcuts
the extension installed.


Stefan
ellipse data systems

NewsArchive
02-03-1998, 01:00 AM
I did the following (ISX version 2):

1. I created a Workstation Setup Kit, which ONLY installs the required
system files in the System directory (It also creates a dummy directory on
the local PC, with one file in it -- I think it's _DEISREG.ISR).

2. I created a Network Install kit, which includes all of the required
files in the network application directory, plus several subdirectories.
One subdirectory is called <INTALLDIR>\WSSetup, and contains all of the
files in the Workstation setup kit. The network install is done once.
Then, each PC runs the Setup.EXE from the WSSetup directory. There are
only two problems, neither of which is fatal:

a) The user running the Network Setup kit MUST specify the path to
install in (there is no way to force a prompt), or the setup will crash;
and
b) Since the Workstation Setup kit does not know where the Network
application is, it cannot create an Icon on the desktop -- therefore, the
icon must be created manually.

By the way, my application contains a number of files which may be updated
by the users, including an .INI file and a number of "translation tables".
I place these in a <INSTALLDIR>\SAMPLES. That way, if the network install
is done a second time (e.g. to apply an update), only the samples are
overwritten.

--
Fletcher James
Levit & James, Inc.
(703) 771-1549

Leonard H. Erickson <lenny@rapidstudy.com> wrote in article
<346BD3A4.7F054EF1@rapidstudy.com>...
> I have ISE2, and want to make a install for my VB4 & VB5 apps.
> I've made simple installs for standalone PC's but, have no idea on
> how to make a install for a 20 user Novell network..
>
> My program uses lots of OCX's, and DLL's.. If I'm right in thinking all
> of these files
> will have to put on all workstations by my install?
>
> I'm totallly lost, your help will be greatly apppreciated..
>
> Len
>
>