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 ... 81 82 [83] 84 85 ... 89
1231
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.

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

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

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

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

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

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

1238
Hardware / Re: Anyone successfully using Brother HL-5470dw?
« on: February 11, 2016, 05:17:35 am »
Hi Alex,

Two suggestions... First, print to file and compare the output Postscript file for both the working and non-working scenarios.
Second, try varying the font used for printing text format (printer object properties, tab 'Text Format', font option).

Great suggestions...I had actually ventured down that road last night hoping to sneak a peek at what the driver is actualy building in the print job itself. Specifically I was hoping to see the HQ1200 vs 1200 dpi resolution settings.

As it turned out, even a basic TXT file when using the PSPRINT driver produced a fairly large output job when printed @ 1200dpi, here is a quick comparison:

2-09-16   8:50p      9665           0  output_pscript_1200.txt
2-09-16   8:11p    568252           0  output_ps_1200.txt
2-09-16   8:17p      9343           0  output_ps_1200_nofont.txt
2-09-16   8:16p      9218           0  output_ps_300.txt
2-09-16   8:14p      9224           0  output_ps_600.txt

the output_ps* files are from your PSPRINT driver, whereas the single output_pscript_1200.txt file is from the IBM PSCRIPT driver. what I found strange is that at the lower resolutions the resulting text files did NOT embed fonts, whereas at the 1200dpi they did.

Finally, HQ1200 failed to print altogether where I would encounter a crash in the PSPRINT driver itself, here is the entry from my POPUPLOG.OS2 file:

=== START ===
G:\OS2\PMSPOOL.EXE
c000009b
163e0bdc
EAX=00000000  EBX=0000002c  ECX=00000000  EDX=00000000
ESI=0283000c  EDI=02771400 
DS=0053  DSACC=f0f3  DSLIM=ffffffff 
ES=0053  ESACC=f0f3  ESLIM=ffffffff 
FS=150b  FSACC=00f3  FSLIM=00000030
GS=0000  GSACC=****  GSLIM=********
CS:EIP=005b:163e0bdc  CSACC=f0df  CSLIM=ffffffff
SS:ESP=0053:02525bac  SSACC=f0f3  SSLIM=ffffffff
EBP=02525c6c  FLG=00010246

PSPRINT.DRV 0001:00040bdc
=== END ===

The good news (I suppose/hope...???) is that the crash was consistent between the PSCRIPT and PSPRINT drivers, here is the matching log for the PSCRIPT driver:

=== START ===
G:\OS2\PMSPOOL.EXE
c000009b
1657d46c
EAX=00000000  EBX=0000002c  ECX=00000000  EDX=00000000
ESI=0285000c  EDI=02791400 
DS=0053  DSACC=f0f3  DSLIM=ffffffff 
ES=0053  ESACC=f0f3  ESLIM=ffffffff 
FS=150b  FSACC=00f3  FSLIM=00000030
GS=0000  GSACC=****  GSLIM=********
CS:EIP=005b:1657d46c  CSACC=f0df  CSLIM=ffffffff
SS:ESP=0053:02565aac  SSACC=f0f3  SSLIM=ffffffff
EBP=02565b6c  FLG=00010246

PSCRIPT.DRV 0001:0002d46c
=== END ===

Both the crashes produced a SYS3184 error.

Any chance you can troubleshoot this? While printing from your AE editor I was actually getting a "divide by zero" error...but no log in POPUPLOG.OS2.

1239
Hardware / Re: Anyone successfully using Brother HL-5470dw?
« on: February 10, 2016, 02:32:35 am »
Hi Roberto!

The as-is Brother PPD, where the print quality is left in the "Features" section does not appear to actually impact print quality in our OS/2 driver. So, in other words, when the default resolution is 600dpi, no matter what I select in the Features section of the driver I still ONLY get 600dpi output. Yeah...you bet, that's lousy!!!
Now I think I begin to understand .

Sorry, I wrote in my earlier post that I was using psprint 30.905 driver...easily missed though...no worries.

Quote
I increase the resolution to my PSPRINT.Brother MFC-L2720DW BR-Script3, to HQ1200 and print a white paper. But I open the printer --select printer driver ---options-- and print font capacity   And the printer print a page with this info:
-----ini print text---------------
Available Font Memory (bytes) = 16103784
Suggested Maximun Downloaded Fonts : 32
------end print text------------
In the driver show me 110 fonts, I reduce it to 32. Save and close.
After this is printing ok, with epm.exe, , and with lucide the text does not start in the right place , moved out .
If modify in Jobs properties High Quality Print ON or OFF, in epm.exe is the same, but in lucide, move to other bad position.

