Recent Posts

Pages: 1 [2] 3 4 ... 10
11
Programming / Re: PMPrintf package v2.80 and PMPrintf_abtrace code samples
« Last post by Martin Iturbide on April 22, 2024, 03:50:08 pm »
Thanks Andi B.

I had also uploaded it to HobbesArchive.com to have it as backup too.

Regards
12
Programming / Re: Dive: Why does not this work
« Last post by Jochen Schäfer on April 22, 2024, 12:35:44 pm »
I wonder then, how SDL work then. There is not one mention of WM_VRN*. It just blits the whole SDL surface to the buffer (no direct VRAM access).
13
Programming / Re: Dive: Why does not this work
« Last post by Lars on April 22, 2024, 12:27:08 pm »
The samples seem to indicate that you are forbidden to drive screen updates in between calls WM_VRNDISABLED and WM_VRNENABLED. That is, there is a timespan where you are not allowed to blit anything to the screen, that means, the Classicube draw buffer function should do nothing during that timespan.
That in turn means, the proper point in time to call DiveSetupBlitter are WM_VRNDISABLED and WM_VRNENABLED. The "Remarks" section for DiveSetupBlitter even states that DiveSetupBlitter is "not intended to be called at high frequency".

This would be even more relevant for direct screen updates (that is, if you used DiveAcquireFrameBuffer / DiveDeacquireFrameBuffer / DiveSwitchBank / DiveCalcFrameBufferAddress and direct writes to the video aperture "ppFrameBuffer" as returned by DiveOpen) but for already mentioned reasons you should not do that anyways.

Still, it looks as if DIVE still needs to be notified via DiveSetupBlitter when WM_VRNDISABLED and WM_VRNENABLED are called for a specific window even if you do not do direct screen updates.
14
Programming / Re: Dive: Why does not this work
« Last post by Jochen Schäfer on April 22, 2024, 11:33:25 am »
I understand that, but Classicube calls the draw buffer function with a rectangle to paint, so I setup the blitter in the draw function. This should work I would think.
15
Programming / Re: Dive: Why does not this work
« Last post by Lars on April 22, 2024, 11:23:35 am »
Look at the OS/2 toolkit, in the "beehive" sample code (in that code you can ignore everything that centers around sprite creation. You can also ignore everything that centers around full screen DIVE unless you really want to do that, that includes loading GAMESVR [deprecated since Warp 4] or PMMERGE  Dive Fullscreen Init procedure).

I think you will need to support the WM_VRNDISABLED and WM_VRNENABLED window messages and use DiveAllocImageBuffer,DiveBlitImage,DivFreeImageBuffer. Note that the sample does the blitting from a secondary thread.
Yes, I do use the Dive functions, but WM_VRNDISABLED AND WM_VRNENABLED are not much use for me, since Classicube gives me the rectangles it wants to paint to, anyway. Moreover, SDL2 works without using the window messages, so it seems optional.

Look at the help for the "DiveSetupBlitter" function. You need to support WM_VRNDISABLED and WM_VRNENABLED in order to notify the Dive Blitter via "DiveSetupBlitter" that changes to the visible regions will start or end to occur.
On a reception of WM_VRNDISABLED you need to disable the blitter, on a reception of WM_VRNENABLED you will need to set up again the blitter with the proper values.
16
Applications / Re: LarsenCommander - new test version
« Last post by Mentore on April 22, 2024, 08:26:44 am »
I've just uploaded v1.08.02 at https://sourceforge.net/projects/lcmd-git/files/

From the Readme -
Code: [Select]
Change History:
---------------
20240416 v1.8.2
- Improve EA handling routines to reduce memory leaks and silent crashes
- Fix TRAP 000e in JFS while copying >69000 files. Hint, please use latest ArcaOS (kernel, JFS, ACPI 3.23.17, ...)
- Removed gl16os2.dll dependency (link .obj into .exe)
- Handel out of memory conditions more gracefully
- Added abtrace for logging via pmprintf.dll (if available on target system)
- Improved build cmd files to break on error (ERRORLEVEL handling)
- Tuneed lxlite options to not remove bldlevel info
- Change to David G. icon files (no clue where they are used)
- Again tuning of dynamic copy buffer size adoption (even more speed on my system :-) )
- Change icons to the ones supplied by David G. Thanks for that although it's not clear to me where they are used.
(- Disable integrated exception handlers in favor of exceptq) reverted back
- Disabled ExceptQ handler as I can't get it to work in conjunction with lcmds own handlers

