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 Bissett

Pages: 1 ... 96 97 [98]
1456
Applications / Re: Qpdf
« on: January 25, 2013, 12:21:00 am »
cups.dll is used to support printing as it provides the cient side api's to talk to a cups server.

Hmmm. That might explain some of the odd occurrences that I see when trying to print using CUPS. I have this:
--------------------
 6-10-12  6:57p       920,419    124 a---  cups.dll
        1 file(s)     920,419 bytes used

Directory of M:\cups\sbin

 8-31-11  6:19p       869,291      0 a---  cups.dll
        1 file(s)     869,291 bytes used
------------------------------

Which one is right? Neither one of them is in LibPath. Perhaps that explains why I can't print from QPDFView. AHA!, yes it does. I tried BeginLibPath to M:\cups\lib and it no longer hangs. It still doesn't print. It pops up a message box that says "Could not print <the file name>". Not extremely helpful, but better than a hang. Now, to try more things...

1457
Applications / Re: Qpdf
« on: January 24, 2013, 09:28:39 pm »
If I try to open a pdf from another directory than that where qpdfview is installed it complains about popqt44.dll not found. So it seems to me that qpdfview doesn't look in it's own directory for its dlls. Is that correct and does it have to be placed in the path or at least do the dlls have to be moved to a directory in the path?

Two things should help. One is that the Working Directory (in the program icon properties) should be the directory where QPDFView is installed. The other is that you should have ".;" (dot semi-colon, without the quotes) in the LibPath statement, in CONFIG.SYS. That is usually close to the beginning of that line. Having the dot entry tells the system to look in the current path (the Working directory) for DLLs. Of course, if you try to use QPDFView from the command line, you need to put the install directory in LibPath, or put the DLLs in a directory that is in the LibPath.

1458
Applications / Re: Qpdf
« on: January 24, 2013, 06:07:56 pm »
I installed QPDFView (after figuring out that there is bad information about JPEG, which should be LIBJPEG). It seems to display okay, but trying to print locks the program, and the desktop. I can CAD to CADH, and kill it, but something is wrong. Yes, I do have CUPS 1.4.8 installed, but it doesn't work very well with my printer (Canon i960, using the BJC-8200 CUPS driver, which is recommended for this printer. It works far better with the OMNI driver for the Canon i950).

