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 ... 12 13 [14] 15 16 ... 21
196
Applications / PMChart - and other v 2.1 applets
« on: February 26, 2019, 07:19:06 pm »
Does anyone have PMCHART hanging around from an old OS/2 v 2.1 installation? Or know what the format of the file is and how to extract the app from the OS/2 2.1 CD? It is in the directory

OS2SE21\DISK_7

on the CD.

It appears that PMCHART.EXE also needs PMCHART.HLP, and possibly MGXVBM.DLL, MGXLIB.DLL, INVEST.DAT, INVEST.GRP, FASHION. DAT, FASHION.GRP, GREEN.DAT, GREEN.GRP and maybe MIRRORS.DLL

I believe there were also some other applets that came with v 2.1 and disappeared in later versions. For example I cannot find PMCHART on the Warp 3 CD.

197
Applications / Re: WinZip
« on: January 19, 2019, 06:59:46 pm »
After you install WinZIp, when you click the Help - About Winzip... button you will see a Register button.

Click on the Register button and you will get a dialog to enter the registration code  - see the attachment.

After you have registered the product the Registration button turns into a License button - which simply brings up help on the license.

FWIW the install program (setup.exe) stopped with an error saying the timestamp of the README.TXT file did not match the timestamp of SETUP. I fixed that by running TOUCH *.*  on the install files and restarting SETUP.EXE. Also the registration for later versions works on earlier versions, but not vis a versa - according to WinZip's website.




198
Mathias,

I had an issue of directories not showing up in the WPS - I think similar to your issue. The solution was to remove the extended attributes from a file. That thread is https://www.os2world.com/forum/index.php/topic,1273.msg11930.html#msg11930

Someone else (Dariusz) had what might be a related issue, which I don't know if he ever got fixed. That thread is https://www.os2world.com/forum/index.php/topic,1479.0.html

On the second thread you will see that Roberto had a similar issue across a network - his solution was to replace the network driver.

You will also see on the second thread that a question arose as to whether the issue was an xWorkplace issue or in the WPS itself. That question is never answered in the thread, but Rich Walsh has a posting on how to disable xWorkplace in order to try an isolate the problem. (If Dariusz reads this perhaps he can give us an update on his WPS/xWorkplace issue.)

As to your general question of has anyone else seen this issue - I don't know about your specific issue, but the WPS is an interesting, complex animal. I strongly suggest archiving your desktop periodically - right click on the desktop, select Properties, and then the Archives tab. I used to archive at every desktop start up but that turned out not to be too smart. You can only store 9 archives and I found myself needing to go back more than 9 to get to a stable archive. So I suggest manually archiving when appropriate - so maybe once a week or when you make major changes.

199
Applications / Re: PMMail - COMCAST - secure tunnel
« on: January 09, 2019, 05:18:17 am »
Seems to me if we, the OS/2 community, have access to the source code of PMmail and can make whatever changes or fixes that are needed or desired, then that is close enough to open source.

I agree with Doug Bissett in prefering email messages in text format rather than HTML format. Maybe its my age, maybe its my paranoia, but I don't want email as HTML: I don't want someone else monitoring which messages I read, when I read them, and how often I read them.

I tried switching from PmMail to ThunderMonkey  some years ago but it could not handle sending emails out on different accounts; it could receive from multiple accounts but could only send out using a single account.  Plus there was the email as HTML issue. So I stuck with PmMail.

PmMail is a strange animal that works well in so many ways, and at the same time has some ah, interesting, design issues. Like storing messages as files and using Presentation Manager containers as the user interface.

200
Setup & Installation / Re: REGEDIT2 export & import
« on: December 27, 2018, 12:55:54 am »
Andre,

Acrobat version 5 can be downloaded at www.os2site.com/sw/util/pdf/os2kitacrobatreader51preview1.exe.

I have problems printing with both version 4 and version 5: they both produce a *.spl file that just sits in the queue - I am using AROS. Strangely enough if you double click on the file in the printer object (which opens it in the system editor), then save it as a *.ps, then drag it back to the printer object it will then print.

You might also want to try qpdfview.exe. Although since (I believe) it is a qt user interface to the same PDF library that Lucide it might not fix your problem. I like it because I can open multiple PDFs at once - but it only prints using CUPS.


201
Applications / Re: ODBC v 3 - SQLConnectW() - DB2 CLI
« on: December 19, 2018, 06:31:49 pm »
Thanks Roberto for the suggestion.  I have the DB2 v 7.2 client setup to use either Netbios or TCP/IP. I get the crash either way.

