Instalación Equipo PASABAN 1

8/13/2019 Instalación Equipo PASABAN 1

http://slidepdf.com/reader/full/instalacion-equipo-pasaban-1 1/14

Tutelkan Ltda.

EQUIPO PASABAN 1 – CMPC PLANTA MAULE

PROCEDIMIENTO DE INSTALACIÓN

PASABAN I





www.tutelkan.com Página 3 de 14


1. PASOS PREVIOS A LA INSTALACIÓN

En

primer

lugar

es

necesario

actualizar

el

antivirus

instalado

en

el

equipo,

en

este

caso se trata de McAfee VirusScan Enterprise Ver. 8.5i. Luego se instala el Service Pack 3

para Microsoft Windows XP.

1.1. REQUERIMIENTOS MÍNIMOS DEL SISTEMA

Hardware

• Intel Pentium 166 MHz o superior (recomendado Pentium 4 de 2.8 GHz).

• 256

Mb

de

memoria

RAM

(recomendado

1

Gb).

• Disco Duro de 40 Gb.

• Unidad de CD‐ROM.

• Resolución monitor VGA o superior.

Software

• Microsoft Windows XP Profesional

• VNC (Virtual Network Computing)

Otros

• Es necesario particionar el disco duro en dos unidades lógicas, esto es, tener unidades C y D. El propósito de esto, es tener un respaldo en el mismo equipo

de los instaladores y código fuente de la máquina Pasaban.







• A continuación aparecerá una ventana como en la figura 3. Allí se debe escribir la

contraseña para el usuario elegido y se presiona el botón “Aceptar”.

Figura 3.‐

Luego de esto, el sistema iniciará sesión automáticamente con el usuario

“Administrador” sin necesidad de ingresar la password.





1.3. INSTALACIÓN DE BORLAND DELPHI V7 ENTERPRISE

Desde

la

carpeta

“E:\BORLAND

DELPHI

V7

STUDIO

ENTERPRISE”,

se

ejecuta

la

aplicación setup.exe, donde aparecerá una pantalla como muestra la figura 4.

Figura 4.‐

Luego se ingresa el Serial Number “6AMD‐PKG68E‐DB8PP7‐9SFE”, y la

Authorization Key “3QH‐9QW”. Ver figura 5.

Figura 5.‐





Para el resto de la instalación, se deben considerar todos los componentes por defecto que considera la aplicación.

1.4. INSTALACIÓN DE FIREBIRD 1.5.1

Se instalará la versión 1.5.1, la cual fue descargada desde: http://prdownloads.sourceforge.net/firebird/Firebird‐1.5.1.4481_embed_win32.zip

• Se debe copiar la carpeta “\Firebird‐1.5.1.4481_embed_win32” desde el CD de

instalación al disco duro “C:\”.

• Luego, dentro de la carpeta “C:\Firebird‐1.5.1.4481_embed_win32”, se crea

una copia del archivo “fbembed.dll” y se renombra como “gds32.dll”. • Por último, se copia el archivo “gds32.dll” a la carpeta raíz que contiene la

aplicación PASABAN.

1.5. INSTALACIÓN DE COMPONENTES APRO (Async Professional)

• Se debe

copiar

la

carpeta

“\APRO”

desde

el

CD

de

instalación

al

disco

duro

“C:\”.

• Ejecutar el DELPHI.

• Luego, desde el menú principal de DELPHI, ir a “Tools‐>Environment Options…”, donde aparecerá una ventana como muestra la figura 6.





Figura 6.‐

• En la pestaña “Library”, en el campo “Library path” se debe agregar la ruta

“C:\APRO\SOURCE”

• Luego, desde DELPHI, se abre el paquete “A406_D70.dpk” ubicado en la

carpeta “C:\APRO\PACKAGES”, y se presiona el botón “Compile”.

Figura 3.

‐

• Por último, una vez compilado el paquete, se presiona el botón “Install”.





1.6. INSTALACIÓN DE LA APLICACIÓN PASABAN

• Se

debe

copiar

la

carpeta

“\PASABAN”

desde

el

CD

de

instalación

al

disco

duro

en

unidad “C:\”.

• Se debe abrir con DELPHI el archivo de proyecto “cutter.dpr” desde la carpeta

“C:\PASABAN\CMPC_23”.