On the bright side, I no longer have a mangled display, when scrolling a few lines at a time (at least I haven't seen such a thing, yet). I was never able to get Lucide to edit a PDF file, and QPDFView does do that, although I am not sure that the font that it uses will be acceptable to the government bureaucrats for the form that I want to edit. I will need to compare what it does to Acrobat reader in windows.

I am not sure why I would want plugins. All I ever use Lucide, or now QPDFView, for, is to read, and print, PDF files (and now, possibly, to edit them, as allowed). Since QPDFView won't print (for me), I guess I need to keep Lucide for that job.

The big problem I find with qpdfview is that if I try and open a pdf on another partition (qpdfview installed in e:\qt4-apps, want to open pdf in f:\download) it locks the machine solid and I have to power off and then on again.

I tried that. It works okay, for me. That may indicate that something in printer support is causing a problem. AH!. My CUPS printer driver is installed on my boot drive (poor choice of location, but not worth moving it now). The test, that hung, that I did was on my data drive, where I installed QPDFView. I copied the test PDF to my boot drive, and it opens with no trouble. It still hangs when I click Print. KLibc Pathrewriters might be needed. I will need to find the time to experiment with that stuff.

1459
Comments, Suggestions & Questions / Re: Cruelty in OS2World
« on: January 17, 2013, 05:40:43 pm »
When I log in, there is an option to stay logged in "forever". I always click on that, and I don't get bumped off.

1460
Setup & Installation / Re: Migration problems
« on: January 15, 2013, 01:45:30 am »
You may want to consider removing a couple of lines in your CONFIG.SYS:

According to the ConfigTool database:

SET PM_ASYNC_FOCUS_CHANGE=ON 9000
is for warp 3 only, and should be set in the warp4 (and up) settings, not in CONFIG.SYS.

SET QUEUE_SIZE_THRESHOLD=20000
is also for warp3 only.

You could also try adding the line:
dllbasing=off
near the top of your CONFIG.SYS

1461
Programming / Re: Have questions about porting software to eCS?
« on: January 05, 2013, 04:11:55 am »
Thanks to Paul, I updated to his latest build environment, and applied the DIFF to the WGET 1.14 source (not sure that I did it right, but it works), and now I can build WGET 1.11.1 and WGET 1.14.  :-*

Unfortunately, I broke building PMMail when I did the update. I obviously deleted something that was added to something that got replaced.  :(

Oh well, you win some, and you lose some. Now, to sort out the PMMail build problem.

Well, it took a lot of time, but I got PMMail to build, and I can build WGET 1.14, using the DIFF described earlier by Paul.

I was going to restart a thread about building WGET 1.14, but it seems that all you need is Paul's latest build package, download the WGET package of choice from:

http://ftp.gnu.org/gnu/wget/

(I took the 1.14 tar.gz package), unzip it, and follow Paul's instructions.

Once you get that far, you know that the build environment is basically working, so you can then progress to other projects. It is probably best to pick something relatively simple, that has been done before, so it will be easier to get help when something doesn't go as expected, before going on to building more advanced things (like VirtualBox).   ;D

Have fun... ;)

1462
Programming / Re: Have questions about porting software to eCS?
« on: December 31, 2012, 05:45:04 am »
Thanks to Paul, I updated to his latest build environment, and applied the DIFF to the WGET 1.14 source (not sure that I did it right, but it works), and now I can build WGET 1.11.1 and WGET 1.14.  :-*

Unfortunately, I broke building PMMail when I did the update. I obviously deleted something that was added to something that got replaced.  :(

Oh well, you win some, and you lose some. Now, to sort out the PMMail build problem.

1463
Programming / Re: Have questions about porting software to eCS?
« on: December 29, 2012, 04:55:34 pm »
Quote
Fairly trivial.

For you maybe.  :)

Anyway, now I need to find the time to figure out what you just said, and get this thing to build.

Thanks...

1464
Programming / Re: Have questions about porting software to eCS?
« on: December 28, 2012, 08:14:22 pm »
Quote
FWIW, I downloaded the wget 1.14 source this evening and have run configure.  Will see what's required for me to get it building and post back here

Don't waste too much time on it. I can't get wget 1.11.1 to build either. There is something in my configuration that is wrong, and I won't have time to try to figure it out, until next year.

1465
Programming / Re: Have questions about porting software to eCS?
« on: December 28, 2012, 07:55:04 am »
Quote
wget built very easily with Paul's environment...

I assumed that that was the case, since Paul suggests starting with wget. As I said, I need some guidance, but I also need the time to tackle it again. The main objective, with this project, is to get the build environment to work with a simple project that is known to work, since others have done it. After that, it is easier to move on to more complicated projects.

1466
Programming / Re: Have questions about porting software to eCS?
« on: December 27, 2012, 05:31:39 pm »
I'd suggest starting with a simple command line app like wget

People seem to want to be ambitious and start with something like virtualbox!

I was trying to lead a thread to get wget to build. The latest one wasn't cooperating. Then OS2world ended. I did download an older version, which has been built in the OS/2 environment previously, but I have done nothing with it, other than discover that it won't build either. I am pretty sure that it is just a minor setup problem, but I don't see what it might be, and need some guidance from those who know about these things.

I intend to restart that thread, sometime early next year, unless somebody else wants to start it earlier. Hopefully, it will serve as a guide for others, but it should also serve as a guide to get the build environment to work with a basic project, before a user decides to tackle more complicated things, like virtualbox.   ;D

1467
Off Topic discussions / Re: Merry Christmas
« on: December 25, 2012, 07:20:39 pm »
Welcome back. You were missed.

To all, a Cool Yule.

Pages: 1 ... 96 97 [98]