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 ... 41
1
Applications / Re: WPS - folder refresh failure...
« on: December 08, 2019, 05:27:15 pm »
Well, so a week later I am happy to report that in my case shutting off XWP's Folder Refresh feature has completely addressed the issue I was seeing.

As an added benefit the occasional WPS crashes I was seeing are now also completely gone (that was the trap screen I attached to the previous post).

Anyways, I realize the XWP logic is probably fairly complex - so I'm not just outright knocking the thing - but for what its worth doing away with that feature has resulted in a more stable system here.

2
Applications / Re: WPS - folder refresh failure...
« on: December 01, 2019, 03:00:19 pm »
Hey Doug!

Yes I have seen this - both on folders on a remote machine and folders on local drives. 

My problem was files that I knew to be in a directory were not showing up in WPS.  I have also seen where I drop a folder template on a drive object and the new folder does not appear - even after hitting refresh...

Ahh, good reminder. I had actually responded to your post back then for a slightly different reason, although it may very well be the same reason that's causing me a problem today.

I've had a re-occuring issue with XWP where WPS folders stop populating. In it's most obvious form the WHOLE folder goes blank, nothing shows up and the moment this occurs the whole WPS filesystem object structure is impacted. The only way to fix is to do a Desktop re-start, and if that hangs, well a re-boot is required.

Over the years I have tracked that down to what appears to be the very same crash in XWP. Take a look at the attached capture (all these entries show up in the xwptrap.log file), I shared with Rich Walsh previously (who I believe maintains XWP today). Unfortunately he has not been able to find the root cause.

Anyways, for now given that I suspect the two things I'm seeing here have common root cause I turned OFF XWP's folder refresh option. This means I am relying on the native WPS processing. I hate to say it but so far I haven't ran into a single occurence of either one of the issues I described above. This has only been a couple of days, so far too short of a duration to say this is IT...so more testing is needed.

Oh, btw: I'm seeing this behaviour with ALL file objects, regardless of whether they have EAs or not. In particular the NAS stuff does not have any EAs, b/c the ZyXel box Samba implementation does not support EAs.

3
Applications / WPS - folder refresh failure...
« on: November 29, 2019, 10:48:28 pm »
I'm curious how many of you are running into a situation where the WPS itself does not appear to be showing refreshes of folders?

Let me explain a bit my situation b/c this is a bit more complicated.

My OS/2 box (4.52 SMP) has XWP installed (latest Aug_2019 1.0.13 release). What I am consistently running into is seeing my NAS hosted folders not showing new contents. For example, I have a SYSLOG deamon running on my NAS and collect LOGs from all the PCs on the network on the NAS. On my OS/2 box I have a shadow to the NAS folder where these exist, yet despite the fact that new files are being created in that folder (on the NAS) I often times do not see the matching OS/2 folder refreshes happen. Even if I invoke the 'Refresh Now' option those NEW files never appear.

The NAS is accessed through a Samba share and NetDrive mapping. Yet this is not a samba/netdrive issue (as best as i can tell so far) b/c checking the contents of the NAS folder through CLI clearly shows the NEW files. So at the Samba/netdrive interface level this appears to be fine.

My XWP has the option turned ON to replace the native WPS folder refresh process. As I attempt to track this down I will shut this OFF and monitor.

But back to my original Q: is anyone else seeing something similar to this behaviour?

4
Applications / Re: Gotcha 2.0.0.1
« on: November 28, 2019, 05:53:26 am »
I'm not familiar with Gotcha functionality...but for anyone using that or Embelish or any other apps, why not use PMView?

It has multiple way of doing screen capture...extremely flexible...never let me down in any of my attempts!

5
Networking / Re: OS/2 to Ubuntu: Any options other than Samba?
« on: November 24, 2019, 03:55:51 am »
Hi Ben,

...I would very quickly dump any version of *nix and use OS/2 exclusively if it could handle the two 4Tb drives.

I wonder... is there any hope of that happening? I understand that this is not possible, but, I've heard such things said before. So, I remain  realistically hopeful.[/color]

Have you tried building a logical LVM volume from multiple 2T partitions?

I am not sure if this would work (seeing that JFS is maxed at 2T anyways) but if the issue is a mapping to actual hardware vs logical addressability of the filesystem space then the logical LVM volume approach may work.

6
Applications / FYI - Lotus 1-2-3 and browser setups
« on: November 23, 2019, 08:30:21 pm »
Over the years I have created a pile of Lotus 1-2-3 worksheets. Despite the fact that we have OpenOffice it's been a time consuming task to migrate...subsequently as you can imagine the native Lotus 1-2-3 continues to get a good "work-out"...LOl!  8)