Yeah...I'm starting to see some weird things here...in particular...if I print using PSPRINT driver and embed fonts in my print job, the output is garbled, now this is ONLY with a simple TXT file...however, the full text prints on a single line.

If on the other hand I disable font embedding (by setting the driver=>Output=>Use Downloaded Fonts to OFF) then I have a good printout, text prints OK as it should in the place it should. Of course this approach defeats the purpose of running PSPRINT as opposed to PSCRIPT, since the benefit of PSPRINT is being able to embed fonts.

With my printer the driver suggests I use up to 78 fonts for the download...which is how I left them.

I will do a PPD import of the modified resolution Brother file into PSCRIPT driver next and see if I'm seeing any differences there.

1240
Hardware / Re: Anyone successfully using Brother HL-5470dw?
« on: February 08, 2016, 05:32:57 am »
...However....somewhat strangely enough, I am getting the following error out of PIN.EXE:

=== START ===
[G:\TEST\PSCRIPT]pin ppd \test\pscript\5470 \test\pscript\5470
PostScript resource packaging utility version 1.00
Copyright (c) IBM Corp. 2000,2001. All rights reserved.

Producing Printer Device PAK
reading driver extended attributes
  fail
SYS0005: Access is denied.

fail
=== END ===...

Well, this is embarrasing...notice my "pin" command above, for some reason my problem was the fact that the last parameter is a fully qualified reference to the PSCRIPT.DRV file, that means, it needed to be stated as "\test\pscript\5470\pscript.drv", I simply left out the actual printer driver filename...duh....

OK, having overcome that obstacle I must report on some findings.

The as-is Brother PPD, where the print quality is left in the "Features" section does not appear to actually impact print quality in our OS/2 driver. So, in other words, when the default resolution is 600dpi, no matter what I select in the Features section of the driver I still ONLY get 600dpi output. Yeah...you bet, that's lousy!!!

So as it turns out the only way to make this work is by moving the whole Features print quality section over to the Output tab under Resolution. However, as I did that and as I preserved the Brother device controls I found out that the HQ1200 mode consistently crashes the driver. So whatever app I'm actually trying to print for, if I select HQ1200 Resolution the app will crash.

Since both 1200 and HQ1200 appear to be coded using the same HWResolution parameters but different  statusdict settings it appears that I can only use the 1200dpi (highest-resolution) settings reliably.

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

*CAPT   Fine/HQ 1200: "<</HWResolution [1200 1200] >> setpagedevice
statusdict/true1200 known{statusdict begin false true1200 end}if"

Anyways...I will experiment with a few more configurations, but for now at least I have no way to understand why HQ1200 crashes the driver.

1241
Hardware / Re: Anyone successfully using Brother HL-5470dw?
« on: February 07, 2016, 06:10:00 am »
So I took Roberto's Linux/cups based PPD and re-fitted the Brother PPD with the *Resolution section, I preserved the 'setpagedevice' settings from the Brother drivers:

=== START ===
*%%%%% Resolution and Appearance Control %%%%%
*OpenUI *Resolution: PickOne
*OrderDependency: 11 AnySetup *Resolution
*DefaultResolution: 600dpi
*Resolution   300dpi: "<</HWResolution [300 300] >> setpagedevice"
*Resolution   600dpi: "<</HWResolution [600 600] >> setpagedevice"
*Resolution   HQ1200dpi: "<</HWResolution [1200 1200] >> setpagedevice
statusdict/true1200 known{statusdict begin false true1200 end}if
"
*Resolution   1200dpi: "<</HWResolution [1200 1200] >> setpagedevice
statusdict/true1200 known{statusdict begin true true1200 end}if
"
*CloseUI: *Resolution
=== END ===

However....somewhat strangely enough, I am getting the following error out of PIN.EXE:

=== START ===
[G:\TEST\PSCRIPT]pin ppd \test\pscript\5470 \test\pscript\5470
PostScript resource packaging utility version 1.00
Copyright (c) IBM Corp. 2000,2001. All rights reserved.

Producing Printer Device PAK
reading driver extended attributes
  fail
SYS0005: Access is denied.

fail
=== END ===

Almost looks like the PSCRIPT.DRV file is throwing the 'Access is denied' error...is this some kind of OS/2 built in protection mechanism on the PSSCRIPT.DRV file??? I copied a fresh ZIP of the PSCRIPT 30.800 driver to my test directory so as to avoid any issues attempting to update the existing driver in \os2\dll\pscript.

