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 - Dariusz Piatkowski

Pages: 1 ... 88 89 [90] 91 92 ... 96
1336
Hi Dave!

My os2tk45 has this in the readme.1st
Quote
This package updates IBM Developer's Toolkit for OS/2 v 4.50 and 4.51 to the
current level (4.52 with HIGHMEM update). To install it, copy the entire
directory structure over your existing Toolkit setup.

New content added since 4.50 includes the OMF and LX executable format
documentation (BOOK\OMFREF.HTM and BOOK\LXREF.HTM).

So yes, uninstall the v4 toolkit and install v451 and then v452 over it.

Great insight...I did not catch this but it does give me a pretty good idea regarding how to install the 4.52 stuff.

As it happens, shortly after I posted here I did come across the GitHub repository which I believe attempts to make the latest version of the toolkit available, see https://github.com/bitwiseworks/os2tk45. Full ZIP release is there, but it is not an install, instead it is very much meant to be deployed on top of an existing install, so very much like the 4.52 version which you have.

OK, now onto what I had not actually expected to be the more challenging part of this process, which is the actual 4.00 un-install...I have VACPP objects in my "Installed Features" folder (attached photo shows this). Both of the "VACPP_FI" objects point to the "OS/2 Toolkit - xxx" features, however I have no idea why the heck I have two of the "VACPP_FI" objects in the first place. What I do not have anywhere is a 4.00 Toolkit un-install object or even a stand alone "Installed Features" object.

Either way, I have not attempted to un-install from here, but something tells me I should try this first. My only worry is that I do not want to impact the actual VisualAgeC++ or my IBM C/C++ installations...boy...it's been a while since I have done this...sure got a little "rusty" on the know-how...LOL!

1337
Quite some time ago I installed a Warp4 version of the OS/2 Toolkit on my machine, however, I am wanting to get "updated" and take a stab at a few small things (like PUMon which eats up 50% of CPU on a single core when I run my system with all 6-cores enabled - it does not exhibit this behaviour when only 5 cores are enabled though...LOL). So the intent is to build a workable debug environment and re-compile source code as needed.

Over the years I have accumulated an assortment of various Toolkit updates (although none of them beyond the original War4 Toolkit CSDs have been installed) and as best as I can tell I have what looks to be an official 4.50.2 (XR04520) release. Are there any newer official OS/2 Toolkits/updates out there?

Now regarding the actuall install/un-install process. I have the VisualAgeC++ and IBM C/C++ Compiler (3.6.5) tools installed as well. A few years back I had a working development environment set up and did a little OS/2 investigating trying to understand how the development environment was structured.

Quite frankly, I can not remember if the OS/2 Toolkit was a separate install, or whether that was part of the IBM C/C++ install...pretty certain it was not included with VisualAgeC++.

Can anyone recommend the best practice to follow here to get this cleaned-up? I am thinking it would be best to un-install the Warp4 Toolkit and then install the newer 4.5x stuff...I have the following versions available:

1) IBM OS/2 Developer's Toolkit Version 4.5 - XR04500 - 4.50
2) IBM OS/2 Developer's Toolkit Version 4.5 - XR04510 - 4.50.1
3) IBM OS/2 Developer's Toolkit Version 4.5 - XR04520 - 4.50.2

Do I un-install my Warp4 Toolkit and install all of the above 1 after the next (additive install), or should I go directly to 4.50.1 and then apply the 4.50.2 on top of it? The 4.50.2 drop I have may be an un-official release as it appears to be made up of just the stuff that was updated and does not have a CSD style install.

1338
Applications / Re: AVxCAT 1.4 alpha
« on: February 20, 2016, 05:40:05 am »
...How many files do you have under the path you open through internal filemanager ? What is your path name where ?...
Not many files, about 6 files that match the filter extension...but about 18 files in total in that directory...the path name I've used is "G:\tmp\camtest"

From a process perspective here is what PSTAT returns:

