Niakwa, Inc.

    

 


What's News
NPL Products
NPL Support
NPL Downloads
System Integration
swiggle_small.gif (991 bytes)

swiggle_small.gif (991 bytes)

December 20, 2000 No. 97

Packaging a Vinny Project for Distribution

Since the release of 32-bit Vinny it has become apparent that the distribution information contained in the original documentation is incomplete.  This tech note is being published to correct that situation.  The steps outlined in this Tech Note were developed using Visual Basic 6.0.

The same setup files were test by being deployed to a Windows 98 machine and a Windows NT 4.0 machine.

NOTE: A dependency file is needed for the Visual Basic 6.0 Package and Deployment Wizard to identify and package the files needed for the Vinny application to install properly.  Download the Vncon32.dep file from the Niakwa ftp site

ftp://ftp.niakwa.com/pub/windows/vnsetup.zip

and copy it into the directory where the Visual Basic Vinny Project files are.

Step by step instructions.

1. Open the Package and Deployment Wizard tool.  This is a Visual Basic tool that creates a setup package and distribution files for your VB project.

2. You have tell the program where to locate your Visual Basic Project file (*.VBP).   You can either browse to the *.VBP file or directly enter the path and file name.

3.  Choose the "Package" option.  This option will collect the files, create the necessary setup routines, and package it all together into a single file or smaller files that can be copied onto a diskette set.

4. You will be asked to choose the type of package you want to create.  Choose "Standard Setup Package".

5. You need to decide where your package will be assembled.  The files will be created on the local hard drive and will have to be transferred to the distribution media later.

6. You are shown a list of the files that will be included with your distribution files.  At this time you will need to remove or include any additional files your application needs to function.

The Package and Deployment Wizard will not be able to determine what specific NPL related files are needed.  These will have to be manually added. 

Add VNPL.NPL and all other necessary data and program diskimages to the wizard. 

Add the names of all your data files.

Make sure the "install location" for the NPL related files is $(AppPath).  The DLLs and OCX files should be installed to a different location.

Verify that the following files are included.  If any of them are missing they will have to be added manually.

These are the minimum files required for a Vinny or Instant Vinny application to function.  Other DLLs or OCXs may also be required if the application references them.

VNCON32.OCX
VNPL32.DLL
VNPL.NPL

If your application requires any custom written DLL's, add them now if they are not already included.

7.  Check in the "install location" screen to make sure all the DLL and OCX files are being added to the $(WinSysPath).  Manually added DLLs and OCXs will default to the $(AppPath).  These will have to be changed to the $(WinSysPath).

8. If the wizard asks if a set of files are to be installed "shared" place a check mark in the box next to the file name and select "Next" then "Finish".

9. When done, the Wizard will advise you of the number of CAB files that were created in the "package" directory.

10. Copy the cab files, setup.exe, and setup.lst onto the distribution media.  If you are using a multiple diskette floppy set, make sure setup.exe, setup.lst, and the first .CAB file are on diskette one. 

You have now created a distribution file set for your Vinny or Instant Vinny application.  Keep in mind, each location where these files are distributed will require a working Release 5 RunTime.

CAUTION: The VB Package and Deployment Wizard tool will, by default, create a program group with a shortcut to the included EXE file.  This EXE file must be launched by the Vinny App, and will not execute on it's own.  This shortcut should be deleted to avoid confusion for the end user.

The Setup routine will stop and force a reboot part way into the installation if system files have to be updated.  After the reboot, re-run the setup routine to complete the installation.

Troubleshooting the Distribution routine.

I get an error message that one of the OCX or DLL files failed to self-register.

Make sure the file named in the error message is present in the windows\system (winnt\system for NT) directory.

I checked, and the file in the error message is in the correct location.

Check to make sure all the other DLLs and OCXs are in the windows\system (winnt\system for NT) directory.

Once you locate the misplaced file, move it into the windows\system (winnt\system for NT) directory.

Then you can manually register the file by using the regsvr32.exe program.  The syntax is:

                regsvr32 /s C:\WinSysPath\DllOrOcxName

Troubleshooting the Application

If the application fails to run, what do you do?  How does it fail?

I double click on the icon and nothing happens.

Verify that there is a functional Release 5 or greater runtime available on the system.   Make sure you are using the RunTime to execute the NPL Vinny application and not just trying to execute the compiled VB executable alone.

I get an NPL screen with the error "external subroutine not found".

Make sure any external libraries that the application needs are being loaded either with the /x command line option or in the RTIWIN.INI file, especially VNPL32.DLL.

I get the error  "External Library VNPL32.DLL not found".

1. Verify that all the 32-bit Vinny DLLs and OCX files are in the windows\system (winnt\system for NT) directory.  If one or more are missing, locate them and move them to the correct location.

2. Manually register VNPL32.DLL and VNCON32.OCX.

 

blank.gif (841 bytes)


Niakwa, Basic-2C and NPL are trademarks of Niakwa, Inc. All other products mentioned are registered trademarks or trademarks of their respective companies.

Questions or problems regarding this web site should be directed to webmaster@niakwa.com.
Copyright 1996-2010 Niakwa, Inc. All rights reserved.
Last updated: Thursday January 07, 2010.