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 2 [3] 4 5 ... 74
31
Programming / Re: GSView - make complains of "No such file or directory"
« on: January 29, 2022, 04:18:41 pm »
Hmm...so much for that idea...LOL, b/c I now have the same issue with common.mak, and as best as I can tell there is only a single target in there, that being:

Code: [Select]
...
#################################################################
# Cleanup

commonclean:
-$(RM) $(CLEAN1)
-$(RM) $(CLEAN2)
-$(RM) $(CLEAN3)
...

Alright...time to get edumacated further on the inner depths of 'make'...LOL!

32
Programming / Re: GSView - make complains of "No such file or directory"
« on: January 29, 2022, 03:52:38 pm »
Try doing "SET MAKESHELL=sh.exe" and retry

Thanks Dave, but that did not work.

No sense spending huge time on this...I get the idea behind this, but this software isn't going to go through numerous future changes. Heck, all I need is to change the printer device name here. I'm going to build that gsvver.h file manually and take that include out of the makefile.

33
Programming / Re: GSView - make complains of "No such file or directory"
« on: January 29, 2022, 04:53:21 am »
Ahh...fixed a couple more issues in the main makefile (spaces instead of TABs), now it looks like i'm getting a bit further, but still hitting this:

Quote
[G:\code\source\os2\gsview-5.0]g:\code\tools\vslick\os2\gcc_build.cmd
g:\code\tools\vslick\os2\gcc_build.cmd                               
makefile:85: ".\src\common.mak": No such file or directory           
makefile:86: ".\src\gvcver.mak": No such file or directory           
make.exe: *** No rule to make target `".\src\gvcver.mak"'.  Stop.     
Exited                                                               

gvcver.mak is short:

Code: [Select]
# GSview version
GSVIEW_VERSION=50
GSVIEW_DOT_VERSION=5.0
GSVIEW_DATE=2022-01-28

$(OD)gsvver.h: $(ECHOGSV) $(SRC)gvcver.mak
        $(ECHOGSV) -w $(OD)gsvver.h "/* gsvver.h - automatically generated by gvcver.mak */"
        $(ECHOGSV) -a $(OD)gsvver.h -x 23 "define GSVIEW_VERSION " $(GSVIEW_VERSION)
        $(ECHOGSV) -a $(OD)gsvver.h -x 23 "define GSVIEW_DOT_VERSION " -x 22 $(GSVIEW_DOT_VERSION) -x 22
        $(ECHOGSV) -a $(OD)gsvver.h -x 23 "define GSVIEW_DATE " -x 22 $(GSVIEW_DATE) -x 22
        $(ECHOGSV) -a $(OD)gsvver.h -x 23 "define GSVIEW_DOCPATH " -x 22 $(GSVIEW_DOCPATH) "/gsview-" $(GSVIEW_DOT_VERSION) "/" -x 22
        $(ECHOGSV) -a $(OD)gsvver.h -x 23 "define GSVIEW_ETCPATH " -x 22 $(GSVIEW_ETCPATH) "/gsview/" -x 22

So you can tell that it simply auto-creates gsvver.h here, based on the variables that are defined in the gvcver.mak.

Looks to me like make.exe doesn't know what to do with that makefile though...

34
Programming / GSView - make complains of "No such file or directory"
« on: January 29, 2022, 04:29:49 am »
I decided to take a stab at building an updated version of GSView (because the pswrite device is no longer present in our ghostscript 9.18 release and the latest GSView verison seems to have it hard-coded instead of picking the device name up from the gvpm.ini file and using that).

Anyways...couple of small tweaks to the makefile, but I'm getting stumped by a reference to two other makefiles: one for common objects and the other is a GSView version mak (auto-updates the GSView header that contains the version info).

I've attached the makefile here, and I'm seeing the following error:

Code: [Select]
...
[G:\code\source\os2\gsview-5.0]\usr\bin\make
makefile:85: ".\src\common.mak": No such file or directory
makefile:86: ".\src\gvcver.mak": No such file or directory
makefile:174: *** missing separator (did you mean TAB instead of 8 spaces?).  St
op.
...

which is a result of the following lines in the main makefile:

Code: [Select]
...
#################################################################
# Common

include "$(SRC)common.mak"
include "$(SRC)gvcver.mak"
...

And yet, from a CLI where I am executing make from I can certainly do a "dir" and both of those files are certainly there:

Quote
[G:\code\source\os2\gsview-5.0]dir .\src\*mak

The volume label in drive G is OS2.
The Volume Serial Number is 45B6:75C3.
Directory of G:\code\source\os2\gsview-5.0\src

11-17-07  4:14p         2,409      0 a---  bzlibmsc.mak
 5-28-11 12:21p         5,677      0 a---  common.mak
 1-17-12  9:26p        23,686      0 a---  gvc.mak
 1-28-22 10:21p         1,802      0 a---  gvcver.mak

So what am I tripping over here?

Is this a OS/2 vs Linux path separator issue?

For what it's worth I tried the "/" vs "\" with no difference.

Thanks!

35
Paul,

In the case of GSView, it is the ghostscript version that's important. Are you able to confirm the ghostscript version, and if it uses Poppler?

I am using GScript 9.04 here...so I suspect this is not using poppler in any way.

36
Utilities / Re: MeShell commandline frontend timetable
« on: January 28, 2022, 01:52:53 am »
Hi Martin,

>I will say this though: the "page size" seems to be hardcoded to be 25 lines??? In my case the MeShell window is about 60 lines high...so even trying "page full" settings always shows just half the page.

On my computer, it seems to work. The last line is repeated as the first line on the new page.

Well, take a look at the attached screen capture. The MeShell window is actually about 60 lines tall, while the default "page" setting appears to be about 25 lines...so my point here is: your page setting should respect the size of the MeShell VIO window which I created, instead of some arbitrary (or pre-defined static value).

I suspect the actual CMD.EXE window which you spawn is 25 lines and therefore the output is driven by that definition though?

...
>Lastly, from a new features perspective, can you implement 'cls' (clear screen)? Sometimes it's awefully nice to just wipe the VIO window clean and start at the very top, especially for commands that sometimes provide special formatting. MeShell today does not appear to support this, nor am I aware of another way one could do this?

I wonder why CLS does not has an effect to the VIO window. It has no effect to the editor window, of course. You can delete the editor window by clicking to the red cross topright of the MeShell window. I have to think about why it does not delete the VIO window. Perhaps I have to implement this by myself. It would be possible, I think.

Yes, you are right about the red 'X' doing the same thing...but when you are at the CL in a VIO window who wants to pause typing in order to navigate the mouse pointer to that red 'X'???

37
Can you please confirm the versions of Lucide issue, GSView as and QPDFView that are in use? Poppler may be a common theme here.

1) Lucide - 1.5.0 GA (2019-03-20)
- lupplr PDF plugin, based on poppler library 0.59.0

2) GSView - 5.0 (2012-01-17)

3) QPDFView - 0.4.17.beta2
- PDF support using Poppler 0.52.0

Here is the Poppler installed RPM package info:

poppler.pentium4                        0.90.1-1.oc00
poppler-cpp.pentium4                  0.90.1-1.oc00
poppler-data.noarch                     0.4.9-1.oc00
poppler-legacy-65.pentium4          0.49.0-2.oc00.L
poppler-legacy-66.pentium4          0.52.0-1.oc00.L
poppler-legacy-70.pentium4          0.59.0-3.oc00.L
poppler-legacy-72.pentium4          0.61.1-1.oc00.L
poppler-legacy-94.pentium4          0.84.0-1.oc00.L
poppler-qt.pentium4                     0.90.1-1.oc00
poppler-utils.pentium4                  0.90.1-1.oc00

38
Hi Paul,

Please use https://smedley.id.au/tmp/ndpsmb-3.7.3-samba411-20220108.zip if possible

Alright, I grabbed that plugin, deployed and tested with three test-cases:

1) JPEG
regular JEPG image, see log.ndpsmb.JPEG

2) PDF - Large file
PDF file, this one is about 5.6M is size, see log.ndpsmb.PDF_large

3) PDF - Small file
PDF file, this one is about 175K in size, see log.ndpsmb.PDF_small

Each test-case was re-started from scratch, meaning: NDCTL re-start each time, which produced a clean log.ndpsmb file, so the log files you see above contain JUST the information pertinent to that single test-case.

Otherwise, I have my share configured to do:

1) Cache Timeout of 10 sec (default)
2) Cache Lsting of 80 (as opposed to the default of 32 I think - this appears to have made my NAS connectivity mroe stable, at least as far as WPS file operations go)

I have tried multiple configurations here of the above values in hopes of figuring out if one of these settings causes a too-frequent cache refresh, which in turn kills the performance, but I haven't found anything here. Either way, the other file types do not appear to be impacted, just the PDFs.

See attached ZIP file, let me know if you want me to send it anywhere else?

Thank You!

39
Hi Mike!

Hi Darius,

kindly try to disable the "Supports EA" flag when you mount the share of your NAS. That helped me in a similar case.

Greetings from Potsdam, Germany.
Mike

The NAS box does not support EAs, so I have that disabled in my NetDrive share configuration.

I remember trying to troubleshoot this a while back...I think I captured the LOGs that Paul is talking about and it looked like the PDFs were getting transfered in tiny chunks, we are talking here like 2-3K, while other objects (such as JPEGs for example) would max out at about 32K.

OK, yeah, I saved that old debug log and here is what I found:

1) JPEGs
Code: [Select]
...
NdpQueryPathInfo <public\DOCUMENTS\Family\Finance\TAX\2016\US Info\2016 - MI - Tax Refund Statement.jpg> () 0
2020/06/11 16:18:53.50: 9 2: smbopen in [0x6e3a80] -1
2020/06/11 16:18:53.50: 4 2: cli_open(\public\DOCUMENTS\Family\Finance\TAX\2016\US Info\2016 - MI - Tax Refund Statement.jpg) attr 00000000 mode 100 denymode 04
2020/06/11 16:18:53.51: 9 2: smbopen <public\DOCUMENTS\Family\Finance\TAX\2016\US Info\2016 - MI - Tax Refund Statement.jpg> (\public\DOCUMENTS\Family\Finance\TAX\2016\US Info\2016 - MI - Tax Refund Statement.jpg) 00000100 08000040 00000000 0. file = 17556
2020/06/11 16:18:53.51: 9 2: NdpFileQueryInfo in [0x6e3a80]
2020/06/11 16:18:53.51: 9 2: fname \public\DOCUMENTS\Family\Finance\TAX\2016\US Info\2016 - MI - Tax Refund Statement.jpg
2020/06/11 16:18:53.51: 9 2: btime 1494688532 Sat May 13 11:15:32 2017
2020/06/11 16:18:53.51: 9 2: atime 1591275626 Thu Jun  4 09:00:26 2020
2020/06/11 16:18:53.51: 9 2: mtime 1494688532 Sat May 13 11:15:32 2017
2020/06/11 16:18:53.51: 9 2: ctime 1494688532 Sat May 13 11:15:32 2017
2020/06/11 16:18:53.51: 9 2: ftimeLastAccess 11:15:32
2020/06/11 16:18:53.51: 9 2: NdpFileQueryInfo <\public\DOCUMENTS\Family\Finance\TAX\2016\US Info\2016 - MI - Tax Refund Statement.jpg> 0
2020/06/11 16:18:53.51: 9 2: NdpFileSetFilePtrL in [0x6e3a80]
2020/06/11 16:18:53.51: 4 2: lseek 1 0 0
2020/06/11 16:18:53.51: 9 2: NdpFileSetFilePtrL <\public\DOCUMENTS\Family\Finance\TAX\2016\US Info\2016 - MI - Tax Refund Statement.jpg> 0 1 0 0
2020/06/11 16:18:53.51: 9 2: NdpFileQueryInfo in [0x6e3a80]
2020/06/11 16:18:53.51: 9 2: fname \public\DOCUMENTS\Family\Finance\TAX\2016\US Info\2016 - MI - Tax Refund Statement.jpg
2020/06/11 16:18:53.51: 9 2: btime 1494688532 Sat May 13 11:15:32 2017
2020/06/11 16:18:53.51: 9 2: atime 1591275626 Thu Jun  4 09:00:26 2020
2020/06/11 16:18:53.51: 9 2: mtime 1494688532 Sat May 13 11:15:32 2017
2020/06/11 16:18:53.51: 9 2: ctime 1494688532 Sat May 13 11:15:32 2017
2020/06/11 16:18:53.51: 9 2: ftimeLastAccess 11:15:32
2020/06/11 16:18:53.51: 9 2: NdpFileQueryInfo <\public\DOCUMENTS\Family\Finance\TAX\2016\US Info\2016 - MI - Tax Refund Statement.jpg> 0
2020/06/11 16:18:53.51: 9 2: NdpFileRead in [0x6e3a80], ulRead = 32768
2020/06/11 16:18:53.52: 4 2:  smbwrp_read successful, nread = 32768, ret = 0
...

2) PDFs
Code: [Select]
...
NdpQueryPathInfo <PUBLIC\DOCUMENTS\Family\FINANCE\TAX\2016\US Info\2016 - MTOR - Paystub - FINAL.pdf> (\PUBLIC\DOCUMENTS\Family\FINANCE\TAX\2016\US Info\2016 - MTOR - Paystub - FINAL.pdf) 0
2020/06/11 20:53:17.76: 9 2: smbopen in [0x6fb340] -1
2020/06/11 20:53:17.76: 4 2: cli_open(\PUBLIC\DOCUMENTS\Family\FINANCE\TAX\2016\US Info\2016 - MTOR - Paystub - FINAL.pdf) attr 00000000 mode 100 denymode 04
2020/06/11 20:53:17.76: 9 2: smbopen <PUBLIC\DOCUMENTS\Family\FINANCE\TAX\2016\US Info\2016 - MTOR - Paystub - FINAL.pdf> (\PUBLIC\DOCUMENTS\Family\FINANCE\TAX\2016\US Info\2016 - MTOR - Paystub - FINAL.pdf) 00000100 08000040 00000000 0. file = 17563
2020/06/11 20:53:17.76: 9 2: NdpRsrcQueryInfo in
2020/06/11 20:53:17.76: 9 2: NdpRsrcQueryInfo 0
2020/06/11 20:53:17.76: 9 2: NdpFileSetFilePtrL in [0x6fb340]
2020/06/11 20:53:17.76: 4 2: lseek 2 0 0
2020/06/11 20:53:17.76: 9 2: NdpFileSetFilePtrL <\PUBLIC\DOCUMENTS\Family\FINANCE\TAX\2016\US Info\2016 - MTOR - Paystub - FINAL.pdf> 0 2 4322 0
2020/06/11 20:53:17.76: 9 2: NdpFileSetFilePtrL in [0x6fb340]
2020/06/11 20:53:17.76: 4 2: lseek 2 0 4322
...

I'll get a NEW log built because that was way back in 2020 (June) and I'm pretty sure we've had Samba client updates since.

40
Utilities / Re: MeShell commandline frontend timetable
« on: January 25, 2022, 08:48:23 pm »
Hi Martin!

Quote
I can only move the CHILD window, but I cannot move the PARENT window because as soon as I try that they always follow each other.

There are two possibilities: It would be possible to make a checkbox on the "VIO" page of the settings notebook. "Move main window without moving VIO window" or pressing Ctrl while moving the checkbox omits moving the VIO window. What would you prefer?

I think I'd rather have a setting that allows me to either set this behaviour to ON or OFF. So that would be the 1st suggestion you provided.

...
Quote
The whole output scrolls, and yes, I can then afterwards go back up the page, but sometimes that's not the point, instead I'd like to stop at exactly a pagefull, review that info before I proceed further.

Do you have seen the settings notebook page "Scroll"? Is it really useful to stop the output when you have unlimited acces to the text above after finishing the command?

Yes, so I had actually stepped through each one of these options and picked the 'static no jump:...' (the last one) because that most closely resembled the behaviour I was going after. Even then though it does not match what I see in a normal CLI session. So I wasn't sure if that was by design, or a true side-effect?

For example, when reading a man page, one doesn't really want the full man content to just scroll by, instead you do in fact read it 'page at a time' until you get to the marker in the man help file that matches what you are looking for.

I will say this though: the "page size" seems to be hardcoded to be 25 lines??? In my case the MeShell window is about 60 lines high...so even trying "page full" settings always shows just half the page.

Lastly, from a new features perspective, can you implement 'cls' (clear screen)? Sometimes it's awefully nice to just wipe the VIO window clean and start at the very top, especially for commands that sometimes provide special formatting. MeShell today does not appear to support this, nor am I aware of another way one could do this?

41
Guys!

I've had a pesky problem on my OS/2 box for a while now, that being on Samba connections Lucide takes far too long to open a PDF that's sitting out there on my NAS box. This is not just a Lucide issue, GSView as well as QPDFView show the same behaviour.

We are talking here PDF files that are about 70-150k in size that take 5-10 secs to open up.

To be clear, I am using NetDrive Samba plugin to make this work, and that could certainly be adding, I just can't tell.

What I can see is that as I open a PDF file my TCP/IP monitor shows multiple traffic spikes, they continue (back and forth) until the file is opened up. Now nearly each one of these are spikes are actually larger than the actual PDF file itself, so that's literally flooring me as I can't for the life of me understand what is causing the traffic to happen.

Alright...so how can I troubleshoot this in order to figure out what all that "overhead" is that appears to be moving back and forth?

I've got Wireshark installed, so I could capture the packets as the transactions start...but is there something a little more human-digestable? I'm thinking Samba logging perhaps?

Thanks!

42
Utilities / Re: MeShell commandline frontend timetable
« on: January 24, 2022, 10:31:15 pm »
Hi Martin,

I paused following this thread for a couple of month. What is Xit?

Xit is a VERY old utility that basically enhances the WPS and beyond it, such as CLI, etc. I have had it installed on my machine for many years now, but occasionally it'll run into a problem with some apps. It does have the option to be disabled for such apps, which is what I had to do with your MeShell utility.

Does anyone has found bugs?

Three things:

1) Bug maybe not, but I find that programs initiated from within MeShell once closed cause the background VIO window ("top (VIO 1)") to be placed into FOREGROUND...so now they become visible, which is not what I think should happen. I would prefer that this window remains in the background and continues to server it's purpose.

2) When a new window is created by MeShell, that window becomes "glued" to the location of MeShell. This means that I cannot move the MeShell and the started VIO session independently of each other, or to clarify: I can only move the CHILD window, but I cannot move the PARENT window because as soon as I try that they always follow each other. This may be fine on a single screen, but on my dual monitor display as soon as I scroll off the screen (with my mouse) the CHILD window stops moving while the PARENT MeShell window continues to go off-screen, this messes up the arrangement between the two and creates some funny (completely off-set, overlapped, or disjointed) windows.

3) Attempts to pipe output to something like "less" simply do not work. The whole output scrolls, and yes, I can then afterwards go back up the page, but sometimes that's not the point, instead I'd like to stop at exactly a pagefull, review that info before I proceed further.

Thanks again!

43
Networking / Re: Samba Shares - default CAPS in filenames?
« on: January 24, 2022, 02:33:00 am »
Hmm...interesting.

So now that I'm aware of this symptom, and can readily replicate it, I spent a little more time learning about the Samba aspects.

As best as I can tell the pertaining section of the smb.conf file is:

Code: [Select]
...
case sensitive  = auto
default case    = lower
preserve case   = yes
short preserve case = yes
...

I specifically have these under the [global] group, which means that the same settings apply to all the shares.

I have been able to determine that my Win 7/10 shares behave as expected: the case is preserved when a NEW file is created. It is only my NAS box that does not.

However, further on I discovered that in a CLI window the actual file object does in fact have the correct lower/upper-case, only the WPS folder listing shows the filename in ALL CAPS.

Further still...once a re-boot happens the WPS itself switches to show the correct mix of upper/lower-case, which is a perfect sync with what I see in the CLI itself.

Alright...so I'm running XWP here (1.0.14 - Oct_2021), not sure if that is causing this behaviour, however it is VERY weird that after a re-boot what XWP shows is correct.

Re: smb.conf settings, to rule out any of the above combinations as causing this behaviour I tried multiple combinations, including completely commenting these out. Turns out this had no impact.

What is interesting is that my Win 7/10 shares are flagged as supporting EAs, while the NAS box does NOT, so maybe that has some bearing on the outcome as well?

44
Networking / Samba Shares - default CAPS in filenames?
« on: January 22, 2022, 05:35:38 pm »
Hi Everyone,

I've noticed this the other week: it would appear that ALL newly created documents which I am saving on my NAS (therefore using Samba client connection) are using UPPERCASE letters, this is despite the fact that within the application itself I am actualy saving with lowercase, and/or combination of the two.

Has anyone else noticed this?

I recall having a sporadic occurence of this before, but I just attributed that to "human mistake" as I rarely create a lot of NEW documents on my NAS. But recently I have been doing a bit of a re-org and moving some of my OS/2 application specific things to formats that non-OS/2 apps can read and that is how I discovered this issue.

The NAS confirmation has not changes at all and so far I haven't spent much time researching the Samba config side of it, that'll be my next step though. In the meantime I was curious if anyone else has been encountering this behaviour?

Thanks!

45
Networking / Re: Squid Cache
« on: January 22, 2022, 05:20:53 am »
Guys...I'm curious: what's the purspose of setting up Squid on a client machine?

If I understood it's intended purpose correctly, it's meant to be a caching proxy primarily for server environments where the clients which are connecting to the server may fetch the very same data, and when that's coming from the caching proxy instead, it makes the response that much quicker, thus providing scalability, etc.

So when deployed on a client I'm thinking there is a very limitted benefit, no?

I haven't tried it, so no actual metrics to toss into the YEY or NAY side.

Thanks!

Pages: 1 2 [3] 4 5 ... 74