G:\APPS\MULTIMEDIA\AVXCAT\AVXCAT.EXE   005F       2B      G:\OS2\DLL\REXXAPI.DLL
                                  G:\OS2\DLL\DOSCALL1.DLL*
                                  G:\OS2\DLL\QUECALLS.DLL*
                               G:\OS2\DLL\REXX.DLL
                                  G:\OS2\DLL\DOSCALL1.DLL*
                                  G:\OS2\DLL\REXXAPI.DLL*
                                  G:\OS2\DLL\KBDCALLS.DLL*
                                  G:\OS2\DLL\NLS.DLL*
                                  G:\OS2\DLL\SESMGR.DLL*
                                  G:\OS2\DLL\QUECALLS.DLL*
                                  G:\OS2\DLL\MSG.DLL*
                               G:\OS2\DLL\DOSCALL1.DLL*
                               G:\OS2\DLL\PMGPI.DLL*
                               G:\OS2\DLL\PMWIN.DLL*
                               G:\OS2\DLL\PMSHAPI.DLL*
                               G:\OS2\DLL\PMDRAG.DLL*
                               G:\OS2\DLL\PMCTLS.DLL*

1339
Applications / Re: AVxCAT 1.4 alpha
« on: February 20, 2016, 05:30:39 am »
Remy,

...Could you please provide me some information about your environnement ( ECS V? OS2 v?, number of drives etc ... )...

No worries, this may be an issue that others may run into so I like to share as much of my experience with our OS/2 community as possible.

OK, so we are talking 4.52 SMP machine here. 6-core AMD Phenom II X6 CPU running on MSI 880G-E45 series motherboard. Running ACPI 3.22.08 release here.

Now the drives...oh boy (you are probably going to shake your head, but here it comes), in total I have 19 drives (volumes really across 3 physical hard-drives), 2 are not accessible (file-system not mapped), 7 are main OS/2 install, 7 are HOT/nightly backups, 3 are Samba drive mappings to other home PCs (windows boxes).

All my OS/2 drives run HPFS386, all are 60Gig in size.

I tested your "pre" user-command, works great...the conversion of my 130Meg MJPG to h264 MP4 took all of about a 30 sec with all cores chugging away (threads=4, I could have ran more given 6 CPU cores though, however that Settings spin-button only let me go to 4, if I leave on 'auto' the program runs into a problem and ffmpeg claims that the pipe was shut-down/broken, I will capture the specific details later on).

Thanks again...even with the SMP on/off manual flip this is great already!!!

1340
Applications / Re: AVxCAT 1.4 alpha
« on: February 20, 2016, 05:17:53 am »
This sounds like a simple smp problem and perhaps can be fixed by marking avxcat.exe as MPUNSAFE. At least it would be worth trying. I believe the syntax is
Code: [Select]
markexe MPUNSAFE avxcat.exe

Tried that already...same result...the only thing that seems to work is running 'setproc' utility...not sure who wrote that...but you can find it on Hobbes here => http://hobbes.nmsu.edu/download/pub/os2/util/system/setproc.zip

Here is something else I noticed. When I start up either PSI or Remy's app I see libc06b4.dll showing up in Theseus...but that is a DLL that is quite old and is "retired" now...lol...yet both apps still pull it in, my DLL details are:

 2-01-05  10:21a    562710           0  libc06b4.dll

...and here is the full list of all libcxxx DLLs:

10-27-03   5:13p    230785         124  libc04.dll
 4-14-04   4:37p    356330           0  libc05.dll
10-26-14   8:17p     48179           0  libc06.dll
10-26-14   8:17p     48179           0  libc061.dll
10-26-14   8:17p    157161           0  libc062.dll
10-26-14   8:17p    157161           0  libc063.dll
10-26-14   8:17p    157213           0  libc064.dll
 8-11-08   5:53a   1353252         124  libc064x.dll
10-26-14   8:17p    157213           0  libc065.dll
10-26-14   8:16p   1361666           0  libc066.dll
 2-01-05  10:21a    562710           0  libc06b4.dll
12-30-11  11:08a    114176           0  libcbeta
 2-01-05  10:21a    562710           0  libcbeta.dll

So maybe some sort of DLL conflict where one of these is not SMP-safe?

1341
Applications / Re: AVxCAT 1.4 alpha
« on: February 19, 2016, 05:10:43 am »
Hi Remy!!!