Anyways, recently I was going through some older worksheets which had URL links in them. Since it's been quite some time that I've used these, I came to find out that the old (original I suppose?) Lotus 1-2-3 browser setups were no longer functioning (error msg about missing browser would pop-up when attempting to select a URL). Below is a quick FYI type of a note to those who may be in a similar situation and want to update the Lotus 1-2-3 install to use a new/modern OS/2 browser, FF in my case.

1) the Lotus 1-2-3 readme will point out that you can setup a browser in the following section:

Code: [Select]
======================================
I. INFORMATION ABOUT 1-2-3 RELEASE 1.5
======================================
..snip...
 5. The Default Internet Browser
...snip...

Specifically that '5. The Default Internet Browser' will reference the following:

Code: [Select]
-------------------------------
5. The Default Internet Browser
-------------------------------
The SmartSuite Install program automatically defaults to using
Netscape Navigator as the Internet browser for all of the
SmartSuite applications. You can use the REGRX program to change 
to another Internet browser

Executing that REGRX utility will allow you to configure some SmartSuite options, including the default browser.

Now, back in the day the main browser were:
1) IBM WebExplorer
2) Netscape Navigator

Subsequently, the native SmartSuite REGRX utility will leave you at a proverbial dead-end (unless you do in fact want to use one of these browsers). Alas, do not despair ( ;)) there is a way to get your choice of browser hooked up.

Take a look at the screen capture I did, this is the extended help present in the application on this topic. In short, fire up Registry Editor and head on over to the appropriate registry KEY...either replace the existing one (most likely pointing to Navigator), or create one from scratch.

If you need to create one it'll be something like this (replace my G:\ drive references with your install details): http=>shell=>open=>command=> (Default) => "g:\apps\tcpip\firefox\firefox.exe" "%1"

These setups work for me to invoke FF when a Lotus 1-2-3 cell points to a URL.

7
Applications / Re: XWP and folder file size listing
« on: November 18, 2019, 06:27:40 pm »
roberto, everyone...
I wanted to ask, how do you make the command com show you in an extra long window?...

I actually use something a tad different from what everyone has described so far, although that base OS/2 functionality absolutely works.

In my case I use a little utility called 'sizer', here is a quick help screen:

Code: [Select]
[G:\]sizer

 VIO session sizer   v 0.0.2

 Usage: sizer [-p <filename>] [-aim] [other options]

-p   program_filename   Program to be executed
-a   arguments          Arguments passed to the program (keys, filenames, etc)
-w   dimensions         Set window dimensions as 'columns,rows'
-o   origin             Set window corner position (left, bottom) as 'x,y'
-c                      Place to the center of screen (if -o not used)
-t   title_string       Set title as...
-f   font_size          Set "System VIO" font size as 'width,height'
-i   icon_filename      Set icon
-min                    Start minimized
-max                    Start maximized
-aim                    Aim mode (window corner position as title)
-vd  desktop_number     Place on the virtual desktop numbered as 'x,y'
                        (relative screen shift from the current '0,0' desktop)
-pl  priority,level     Set priority 'i'dle, 'r'egular, 't'ime-critical or
                        'f'oreground server and level 0...31 as 'p,l'

Attention! Using of -i option will cause program take up additional RAM

Now that in turn allows me to create the following program object for VIO sessions (see attachment).

So as you can tell I still execute cmd.exe from there, but I pass it the col & row counts, the positioning on the screen (if I want it to be in a specific location, maybe PRIMARY vs SECONDARY display, etc.).

All in all, this was a pretty nice utility to deploy.

8
Setup & Installation / Re: Monitor DPMS controls : SNAP config?
« on: November 18, 2019, 05:07:41 am »
Dave,

Interesting, I've been using the same SDK but didn't look into it much as I'm generally not using SNAP, so was just interested in getting the screensaver to build. It does bring up the possibility that the c:\scitech\lib\release\os232\ow10\pm.lib that I'm linking against is not quite right.

Hmm...so how is it that your version of DSS successfully managed to load SNAP and yet mine does not?

Not quite sure what you mean?

Well, you are building the test versions of DSS, and I am certainly able to run it here. The outcome I am seeing is that somehow the DSS codebase you have, having been compiled and linked against the SNAP generated libs is then able to successfully call SNAP functions on my current SNAP build 505 install.

In comparison, even though I can successfully compile the sample code (such as the EDIDTEST project, which is incredibly simple code), I am unable to successfully execute. Therefore, why the failure on my machine to load SNAP drivers when executing my sample EDIDTEST code, and yet no failure when running your test versions of DSS?

