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 - Rich Walsh

Pages: 1 [2] 3 4 ... 23
16
Programming / Re: Bigicons
« on: March 10, 2024, 03:31:17 am »
my guess it is a workplace shell limitation at this time.  Rich had said WPShell was a mess

No, I said Dynamic Icons was a mess. Multiple shortcomings prevent Details view support and limit Tree view to the same sized icons as Icon view. Here's why:

1) DI's "dirty little secret" is that it creates a separate, standalone PNG image for every single object you see during a session. When you open a folder with 100 JPGs, it generates 100 png images each requiring 16k. The same is true for every folder, every datafile, every everything. Over the course of a session you could end up with thousands of images.

2) DI caches these images to avoid the compute-intensive job of recreating them. However, each object can only cache one icon. If you display an object in Icon view at 64 pixels, then open the same folder in Details view using 32 pixel icons, DI will have to destroy all of the 64px images and recreate them at 32px. In a worst-case scenario where both views are open, DI might have to destroy and recreate every icon for every refresh!

Happily, there's a solution in the pipeline for #1. After our earlier discussion, I rewrote large parts of DI to eliminate duplicate icons as much as possible. Some users may see an 80-90% reduction in DI's memory usage when AN releases it. However, it will require a thoroughly revised 'bigicons.txt' file to achieve these savings. @David, could you send me a PM with your email address so we can discuss this and exchange files?

Sadly, the shortcomings that prevent Details view support and limit Tree view will remain for the foreseeable future...

17
Programming / Re: DosDevIOCtl disabling keyboard in VIO mode
« on: March 07, 2024, 07:19:01 pm »
Quote
I'm surprised that the program you wrote about originally ever ran if it had this kind of layout.
The original program (almost same source code) was built with Watcom tools. What you see above is a new suite of tools.

If you expect these programs to run on OS/2 - even if only to prove that (some) OS/2 programs run on your OS - then fix your tools to create bona-fide OS/2 executables. It's not optional.