Success....but...read on please...

- Corrected some code when clicking on files ( a proc was called 2 times )
- Added option under parameters to see LOCAL or USED drives ( was set to USED drives by default )
- Included code to check existing of a file called "owncmd.txt' under avxcat path into which some user os2 commands could be added ( do not include single quotes because avxcat will add single quotes at start and end of each included cmd line. these commands are put/issued prior the ffmpeg exe.  e.g.   CLS ...

OK, so I had closed all my front-end apps before testing, in case it might freeze up...to my amazement and excillaration the Open File dialog box popped up and off I went picking files. Great...I shut-down the app, re-booted, re-tried the test to confirm the behaviour and ran straight into the same old freeze problem...why???

Well, I start up a few apps by default during system boot, one of them is PSI (IM client), through additional testing I found out that if I kill PSI before starting your app, it will open up the File dialog box fine. If on the other hand I leave PSI up and running the old behaviour persists and even the very 1st File attempt will lock things up.

Knowing this I tested further.

This time, having opened the File dialog once I wanted to rule out multiple File pick options, and here is where I ultimately got stuck. Even with PSI not running, attempting to open the File dialog for the second time will freeze the app. The LOCAL/USED drive settings did not seem to make a difference here.

One more test remains, and that is the "owncmd.txt" file approach...but as best as I can tell this only allows me to execute a "pre" command, is there a "post" command option as well? To avoid the freeze I effectively need to run in a single-core mode while using the app and only switch to all-cores when ffmpeg is actually running, then back to single-core only.

1342
Applications / Re: AVxCAT 1.4 alpha
« on: February 17, 2016, 03:36:58 pm »
Hi Remy,

...About long process, older ffmpeg was single thread only while the latest one I suggested to give it  try is multi-thread and under my system which has 4 enabled CPU core ( I also tried it using the 4 additional virtual core ), it works well and conversion is mutch faster with the latest ffmpeg suggested build...

Let me explain better, the long time it takes to re-encode my videos is due to several reasons:
1) MJPGs produced by my DSLR (Pentax K5) are big...we are talking on the order of 1.5-2gig for just a couple of minutes
2) since I can not use your app with multiple CPU cores enabled, I shut off all but one, then encoding happens in a "single thread" fashion since all other CPU cores are effectively disabled
3) I have previously used ffmpeg-os2-r26099, which is multi-thread enabled (it was a Dave Yeo drop)...so if I do the conversion outside of your app (command line) I am able to crunch through the data much faster as the work is done in parallel

I did download and install your recommended ffmpeg-os2-r2_1_5-Fourier version...haven't gotten a chance to try it out yet though.

Here is an idea I've been investigating to get around my app freeze situation. I could configure the application start cmd file to shut off all cores and run in a single-core mode. When the time comes to actually start the encoding operation if there was a way for your process to tie-in to a user defined "prep cmd step" I could then re-enable all the cores and really let the machine fly through the process. Since your app builds the final ffmpeg command on-the-fly I'm wondering if there is a way for me to do this?

So here is an example of what I'm talking about:

=== START ===

/* auto generated program by FFMPEGCA to execute ffmpeg in start using pipe */
Parse arg copy_metadata
ff_inputfile="I:\Movies\Family\Amelia - Baby Boots 2.MPG"
ff_inputfile='"'||ff_inputfile ||'"'
ff_outfile="G:\HOME\.ffmpegca\Amelia - Baby Boots 2.mp4"
Out_AVmap=" -map 0.1 -map 0.0"
more_map=""
ff_outfile='"'||ff_outfile||'"'
ffmpeg_prms='  -i '||ff_inputfile||' '||Out_AVmap||' -vcodec libx264 -b 1400k -r 29.97 -qmin 2 -qmax 35 -async 3'
/* --- x264 preset used : external --- */
ffmpeg_prms=ffmpeg_prms||' -vpre hq'
ffmpeg_prms=ffmpeg_prms||' -ar 44100 -acodec ac3 -ab 192k -vol 256 -ac 2'
ffmpeg_prms=ffmpeg_prms||' '||copy_metadata||' '||ff_outfile||' '||more_map

