OS2 World Community Forum

OS/2, eCS & ArcaOS - Technical => Applications => Topic started by: Martin Iturbide on January 28, 2016, 04:24:16 pm

Title: Experiment: cWarp - Crappy Warp / Changing the stuff.
Post by: Martin Iturbide on January 28, 2016, 04:24:16 pm
Hi

As the next step of my older experiment (bWarp (http://www.os2world.com/forum/index.php/topic,841.msg8042.html#msg8042)) I created cWarp.

The goal of this experiment was to remove IBM's OS/2 components based on what is available for free and/or open source. 

The goal remains to have:

- Boot the OS
- Run PM and WPS (so SOM is still there)
- Run cmd and PM applications
- Ability to run REXX scripts
- DHCP working
- Ping google.com
- CD/DVD Support
- JFS / HPFS Support (ok JFS is not that solid now)
- E.EXE is still there.

You can found information about this experiment at:
- cWarp (http://www.os2world.com/wiki/index.php/CWarp)
- cWarp Directory/Files Structure (http://www.os2world.com/wiki/index.php/CWarp_Directory/Files_Structure)
- cWarp Config.sys (http://www.os2world.com/wiki/index.php/CWarp_Config.sys)

For the moment it is working, it is broken of course, there are things that are not running. But PM apps, Qt Apps, Rexx scripts are running. Yum runs and installs the software on C:\Programs\FHS\. Of course that somethings are very broken (http://www.os2world.com/wiki/index.php/CWarp_Broken_Things).

I focused on leaving all the IBM's Binaries on \OS2 (Expect of the Kernel), every replacement I was able to find (and that is allowed to be moved) was located on \WARP. 

So I'm looking for any replacement of this files: Required Replacements (http://www.os2world.com/wiki/index.php/Required_Replacements)
Any way to help me with the files that are not marked, or marked in white are welcome. I want to keep experimenting how much can be replaced.

Regards
Title: Re: Experiment: cWarp - Crappy Warp / Changing the stuff.
Post by: Wim Brul on January 29, 2016, 10:58:12 am
Quote
Issue #5 - ObjectRexx Programs broken
SockLoadFuncs seems to be part of ObjectREXX which was removed since BWarp.
You need RXSOCK.DLL for REXX Socket Support.
Title: Re: Experiment: cWarp - Crappy Warp / Changing the stuff.
Post by: Jan-Erik Lärka on January 29, 2016, 11:23:21 am
Issue #4
rexxqueue is a separate application that many rexx scripts use to capture output (stdout/stderr) from textmode applications.
You can find code for it here and build it with OpenWatcom.

https://fossies.org/dox/ooRexx-4.2.0-source/rxqueue_8cpp_source.html
Title: Re: Experiment: cWarp - Crappy Warp / Changing the stuff.
Post by: Martin Iturbide on January 29, 2016, 03:42:21 pm
Thanks for the tips and the links.

I had recovered the RXSOCK.DLL and RXQUEUE.EXE files.

ArcView works now, it gives other error on the VX-REXX console (check picture), but the unzipping is working.

ANPM is also working, it is giving me an error suggesting me to change the LIBPATH order, I had set Yes and reboot. But on the next reboot it asks me for the same thing. I just press "no" and it works. It seems to be installing fine for the moment.

If someone will ever like to generate a RXSOCK.DLL (https://fossies.org/dox/ooRexx-4.2.0-source/rxsock_8cpp.html) and RXQUEUE.EXE (https://fossies.org/dox/ooRexx-4.2.0-source/rxqueue_8cpp_source.html) from the Open Object Rexx code I will try it out on cWarp just for fun :)

Regards
Title: Re: Experiment: cWarp - Crappy Warp / Changing the stuff.
Post by: Doug Bissett on January 29, 2016, 04:26:30 pm
Quote
ANPM is also working, it is giving me an error suggesting me to change the LIBPATH order

This is not an error. It is a suggestion, for those who want it to work properly. If you go to View-> Preferences, there is a setting to Skip the path validation. That is meant for those who really know what they are doing (developers), but it would stop the message from popping up. Whether you will see other problems from moving the directory remains to be seen (you may not even know that it is not working properly).
Title: Re: Experiment: cWarp - Crappy Warp / Changing the stuff.
Post by: Martin Iturbide on January 29, 2016, 06:54:17 pm
If you go to View-> Preferences, there is a setting to Skip the path validation...

Thanks Doug for that.

I'm also trying to find out more about the \CODEPAGE\ files. Checking the files that I have maintained from OS/2 (http://www.os2world.com/wiki/index.php/Required_Replacements) I'm still do know much about those files: IBM1004, IBM1006.... and so on.

Any idea on how those files are generated on OS/2?

Any pointer to any other file on this list (http://www.os2world.com/wiki/index.php/Required_Replacements) that had been already replaced is welcome.

Regards
Title: Re: Experiment: cWarp - Crappy Warp / Changing the stuff.
Post by: Martin Iturbide on February 04, 2016, 01:02:10 pm
Hi

I will also appreciate if someone can compile me some version of IBMKBD.SYS , SCREEN01.SYS and TIMER0.SYS that is on IBM DDK. I don't care if those are the latest level, I only want to try it on this experiment.

Regards
Title: Re: Experiment: cWarp - Crappy Warp / Changing the stuff.
Post by: Wim Brul on February 12, 2016, 04:30:09 pm
Quote
I will also appreciate if someone can compile me some version of IBMKBD.SYS , SCREEN01.SYS and TIMER0.SYS that is on IBM DDK. I don't care if those are the latest level, I only want to try it on this experiment.

I only have the IBM DDK source of IBMKBD.SYS that I downloaded way back from their website. ;) Here it is.
Title: Re: Experiment: cWarp - Crappy Warp / Changing the stuff.
Post by: Martin Iturbide on February 12, 2016, 05:10:28 pm
Thanks Wim. It worked great on the cWarp experimental VM.

Regards
Title: Re: Experiment: cWarp - Crappy Warp / Changing the stuff.
Post by: Martin Iturbide on February 15, 2016, 06:43:55 pm
Hi

I want to see if I can replace KEYBOARD.DCP. It seems that some replacements was done on the past and there is even this article "KEYBOARD.DCP File Format (http://www.edm2.com/index.php/KEYBOARD.DCP_File_Format)" (which I don't understand much since I don't code), but it will be interesting to know if there are some source code or binaries released about this "Keyboard layout file".

For the moment I don't have any source code or non-IBM binary of it.

Regards
Title: Re: Experiment: cWarp - Crappy Warp / Changing the stuff.
Post by: Wim Brul on February 17, 2016, 10:57:33 am
Hi Martin,

Just for fun I created a.o. replacements of bkscalls.dll and kbdcalls.dll with source code.
These now show their fully qualified drive, path, filename and extension at boot up.

Regards, Wim.
Title: Re: Experiment: cWarp - Crappy Warp / Changing the stuff.
Post by: mike on February 23, 2016, 08:30:09 pm
Just for fun I created a.o. replacements of bkscalls.dll and kbdcalls.dll with source code.

Wim = hero  ;)
Has this some relation to the console API?
Title: Re: Experiment: cWarp - Crappy Warp / Changing the stuff.
Post by: Martin Iturbide on February 24, 2016, 03:10:48 am
Hi Mike

I can not say I know exactly about those files. I just documented what I was able to find on the EDM/2.

* KBDCALLS.DLL (http://www.edm2.com/index.php/KBDCALLS.DLL)    - Keyboards calls dynamic link library.
* BKSCALLS.DLL (http://www.edm2.com/index.php/BKSCALLS.DLL) - Base keyboard calls.

If someone wants to add more to the EDM/2 wiki or make a correction is welcome.

Regards
Title: Re: Experiment: cWarp - Crappy Warp / Changing the stuff.
Post by: Wim Brul on February 24, 2016, 07:15:30 pm
I want to see if I can replace KEYBOARD.DCP. It seems that some replacements was done on the past and there is even this article "KEYBOARD.DCP File Format (http://www.edm2.com/index.php/KEYBOARD.DCP_File_Format)" (which I don't understand much since I don't code), but it will be interesting to know if there are some source code or binaries released about this "Keyboard layout file".

For the moment I don't have any source code or non-IBM binary of it.

I have attached a replacement for keyboard.dcp with free source code.
Supports code pages 437 and 850 and the "US 103" and "BR 274" languages.
Best suited :) for crappy warp I think. Have fun.
Title: Re: Experiment: cWarp - Crappy Warp / Changing the stuff.
Post by: Wim Brul on February 24, 2016, 07:32:19 pm
Just for fun I created a.o. replacements of bkscalls.dll and kbdcalls.dll with source code.

Wim = hero  ;)

Being called a hero, I better supply the other replacements that I created.
wmbmou00.zip contains bmscalls.dll and moucalls.dll with source code.
wmbvio00.zip contains bvscalls.dll and viocalls.dll with source code.
Title: Re: Experiment: cWarp - Crappy Warp / Changing the stuff.
Post by: Martin Iturbide on February 24, 2016, 09:34:01 pm
Thanks Wim

I replaced Keyboard.dcp and the English keyboard is working without any issues, which is good enough for this experiment.

Thanks for the source code, it can also "add up" to the community collective knowledge to know more about OS/2 files. I will be adding some pointers on the EDM/2.

Regards

Title: Re: Experiment: cWarp - Crappy Warp / Changing the stuff.
Post by: Martin Iturbide on February 24, 2016, 09:36:46 pm
Hi

By the way. I will be also happy to know which of the files of this list (http://www.os2world.com/wiki/index.php/Required_Replacements) can be easy replaced. Just to continue this experiment.

Regards
Title: Re: Experiment: cWarp - Crappy Warp / Changing the stuff.
Post by: Wim Brul on February 29, 2016, 05:49:10 pm
Thanks Wim

I replaced Keyboard.dcp and the English keyboard is working without any issues, which is good enough for this experiment.

Thanks for the source code, it can also "add up" to the community collective knowledge to know more about OS/2 files. I will be adding some pointers on the EDM/2.

Regards

Hi Martin,

With wmbkbd02.zip you can not use the three so-called window keys and some of the multimedia keys. With wmbkbd03.zip their scancodes are available and functions can therefore be assigned to a.o. the User (Moon) and E-Mail buttons.

Good to have pointers on the EDM/2. 

Regards, Wim.
Title: Re: Experiment: cWarp - Crappy Warp / Changing the stuff.
Post by: arr531 on March 01, 2016, 01:08:28 am
A very interesting experiment Martin. Did you consider using Jonathan De Boyne Pollard's 32 bit command interpreter and his command line utilities. It would be interesting to see how it runs in a VM and with QSInit. just for kicks.
Title: Re: Experiment: cWarp - Crappy Warp / Changing the stuff.
Post by: Martin Iturbide on March 01, 2016, 04:30:49 pm
Hi Wim. Thanks I'm tryinng it on the cWarp experiment.

Hi adan. I haven't tried Jonathan de Boyne Pollard command line tools on cWarp. The good thing is that I found some open source command line tools replacements from OSFree, which I'm using on the experiment. But I will check Jonathans tools.

Regards
Title: Re: Experiment: cWarp - Crappy Warp / Changing the stuff.
Post by: Wim Brul on March 08, 2016, 11:22:10 am
I will be also happy to know which of the files of this list (http://www.os2world.com/wiki/index.php/Required_Replacements) can be easy replaced. Just to continue this experiment.

Hi Martin,

I have attached a replacement for country.sys with free source code. Supports Ecuador (country code 593 with code pages 850 and 437), Netherlands (country code 31 with code pages 850 and 437) and United States (country code 1 with code pages 850 and 437).

Regards.
Title: Re: Experiment: cWarp - Crappy Warp / Changing the stuff.
Post by: Martin Iturbide on March 08, 2016, 04:46:18 pm
Thanks Wim.
You made my day.

It worked on cWarp, I'm loading it as:

Code: [Select]
CODEPAGE=437,850
COUNTRY=001,C:\WARP\DRIVERS\COUNTRY.SYS

It is working. Nothing that boots on cWarp complains about it. Keyboard is still working fine.

Thanks a lot.

Regards
Title: Re: Experiment: cWarp - Crappy Warp / Changing the stuff.
Post by: Martin Iturbide on March 22, 2016, 02:39:03 pm
Hi

I will apreciate if someone with the IBM DDK can generate some binaries to test it on cWarp. I really do not care if those are from an older version, I just need them to be freeware for my experiment.

According to what I had researched SCREEN01.SYS , TIMER0.SYS, TESTCFG.SYS source code is on IBM DKK, if someone has sometime to compile those and send it over me (binaries only) I will apreciate it.

Regards
Title: Re: Experiment: cWarp - Crappy Warp / Changing the stuff.
Post by: Wim Brul on March 27, 2016, 06:32:22 pm
Hi Martin,

I have attached a replacement for viotbl.dcp with free source code. Supports code pages 437 and 850.
I used the Display Font Editer for OS/2 v0.02 (pmfoed002a.zip on hobbes) to edit the fonts.

Regards.
Title: Re: Experiment: cWarp - Crappy Warp / Changing the stuff.
Post by: Martin Iturbide on March 28, 2016, 01:45:04 pm
Hi Wim

Thank you very much. I will be trying it on my experiment.

Just one thing to confirm, are the .rom of your files the fonts?

Regards
Title: Re: Experiment: cWarp - Crappy Warp / Changing the stuff.
Post by: Wim Brul on March 28, 2016, 03:43:20 pm
Quote
Just one thing to confirm, are the .rom of your files the fonts?

Yes . When you run vio593.cmd then it invokes vio593.exe which in turn will read the six cp*.rom files and write the resultant vio593ec.dcp file. The content of the cp*.rom files is used unchanged and the added header data defines these as the 8*8, 8*14, 9*14, 8*16, 9*16 fonts for code pages 437 and 850.

cp437cga.rom and cp850cga.rom contain 8*8 rom fonts (like from a cga adapter).
cp437ega.rom and cp850ega.rom contain 8*14 rom fonts (like from a ega adapter).
cp437vga.rom and cp850vga.rom contain 8*16 rom fonts (like from a vga adapter).
Title: Re: Experiment: cWarp - Crappy Warp / Changing the stuff.
Post by: Martin Iturbide on March 28, 2016, 07:59:26 pm
Thanks Wim.

I just replaced it on the cWarp experiment and it didn't break anything.
The only change that I noticed is that the fonts looks different on the messages when it boots, but "different good".

Regards
Title: Re: Experiment: cWarp - Crappy Warp / Changing the stuff.
Post by: Wim Brul on March 31, 2016, 12:30:27 pm
Hi Martin,

I have attached a stub replacement for isapnp.snp and pnp.sys with free source code.

Code: [Select]
copy pnp593ec.sys c:\os2\boot\isapnp.snp
copy pnp593ec.sys c:\os2\boot\pnp.sys

Regards.
Title: Re: Experiment: cWarp - Crappy Warp / Changing the stuff.
Post by: Martin Iturbide on March 31, 2016, 02:08:17 pm
Wow, thanks a lot.

Is it the same file (isapnp.sys and pnp.sys) that just need to be renamed?

I will be trying it. 

Thanks.
Title: Re: Experiment: cWarp - Crappy Warp / Changing the stuff.
Post by: Wim Brul on March 31, 2016, 05:40:26 pm
Quote
Is it the same file (isapnp.sys and pnp.sys) that just need to be renamed?

Both isapnp.snp and pnp.sys need to be replaced by the very same pnp593ec.sys file.

The Hardware Manager under "ISA_Bus" will no longer show the "PnP Isolation/Detection Driver".
See the PnP Basics (http://www.edm2.com/index.php/Writing_Device_Drivers_-_Plug_and_Play_Basics) article on EDM/2 for more information about the PnP i/o ports.
Title: Re: Experiment: cWarp - Crappy Warp / Changing the stuff.
Post by: Martin Iturbide on March 31, 2016, 11:38:18 pm
Hi

I just tried it out. I replaced PNP.SYS and ISAPNP.SNP with your file and cWarp keeps booting fine on the Virtual Machine.

Thanks a lot.

Title: Re: Experiment: cWarp - Crappy Warp / Changing the stuff.
Post by: Martin Iturbide on April 14, 2016, 04:01:41 pm
Hi

Yesterday someone made me remember that we already have an open source REXXUTIL.DLL replacement. I even uploaded it to github some time ago but I forgot about it.

I had replaced it on cWarp without any issues and I marked it as green on my "Required Replacements (http://www.os2world.com/wiki/index.php/Required_Replacements)" page.

I'm still looking for someone to compile SCREEN01.SYS, TIMER0.SYS and TESTCFG.SYS from teh IBM DDK. No matter if it is backlevel, it is just for the experiment.

Regards
Title: Re: Experiment: cWarp - Crappy Warp / Changing the stuff.
Post by: Wim Brul on April 24, 2016, 04:25:56 pm
Hi Martin,

Quote
I'm still looking for someone to compile SCREEN01.SYS, TIMER0.SYS and TESTCFG.SYS from the IBM DDK. No matter if it is backlevel, it is just for the experiment.

I don't have the source code for these drivers, but writing my own testcfg.sys was possible.
I have attached a minimal replacement for testcfg.sys with free source code. It only supports:
Generic IOCtl Category 80h, Function 40h - Obtain a Copy of BIOS/Adapter Memory.

Regards,

Wim
Title: Re: Experiment: cWarp - Crappy Warp / Changing the stuff.
Post by: Jan-Erik Lärka on April 26, 2016, 11:44:36 am
Martin, the rexxutil.dll is older and crippled.

It's a problem to use old and obsolete code as it is severely limited in use and function.

it would take many man hours to rewrite only that, to reach even the current level, even more for the OS itself.
One should negotiate with the one that "own" OS/2 object rexx and get the parts that differ from the ones that was open sourced to rexxla.org and incorporate their improvements.
Title: Re: Experiment: cWarp - Crappy Warp / Changing the stuff.
Post by: Martin Iturbide on April 26, 2016, 02:34:14 pm
Thanks Wim

I will be trying that file on the experiment.

Regards
Title: Re: Experiment: cWarp - Crappy Warp / Changing the stuff.
Post by: Martin Iturbide on April 26, 2016, 02:59:29 pm
Hi Jan-Erik.

This experiment it is not about functionality, it is more about replacing components to have a "set of basic functionality" with replacements.

Martin, the rexxutil.dll is older and crippled.
Do you mean the Open Source REXXUTIL.DLL clone? Maybe it is crippled since I don't know it in detail since I don't have experience with REXX. But I can not agree it is older. From what I see on the binaries IBM REXXUTIL.DLL is from "9-06-2000 12:42    1999.518152034    68,119 bytes" while OSS Clone REXXUTIL.DLL is "3-06-2008 9:40p    2.10.1    68,482 bytes" (Source (http://www.edm2.com/index.php/REXXUTIL.DLL)) If there is a newer IBM REXXUTIL.DLL let me know so I can update the EDM/2 wiki.

For me is as basic as "Good close source/abandonware software can not be improved. Bad open source software can be improved."

One should negotiate with the one that "own" OS/2 object rexx and get the parts that differ from the ones that was open sourced to rexxla.org and incorporate their improvements.

The one that owns OS/2 Object REXX is IBM, they are not currently releasing any source code from OS/2. If you know the person in charge of Object REXX that has contacts within IBM maybe I can talk to him, but for the moment I don't have faith on IBM releasing source code.

Setting away the topic from my cWarp experiment. My person opinion (which can be discussed on other thread) is to start moving to REGINA REXX slowly. Let's migrate any script that is currently used in REXX and that can be moved to REGINA without too much trouble now, and lets grow the Regina interest. From other discussion that we had (2014 - Regina REXX vs. OS/2 REXX (http://www.os2world.com/forum/index.php/topic,534.msg4999.html#msg4999)) we have the following challenges with REGINA:

1) All the OS/2 REXX scripts should need to be adapted for Regina.
2) Every app in "Object REXX" will fail running over Regina. Plus we don't have "Open Object Rexx" ported.
3) While OS/2 REXX is integrated with the os, Regina is a separate executable. A better integration needs to be created.

I know this is the area of "Fixing what is not broken" and people are scared to comment or try, but again, I prefer bad open source code over good abandonware. (personal taste).  I think it can be great if someone can take the REGINA Flag inside the OS/2 community and start doing experiments and try different things.

Regards
Title: Re: Experiment: cWarp - Crappy Warp / Changing the stuff.
Post by: Martin Iturbide on April 28, 2016, 06:53:45 pm
Thanks Wim.

cWarp keeps booting with your experimental TESTCFG.SYS. I updated my list of "Required Replacements (http://www.os2world.com/wiki/index.php/Required_Replacements)" and also uploaded your code to GitHub (https://github.com/OS2World/SYSTEM-DRV-Wims_Experimental_Files).

Regards.
Title: Re: Experiment: cWarp - Crappy Warp / Changing the stuff.
Post by: Martin Iturbide on October 17, 2016, 02:49:00 pm
Hi.

I would like to find out more about "PMMRGRES.DLL (http://www.edm2.com/index.php/PMMRGRES.DLL)". I want to know if this file can be generated from other ways, or if there is any replacements available, or at least try to document what it has inside.

Regards