• Luego, se debe compilar la aplicación desde el menú “Project”, opción “Compile

Cutter”

• A continuación, se genera el ejecutable “cutter.exe”, a través del menú “Project”, opción “Build Cutter”.

• Por último se crea un acceso directo en el escritorio del equipo para la aplicación

“C:\PASABAN\CMPC_23\CUTTER.EXE”.

Nota: La aplicación también podría funcionar, sólo al copiar el ejecutable cutter.exe y

generar un enlace directo en el escritorio de la máquina, sin embargo, se recomienda

compilar la aplicación para garantizar que tanto el fuente, como todos los

componentes empleados sean los correctos, de lo contrario el ejecutable por sí solo

podría no funcionar.





1.7. ANEXO A – Documentación Adicional Firebird 1.5.1

Firebird 1.5.1 Embedded Server notes

1. GENERIC INFORMATION

The embedded server is a fully functional server linked as a dynamic library (fbembed.dll). It has exactly

the same features as the usual server and exports the standard Firebird API entrypoints.

2. ISSUES AND LIMITATIONS

2.1. Registry The Firebird registry entries are ignored. The root directory of the embedded server is the directory of its binary file (library).

2.2. Database

access

Client access can be only via the TCP/IP local loopback protocol, i.e. a TCP/IP connection string that includes the server name "localhost" or IP address 127.0.0.1; or by using the Named Pipes protocol incorporating the Windows server name.

The embedded server does not support the IPServer "local connect" to a database file path without a

server name. The client must have exclusive access to the database file.

The embedded server acts as a true local server for a single client accessing databases on a local machine. It can also act as a remote gateway that redirects all network calls to other hosts, just as the

regular client library does.

2.3. Authentication and security The security database (namely security.fdb) is not used in the embedded server and hence is not required. Any user is able to attach to any database. Since both the server and the client run in the

same address space, the security becomes just an agreement between both sides which can be easily

compromised. But note that SQL privileges are still checked.

2.4. Compatibility You may run any number of applications with the embedded server without any conflicts. Having IB/FB

server running is not a problem either.

But you should be aware that you cannot access single database from a number of the embedded

servers simultaneously, because they have SuperServer architecture and hence exclusively lock

attached databases.

3. USAGE

Just copy fbembed.dll into the directory with your application. Then rename it to either fbclient.dll or gds32.dll depending on your database connectivity software. Then start your application and it will use

the embedded server as a client library and will be able to access local datasases. You should also copy

firebird.msg and firebird.conf (if necessary) to the same directory.





If external libraries are required for your application, then you should have them separately. Most probably, it will be INTL support (fbintl.dll) or UDF libraries. To be able to use them, you should place

them into the directory tree which emulates the Firebird server one, i.e. has subdirectories like /intl or /udf:

c:\my_app\app.exe

c:\my_app\gds32.dll c:\my_app\ib_util.dll c:\my_app\firebird.conf c:\my_app\firebird.msg c:\my_app\intl\fbintl.dll c:\my_app\udf\fbudf.dll

If you want to place the Firebird files (excluding the renamed fbembed.dll) in another directory, you

need to modify your firebird.conf and set Root Directory to the Firebird directory tree. Example:

c:\my_app\app.exe

c:\my_app\gds32.dll c:\my_app\ib_util.dll

c:\my_app\firebird.conf d:\fb\firebird.msg

d:\fb\intl\fbintl.dll d:\fb\udf\fbudf.dll

firebird.conf: RootDirectory=d:\fb





1.8. ANEXO B – INSTALACIÓN DE LOS COMPONENTES APRO

TurboPower Async Professional

Table of contents 1. Introduction

2. Package names

3. Installation

4. Version history

4.1 Release 4.06

1. Introduction

Async Professional is a comprehensive communications toolkit for Borland Delphi, C++Builder, & ActiveX

environments. It provides direct access to serial ports, TAPI, and the Microsoft Speech API. It supports faxing, terminal emulation, VOIP, & more.

This is a source‐only release of TurboPower Async Professional (APRO). It includes designtime and

runtime packages for Delphi 3 through 7 and C++Builder 3 through 6.

For help files and a PDF manual, please see the tpapro_docs package on SourceForge