==> BEFORE ffmpeg.exe kicks off below I'd re-enable the CPU cores

'G:\util\misc\priority.exe 1 3 G:\APPS\MULTIMEDIA\ffmpeg\bin\ffmpeg.exe -y '||ffmpeg_prms||' 2>\pipe\ffmpegca_122'

==> AFTER ffmpeg.exe finishes above I'd disable the CPU cores

=== END ===

...any chance for this?

1343
Hardware / Re: Anyone successfully using Brother HL-5470dw?
« on: February 16, 2016, 02:08:51 pm »
You're on the right track already. Basically, dig into the job's Postscript output until you find the bit that's causing the problem, and then figure out what the correct code should look like. :p

I only wish I could actually get that far...the crash happens before I can successfully print anything...so literally as soon as I try to print using the HQ1200 setting I am getting a "divide by zero" error.

What actually helped is attempting to print from your handy AE, it produces a pretty descriptive error, while most other apps simply crash. I've attached the screenshot of what that error message actually is. This implies that whatever operation the driver attempts to perform to instantitate the HQ1200 mode produces an error which is then sent back to the program, I assume as an API return code?

I'm now looking at the PAK tools/utilities you made available on your site to understand the details of the AUXPRINT.PAK file. My assumption here is that as PIN imported the PPD with the specific control "codes" to put the printer in HQ1200 mode it either did not convert correctly because it did not know how to do it, or it failed to import altogether (although during the PPD import process no errors are generated).

1344
Hardware / Re: Anyone successfully using Brother HL-5470dw?
« on: February 15, 2016, 02:17:18 am »
...The 2 files brp5470......ppd are not pscript, are PCL5 or PCL6, this is a HP LaserJet code.
*%==== PostScript Patches ==========
*%*JobPatchFile 1: "statusdict/setusbbinary known{statusdict begin true setusbbinary end}if"

*%==== JCL Features ==========================
*%JCLBegin:           "<1B>%-12345X@PJL JOB<0A>"
*%JCLToPSInterpreter: "@PJL ENTER LANGUAGE = POSTSCRIPT <0A>"
*%JCLEnd:             "<1B>%-12345X@PJL EOJ <0A><1B>%-12345X"
...

I'm sorry, but the very same files you picked that section from start as follows:

=== START ===
*PPD-Adobe: "4.3"
*%================================================
*%   Copyright(C) 2012 Brother Industries, Ltd.
*%   "Brother HL-5470DW BR-Script3"
*%================================================

*%==== General Information Keywords ========================
*FormatVersion: "4.3"
*FileVersion: "1.0"
*LanguageEncoding: OS2-850
*LanguageVersion: English
*Manufacturer: "Brother"
*PCFileName: "BRP5470E.PPD"
*Product: "(Brother HL-5470DW series)"
*PSVersion: "(3010.106) 5"
*ShortNickName: "Brother HL-5470DW BR-Script3"
*ModelName: "Brother HL-5470DW BR-Script3"
*NickName: "Brother HL-5470DW BR-Script3"
...
=== END ===

So YES, these in fact are printer PPDs, they describe the printer controls using Postscript formatting/control statements. The output files I included are also poscript raw jobs, literally, stuff that normally would have gone out to the printer but was instead re-directed to a flat file.

Anyways, the JCL section you pointed out tells the printer to invoke the Postscript interpreter for this particular printer. In fact, the WIN7 generated files actually show this taking effect:

=== START ===
%-12345X@PJL JOB
@PJL SET STRINGCODESET=HPROMAN8
@PJL ENTER LANGUAGE=POSTSCRIPT
%!PS-Adobe-3.0
...
=== END ===

I've attached the "PostScript - Printer Description File Format Specification - PPD_Spec_v4_3" for reference, it goes into much more details then what I can make sense of at the moment...LOL

As I stated before, my printer works great with all resolutions but HQ1200, your PPD definitions do not address this, they are only for standard dpi resolutions.

1345
Applications / Re: AVxCAT 1.4 alpha
« on: February 14, 2016, 03:15:57 pm »
Hi Remy,