1242
Hardware / Re: Anyone successfully using Brother HL-5470dw?
« on: February 06, 2016, 01:55:10 am »
Guys!!!

Great news...I was a little delayed in getting this through, but I finally managed to pick up the printer locally (Staples Canada matched the on-line sales price, thumbs-up to them).

Anyways, glad to report the printer is chugging along quite nicely. So after I extracted the PPD file from the Win version of the driver package I proceeded with the import using Alex's drivers (PSPRINT 30.905). No errors were encountered, I then setup a new SLPR port and off I went.

All current apps readily print w/o any problems. The printer is a speedy little thing, at least as compared to my HL1650 machine. The Postscript options listed in Windows are all recognized by the OS/2 driver.

OK, so all good news....BUUUUTTTT....there is always a "but" right? LOL

Well, not all that bad of a "but", rather a simple definition of a printer control. So the 5470dw printer driver moves the "Resolution" settings to the "Features" tab of the driver settings. No big deal, I can still access them and as I make the changes I see that the printed output matches. However, my HL1650 shows the resolution controls in the "Output" tab. So at least from my liking perspective I would like to maintain this. Now from the "will it work elsewhere" perspective (and I have no idea if there is some sort of dependency here or not) I am worried that the only option in the 5470dw is 600dpi and therefore if an application is actually looking for the printer resolution capability it may in fact force 600dpi print output.

Looking at the PPD files here is how the HL1650 and 5470dw drivers differ:

1) HL1650

*%%%%% Resolution and Appearance Control %%%%%
*OpenUI *Resolution: PickOne
*OrderDependency: 11 AnySetup *Resolution
*DefaultResolution: 600dpi
*Resolution   300dpi: "<</HWResolution [300 300] >> setpagedevice"
*Resolution   600dpi: "<</HWResolution [600 600] >> setpagedevice"
*Resolution   1200dpi: "<</HWResolution [1200 1200] >> setpagedevice"
*CloseUI: *Resolution

2) 5470dw

*%%%%% Resolution and Appearance Control %%%%%
*DefaultResolution: 600dpi
*OpenUI *CAPT/Print Quality:PickOne
*OrderDependency: 10 AnySetup *CAPT
*DefaultCAPT: Middle
*CAPT   SFine/1200 dpi: "<</HWResolution [1200 1200] >> setpagedevice
statusdict/true1200 known{statusdict begin true true1200 end}if
"
*CAPT   Fine/HQ 1200: "<</HWResolution [1200 1200] >> setpagedevice
statusdict/true1200 known{statusdict begin false true1200 end}if
"
*CAPT   Middle/600 dpi: "<</HWResolution [600 600] >> setpagedevice"
*CAPT Low/300 dpi: "<</HWResolution [300 300] >> setpagedevice"
*CloseUI: *CAPT

I have not looked up any Postscript references yet to see if I can actually move my 5470dw "CAPT" settings over to the "Resolution" definition, but both printers claim to support Postscript 1.3, therefore I have no reason to suspect that the 5470dw PPD could not be successfully re-written to move the options to the "Resolution" definition.

If anyone has some input on this I'd love to see them. I will most likely give this a try over the weekend.

1243
Games / Quake/2 now broken???
« on: January 11, 2016, 03:40:29 pm »
So a while back...yeah, maybe a couple of years ago, or longer...my Quake/2 install was working great...then somehow, somewhere something broke...end result is that none of my Quake2 setups (so Quake local, LAN, QuakeWorld) no longer work.

Was hoping to bring back some of that "back in the early days of gaming" feeling for my son and play a bit of LAN Quake here...so I'm curious if anyone has this working on their machine?

I have ATI X850 XT video card here with SNAP drivers.

Here is what I'm finding in my POPUPLOG.OS2:

01-10-2016  20:13:52  SYS3184  PID 00b9  TID 0001  Slot 00b0
G:\APPS\GAMES\QUAKE\QUAKEFS.EXE
c000009b
0002b619
EAX=ffff63c0  EBX=000000c8  ECX=ffff63c0  EDX=00000000
ESI=0110fd24  EDI=035a0000 
DS=0053  DSACC=f0f3  DSLIM=ffffffff 
ES=0053  ESACC=f0f3  ESLIM=ffffffff 
FS=150b  FSACC=00f3  FSLIM=00000030
GS=0000  GSACC=****  GSLIM=********
CS:EIP=005b:0002b619  CSACC=f0df  CSLIM=ffffffff
SS:ESP=0053:0110ec40  SSACC=f0f3  SSLIM=ffffffff
EBP=00000000  FLG=00010246