Bug reports please here - https://sourceforge.net/p/lcmd-git/tickets/

Of course I'll keep reading here as well from time to time. Have fun.

Btw. I've a really hard time to track down and reduce this terrible JFS traps when copying a lot of files. It seems to me that JFS still does not touch some memory pages when feed with >4k buffers some times which I guess leads to these 000e traps. Combined with the memory leaks which LCMD suffered when lot of files where copied I had uncountable crashes with long chkdsks afterwards. Now the I reduced memory need for extended attribute handling I can't see these memory leaks anymore with above512. But on some scenarios LCMD still seems to eat up some system resources which report out of memory. Closing LCMD will recover from such situations now.

If you encounter hangs of LCMD you may look at the lcmd.log file in the directory of lcmd.exe. F.i. tail -n 50 lcmd.log will show you the last messages which usually shows some exception infos. For this you've to enable 'Debug' or 'Test' in Help - Debug - Options. Be aware running LCMD with 'Debug' for a long time or while copying huge amount of files let lcmd.log become very big in minutes.

Btw. if you've pmprintf.dll on your system PmPrintf.exe will show you these messages from LCMD with 'Debug' or 'Test' enabled too.

Downloading right now, I use LCMD all the time.
Should I notice some bug, I'll report it ASAP.
Thanks a lot Andi!

Mentore
17
General Discussion / Re: PMfax
« Last post by Neil Waldhauer on April 22, 2024, 05:09:53 am »
The system installs COM ports at boot time while parsing the Config.Sys. The COM port number depends on the ordering of the statements in Config.Sys, and which of them claims a serial port. (Some might not be obvious)

I'm not sure how many COM ports OS/2 supports. Some say 99, some say 255.

In the time since I last posted, both ends of the POTS line have ended service. AT&T has applied for a permit to stop providing POTS to anyone.
18
General Discussion / Re: PMfax
« Last post by Wayne A. Smith on April 21, 2024, 11:18:23 pm »
Neil,
How right you are ...  It's bit a long time since i had to configure this kind of connection, though I'm trying again after a long hiatus in trying PMFax Pro again.

I also have a US Robotics External 54K Voice FaxModem Pro, connected by the USB cable and to a landline.  While PMFax is (I believe) installed properly, I can't get a dial-in recognized by it.  (I first used Suntan Special for installation but got an Error that "Product not enabled."  I then copied an old directory, and used the Registry Editor to change the directory reference.)

USBCOM.SYS is referenced in <config.sys>.  Since FMD1 as the Port didn't work, I tried COM1 but No Joy there either.

Looking in <system.ini> for COM1, the PORTDRIVER key is "Serial".  Since the modem now has a USB connection, is this the problem?  (I also have a Serial cable for it and might be able to use an adapter to connect it to my ThinkCentre M93p, but would prefer to avoid this if this extra work would be in vain.)

Any ideas?
19
Programming / PMPrintf package v2.80 and PMPrintf_abtrace code samples
« Last post by Andi B. on April 21, 2024, 07:43:39 pm »
I've packed together my latest code base of PMPrintf and packed it together as v2.80. See https://sourceforge.net/projects/pmprintf-os-2-debug-helper/files/

PMPrintf sends standard printf formatted debug messages into a queue. If the PM viewer application (PMPrintf.exe) or CLI logger (PmPfLog.exe) is running it will display these queued data. Otherwise they go to NULL. Log files can be written to disk in parallel too.

If you never used PMPrintf I strongly suggest looking at the code and usage samples at https://sourceforge.net/p/pmprintf-abtrace/code/ci/master/tree/. These samples loads pmprintf.dll dynamically if it is available on the target system. If not your program will normally run and your debug messages goes to NULL. There is no need to make extra release and debug builds. The small overhead will be negligible most of the time. A programmers life can be so easy :-).

Have fun.
20
Applications / Re: LarsenCommander - new test version
« Last post by Andi B. on April 21, 2024, 06:20:25 pm »
Oh, I never used these setting page by myself. In fact I took the usual OS/2 way - drag/drop a font from the font palette to the desired place. I think I remember all these dropped fonts (and colors, and background colors) are saved and restored. So I think you only have to drop your desired fonts on the different controls and you're done. Does this not work for your on one of the controls?

Though I for myself rarely had the need to change my fonts the last decade or so as I still use monitors with 94-105dpi (most of the time).



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