Based on the info from IBM on the issues of going to version 7.2 on Unix I installed the DB2 client version 7.1 on another machine (eCS 2.0)  along with a version 3 ODBC driver manager. That works. The DB2 ODBC driver reports itself as ODBC version 3. It appears that one of the differences between DB2 v 7.1 and 7.2 is the ODBC driver was upgraded to  version 3.52.

The conclusions at this point are:
1) if you have an ODBC driver manager at version 3 you can use DB2 client version 7.1 but not version 7.2.
2)  If you have an ODBC driver manager at version 2.5 you can use either version of the DB2 client.
3) If you bypass ODBC and call into the CLI library directly you can call the ANSI version of the functions and it appears to work OK.


I am pasting some info from the DB2 site about ODBC and unicode.  Based on the name, I believe the version 3 OS/2 driver manager is DataDirect. Earlier versions of driver managers can be DataDirect or Visigenic

stuff from DB2 site
--------------------------------------
DB2 10.5 for Linux, UNIX, and Windows
CLI applications that are ODBC-compliant can access a DB2® database through the CLI/ODBC driver in one of two ways:
linking to the CLI/ODBC driver library or linking to the ODBC driver manager library.

CLI applications can access a database by:

    Direct access - An application links to the CLI/ODBC driver library and makes calls to exported CLI/ODBC functions.
    Unicode applications accessing the CLI/ODBC driver directly should access and perform transactions against the
    database using the CLI Unicode functions, and use SQLWCHAR buffers with the understanding that all Unicode data
    is UCS-2. To identify itself as a Unicode application, the application must connect to the database using either
    SQLConnectW() or SQLDriverConnectW().
   
    Indirect access - An application links to an ODBC driver manager library and makes calls to standard ODBC functions.
    The ODBC driver manager then loads the CLI/ODBC driver and calls exported ODBC functions on behalf of the application.
    The data passed to the CLI/ODBC driver from the application might be converted by the ODBC driver manager. An
    application identifies itself to an ODBC driver manager as a Unicode application by calling SQLConnectW() or SQLDriverConnectW().

When connecting to a data source, the ODBC driver manager checks to see if the requested driver exports the SQLConnectW()
function. If the function is supported, the ODBC driver is considered a Unicode driver, and all subsequent calls in the
application to ODBC functions are routed to the functions' Unicode equivalents (identified by the 'W' suffix; for example,
SQLConnectW()) by the ODBC driver manager. If the application calls Unicode functions, no string conversion is necessary,
and the ODBC driver manager calls the Unicode functions directly. If the application calls ANSI functions, the ODBC driver manager
converts all ANSI strings to Unicode strings before calling the equivalent Unicode function.

If an application calls Unicode functions, but the driver does not export SQLConnectW(), then the ODBC driver manager routes
any Unicode function calls to their ANSI equivalents. All Unicode strings are converted by the ODBC driver manager to ANSI
strings in the application's code page before calling the equivalent ANSI function. This might result in data loss if the
application uses Unicode characters which cannot be converted to the application's code page.

Various ODBC driver managers use different encoding schemes for Unicode strings, depending on the operating system:
Table 1. Unicode string encoding schemes by operating systemDriver manager
Operating system                        Microsoft Windows    Linux and UNIX
Microsoft ODBC Driver Manager            UTF-16*            not applicable
unixODBC Driver Manager           UCS-2                   UCS-2
DataDirect Connect for ODBC Driver Manager    UTF-16*    UTF-8

* UTF-16 is a superset of UCS-2 and therefore is compatible

The DataDirect ODBC driver manager for DB2® can be used for connections to the DB2 database.
Restrictions

Complications arise when using the CLI/ODBC driver with the DataDirect Connect for ODBC Driver Manager
in the UNIX environment because of the use of UTF-8 character encoding by the driver manager. UTF-8 is a variable length
character encoding scheme using anywhere from 1 to 6 bytes to store characters. UTF-8 and UCS-2 are not inherently compatible,
and passing UTF-8 data to the CLI/ODBC driver (which expects UCS-2) might result in application errors, data corruption, or application exceptions.

To avoid this problem, the DataDirect Connect for ODBC Driver Manager 4.2 Service Pack 2 recognizes a CLI/ODBC driver and not
use the Unicode functions, effectively treating the CLI/ODBC driver as an ANSI-only driver. Before release 4.2 Service Pack 2,
the DataDirect Connect for ODBC Driver Manager had to be linked with the _36 version of the CLI/ODBC driver which does not export
the SQLConnectW function.




202
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

203
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?

204
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?

205
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.

206
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.


207
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? 

208
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.

209
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.

210
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?

Pages: 1 ... 12 13 [14] 15 16 ... 21