Internet components and apps

> Anybody know what I have to change in the W95 register  of the client computer
> for use in it  my development program who use the POP component of Delphi 3
> internet palette & if i must copy any .dll or .OCX to the clientes
> windows/system?
> to install D3 in client computer is discarted,,
> I ´ve combined de .reg file of licenses in the register of client but the
> program still don´t run , "Class no registered"

Applications built with the Internet Solutions Pack can be
redistributed using most third party installation programs,
including the InstallShield Express utility that ships with
Delphi 2.0 Client/Server and Developer.  In order to deploy
your application, any OCX controls you used in building the
application need to be redistributed along with your executable,
as well as any other necessary files (eg. dll's) your programrequires.
In addition, the Internet controls are dependent upon NetMasters
support dll's, and must be included with your program.  The
following list contains of all the OCX files and NetMasters DLLs
that ship with the Internet Solutions Pack (and that may need to
be redistributed):   OCX files   ---------   HTML.OCX   HTTPCT.OCX   NNTPCT.OCX
   POPCT.OCX   SMTPCT.OCX   WINSCK.OCX   FTPCT.OCX   NetMasters DLLs
   --------------   NMOCOD.DLL   NMSCKN.DLL   NMFTPSN.DLL   NMW3VWN.DLL
   NMORENU.DLLFor a list of which files you actually need to include with your
distribution, use the following dependency matrix:
             ----------------------------------------------------
                           | Winsock | FTP | NNTP | SMTP | POP3 | HTTP | HTML |
 ---------------------------------------------------------------                                               |
|NMSCKN.DLL  |    X          |  X      |   X     |   X       |   X       |   X      |   X       |
|---------------------------------------------------------------|
|NMORENU.DLL |         |  X  |   X  |   X  |   X  |   X  |   X  |
|---------------------------------------------------------------|
|NMOCOD.DLL  |         |  X  |   X  |   X  |   X  |   X  |   X  |
|---------------------------------------------------------------|
|WINSCK.OCX  |    X    |     |      |      |      |      |      |
|---------------------------------------------------------------|
|FTPCT.OCX   |         |  X  |      |      |      |      |      |
|---------------------------------------------------------------|
|NMFTPSN.DLL |         |  X  |      |      |      |      |      |
|---------------------------------------------------------------|
|NNTPCT.OCX  |         |     |   X  |      |      |      |      |
|---------------------------------------------------------------|
|SMTPCT.OCX  |         |     |      |   X  |      |      |      |
|---------------------------------------------------------------|
|POPCT.OCX   |         |     |      |      |   X  |      |      |
|---------------------------------------------------------------|
|HTTPCT.OCX  |         |     |      |      |      |   X  |      |
|---------------------------------------------------------------|
|HTML.OCX    |         |     |      |      |      |      |   X  |
|---------------------------------------------------------------|
|NMW3VWN.DLL |         |     |      |      |      |      |   X  |
 ---------------------------------------------------------------Patches:
The following patches are available for download from the Borland
Delphi 32 CompuServe Forum (BDELPHI32) and the Borland website(www.borland.com).
NMPATCH.ZIP - Unzip this file and follow the included directions.
This patch was supplied by NetMasters and will actually update the
controls themselves.
ISP.DCU - Place in the Delphi 2.0\lib subdirectory and recompile
your project. This will prevent the error message about not beinglicensed.
To deploy your program using InstallShield Express, follow thesesteps:
1)     Start up ISXpress, and build your Setup project as you
        normally would (if you are unfamiliar with building a
        Setup project with InstallShield Express, refer to the
        InstallShield online help).
2)     In the Components & Groups portion of the setup, add your
        executable file into an appropriate group (eg. the Program
        Files group (default)).
3)     Create a new group for the shared files (eg. "Shared Files"),
        and set the Destination Directory to <WINSYSDIR>.  Then launch
        the Explorer and drag the necessary files (as determined by
        using the above matrix) to the newly created folder.  These
        files should be located in your Windows\System directory on
        your hard drive (if not, you can find them on the Delphi 2.0
        CD-ROM under \RUNIMAGE\DELPHI20\WINDOWS\SYSTEM32).
4)     Finish the rest of the Setup procedure.
You are now ready to deploy your application.  InstallShield will
automatically register all OCX's and DLLs that have <WINSYSDIR> set
as their destination directory.
-----
I´ve performed your indications in the client computer:
-To Copy  NMODCOD.DLL & POPCT.OCX (nedeed component popmail) to the
\windows\system component
-To Run REGSRV /S NMODCOD.DLL &  REGSRV /S POPCT.OCX
..but, the client computer when I ran the program shaw the message 'libraries
nedded not found'
..so I had to look the .dll that was loaded& active  in the (Delphi computer)
when the program was runing and compare with it wasn´t. I found two new
libraries:
NMORENV.DLL & NMSCKN.DLL.

Then I copied these to the \windows\system of the client computer & the program
ran ok. ....

--------
Subject:  Re: How to register classes of intenet solution Pack D3

Harry,
Take a look at this.....straight out of the help file for the NetMAnage
Controls...

To install your package with support for NetManage ActiveX controls on a
target system, follow the procedures below.

Step1. Search for previously installed versions.

Your installation process should search for previous versions of the
controls on the target machine. The purpose of this is to verify that the
software you are installing is the latest.
The NetManage and Microsoft files should be found in the Windows system
directory of the target machine. For Windows 95, this directory would be
%windir%\system. For Windows NT, this directory would be %windir%\system32.
You can use Microsoft's VerFindFile() function to determine if the ActiveX
files exist on the target machine.
If files are found, go on to Step 2; otherwise, go to Step 3.

Step 2. Compare file versions

If step 1 found some of the NetManage files to installed already on the
target machine, you will need to check the version of both the files you
are installing and the files already on the machine. We suggest you replace
the files on the target machine if the files you are installing are newer.
Microsoft's VerInstallFile() function can be used to install files based on
the version information. This function checks the file version and can also
install the file.

If the files on the target machine are older, go to Step 3; otherwise, go
to Step 4.

Step 3. Install files

As described in Step 1, the NetManage redistributable files should be
installed in the Windows system directory.

Step 4. Registration

You must register the common DLL for the ActiveX controls. After this file
is registered, you may register some or all of the controls, depending on
your applications requirements.
To register these controls, run the following commands from your installer.

REGSVR32 /s NMOCOD.DLL
        REGSVR32 /s FTPCT.OCX
        REGSVR32 /s HTML.OCX
        REGSVR32 /s HTTPCT.OCX
        REGSVR32 /s HTTPSR.OCX
        REGSVR32 /s INETCT.OCX
        REGSVR32 /s INETSR.OCX
        REGSVR32 /s MIME.OCX
        REGSVR32 /s NNTPCT.OCX
        REGSVR32 /s POPCT.OCX
        REGSVR32 /s SMTPCT.OCX
        REGSVR32 /s WCGI.OCX
        REGSVR32 /s WINSCK.OCX

You must run REGSVR32 on NMOCOD.DLL before you register any other OCX. You
need not register more OCXs than those used in your control. For example,
if you only used FTPCT.OCX, you only need to register NMOCOD.DLL and
FTPCT.OCX.

There is another topic called Distributable Files. Check this out too for
required files based on the controls in use within your application. It's
all there in the help file for the controls.