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 - Andi B.

Pages: 1 [2] 3 4 ... 54
Can someone please remind me where I find the ignore user setting? My KI / KNI / AI / NAI / useless non-related nonsense detector get triggered regularly.

Networking / Re: Updated Samba Client
« on: January 16, 2024, 09:07:56 am »
Isn't it enough to disable EAs for Samba shares? Or what is the option in smb.conf good for? I've it in the global section. I ever thought it is for the server, right?.

AFAIR the netdrive smbfs dialog has an option to enable/disable EAs too.

Applications / Re: NewView - control over NEW window placement?
« on: January 14, 2024, 05:32:14 pm »
For the ones who wanna position a window on a defined place other the one the OS has stored - maybe you wanna check out "PGMCNTRL V1.07 - C.Langanke 1996-2004".

F.i. I've a cli window (ssh to one of my linux boxes) which I wanna always like to open on the same place and I use for that an object like the picture below. The Parameters line is -
Code: [Select]
/c mode 120,65 & pgmcntrl /po:2100,25,820,950 & p:\4os2\4os2.exe @p:\4os2\4os2.ini "p:\4os2\4start.cmd & p:\usr\local\bin\old\ssh -l git nas-ab"

Programming / Re: Installing VisualAge 4 on ArcaOS 5.x
« on: January 09, 2024, 09:39:07 am »
Did your install run through fully? A few months ago I tried to install over an existing installation but it failed. Even from the original CD it does not install all the things needed for the help system. AFAIR the installer crashed whatever I tried.

Applications / Re: NewView - control over NEW window placement?
« on: January 09, 2024, 08:55:37 am »
would open exactly on top of the first one, which is obviously not desirable.
Which I think is not that bad. I think this is the usual way window positioning worked the last centuries. I mean why should a program decide by itself where it is positioned and sized? It's the task of the OS to keep window positions (and sizes) stored and restore them. Usually at the place it was when closed the last time. When a user explicitly wanted to have it positioned on some special other place, you can always use pgmctrl or like or implement cli options or.... But hey - I wanna my windows at the place I put it. That's one reason I stay with OS/2. I don't wanna an OS or a program which decides this by itself. YMMV, but in this case you have other OS options anyway.

It's a big bug in latest versions of Win that they forgot about this OS (window manager) task. Although I understand their design decisions (which do not apply to our OS).

Applications / Re: ArcaOS is the best multitasking system there is
« on: January 08, 2024, 09:39:31 am »
I don't wanna say anything against your positive view on ArcaOS. But of course there are often similar tools for similar task with other OSes. F.i.
In Windows, they have to setup external monitors to do what Xpager does.
I use VirtuaWin (v4.5) on Win to replicate xpagers behavior and even set up the same keys for switching between the pages. There are other tools which do the same. But long time ago when I looked for it I choosed this one.

I also have DesktopOK and WindowManager (DeskSoft) on every of my Win installations together with a lot of other utilities to make this OS somewhat user frindly (for me).

Remember, on OS/2 (ArcaOS) we also need different third party utilities (like XWP and a lot of others) to make the system behave the way we like it.

Programming / Re: Where to find Toolkit2.0 - SOM compiler .sc files....
« on: December 27, 2023, 12:38:12 pm »
Thanks Lars. I'll try to integrate that into the build system of pmprintf (polymake and...). But maybe will take a while until I worked out some other problem.

Programming / Where to find Toolkit2.0 - SOM compiler .sc files....
« on: December 23, 2023, 04:58:35 pm »
I've toolkit 2.1 and probably all newer ones. Even Watcom10.6 includes some .sc files. But the project I'm working on seems to need Toolkit v2.0.

I've no clue about SOM and classes and.... but there is one .csc file in my project which constantly bothers me. There should be a way to convert this .sc file to the newer .idl form. ctoi.cmd which is included in os2tk45. But it complains about a file in toolkit21
Code: [Select]
{0}[e:\_work\pmprintf\trunk] ctoi WPSTEST.CSC
"", line 440: error: Override method "somInitClass" not in base class.
"", line 444: error: Override method "somNew" not in base class.
"", line 448: error: Override method "somRenew" not in base class.
Number of errors: 3
error in converting WPSTEST.CSC

So I think I need toolkit20. Where can I find it? Any other ideas? Maybe I try to disable all these SOM things in pmprintf cause I guess nobody will ever use pmprintf with som classes anymore anyhow.

Applications / Re: Panorama Maximum Resolution
« on: December 21, 2023, 04:47:34 pm »
At the moment I'm experiencing that if you BIOS does not support that resolution I can not make a 4K monitor
I would it express in other words - the BIOS offers Panorama only resolutions it thinks the 'monitor in conjunction with the current connection' (DP, DVI, HDMI, ...) is capable. Then Panorama tries to select the predefined BIOS mode (resolution) which matches best OR tries to patch on of the BIOS modes to a better resolution.

