Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Doug Clark

Pages: 1 ... 6 7 [8] 9 10 ... 15
106
Applications / Re: PMMail - COMCAST - secure tunnel
« on: December 19, 2018, 08:18:51 am »
Thanks Dave.

Your screen shots helped me correctly setup PM Mail.  I had version 3.06 which still would not work. But after upgrading to v 3.22 everything is working.

Thanks again.
Doug

107
Applications / PMMail - COMCAST - secure tunnel
« on: December 19, 2018, 06:32:41 am »
Comcast has closed their port for plain text authentication. I am trying to get PM Mail to use secure tunnel but I apparently do not have it set up right.

1) On the secure channel setup should the server port and local port be the same number?

2) Should the port number on the account setup be the same as the local port?

3) Has anyone successfully connect to COMCAST with PM Mail using secure channel?

108
Setup & Installation / Re: REGEDIT2 export & import
« on: December 18, 2018, 10:21:08 pm »
BTW Andre,

If you are going to use Acrobat, why Acrobat 4 and not Acrobat 5?

109
Setup & Installation / Re: REGEDIT2 export & import
« on: December 18, 2018, 10:19:39 pm »
Andre,

What you actually need is a Rexx function package called w32util. Since that is compiled to work with Regina Rexx - as opposed to IBM Rexx - then you also need Regina Rexx for Windows and the associated RexxUtil package.

Although I have not tried it, I am guessing that Regina Rexx for windows will run in ODIN.

There was a short period of time when VAC++ 4.0 would not install on Windows 2000, so I made a little "installer" in order to install it. (That problem has been fixed and VAC++ 4.03 installs on Windows 7.) I have attached the script to show how to update the registry using Rexx and the w32util package.

110
Applications / Re: ODBC v 3 - SQLConnectW() - DB2 CLI
« on: December 18, 2018, 07:48:43 pm »
The DB2 client installed is version 7.2, running on AOS.

The DB2 client does come with an ODBC driver manager, but it is version 2.5. The IBM ODBC driver works correctly with version 2.5 ODBC driver managers,  the one supplied by DB2 and others that are available.

The version 3 ODBC driver manager I am using works with version 3 drivers, e.g. dbase and text, and with the SQL Anywhere ODBC driver which is version 2.5

I think the GRAPHIC keyword simply controls what SQLGetTypeInfo() returns in its result set - which is the list of column types supported by the database.

The keyword I was trying to use is "DisableUnicode". I tried putting that in the db2cli.ini, and passing it as a keyword in SQLDriverConnect(). Neither made any difference. This keyword is described in the readme and does not appear in the GUI for ODBC driver setup.

I am going to try and find the v 7.1 ODBC and try that, based on the following from release.txt, even though it is specific to UNIX.

4.37 Merant Driver Manager and the DB2 UDB Version 7 ODBC Driver on UNIX

Incompatibilities have been encountered with Unicode support when the
Merant Driver Manager accesses DB2's ODBC driver on UNIX. These
incompatibilities result in Unicode being used by the Merant Driver Manager
regardless of whether the application has requested its use. This can lead
to problems with products such as the Data Warehouse Center, Information
Catalog Manager, and MQSI, which require the Merant Driver Manager to
support non-IBM data sources. You can use an alternate DB2 ODBC driver
library without Unicode support enabled until a permanent solution is
available. The affected versions of DB2 UDB include Version 7.1 with FixPak
2 or later, and Version 7.2 at any FixPak level.

An alternative DB2 ODBC driver library without Unicode support enabled was
shipped with DB2 Versions 7.1 and 7.2 for AIX, HP-UX, and Solaris Operating
Environment. To use this alternative library, you must create a copy of it,
giving the copy the original DB2 ODBC driver library's name.


111
Applications / ODBC v 3 - SQLConnectW() - DB2 CLI
« on: December 17, 2018, 08:00:00 pm »
The DB2 v 7 ODBC driver is at version 3.52, which supports Unicode. The ODBC driver manager shipped with Lotus Smartsuite is version 3 - which was before Unicode was supported.

When I attempt to connect to DB2 using a DB2 v 7 ODBC driver with a version 3 ODBC Driver Manager I crash. It appears to me from tracing that the ODBC driver manager is, for some reason, calling the wide/unicode version of the DB2 CLI functions instead of the ANIS version. For example there is a SQLConnect() which is ANSI and a SQLConnectw() which is unicode; SQLConnectw() is getting called.

I assume my crashing is related to wide version returning data in buffers allocated for ANSI lengths of data. My believe is, in part, based on the tracing, and the fact that if I call SQLConnect() directly by linking to the CLI library rather than the ODBC library the connection succeeds.