...About this alpha build, I left some code in it to allow opening a drdialog box only in case of internal errors to get more information...

Sorry about the delay...alright...tested this, but the old problem remains...the minute I push the "Files" button the system goes into a SOFT freeze, meaning CTL-ALT-DEL still recovers but that leads to a shut-down.

Soo...for what it's worth, this only happens when I have all 6 CPU cores up and running...if I shut down 5 of them then it appears to work. Of course the problem this leads to is that any sort of covnersionn process takes extremely long. In my case I have massive MJPG videos from my Pentax DSLR.

Anyways, if you want me to try anything just let me know. Thanks for continuing the work on this app...

1346
Hardware / Re: Anyone successfully using Brother HL-5470dw?
« on: February 13, 2016, 11:36:01 pm »
...I think the root of the problem is in your statement
Quote
the Linux "driver" files I have looked at all reference CUPS print system

Almost all laser printers have a basic engine resolution of 600 dpi.  Anything above that is provided as a function of the driver with the PPD only telling the driver what to show in is settings page.  This is true for the windows, OS x and CUPS drivers.

I don't think any native OS/2 driver, laser or otherwise, sees anything beyond 600 dpi. By asking for 1200 dpi the driver does not know how to interpret that and, being dumb, sends the wrong code to the printer.

Hmm...OK, point noted. However when I print here there is a very real difference between the output of a 600dpi vs 1200dpi print job. So it appears at least that the PPD supplied Postscript job control "string" does somehow cause the driver itself to format the remainder of the print job into a higher resolution. It is only the HQ1200 setting that causes the OS/2 print driver to crash.

Take a peek at the attached output files, these are a result of:

1) producing a Postscript job on win7 using Brother HL-5470DW Postrcript drivers (win_xxx)
2) producing a Postscript job on OS/2 using Brother HL-5470DW PPD and PSCRIPT driver (pscript_xxx)
3) producing a Postscript job on OS/2 using Brother HL-5470DW PPD and PSPRINT driver (psprint_xxx)
4) producing a Postscript job on OS/2 using Generic Postscript (Enhanced) PPD and PSPRINT driver (as per Alex's earlier suggestion) (genen_xxx)

You will find that in the win7 produced print jobs the ONLY difference is the PPD supplied control string for HQ1200 resolution, namely:

1200dpi
======
featurebegin{
%%BeginFeature: *CAPT SFine
<</HWResolution [1200 1200] >> setpagedevice
statusdict/true1200 known{statusdict begin true true1200 end}if

%%EndFeature
}featurecleanup

HQ1200
======
featurebegin{
%%BeginFeature: *CAPT Fine
<</HWResolution [1200 1200] >> setpagedevice
statusdict/true1200 known{statusdict begin false true1200 end}if

%%EndFeature
}featurecleanup

For some reason that HQ1200 control string is causing our OS/2 driver to die.

Alright...how the heck does one debug a printer driver? Alex??? lol...what's the "secret sauce" to actually do this with?

1347
Hardware / Re: Anyone successfully using Brother HL-5470dw?
« on: February 13, 2016, 03:40:21 pm »
Roberto,

...This is what you would expect . If you want to go with fiat 500 to 300kmh . You're defining your printer as having the ability to print an array of 1200x1200 = 1440000 points , and that is not so. Your printer can only print 2400x600 = 1440000 points. In both cases the final resolution is 1200

Oh boy, your interpretation of what I'm attempting to do is quite incorrect.

The printer (HL-5470DW) very much has the capability I am instructing it to use. The specs state the following:
1) 1200 dpi = 1200x1200
2) HQ1200 = 2400x600

...so it certainly can print HQ1200 at the resolution I specify in the PPD control string, but it is the additional control parameter that actually "translate" the [1200 1200] to [2400 600] resulting dpi setting.

I've attached the Brother PPD file with the Features section defintion and my final PPD with the Resolution section definition.

...In my reply nÂș13, I send you linux file for this printer, from the manufacture, for this printer model. And you are using a ppd description from other printer capable to print 1200x1200 us HL-5250dn....