I'm not sure if I got it correct, but to my understanding Panorama is sometimes capable to patch (overwrites) one of the modes in some BIOSes. That's the reason why I see a slight chance that there could be a difference when you use traditional BIOS mode instead UEFI. Currently you're running the 'UEFI BIOS emulation' driver not the real BIOS. Of course I could be totally wrong. Maybe when you open a ticket David will explain to you the real truth.

Applications / Re: Panorama Maximum Resolution
« on: December 20, 2023, 09:01:23 pm »
I think this
Code: [Select]
Panorama v1.18 log for GID=0 started at 2023-12-8 10:9:43
This copy of Panorama is licensed to Martin Iturbide #xxxxxxxxxx.
Profile setting for Shadow...Enabled
VESA version is 201
BIOS-supplied information
OemVendorNamePtr  = 8B000022
OemProductNamePtr = 8B000031
VideoModePtr      = 8B00004D
TotalVramSize     = 1000000
OemVendorName     = Arca Noae, LLC
OemProductName    = UEFI VESA Emulator v1.0
Emulated environment detected.
Initial PmRes X=1920 Y=1080 C=16777216
EDID Version 1.4
Display size 31 cm x 17 cm
Display resolution is 1920x1080
Info: 14100,1920,1080,184,36,16,16,3,14
Checking BIOS...
Mode 0x120: 1920x1080x32bpp planes=1 Attr=0xDB
Mode 0x121: 640x480x32bpp planes=1 Attr=0xDB
Mode 0x122: 800x600x32bpp planes=1 Attr=0xDB
Mode 0x123: 1024x768x32bpp planes=1 Attr=0xDB
Mode 0x124: 1280x1024x32bpp planes=1 Attr=0xDB
Mode 0x125: 1366x768x32bpp planes=1 Attr=0xDB
PmRes X=1920 Y=1080 C=16777216
X=1920 Y=1080 C=16777216 LoX=65535 LoY=65535 LoC=0
Requested mode=120
Video Aperture: Base=0xD0000000 Size=0x800000
Attempt to allocate shadow buffer...Success
Shadow Buffer locked at 0x5E5F7000, Length 0x800000 bytes
Trying D0000000 size 800000.
MTRR Write Combine caching enabled Base=D0000000 Size=800000.
Requested mode=120

 is the most relevant part. It shows that you are using the UEFI emulation. No clue if this has additional limitations. But it does not show how you have attached your monitor. If this is a notebook there's nothing you can do about of course. But if it's a desktop system then you really need DP. And don't attach another cable during boot in parallel, only DP nothing else. If no DP is available then try HDMI. Remember only one cable attached during boot.

You can compare what I've here -
Code: [Select]
Panorama v1.16 log for GID=0 started at 20.12.2023 20:26:17
This copy of Panorama is licensed to andreas.xxxxxxxxxxxxxx.
Profile setting for Shadow...Enabled
VESA version is 300
BIOS-supplied information
OemVendorNamePtr  = C0000170
OemProductNamePtr = C0000102
VideoModePtr      = 8D000044
TotalVramSize     = 3000000
OemVendorName     = (C) 1988-2010, Advanced Micro Devices, Inc.
OemProductName    = LEXA
Manual custom resolution is set to 3840x2160
Checking BIOS...
Mode 0x110: 640x480x16bpp planes=1 Attr=0xBB
Mode 0x111: 640x480x16bpp planes=1 Attr=0xBB
Mode 0x113: 800x600x16bpp planes=1 Attr=0xBB
Mode 0x114: 800x600x16bpp planes=1 Attr=0xBB
Mode 0x116: 1024x768x16bpp planes=1 Attr=0xBB
Mode 0x117: 1024x768x16bpp planes=1 Attr=0xBB
Mode 0x119: 1280x1024x16bpp planes=1 Attr=0xBB
Mode 0x11A: 1280x1024x16bpp planes=1 Attr=0xBB
Mode 0x165: 1280x960x16bpp planes=1 Attr=0xBB
Mode 0x166: 1280x960x32bpp planes=1 Attr=0xBB
Mode 0x121: 640x480x32bpp planes=1 Attr=0xBB
Mode 0x122: 800x600x32bpp planes=1 Attr=0xBB
Mode 0x123: 1024x768x32bpp planes=1 Attr=0xBB
Mode 0x124: 1280x1024x32bpp planes=1 Attr=0xBB
Mode 0x145: 1400x1050x16bpp planes=1 Attr=0xBB
Mode 0x146: 1400x1050x32bpp planes=1 Attr=0xBB
Mode 0x175: 1600x1200x16bpp planes=1 Attr=0xBB
Mode 0x176: 1600x1200x32bpp planes=1 Attr=0xBB
Mode 0x1D2: 3840x2160x16bpp planes=1 Attr=0xBB
Mode 0x1D4: 3840x2160x32bpp planes=1 Attr=0xBB
Mode 0x1D8: 2560x1440x16bpp planes=1 Attr=0xBB
Mode 0x1D9: 2560x1440x32bpp planes=1 Attr=0xBB
Video Aperture: Base=0xE0000000 Size=0x2000000
Attempt to allocate shadow buffer...Success
Shadow Buffer locked at 0xABFE0000, Length 0x2000000 bytes
Trying E0000000 size 2000000.
MTRR Write Combine caching enabled Base=E0000000 Size=2000000.
Requested mode=1D4