(http://sourceforge.net/projects/tpapro).

2. Package names TurboPower APRO package names have the following form:

ANNNMKVV.*

| |||

| ||+‐‐‐‐‐‐ VV VCL version (30=Delphi 3, 40=Delphi 4, 70=Delphi 7)

|

|+‐‐‐‐‐‐‐

K

Kind

of

package

(R=runtime,

D=designtime)

| +‐‐‐‐‐‐‐‐ M Product‐specific modifier (typically underscore, V = VCL, C = CLX) +‐‐‐‐‐‐‐‐‐‐‐ NNN Product version number (e.g., 406=version 4.06)

For example, the APRO designtime package files for Delphi 7 have the filename A406_D70.*.

The runtime package contains the core functionality of the product and is not installed into the IDE. The

designtime package references the runtime package, registers the components, and contains property

editors used in the IDE.

3. Installation

To install TurboPower APRO into your IDE, take the following steps:

1. Unzip the release files into a directory (e.g., d:\apro). 2. Start Delphi or C++Builder. 3. Add the source subdirectory (e.g., d:\apro\source) to the IDE's library path. 4. Open & compile the runtime package specific to the IDE being used. 5. Open & install the designtime package specific to the IDE being used. The IDE should notify you

the components have been installed.

4. Version history





4.1 Release 4.06

Please note that the following issue #s are from Bugzilla. These bugs were not exported to

SourceForge.

Enhancements

1880 ‐ Multiple instances 3580 ‐ Error handling

3623 ‐ TAPI Hold and transfer capabilities 3756 ‐ enh: Add ability to force YModem to 128 byte blocks 3981 ‐ Add OnProcessChar commands for cursor on/off 4064 ‐ RAS ‐ Add support for programatic phonebook additions 4065 ‐ RAS ‐ Add support to retrieve connection statistics

Bugs fixed

1350 ‐ TInAddr conflicts with other components

3217 ‐

Once connected

to

an

invalid

ftp

site,

can't

connect

again.

3373 ‐ YModem locks files 3515 ‐ Need update the status when setting DTR and RTS. 3548 ‐ Cannot enter hex values in state conditions 3646 ‐ When switching modes, exception thrown in AdFax checkport procedure. 3688 ‐ TAdModem.BPSRate property not updated

3702 ‐ TApdSendFax, fpPageOK not used for class1

3861 ‐ Invalid modem attributes in XML files 3866 ‐ State machine ‐ Mem leak upon deactivating

3867 ‐ States ‐ StartString and EndString do not escape strings 3879 ‐ Fax ‐ Class 1.0 implementation omission

3887 ‐ Data packet ‐ AV on destroy

3888 ‐ Assign/AssignFile overloads causing problems 3927

‐TAdModem

AV

when

destroyed

3941 ‐ State machine accesses port after closing

3980 ‐ OnProcessChar Command ecAnswerBack does not work. 3982 ‐ Support for Siemens S35i (PDU Mode?) 4004 ‐ Dialing using tone/pulse with TAdModem. 4010 ‐ AV even though ftp://ftp.turbopower.com/pub/apro/updates/APROFixes.htm#3887 was

applied. 4016 ‐ FConnectFired may have broken DoDisconnect. 4050 ‐ Request for read only properties to indicate if scroll bars in use. 4055 ‐ TAdModem ‐ incorrect exception if modemcap folder not found

4056 ‐ TApdModemStatusDialog ‐ Cancel button doesn't work

4057 ‐ TAdModem ‐ AV if port not opened

4062 ‐

Data packet

‐AV

on

destroy

revisited

4066 ‐ Invalid Scroll Regions cause AV

4067 ‐ Provide manual adjustment of character cell sizes in terminal 4068 ‐ TAdTerminalEmulator.teProcessCommand can AV with no terminal 4071 ‐ RAS ‐ Missing some consts 4082 ‐ AV On destroy when turning off mouseselect 4096 ‐ TAdModem ‐ incompatible with user's OnTriggerXxx 4121 ‐ OnTapiFail getting called twice for one failure. 4132 ‐ Fonts changing works incorrectly with VT100





4159 ‐ AdModem ‐ SetDevConfig not forcing initialization

4177 ‐ TApdFaxConverter ‐ idShell conversion may leave reg/ini keys 4186 ‐ TApdSendFax ‐ Class1 error handling

4192 ‐ TApdWinsockPort ‐ DeviceName in log incorrect

Documents

Instalación Equipo PASABAN 1