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 - Martin Iturbide

Pages: 1 2 [3] 4 5 ... 336
31
Internet / Re: otter-browser, Qt5 build
« on: March 30, 2025, 06:45:34 pm »
Hello Dave

Will it be ok if I upload Otter-Browser to Hobbes? I had repackaged it this way, with a little and very quick .txt file. What do you think?

Regards

32
Web applications / Re: OS2World URL Redirect
« on: March 29, 2025, 09:50:36 pm »
Hello Tom
Hello

Neil, today I talked to the webmaster and we have redirected the URLs.
Now if someones goes os2world.com  or www.os2world.com should get to the same site.

Can the same be done with EDM/2? I.e. edm2.com redirecting to www.edm2.com .

I will forward this request to Adrian (Netlabs). I don't have control over that server.

Also, just to let everybody know that I updated the EDM/2 wiki to the latest MediaWiki version in a local VM machine, and the updated database and files are now in the hands of Adrian. I hope he can get some time to put the EDM/2 files back in the server and connect the wiki to his LDAP.

Regards

33
General Discussion / Re: Brainstorm: What is Next with OS/2 ?
« on: March 28, 2025, 01:51:48 pm »

I still think that we are falling behind in applications. A modern web browser will help on that, since there are a lot of applications that are on the web without the need to install those, and on the other side compiling and porting applications are now starting to get complicated because of the 32bits/Memory limitation.

A Modern Browser and solving the memory limitations are getting more important for new apps.

Regards

34
General Discussion / Re: Brainstorm: What is Next with OS/2 ?
« on: March 28, 2025, 01:48:44 pm »
Hello

For the moment we have in no specific order:
1) Modern web browser
2) Wifi Driver.
3) Memory issues
4) IPv6.

And side discussion:
1) There is no need to worry because we have virtualization.
2) The dislike of RPM/YUM or FHS.

Regards

35
Hardware / Re: OpenWatcom Discussion
« on: March 28, 2025, 02:25:03 am »
Hello
As mentioned above, everyone will be confused now.

https://hobbesarchive.com/Home/Download?path=/Hobbes/pub/os2/dev/proglang/cpp/OpenWatcom_C_2-0-1.exe mentioned as Program Contact: David Azarewicz

Unfortunately we do not see who uploaded this. But as Steven mentioned above he and Gregg needed a repo we can only guess if David used these or any other source. I fear David uses his own different repo. But I don't know. We have to ask the unknown uploader or David
It is possible that I'm the uploader of that file, it has my file naming standard.
David has on his site (https://88watts.net/software.html) that file named "open-watcom-c-os2-2.0.1.exe" (18-Dec-2023), and this version is also referenced on "https://www.arcanoae.com/wiki/information-for-developers/"

Regards

36
Programming / Re: Brainstorm: OS/2 on a Different Kernel
« on: March 26, 2025, 05:47:36 pm »
The Presentation Manager would mean mapping PM windows to whatever Linux is using, X11 or Wayland. WPS might be the hardest to support.

How does PM connects to the OS/2 kernel currently? Because I would think that PM only goes through CPI to the kernel, and maybe some other DRIVER$, but the idea will be to make PM run through a different kernel and not necessary linking it to other GUI like X11 or Wayland yet. 

Regards

I don't really know but it has to connect to the video drivers to get access to the frame buffer to create the PM desktop and write/read the framebuffer. Doing things like seamless DOS/WinOS2 support must be tricky too and maybe kernel level.

On the very limited/little research I was able to do sometime ago, PMMERGE.DLL uses (or refers to) SINGLEQ$ and KBD$, so maybe SINGLEQ$ is also vital. But I got no reference to something related to video, maybe PMGPI.DLL has some connection to a DRIVER$ that I don't know.

Regards

37
General Discussion / Re: OS2World Site Update
« on: March 26, 2025, 01:42:09 pm »
Hello Remy

I think you found it.

Joomla let me create a "child" of the template that overrides the father, so I quickly put your template.css (I can also revert it very fast if there is some problem) and I think it worked. You are a genius :)
It works fine on Dooble Qt5, but not our old Firefox. But it is very good, it is a step forward.

Everybody, please test the site further, visit the pages and let me know.

Regards

38
Programming / Re: Brainstorm: OS/2 on a Different Kernel
« on: March 26, 2025, 01:10:19 pm »
The Presentation Manager would mean mapping PM windows to whatever Linux is using, X11 or Wayland. WPS might be the hardest to support.

How does PM connects to the OS/2 kernel currently? Because I would think that PM only goes through CPI to the kernel, and maybe some other DRIVER$, but the idea will be to make PM run through a different kernel and not necessary linking it to other GUI like X11 or Wayland yet. 

Regards

39
Programming / Brainstorm: OS/2 on a Different Kernel
« on: March 25, 2025, 11:32:20 pm »
Hello

I was wondering what would be required to run OS/2 over a different kernel.

Let’s theorize, what if we want to have PC that boots Linux, gets to the command line and run something like “startwarp” and the full OS/2 desktop will boot. (Command line, PM, SOM, WPS) and you can run your OS/2 applications there. (Not the 100% of OS/2 applications, but at least start with some)

What would be required to make the OS/2 binaries believe they are running over the OS/2 kernel to run interpretated and not emulating a x86 machine.

From my limited knowledge point of view will be required:

1.- OS2KRNL: The OS/2 kernel has everything that you need on an OS kernel to talk to the hardware, but those will not be necessary since the Linux kernel already does this with the hardware. What would be needed is a layer with all the functions that OS2KRNL provides to DOSCALL1.DLL …. I guess.
As far was a I know OS2KRNL provides a lot of DosXXXX functions to DOSCALL1.DLL. I’m guessing all of this needs to be cloned over Linux (maybe with libc/gcc) to make believe DOSCALL1.DLL that is talking to the kernel.

