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 - ivan

Pages: 1 ... 94 95 [96] 97 98 99
Applications / Re: libusb-1.0 port to OS/2 - help needed
« on: May 17, 2013, 12:34:31 am »
Hi Paul, yes, it scans.

using scanimage --mode color --resolution 300 I got the attached output - converted to jpg to take up less space.

Using --format tif produces the expected tif file output and all the resolutions work

I used the page I did because it represents the type of pages I have to copy and sometimes OCR.  In fact I'm quite pleased with the results, thank you.

I notice there are a lot of options in the epson2 backend listed as [inactive], will any of these be made active in the future?

Applications / Re: libusb-1.0 port to OS/2 - help needed
« on: May 16, 2013, 01:22:11 pm »
Paul, just doing scanimage >output.pnm on my Epson 640U produces a black and white scan - just readable, would create problems with OCR.

Applications / Re: libusb-1.0 port to OS/2 - help needed
« on: May 15, 2013, 11:27:19 pm »
Paul, here are the outputs from my usb scanner.

Applications / Re: Qpdf
« on: May 14, 2013, 11:22:55 pm »
Sigil is one of the special cases, as it already needs Qt5 and we don't have that atm. So no chance to get a recent version i'm afraid.

As far as I remember Sigil 0.5.3 is the last version that works with Qt4.7.3.  Sigil 0.6.0 series require Qt4.8.x and Sigil 0.7.x requires Qt5.0.x.

I found Sigil 0.5.3 was very usable with many improvements over the v0.2 that Paul produced, which I still use for quick corrections to epubs - saves having to start windows in VirtualBox/2.

If you can tell me what is needed to setup a build environment I have a spare computer I can dedicate to the task.  It should give me something to do in the long evenings and, hopefully, keep my mind in trim - they say old dogs can't learn new tricks but this one is going to try.

Applications / Re: Qpdf
« on: May 13, 2013, 08:46:18 pm »
Progress of a sort. 

I downloaded qpdfview 0.4.2b1 and tried that.  It opens PDF files!!  Downside the PDF files have to be in the same volume as Qpdfview - try opening a pdf on another volume and it locks the WPS requiring a reset button restart.

Qpdfpdf.dll also appears to have no problems.

I will now move Qpdfview 0.4.2b1 to the same volume as the bulk of the PDF files and continue testing but I like what I see at the moment.

Qt4 is v4.7.3 ga2 according to the change log. 
Qt4 was originally installed using warpin but has been updated from zip files using the same directory structure and placement.  As I said all the other Qt4 applications work without problems. CoolReader3 is especially well used for checking how epubs appear - thank you for that - now a question, how much work is it to port a Qt4 based application, I'm wondering if I could do anything like getting Sigil more up to date?


Applications / Re: Qpdf
« on: May 13, 2013, 07:16:56 pm »
This is getting very frustrating.  Pmdll shows that all the dependencies are loaded apparently without problems yet I still get the error that it can not the pdf.

Applications / Re: Qpdf
« on: May 13, 2013, 03:25:35 pm »
To answer your questions.
fntcfg2.dll 05/01/13
freetyp2.dll 05/01/13
jpeg.dll 19/12/11

All the dlls you list are in \os2\dll or the program directory.

Applications / Re: Qpdf
« on: May 13, 2013, 01:31:55 pm »
Thank you Silvan.

Out.txt was blank
out2.txt is attached.  The qpdfpdf.dll is in the same directory as qpdfview.exe, I also tried with it in \os2\dll and got the same results.

Applications / Re: Qpdf
« on: May 12, 2013, 06:00:28 pm »
Thanks for your reply Silvan.

The version that gives the error message is v0.4.1 and I think I have all the DLLs required but I'm not sure as there is no definitive list.  The fact that all the other Qt4 apps that I am using work without any problems shows that Qt4 and the gcc and klibc dlls are installed correctly.  Cups sometimes prints to the printer on the network print server but I think those problems are caused by the print server going into standby mode and not being woken up correctly.

I have z.dll, jpeg.dll, djv.dll, fntcfg2.dll and freetyp2.dll in \os2\dll so the question is what am I missing.

Note that version 0.3.7b1 works as long as the PDF files are on the same volume as qpdf.

Applications / Re: Qpdf
« on: May 12, 2013, 10:52:50 am »
Thanks melf but that didn't do anything - still the same message.  I'm wondering if it has the ecs file structure hard wired in as the readme says to put the dlls into ecs\dll.

Applications / Re: Qpdf
« on: May 11, 2013, 05:27:04 pm »
Reviving this old topic but I would like to know if anyone has got the latest drop to open a PDF file?

All I get when I try to open a PDF is a message box marked Critical with the statement Could not load PDF plug-in!

I have followed the instructions as closely as possible (no ecs dir on WSeB so dlls go into os2\dll), what am I missing?

Games / Re: Running MGL Doom on Warp 4
« on: May 01, 2013, 09:07:48 pm »
Scott, if you are going to keep your Warp 4 install I think it would be a good idea to make a backup of the os2 directory and then reinstall fixpak 17 letting it overwrite newer files except the kernel files then re-apply snap 3.1.8 again letting it overwrite files.

I say this because it sounds as if you have parts of the system backleveled and this is causing your problems.

Games / Re: Running MGL Doom on Warp 4
« on: April 29, 2013, 03:06:27 pm »
Thanks for the correction David re fixpaks - my excuse, it was late at night after a very frustrating long day and I was going on memory ;)

Scott, I have generally allowed the overwrite but just note the file name so I can restore it from backup if necessary as I think all that is checked is the date of the file rather than any internal information.  For example, several of the files in the SNAP video get given dates when they were installed rather than the date they were created so when you go to upgrade they appear to be newer than the update files when in fact they are not.

As I said there could also be a lot of garbage in your ini files that could be removed with advantage - it also reduces the size if the ini files, another advantage.  I do a run of cleanini /c /restart on all the workstations here every Friday evening which removes redundant references to such things as deleted or moved files and so on.

Games / Re: Running MGL Doom on Warp 4
« on: April 29, 2013, 02:06:12 am »
Scott, I can't answer your question directly because I don't have MGL Doom but from this question and your problems with dialogue boxes it sounds as if you have a very messed up system.

A few questions to get things started. 
What was the fixpak that you last installed?  As far as I can remember 5 was the last official but I have the unofficial 6 on all the workstations here.  There is also the device driver fixpak 3, I seem to remember.
Have you run cleanini, xfix (from xworkplace) or checkini (from wptools) in clean mode and so cleaned out the dross in your ini files?
Last, is there anything else that isn't quite working as it should?  If there is then we need to fix your system before you do much more  ;)

Applications / Re: libusb-1.0 port to OS/2 - help needed
« on: April 26, 2013, 11:52:54 pm »
Hi Paul,

Where do you want us to send the debug information?

My report for Lsusb is about the same as Wim's except I have WSeB and am using Usbres (no eCS hence no UsbDock) for usb information

While Lsusb finds and identifies my Epson Perfection 640U scanner the version of Sane you want testing does not.  I have created a debug log file using the test.cmd you supplied in the zip hence my question about where you want that information sent.

Re. usb.ids just remember that not all of us are using eCS - mine is in the same dir as Usbres (\tools\usb).

Pages: 1 ... 94 95 [96] 97 98 99