It also appears from IBM documentation that the DB2's  defaults to the wide/unicode versions unless, somehow, restricted to ANSI functions. For example there is a db2cli.ini keyword DisableUnicode=1 listed in the version 11 documentation which I cannot find in the version 7 documentation.

Does anyone know how to restrict to ANSI only for DB2 v 7? 

112
Setup & Installation / Re: REGEDIT2 export & import
« on: December 16, 2018, 06:34:12 am »
I assume that since Andre is talking about Regedit2 he is talking editing the registry. I think SysIni in Rexx is for editing profiles, i.e. INI files.

 I don't know of an OS/2 Rexx function or extention that modifies the registry - which doesn't mean that one doesn't exist.

I do know that Regina Rexx for Windows has a function package that will modify registry entries. I suppose you could run that in OS/2 using ODIN, although I have not tried that. I have run it in Windows and it works well.

113
Setup & Installation / Re: Setup strings with PARSEDB and DATABASE.DAT
« on: December 03, 2018, 12:13:29 am »
The WPS is designed to be modified and there are modifications to WPS objects by DragText and xWorkPlace - just to name two. Each of those "modifications" have added features to WPS Objects - for example DragText adds tabs to the WPProgram object for Environment and Schedule.

The original WPS program object was written to use the entries of DATABASE.DAT to update the options/settings of the original program object. Which makes sense, but doesn't accommodate future enhancements or modifications to WPProgram objects. I was hoping there was a feature in the tags used by WPProgram/Database.dat that would allow the current mechanisim used by WPProgram and DATABASE.DAT to also be used for options/settings for future enhancements to the Program Object that were unknown at the time OS/2 was first created. Setup strings in DATABASE.DAT would have done that - but alas it appears they didn't think about that at the time.

I suppose it would be possible to subclass WPProgram and add a something that also scans another database, say DATABASE.STR, for setup strings and execute those setup strings every time the "Path and file name" entry on the Program tab is changed.

As you point out, using the application file name as the index into the database can cause some unwanted settings when you have two different programs with the same file name that require different settings.

114
Setup & Installation / Setup strings with PARSEDB and DATABASE.DAT
« on: November 16, 2018, 11:10:12 pm »
When creating or updating a Program Object it appears the WP_PROGRAM object in the WPS searches DATABASE.DAT when you cursor off the "Path and file name" on the Program tab of the program object and updates various settings on the program object based on the settings in DATABASE.DAT.

(This is described starting on page 122 of Redbook GG24-3731)

DATABASE.DAT is created/updated by PARSEDB.EXE based on text in DATABASE.TXT and "tags" in DBTAGS.DAT.

I was hoping I could add a new "tag" in DBTAGS.DAT that equals a setup string, make an entry in DATABASE.TXT/DATABASE.DAT with the setup string for a program, and have the Program Object execute the setup string when the user types a executable name in the "Path and file name" entry field.  But alas, it does not work.

Has anyone messed around with PARSEDB and DATABASE.DAT and created new tags to add settings to DATABASE.DAT that worked?

115
Applications / Re: Problems Installing a PPD for PM
« on: November 11, 2018, 02:09:51 am »
Thanks Roberto, Lars, and Pete for your help.

