Recent Posts

Pages: [1] 2 3 ... 10
1
General Discussion / Re: OS/2 History Newsletters
« Last post by Martin Iturbide on May 01, 2024, 03:48:02 am »
Hello

The "Minnesota OS/2 Users Group Newsletter" is missing some issues.
Missing: Vol1 Number 1 to 4, V1N8, V2N5.

Regards
2
Applications / Re: 3270
« Last post by j on May 01, 2024, 03:32:29 am »
Thank you Neil!
3
Applications / Re: Nomacs Image Viewer
« Last post by roberto on April 30, 2024, 08:19:22 pm »
Hi Tellie,
When you left us the qt6 version, I installed it, and put the qt6core.dll in the same folder of the nomacs.
I ran it and it worked perfectly, and I looked at a lot of photos and a lot of folders.
But, days later I wanted to open it again and it closed, seconds after opening. With an error in exceptq.
Editing the profile, I saw a mega line of a length of approximately 1600 columns, created with the qt6
They were the paths of each photo.
With the epm I left the line at about 600 characters.
I tried on the QT5 version, and it worked perfectly.
I put it back with the QT6 version, and it still works perfectly.
My conclusion : To have a correct profile in Qt6, you first have to have it created in Qt5.
Saludos
4
Programming / Re: OpenDOC - Source Code
« Last post by Lars on April 30, 2024, 07:44:12 pm »
1) the Warp4 Toolkit (NOT the Warp 4.5 toolkit) came with a whole OpenDoc subdirectory, including all documentation (in HTML format)
2) there existed OpenDoc Version 1.2, multiple self-extracting installation executables. It is likely the same stuff as is contained in:
http://www.hobbesarchive.com/Home/Download?path=/Hobbes/pub/os2/dev/tools/toolkits/OpenDoc_1-2.zip
and it can also be found here:
https://www.adofai.gg/HOBBES/dev/opendoc/

I have both on CD-ROM.
5
Programming / Re: libALSA?
« Last post by Mentore on April 30, 2024, 10:11:26 am »
You will have to implement the audio yourself, e.g. you could use KAI.

I was thinking about something like that. BTW the emulator works perfectly, so I'll probably upload it without sound support.
Mentore
6
Programming / Re: libALSA?
« Last post by Jochen Schäfer on April 30, 2024, 09:47:08 am »
You will have to implement the audio yourself, e.g. you could use KAI.
7
Programming / libALSA?
« Last post by Mentore on April 30, 2024, 09:17:40 am »
Hello all,
I finally managed in setting up some projects on OS/2 - mainly focusing on emulatio.
As it seems, I have a QL Emulator under SDL/2 working - never happened before (there was UQLX but needed X11 and I never saw a working copy).

Now for the difficult part:
I'm working on a newer release of FBZX, a ZX Spectrum emulator I already ported before. It uses libpulse, OSS or libALSA for sound - and we don't have any of them.
As UNIAUD is based on ALSA, I'm wondering how difficult it may be to port libalsa under OS/2.
Thoughts, anyone? I'm pulling it from github right now.

Mentore
8
Programming / Re: OpenDOC - Source Code
« Last post by SoundChaser on April 30, 2024, 04:20:15 am »
A fair chunk of the Taligent C++ coding style ended up in the Open Class framework in VAC++4 which unfortunately is too much an esoteric environment to work with. I wonder if anyone tried to compile these modules with another compiler than IBM xlc (say MSFT cl.exe) which would have given a second life to that otherwise very interesting tech.

The book Taligent's guide to designing programs : well-mannered object-oriented design in C++ remains an excellent book.
9
Programming / Re: Any standard on exit codes?
« Last post by Dave Yeo on April 30, 2024, 01:26:36 am »
The "Control Programming Guide and Reference", installed by the toolkit as cp2.inf has a detailed list of error codes, about 64K different ones including reserved.
For GCC/Libc errors, see @unixroot/usr/include/sys/errno.h
10
Programming / Any standard on exit codes?
« Last post by Alfredo Fernández Díaz on April 30, 2024, 12:54:24 am »
Hi everyone,
I am writing a few tools that can report a number of different conditions, e.g. "target file does not exist," "file can't be read," "wrong file type," "parameter out of range," etc. While well-chosen error messages are the best you can give users, when tools are to be chained, it is better to pass along different numeric return codes. Now the question is, in order to cooperate most properly, every tool must know at least the error codes of the previous one, so I wondered whether we have any kind of standard or guidelines regarding this, instead of having a plethora of necessarily arbitrary values.
Thank you in advance.
Pages: [1] 2 3 ... 10