9
Setup & Installation / Re: Monitor DPMS controls : SNAP config?
« on: November 17, 2019, 02:32:16 am »
Dave,

Interesting, I've been using the same SDK but didn't look into it much as I'm generally not using SNAP, so was just interested in getting the screensaver to build. It does bring up the possibility that the c:\scitech\lib\release\os232\ow10\pm.lib that I'm linking against is not quite right.

Hmm...so how is it that your version of DSS successfully managed to load SNAP and yet mine does not?

OK, I have the VA365 versions present here, because I have been primarily working with the IBM compiler in all my previous attempts. Therefore, i find the following in the \snap\lib\release\os232\va36 location:

Code: [Select]
Directory of G:\code\source\snap\lib\release\os232\va36

 8-25-18   5:43p     <DIR>         124  .
 8-25-18   5:43p     <DIR>         124  ..
 3-17-09  10:02p     12354           0  gconsole.lib
 3-17-09  10:02p     12277           0  n_ga.lib
 3-17-09  10:02p    104231           0  pm.lib
10-26-06   4:19p        60         124  readme.txt
        6 file(s)     128922 bytes used

...as such, my pm.lib is what should be getting linked when any locally compiled code is attempting to call SNAP APIs, correct?

10
Applications / Re: XWP and folder file size listing
« on: November 16, 2019, 11:09:35 pm »
Guys!

OK, a single general reply to the last series of posts from Doug, Gregg and Rich.

Doug,
I am running the latest publicly available XWP release, that being 1.0.13 Aug_04_2019 build.

Gregg,
Issue still occurs in XWP 1.0.13.

Rich,
Well, I've had Doodle Screen Saver installed for quite some time now. I have been seeing this issue for equally as long as well, only now I decided to post about it given that it is a cosmetic only type of a thing and I really didn't think it was a functional issue that needed prioritization otherwise. Regarding Doodle SS, until recently (last week or so) I was using a pretty old version of that utility. Now I am running the most recent one that Dave Yeo has published for the tester group (AN).

I can concur regarding the following though: when this issue is exhibited, I can open such a file, close it, and immediately refresh the folder at which point in time the formatting is corrected for all folder items. So the fix you spoke of does in fact appear to work, but perhaps as an after-effect.

11
Setup & Installation / Re: Monitor DPMS controls : SNAP config?
« on: November 16, 2019, 06:28:13 pm »
I talked to the AN folks about an updated SDK a while back. They seemed to think there was no need for an update and weren't interested in updating it.

LOL...well, the real world results sure indicate a different approach is necessary. I shared below information with Lewis earlier today, I'm hoping they will re-consider.

So in my specific case, I wanted to run the EDIDTEST sample code. Compile is OK, however running it produces the following response: "Unable to load SNAP device driver!".

In particular, it turns out this is being brought on by the following procedure call:

Code: [Select]
static GA_devCtx *LoadDriver(
   N_int32 deviceIndex)
{
   GA_devCtx *dc;

#ifdef ISV_LICENSE
   /* Register ISV license for SNAP DDC API */
   DDC_registerLicense(OemLicense);
#endif

   if ((dc = DDC_loadDriver(deviceIndex)) == NULL)
       PM_fatalError(DDC_errorMsg(DDC_status()));
   init.dwSize = sizeof(init);
   if (!DDC_queryFunctions(dc,GA_GET_INITFUNCS,&init))
       PM_fatalError("Unable to get device driver functions!");
   return dc;
}

Either DDC_loadDriver fails, or DDC_queryFunctions. In either case it is the calling code in MAIN that actually handles the 0 (zero) return code from this procedure and puts out that error message.

I have SNAP build 505. The SNAP SDK I have here is build 460 and attempting to boot with it's SDDHELP.SYS causes a freeze at bootup time (right before the GUI stuff comes up). I expected to see that, but I thought I'd give it a go anyways.

12
Applications / Re: XWP and folder file size listing
« on: November 16, 2019, 06:17:42 pm »
Hey Roderick,

Uhuuu is thst xwp? That rather looks like the pmview file open container.
Or is it me?

Ahh...sorry, the image is somewhat missleading, I should have explained it actually. It is a screen capture of both the XView part of folder view as well as the underlying CLI interface. The purpose there was to show the pertinent file details in both environments.

So for example, looking at file editest.map, you can see that the XView shows "13,340,7.0,000,000,000,089", while the CLI shows '133407' for filesize.

In that example, it would appear that the XWP disiplay is offset/shifted by a space.

Now, at first I thought maybe the 'Workplace Shell => Status Bars' settings are impacting this. But having reviewed these I am fairly certain these settings apply to just the folder STATS BAR, so they would not be impacting individual object information, as visible in the XView display.