18
Programming / Re: DosDevIOCtl disabling keyboard in VIO mode
« on: March 07, 2024, 05:56:27 pm »
pdld has been updated to fix a couple of errors, but result is still the same (OS/2 says it can't run it).
I have suggested that the MZ header is too small for OS/2 to cope with, but he thought it was one of the other reasons.

How did you link this thing? Its layout doesn't look anything like an OS/2 LX executable.
Using 'exehdr' (from the OS/2 Toolkit) I find this:

Code: [Select]
no. virtual  virtual  map      map      flags
     address   size    index    size
0001 00400000 00005fcd 00000001 00000006 EXECUTABLE, READABLE, 32-bit
0002 00406000 000006d8 00000007 00000001 READABLE, WRITEABLE, 32-bit
0003 00407000 000067b0 00000008 00000007 READABLE, WRITEABLE, 32-bit

The virtual addresses (2nd column) for a small program like this should be:
0001 00010000
0002 00020000
0003 00030000

The "00400000" looks more like a 16-bit segmented address (i.e. 0040:0000).

Then too, we have:

Code: [Select]
Initial CS:EIP:                 object 1 offset 00000000
Initial SS:ESP:                 object 4 offset 00008000

Your stack is in a non-existent segment. Your entrypoint _could_ be at offset 0x00 but seldom is in most programs. I'm surprised that the program you wrote about originally ever ran if it had this kind of layout.

19
Programming / Re: DosDevIOCtl disabling keyboard in VIO mode
« on: March 04, 2024, 06:46:11 am »
Quote
What are you trying to do?
I am trying to switch off echo and line buffering so that I can write a fullscreen text application, like microemacs 3.6. As a pure 32-bit app (no thunking within my executable). As such - OS/2 should not do keyboard character echoing. The application will deal with that.

I've never had the slightest interest in writing a true text-mode app, so I have no hand-on experience. However, perusing the 'Control Program Reference', I found KbdSetStatus(pkbdinfo, hkbd). The description of the KBDINFO structure's "fsMask" member lists these flags:

Code: [Select]
fsMask (USHORT)
State mask.

  Bits 15-9 Reserved.
  Bit 8 Shift return is on.
  Bit 7 Length of the turn-around character (meaningful only if bit 6 is on).
  Bit 6 Turn-around character is modified.
  Bit 5 Interim character flags are modified.
  Bit 4 Shift state is modified.
  Bit 3 ASCII mode is on.
  Bit 2 Binary mode is on.
  Bit 1 Echo off.
  Bit 0 Echo on.

Isn't this what you're looking for? (I _assume_ this is a 32-bit entry point to a 16-bit function.)

20
Applications / Re: XWP v1.0.16
« on: March 04, 2024, 05:30:04 am »
Query os2.ini->PM_SystemFonts->WindowText to get the font name & size, then use it.

Which specific lswitch282.ini key are we talking about here?

I have no idea. I was simply identifying how you get the current general-purpose font from os2.ini. How lswitcher uses it is up to Gregg...

21
Applications / Re: XWP v1.0.16
« on: March 03, 2024, 07:26:08 pm »
What do you think it is needed for lSwitcher to also respect the XWP font sizes too?

Query os2.ini->PM_SystemFonts->WindowText to get the font name & size, then use it.

22
Programming / Re: DosDevIOCtl disabling keyboard in VIO mode
« on: March 02, 2024, 08:40:26 pm »
Did I make a second mistake in the above code?

Yes: your code fails to accommodate the environment it finds itself in.

In fullscreen mode it works because it assumes ASCII (correctly), switches to binary (to capture special key-combos?), then restores ASCII. IOW, it all works exactly as you'd expect a primitive terminal would when accessing real hardware.

However, iIn VIO mode that isn't the case: this is an _emulation_ provided by Presentation Manager. PM has its own good reasons for switching to binary mode before giving you an emulated console. Since it appears to get unhappy when you mess with it ..umm.. don't.

What are you trying to do? Capture Ctrl-C and the like? If so, there are probably higher-level 32-bit functions to handle this (e.g. DosSetSignalExceptionFocus() ).

23
Applications / Re: XWP v1.0.16
« on: February 21, 2024, 08:17:29 pm »
I notice that the environment tab in some properties notebooks does not seem to honour the text size.
Same with the Objects and Schedule tabs.

I've been meaning to release an update to fix that. Maybe now is the time :)

* Find your DragText directory (on AOS, it's in 'x:\sys\apps\drgtxt39').

* Unlock 'DTPGM39.DLL' using 'unlock.exe' or 'xunlock.exe' (the latter is in your 'xwps\bin' directory).

* Replace the dll with the attached (unzipped) file.

24
Setup & Installation / Re: Install - screen goes blank when pmshell starts
« on: February 01, 2024, 06:45:56 pm »
Thanks Rich.  I was just about to ask whether something like this existed and I saw your post.  I need it because I think I got rid of the files in the ESP.

'CSM2UEFI' is not going to fix - or even touch - your ESP. The following is what it fixes:

Quote
when booted in UEFI mode the screen blanks and then shows static arranged as triangles spread across the screen for about 10 seconds - and then the desktop comes up normal as it should.  Weird.  When booted in legacy mode the desktop just comes up without the weird temporary static stuff.

You are booting UEFI using CSM base video drivers:
  SET VIO_SVGA=DEVICE(BVHVGA,BVHSVGA)
vs.
  SET VIO_SVGA=DEVICE(BVHEFI)

CSM2UEFI will pull 7 files from the ISO, put them in the right places, then update 2 lines in config.sys to give you UEFI-compatible text-mode and DOS video. As you've noticed, you don't need to do anythng to get PM and WinOS2 video working.

Quote
So to avoid having to use the bios boot menu to get a legacy boot on my main drive (drive c:) I removed the ESP and installed AirBoot on the NVME.  Big mistake - because now the mouse doesn't work.

You keep making it worse for yourself. Your ESP *MUST* be on your first drive and it MUST contain all UEFI bootloaders and boot managers for all operating systems. In contrast, your bootable partitions can be on any drive. Use MiniLVM to reinstall the AOS UEFI components.

Afterthought... you say you installed AirBoot on the NVME. Did you _really_ reformat the drive as MBR? Argggh...

25
Applications / Re: AcpiDaemon start
« on: January 30, 2024, 05:16:21 am »
What you are saying is that this programmer did not have all his facts straight.

No, He was correct in **1995**

Quote
This patch that I applied said it was for Warp version.

On or around April 25, 1995 (the date of the package), that was Warp *v3*.

Quote
So, is this patch ignored after it is applied by Warp and later?

I'm not willing to try it to find out. All I know is that it attempts to fix a problem that doesn't exist on Warp v4.5. Even without access to the PM Ref, I still wouldn't have tried a fix that doesn't mention 4.5 but does mention 2.x. If it were genuinely useful, most everybody would know about it and be using it - but they're not. That should tell you something...

26
Applications / Re: AcpiDaemon start
« on: January 30, 2024, 03:23:05 am »
I downloaded a program called The PM Queue Size Patch.

From the "Presentation Manager Programming Guide and Reference":

Quote
WinCreateMsgQueue(hab, lQueuesize);

lQueuesize (LONG) - input
Maximum queue size.

This parameter is ignored for versions higher than version 3 of the OS/2 operating system. The lQueuesize parameter is dynamically allocated. The maximum queue size should be set to zero.

For version 3 and lower of the OS/2 operating system, this parameter is the maximum number of messages that can be queued.

0 - Use the system default queue size which is 10 messages.

Other - Maximum queue size.

27
If the install wont run it appears my work-around is to convert my v 5.1 legacy install from the crapped out motherboard into a UEFI install on the new machine.

A few months ago I posted a util to handle this. See Csm2Uefi migration tool (updated)

28
General Discussion / Re: Hobbes Retirement
« on: January 28, 2024, 05:31:32 pm »
I have decided to cancel work on that mirror as Nathan went ahead.

Who is "Nathan"?  And why would you (or any of us) care what "Nathan" is doing?

29
Networking / Re: ArcaMapper and Network Protocols
« on: January 19, 2024, 10:07:54 am »
how does Samba server fit into ArcaOS, as it seems ArcaMapper is about using Samba Client

It's no different than, say, http:
* if you want your machine to send files to other computers on request, Samba Server
* if you want your machine to request files from other computers, Samba Client

A Peer network just combines both functions in a single package.

30
Networking / Re: Updated Samba Client
« on: January 15, 2024, 10:42:36 pm »
Hey Dave,
Do you know if there is a way to turn that off?

PMFJI...  SET LIBC_UNIX_EAS=[drive letters to include or !exclude]

For example, I disable them on all drives except my boot drive (N:) using:
  SET LIBC_UNIX_EAS=!C-M,N,!O-Z

You can use individual letters or create ranges; use '!' to negate a letter or range.

Note 1: these EAs must be allowed on your boot drive (or maybe it's just your %UNIXROOT% drive) or "bad things will happen".

Note 2; for many of us, the biggest source of these annoyances (IMHO) is Info-Zip. I use an older version which doesn't create them.

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