But I think I’m only talking about the API here, what about the memory management? Where it should go?

Does it make sense?

2.- MOUSE$, KBD$, SCREEN$, CLOCK$. As far as I know this are called “Character Device Drivers”. These are drivers that DOSCALL1.DLL and CPI uses. Here I don’t have the details on how these talks to the CPI. Some layer (DRIVER$ to Linux) to mimic the responses of these driver will be required.

There are a lot more for specific driver like USB, LTP, etc. are also required for software that communicates to hardware, but it had to start with the basic ones to first have a full OS/2 desktop and later improve it with better compatibility.

What would be the vital Character Device Drivers to start with?

Where can I found more information on how CLOCK$ (or any other interacts) with CPI or with any other software that requires it?

3.- Binary compatibility. I don’t know if its completely required that Linux has the “Linear Executable” layer like it was done on the 2ine project. But I think I’m missing this part. I guess that the OS2KRNL provides the instruction to let know that an ,exe file is a “Linear Executable” file, right? Where should that go if we are running a OS2KRNL faked in Linux?

Yes, I know that this theorical version of OS/2 will not be 100% compatible with all software, specially with the software that interacts with hardware. All device driver for OS/2 will be useless, and some new technique will need to be created to grab the Linux drivers and show it on the OS/2 environment (Ex: Linux Audio to UNIAUD1$ bridge). 16 bits may be broken and maybe not required today, VDM will be broken and there will be not full API compatibility first. A proof concept will have an awful compatibility first but it has the potential to grow if it’s open source and if people believe in this kind of long-term strategy.

This will not be easy, because it requires developers with OS/2 and Linux development knowledge to obtain at least a minimum of compatibility to make it usable.

Beside these three components that I theorize, what other thing will be missing to run an OS/2 desktop interpreted in Linux? What do you think? Please correct me where my interpretations of the OS/2 architecture are wrong.

Regards

40
General Discussion / Re: OS2World Site Update
« on: March 25, 2025, 01:55:32 pm »
Hello

Someone at the Joomla forum gave me hint, but still do know if that can be.
With the firefox inspector (on Windows) if I disable "<div class="site-grid">" I get the similar issue on Firefox for Windows. He told me that it is possible that the other browsers does not implement  "<div class="site-grid">"  correctly but I'm still not sure about it.

Regards 

41
Hello Andi B.
There are some bldlevel information when added to an .exe leads to strange things when the exe is loaded by OS/2. Although strictly correct regarding Stevens notes about bldlevel it's yet unknown why f.i. sometimes the menu is not loaded by OS/2. Or even worse some program refuses to start with some bldlevel information.

Summing up my experience with bldlevel infos I made with my projects, if the developer who extensively tests the program don't add a bldlevel info I wouldn't add it later. It may be dangerous and maybe more harm then help.
Thanks for the point of view and recommendation. It is a good warning and I will like to test what kind of program can provide problem to add the bldlevel information later. I will try some command line tools first and post back to see if we can get an issue.

Regards

42
No problem.

I just need to understand what should be on:
- Build Machine: Maybe I should put that on blank, since I don't know the build machine. But I don't know how to do that with AddToFile yet.
- ASD Feature ID: I don't know what is this.
- Fixpack: The OS/2-ArcaOS fixpack level? or I just leave it blank? I also don't know the fixpack level of the build machine.
- Date: I need to find how to put the older compile date with AddToFile and also try not to change the file date.

Regards

43
Hello again

For example, here I attach a file I changed with AddToFile.

I run:
- AddToFile.cmd aacgain.exe,option AAC file normalizer,BLDLEVEL,Glen Sawyer,1.9.0,AAC file normalizer,Fixpack,Asd

Quote
[C:\HOME\MARTIN\DOWNLOADS\AACGAIN-BLDLEVEL]bldlevel aacgain.exe
Build Level Display Facility Version 6.12.675 Sep 25 2001
(C) Copyright IBM Corporation 1993-2001
Signature:       @#Glen Sawyer:1.9.0#@##1## 23 Mar 2025 20:30:58     ARCAOSVM  :
Asd:::0::Fixpack@@AAC file normalizer'
Vendor:          Glen Sawyer
Revision:        1.09.0
Date/Time:       23 Mar 2025 20:30:58
Build Machine:   ARCAOSVM
ASD Feature ID:  Asd
FixPak Version:  Fixpack
File Version:    1.9
Description:     AAC file normalizer'

What I would like to do is to keep the same file date of the compile date. Any suggestions there?

Regards

44
Hi
You understand that you have to rebuild the binaries after patching the makefiles to use Addtofile? Also I just noticed the license doesn't allow hosting the script on any servers so it would have to be downloaded by anyone rebuilding the binary.
Other then that, adding bldlevel info seems a good idea.
I guess I didn't understand it right. I thought that "AddToFile" changed the .exe to include the bldlevel information, and that modified exe was going to be included on the RPM. I didn't know that the binary had to be rebuild. Or that every user had to download "AddToFile" for it to work.

Regards

45
Hello

Do you think it will be good to do an extra things to the executables? I noticed that a lot of the .exe and .dll does not has bldlevel information.
- Will be it be ok to add that information on the exe/dll using AddToFile ?
- would that violates the sacrosanctity of the binary :) ?
- or is it too much OCD ?

I know that it may only be a nice to have, but not completely necessary.

Regards

Pages: 1 2 [3] 4 5 ... 336