What I suppose is a tad stranger is the fact that following a re-boot this very same folder now shows all correct information...LOL, ugh???

13
Applications / XWP and folder file size listing
« on: November 16, 2019, 04:03:50 pm »
Hi everyone!

Can anyone tell me why my XWP is showing such outrageously huge sizes in the Folder=>Xview mode?

It does look like this isn't just a single number, it appears to be a filesize first (which is correct), followed by another value and finally a 3rd value. I have no idea what those other values are though, guessing maybe the free disk space, or simply a max size that can be displayed in this field that's just set to 999,999,999 by default?

This appears to only happen until I actually open a given file...once opened and closed the view does show the correct filesize afterwards.

14
Setup & Installation / Re: Monitor DPMS controls : SNAP config?
« on: November 16, 2019, 03:51:40 pm »
Dave,

...One other test you could do is to try using direct VGA access. There's a couple of icons in the screensavers folder, one for enabling direct VGA access and one for using snap. Need to restart the desktop after switching. The direct VGA access probably won't work but it is easy enough to test...

Yeah, I was thinking of going down this route next, should the SNAP direction not get a result I'm looking for.

So, with the direct VGA access the only option is to actually issue a DPMS OFF call, or at least that's what the DSSAVER tab implies.

I did test this out and BOTH monitors go dark. Now, is that 'dark' an OFF state? Nope, the power LED remains blue and does not go to amber, which is what that gactrl.exe tests show when I test directly. However, there is something different here because if I am in fact running an animated screensaver module upon the VGA access being activated BOTH screens freeze at that instant. This is different from what the SNAP approach does (see my earlier comment on how this works). So this could be getting me a STAND BY mode since the screens respond very quickly once I re-active them.

Anyways, for now I'm just going to stick with the VGA access. I am trying to get the AN folks to release an updated SNAP SDK build, the one I have here is from 10/2006 "Version 3.1 - Release 23", and SDDHELP.SYS build V3.0 - Build 460. Unfortunately any sample SDK code I build refuses to load due to driver load issue. I am playing with their DPMS calls to see if I can write a very simple DPMS mode tester which specifically deals with a multi-head installation.

15
Setup & Installation / Re: Monitor DPMS controls : SNAP config?
« on: November 15, 2019, 12:17:33 am »
Hi Andi.
My main system is a dual-monitor setup with ATI X300, SNAP of course. I've a lot of other systems running and tested with Panorama. But I've never seen a system which switches monitor(s) off with the eCS/ArcaOS included Screen Saver.

OK, so what I'm seeing maybe not be all that un-common after all.

...On my main system with (ATI X300, SNAP) I've extended the old blackout utility to switch of the monitors after a period of inactivity. SNAP couldn't do that with the X300...If you've a X300 or X550 you can try my blackout version too (hobbes).

Hmm...what's the name, b/c current search for blackout across the entire archive results in NO HITS. I'm guessing 'black103_ab.zip' is the file though? d/l'ing it right now...

Well, for what it's worth, as I wrote earlier, testing this out with SNAP's gactrl.exe and option #7 here (DPMS tests) actually provides a working STAND BY and SUSPEND functionality. it's just that Doodle SSaver does not appear to utilize it correctly???

...Btw.
IMHO this has nothing to do with landscape/portrait mode. Your monitor is simply faulty. It reports WRONG data. Obviously there is no workaround for your monitor with wrong EDID in any of our display drivers.

Ahhh, and here, with all due respect I have to differ. So here is the thing, I've actually re-written the EDID coding on the 245T display, progressively simplifying it right down to literally just the bare definition of basic VESA modes and the panel's native 1920x1200 resolution. The DVI and VGA ports have their own EDID records, so I adjusted the VGA side of course. Still the monitor would insist on coming up with this dreaded screen flip display. I thought I would completely take the EDID out of the equation. This meant I actually picked up an EXTRON EDID 101D & 101V module, which are pre-programmed with vanilla (VESA basically) modes, as well as allowing you to record a good EDID off of a monitor that works so that I could fake the video card & video drivers out.

Results => NOPE, nuthin'....still broken.

Better yet, given that my new DELL is recognized correctly, both on DVI & VGA I actually used the EXTRON module to copy the DELL EDID and drive the SNAP driver with that data...nah, no-go, the Samsung 245T would still come up with the wrong resolution.

Therefore, I attribute this completely to an internal monitor logic fault (in terms of how it actually responds to the video signal). This btw is across multiple 245T panels, I have some 4 of them here and am using them with my Winx based machines very successfully, albeit all connected through DVI.

Pages: [1] 2 3 ... 41