QUAKEFS.EXE 0002:0000b619

=================

01-10-2016  20:26:34  SYS3175  PID 00d7  TID 0003  Slot 00aa
G:\APPS\GAMES\QUAKE2\QUAKE2.EXE
c0000005
148943ca
P1=00000001  P2=00000000  P3=XXXXXXXX  P4=XXXXXXXX 
EAX=148a122e  EBX=00b8f838  ECX=00b8fcb4  EDX=00b8f838
ESI=00b8fcb4  EDI=00000000 
DS=0053  DSACC=f0f3  DSLIM=ffffffff 
ES=0053  ESACC=f0f3  ESLIM=ffffffff 
FS=150b  FSACC=00f3  FSLIM=00000030
GS=0000  GSACC=****  GSLIM=********
CS:EIP=005b:148943ca  CSACC=f0df  CSLIM=ffffffff
SS:ESP=0053:00b8f7e0  SSACC=f0f3  SSLIM=ffffffff
EBP=00b8f81c  FLG=00010202

EMXLIBCM.DLL 0001:000143ca

=================

My EMXLIBCM.DLL info:

Directory of G:\code\tools\emx\dll

 3-20-01  11:45a    193603           0  emxlibcm.dll
        1 file(s)     193603 bytes used

Any ideas?

1244
Programming / Re: New OS/4 kernel :: SVN4227
« on: January 07, 2016, 02:23:34 am »
Lars,

...
4) the next ACPI.PSD is in the queue. Do you think it is sensible for the OS4 team to offer patches to ACPI.PSD to make it work with their kernel ad infinitum ?
...

So here is a real-world example why alternative approaches may be worth pursuing.

I have directly benefitted by subscribing to the Arca Noae's DRIVER package, thanks to that I now have a pretty stable SMP environment, although (and this is the big enough of a justification in my mind) of the total of 6 CPU cores I can only boot the machine up with 5, otherwise I end up with the dreadful "PMSHELL blue screen". Having logged a ticket with support organization it was prompty written of as a "known PMSHELL issue"...hmm...so really?...no further debug, no additional follow-up, just a plain "...can't be fixed..."? And this is for software that I actually paid money for...

Now, from my point of view, I am literally locked-out of using nearly 20% of my computing power simply b/c the current de-facto SMP solution won't let me do it. I'm not saying that this is the SOLE reason...heck, I am no os2ldr/krnl/PMSHELL guru, but as long as I have apparently reached the end of the road in one approach I will pursue others if they arise so that maybe in the course of testing/researching I will learn something and maybe someone else in our tiny community will benefit from.

Beyond just that very selfish reason above, here is a more precise one: if the /ST=0 parameter in the ACPI.PSD drive does in fact get ignored, and the authors have set some arbitrary value for the size of the stack, then I would consider this to be a defect. So if the OS4 team patches the binary to actually correct this behaviour then I'm actually questioning why the "core" OS2 maintainer team refuses to fix the code itself?

1245
Quote
This 21" CRT was fully capable of displaying 1800 x 1440/76 Hz NI resolution providing a pretty decent 0.26 mm aperture grille pitch.
...1800x1440 was way to much for this tube and you never could see that much pixels. Simply cause there were not that much stripes in the grill. You can't cheat physics...

Completely agree with all you stated...however, you are leaving out the intended use of the hardware. So while I may have been focused on text quality, the person doing CAD work on this display would certainly be able to take advantage of the higher addressable resolution. In other words, the monitor electornics had the ability to physically address (turn on/off) some 1800 locations on the X-axis...this very much translates to having a functionality where the display can choose from 1800 different points, even though not each of these 1800 points was a unique physical screen location, sort of an interpolation solution I suppose.

For me anyways it all boils down to the functionality one indends to utilize. Image/graphics work on displays is very different then text work. Today's hardware, where the RGB gamut is wholly covered (near 100%) will still fetch a good price at the cash register...and if one is willing to spend that money I can only assume it's because he/she is not focused on text only.

If anyone reading the post is looking at a pretty good review of panel capabilities head on over to http://www.tftcentral.co.uk, these guys do a great mix of usability and tech analysis.

Pages: 1 ... 81 82 [83] 84 85 ... 89