Oh no, that is absolutely incorrect. The PPD files I'm using are the original Brother HL-5470DW PPD files. I am not using another model PPD (as you suggested the HL-5250dn). So from that perspective my results suggest that the Brother PPD defined printer features can not be successfully used in OS/2 given either the PSCRIPT or PSPRINT drivers.

...You want print in a diferent resolution that the manufacture propose for this printer, the error is normal. I untherstand...

No. Again, please take a look at the attached PPD files I am actually working with. These are original Brother HL-5470DW files with only difference being a shift of the Features section to the Resolution section.

I've also attached the Brother SPECs PDF for this particular printer.

Meanwhile, the Linux "driver" files I have looked at all reference CUPS print system. So the actual details of what's contained in the PPD itself actually tell nothing about sending direct JCL statement to the printer, case in point, here is the matching Resolution section:

=== START ===
*%==== 5.14 Finishing Features =================================
*%%%%% Resolution and Appearance Control %%%%%
*OpenUI *Resolution: PickOne
*OrderDependency: 11 AnySetup *Resolution
*DefaultResolution: 600dpi
*Resolution   300dpi: "                      "
*Resolution   600dpi: "                      "
*Resolution   2400x600dpi/HQ1200dpi: "                    "
*Resolution   1200dpi: "                    "
*CloseUI: *Resolution
=== END ===

I've also attached that file to this post.

1348
Hardware / Re: Anyone successfully using Brother HL-5470dw?
« on: February 13, 2016, 03:19:31 pm »
Alex,

This crash strongly suggests that PIN couldn't cope with the PPD. 

Try printing using the 'Generic Postscript (Enhanced)' model and see if you have better luck.

PIN did not produce any import errors...but indeed, it "feels" like something didn't quite go through correctly. The fact that the as-is PPD configuration of moving the Resolution configuration to the Features section does not work implies that the resulting driver import didn't quite configure things correctly.

Is there anything else I can do to better understand what is causing the failure with HQ1200 setting?

1349
Hardware / Re: Anyone successfully using Brother HL-5470dw?
« on: February 13, 2016, 12:11:22 am »
...Well, I do not understand what are you doing to get that error.Can you explain in detail your setting...

I am simply selecting HQ1200 in the Output=>Resolution section of the print driver. The minute I try to send a print job using HQ1200 the actual driver (PSPRINT & PSCRIPT) crashes.

...With the printer HL-5470dw send to ps printing a file , I have no such error, in HQ and with and without font courier new, mark and without mark in options, use downloaded fonts....

OK, but what printer are you actualy using? I did not think you have the same Brother HL-5470DW model that I have. So if you have something different our results may very well be quite different.

Here is another take on this: in the built AuxPrinter pak you kindly made available you have not included the actual PPD, therefore, I can not tell what settings you defined for the HQ1200 and 1200dpi settings. In my case the settings are different, otherwise if the driver simply passes the "<</HWResolution [1200 1200] >>" command to the printer it will not actually set it properly.

Here is what is contained in my final print job, which is a PS file:

%%BeginFeature: *Resolution 1200dpi
<</HWResolution [1200 1200] >> setpagedevice
statusdict/true1200 known{statusdict begin true true1200 end}if
%%EndFeature

So the whole <BeginFeature> -- <EndFeature> is a control string, and this is a different value for 1200dpi vs HQ1200.

1350
Hardware / Re: Anyone successfully using Brother HL-5470dw?
« on: February 12, 2016, 05:14:00 am »
...I printed a small TXT file using AE to file with word wrap on and off using your PSPrint driver with the default font set. I will attach the file and results which are radically different....

Interesting indeed...WRAPON includes the embedded font, WRAPOFF does not.

Further on:

WRAPON translates the font to CourierNew
WRAPOFF simply maps it to Courier

Similar to what I'm seeing with PSPRINT driver and high res:
1200dpi embeds CourierNew...while PSPRINT driver with high res but "No embed" maps to Courier only

Meanwhile, PSCRIPT maps to Courier regardless of what resolution I pick.

Pages: 1 ... 88 89 [90] 91 92 ... 96