My problem (or one of my problems) was I didn't understand that PIN.EXE needs an existing printer driver in order to process the PPD file. And as Lars pointed out, you can't run it in the directory (and probably shouldn't anyway) where it is installed because it will be locked if any application has loaded it.

What I eventually figured out is you have to point PIN to an already existing printer driver file (psprint.drv) or it will fail. The steps that worked for me

copy c:\os2\dll\psprint\psprint.*  f:\temp\driver
copy my.ppd f:\temp\ppd
pin ppd f:\temp\ppd  f:\temp\driver\psprint.drv
use Manage Printers to Add.Update PSPRINT.DRV

The ideal solution is to use the Manage Printers object to directly install the PPD. Unfortunately on my machine (ArcaOS) the Install PPD option of Manage Printers fails with an error, which is why I was using PIN.EXE. (I will note Install PPD  works in eCS 2.2)

But with CUPS installed the other option is to simply install a CUPS printer for the PPD using the -Custom- -- Other Printer (requires PPD) -- option. That automatically imports the PPD to PSPRINT.DRV and creates a printer object in the Printers folder with its output port pointing to CUPS. Very nice, very slick. (I wish I was smart enough to have thought about that a couple of days ago.) Then I can install another printer using the newly imported PPD that has been created in PSPRINT.DRV

As Pete pointed out earlier you don't need CUPS if you are using a postscript printer. But having CUPS (once I figured it out) makes installing a new PPD very easy. Plus qpdfview (tabbed PDF viewer) prints directly to CUPS so you need CUPS to print from that application. I image there are other Qt based apps that will only print directly to CUPS, so you will need CUPS for those even with a postscript printer.

The one problem I have is specifying single side or duplex on an individual print job when printing to CUPS through a PM printer object doesn't work. The printer uses the duplex setting from CUPS regardless of what you specify on the print job - when printing through a PM print object. qpdfview, whichs prints directly to CUPS, does handle the duplex setting correctly. Which is one reason why you need a print object that outputs through lpr or appsocket in addition to the CUPS printer object.

116
Applications / Re: Problems Installing a PPD for PM
« on: November 09, 2018, 02:11:22 am »
Thanks roberto and Lars for your help,

I almost had it all running correctly and then reinstalled a cups driver and everything went back to the start - and now I can't get to where I was before.

Part of my problem was Lucide was not honoring the "print on a single side" / "print on 2 sides" setting in the driver; it always prints on both side no matter what the setting. I thought for a number of hours that it was a printer driver issue but it appears to be a Lucide issue.

There was a period of time when it was printing via CUPS, via lpd from OS/2 and from WinOS2 as postscript, and printing from OS/2 as PCL. But then I did something that took me back to the beginning.

The sad part is the import *.ppd in WinOS2 works great. But the Manage Printer object in ArcaOS has a bug.

[changed Printer Manager to Manage Printer]

117
Applications / Re: Simple CUPS Support Printer Quesion
« on: November 08, 2018, 02:29:34 am »
Pete, and Eric,

Yes hplip is installed on my machine. The version I have is 3.17.11-1. Apparently that hplip contains *.PPD files for multiple HP m452 printers. The problem is some of those printers have duplexers and some don't. But all (both) the *.PPD files have the same nickname, and apparently CUPS uses the nickname to distinguish between "printers". So I found the *.ppd file for m452 with duplexing, changed the nickname, installed that in CUPS, modified the existing m452 printer thingy I already had in CUPS to the new *.PPD and now duplexing, and the printer, are working correctly.

Duplexing shows up in apps that print directly to CUPS, as shown in the attachment, but not in apps that print to the associated PM printer object. I need to figure out how to update the PM printer object with the new PPD file.

118
Applications / Re: CUPS User ID and Password
« on: November 08, 2018, 02:14:51 am »
Eric,

Yes it is. Although when I wrote that I did not realize duplexing wasn't appearing as an option in CUPS. That problem turned out to be the wrong *.PPD file. I found the correct PPD file and attached that to a posting I made in the thread "problems installing a PPD in PM". Duplexing now appears as an option on those apps that print directly to CUPS - such as qpdfview.

Now my problem is getting duplexing to show up as an option for applications that print though the PM print system.

119
Applications / Problems Installing a PPD for PM
« on: November 07, 2018, 10:42:50 pm »
I am attempting to install a PPD using PIN.EXE and get the error message

reading driver extended attributes
   fail
SYS005: Access is denied
fail

Background
-----------------
I have an HP m452dn printer. The m452 family of printers includes m452dn, m452dw (with duplexer) and m452nw (no duplexer).

hplib, which apparently is where CUPS gets (some of) its *.PPD files from has
hp-color_laserjet_452-ps.ppd   and
hp-color_laserjet_452d-ps.ppd

The "d" in the name indicates the PPD for the printers which have a duplexer. Unfortunately the nickname in both those PPD files is the same, so CUPS can't distinguish between the two files.

I found the correct *.ppd for the HP m452 models with a duplexer, changed the nickname and used CUPS to modify the printer I had already installed to the new PPD. (That file is attached as hp_m452d_ppd.zip) Everything works great.

Problem
-------------
Now I want to update the PM printer driver with the new, correct PPD that contains duplexer info.  When running PIN to import the PPD I get an access is denied error - a screen shot of the error message is attached. I also get an error when trying to import the same PPD with the Manager Printers object in the Printers folder.

I get the message running PIN on the PPD before it has been cleaned, and after the PPD has been cleaned with cleanPPD.exe.  I have attached the cleaned PPD

120
Applications / Re: CUPS User ID and Password
« on: November 06, 2018, 10:09:59 pm »
After updating everything I could think of that was related to CUPS, including klusrmgr, I still could not get past the user id and password prompt.

But when I assigned a password to root, and saved the file in klusrmgr, I could then get past the user id and password prompt.  And CUPS started sending stuff to my printer. Very nice.

Thanks for the help


Pages: 1 ... 6 7 [8] 9 10 ... 15