Edit - I see you're talking about a notebook. For such you can only play with BIOS options. No clue if it helps. Especially in UEFI mode. But you can try to select in BIOS something like 'External Display only'. For ArcaOS it's not possible to drive both displays (internal and external) at the same time. You need the right display at boot up (and only that one enabled). At least I can't get it to work on my notebooks. But Neil is much more experienced in this for sure.

Applications / Re: Panorama Maximum Resolution
« on: December 20, 2023, 09:11:55 am »
Code: [Select]
If there is any additional trick you may suggest for 3840x2160 I will try it out.You can search the Mantis ticket about that from me a few years ago. Basically before playing games with custom resolution settings (you shouldn't do that) check what your hardware offers. I think it's listed in a testlog but there's also some util IIRC.

It depends on -
- connection type to your monitor (DisplayPort prefered is capable of all relevant resolutions, DVI can not do more than 1920 x 1440, HDMI varies a lot between different versions, analog RGB can't do very much probably no more than 1920x1200 or something like that)
- your monitors capabilities (read out and offered to the driver via EDID interface)
- your graphic card
- and most important the BIOS in your graphic card.

Sometimes it needs additional work from David to get it to work on your system though.

3840x2160 is running here since some time via PCIe ATI graphic card and the help of David (who included the fixes in 1.18 I think). 

Applications / Re: XWP v1.0.16
« on: December 19, 2023, 05:53:42 pm »
I for myself prefer the sharp crispy font display LCDs can provide. If I wanna have these washed out fonts then I would attach these crappy old blurred tube monitors we had to work with decades ago. Or don't clean my glasses for a while of put them off completely :-).

Of course these is only valid for our carefully selected bitmap fonts used for the WPS. For surfing the net with all these different fonts in different sizes aliasing is necessary. But not for WPS and window menus. YMMV.

Thanks Steven. I've a program object which calls 'ssh -l git nas-ab'. Luckily it's so easy on our platform to change the environment for some objects (think 'Environment' tab is an XWP object extension) I tried with term=vt100 and it sorta works.

Colored dir is working now, thanks.

But nano opens a small window (different to the older ssh) and produces a LIBC PANIC!!. Log is appended if anyone is curious. Have to check different things ....

Btw. TAB does not work either. Which is really a pain on a *nix system. TAB is working with the old OpenSSH though.

I connect to some Linux box via SSH. After figuring out all the keys stuff it works. But now I've updated to 'OpenSSH_8.4p1, OpenSSL 1.1.1s  1 Nov 2022' and see some problems/differences. As I'm not familiar with all these SSH and Linux stuff I want to ask here before opening a ticket.

Old version 'OpenSSH_5.3p1, OpenSSL 0.9.8k 25 Mar 2009' worked fine. I've colored dir (dir, ls -la, ls -ls, ...) but with new version 'OpenSSH_8.4p1, OpenSSL 1.1.1s  1 Nov 2022' the colors are gone. I know I've setup these colors in some conf file on the Linux box (I think) but don't remember where anymore. But there must be a difference between our two ssh versions. Cause I can connect with the old version at the same time as with the new ssh.exe version. Old has colored dir, new not. I'm using the same user of course.

I also noticed that with the old version 'nano' works while with the new version nano gives an 'Error opening terminal: os2.'.

Anyone knows what this 'terminal: os2. means? Or how to change? Or how to find out why the old version works better than the new one?

Additional info - the old ssh version was installed here in /usr/local/bin. No clue from where I got it but most probably not from the netlabs repository as it would have been in /usr/bin then.

Applications / Re: LarsenCommander - new test version
« on: December 14, 2023, 10:36:50 pm »
The solution to this particular problem is to get rid of the DLL -- there's no reaon for it to exist. The original author claimed that VACPP 4.0 couldn't handle a 16-bit call so he created a separately-compiled file. But rather than simply linking it into the exe with all the other .obj files, he created a dll. Why?

It seems it was that easy - add '      source "gl16os2.obj"' to lcmd.icc and don't delete gl16os2.obj during the build. As far as I can see the only 16 bit function which is used by lcmd is Dos16MemAvail. But no clue when it is called. Have to test a while to be sure there's no sideeffect.

Pages: 1 [2] 3 4 ... 54