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 - Valery Sedletski

Pages: 1 [2] 3 4

> I wonder if this FreeLOADER file could be assumed as being legal Software.

Why not legal? It is based on GRUB, indeed, under GPL license, in fact. I wrote it for osFree project, and use for universal bootable CD/flash/etc. It can be used as a boot CD or maintenance system, booted from a hard disk too. Or, as a live OS/2 system.

PS: Which error in fat32 driver, btw?

Off Topic discussions / Re: Genode OS Framework version 17.02
« on: March 02, 2017, 11:12:53 pm »
The Muen separation kernel is one of the target kernels. Genode itself is C++.

Article Discussions / Re: OS/2 Books Fans?
« on: March 02, 2017, 07:08:48 am »

Applications / Re: Regina REXX vs. OS/2 REXX
« on: March 02, 2017, 06:57:44 am »
2Martin: I don't know exactly the list of functions, but it can be determined if we'll add a debug log for rexx.dll and rexxapi.dll, so we can see, which functions it calls. The full list of functions in REXX.DLL is here: and for REXXAPI.DLL: Involved here are SOM functions, so that WPS uses REXX for scripting (to register/deregister WPS classes).

Article Discussions / Re: OS/2 Books Fans?
« on: February 28, 2017, 08:46:56 am »
I have apibas,inf and kdebug.inf

Applications / Re: Regina REXX vs. OS/2 REXX
« on: February 26, 2017, 06:25:58 am »
Hi all. I am working on Regina REXX integration for OS/2 in osFree project. Indeed, the REXX.DLL and REXXAPI.DLL were existed in Regina code, but they were incomplete. Also, we in osFree had our own DLL's as forwarders to REGINA.DLL, so that, you can load REXX.DLL (the interpreter itself) and use it without specifying REGINA.EXE before each script. -- You just run .cmd file and CMD.EXE passes it to REXX interpreter. But there is a problem: CMD.EXE is a 16-bit program, so it uses 16-bit REXX functions in REXX.DLL and REXXAPI.DLL, instead of 32-bit ones. But 16-bit functions were missing, as Regina is a pure 32-bit program. But, using Regina via REXX.DLL/REXXAPI.DLL is working with 32-bit shells like 4OS2. So that, Regina REXX is working with 32-bit programs, but does not work with 16-bit programs. Most notable 16-bit ones are CMD.EXE and WPS (yes, it is, for some reason, using 16-bit functions, not the 32-bit ones). So, if you install our REXX and REXXAPI, WPS won't work too and OS/2 will not start. We extended REXX.DLL and REXXAPI.DLL with some 16-bit functions as wrappers around 32-bit Regina functions, and 32-bit wrappers for CMD.EXE 16-bit subcommand handlers. So, some 16-bit programs began to work. For example, rexxtry.cmd when run in cmd.exe, and executing "CLS" command of CMD.EXE (a 16-bit subcommand handler). But another problem exists. Usually, REXX.DLL is loaded by REXXINIT.DLL, which is, in turn, loaded by PM, and keeps it loaded. REXXINIT.DLL starts thread, which listens a message queue, and  serializes access from applications to REXX.DLL. So, there's another problem: Regina for now works with only one application at one time. So, we can start only one Regina client at one time. So, we need somehow serialize access to regina.dll in rexx.dll. This has to be done, too.

Also, i should note that switchrx.cmd works by swapping different versions of REXX.DLL (the interpreter) and REXXAPI.DLL (the API for extending other programs by REXX). Other DLL's are mostly usable for different interpreters. For example, REXXUTIL from Object REXX can be used with Classic REXX without problems. It has more functions implemented. Also, except for IBM's versions of REXXUTIL, exists WINDOWS version of REXXUTIL (it seems, it is called REGUTIL and is used by Regina too). But we also have two other native OS/2 REXXUTIL versions, with source code available, the one written by Mike Greene and the one supplied with eComstation.

Actually, for switching different REXX interpreters, we can suggest to rename other REXX/REXXAPI versions to CREXX/CREXXAPI and OREXX/OREXXAPI, and RREXX/RREXXAPI and make a wrapper REXX/REXXAPI with a config file, which will specify, which pair of REXX DLL's to use. I also plan to implement this in the future. This will allow to switch different interpreters without a reboot.

Making more 16-bit wrappers for regina.dll entry points will make CMD.EXE and WPS work with Regina. So, we need to finish it too.

I added your notes about missing Regina features to our bugtracker:

And yes, to test our Regina REXX version, You'll need to start runworkplace=d:\os2\cmd.exe instead of d:\os2\pmshell.exe in config.sys. This will start cmd.exe instead of WPS. As we know, WPS requires more 16-bit API's implemented, and may use REXX/REXXAPI from multiple threads. So, WPS needs to be disabled. Then you can run a REXX program in cmd.exe. (This is needed temporarily, because many features are unimplemented)

Setup & Installation / Re: Question about OS/2 3.5 floppy image files
« on: February 25, 2017, 11:45:57 pm »
Physical floppy discs only under Windows hosts afaik.

And OS/2 VBox host now supports physical floppies. The only problem for now that it is now not very stable and slow.

Applications / Re: Vbox5.06 beta
« on: January 10, 2017, 05:02:22 am »
But you can attach USB mouse or USB harddisk to a VM (you only need to add an USB controller to Storage section, and attach a .vdi to it).

??? Why would anybody want to do that? I  can see that USB 3.1 will end up replacing SATA, in the near future, simply because it is cheaper, but it is also FASTER. But doing that In a VM doesn't make sense, at this time.

Just to give an USB controller to a guest OS? VBox is needed not only for you to see your physical USB flash formatted with an exotic filesystem. It is used by developers for testing different configurations in VM's. At least, I sometimes need to test booting OS/2 from USB controller. It is different from a SATA controller from OS' point of view.

PPS: Also, no need to disable sound, as it uses Null audio drier. So, guests will see the audio card, but the sound will be not output. It should not affect the performance.

Well, that is clearly WRONG. When I enable sound, the performance is definitely much slower than without it. 

You seem to be wrong here. I doubt that enabling sound could eat up significant resources.

Perhaps that is because I use the SoundBlaster option, which works a LOT better under win 10.

You can try HDA or AC97 too, but not sure if it will help.

Applications / Re: Vbox5.06 beta
« on: January 10, 2017, 03:25:10 am »
2 ivan and Doug: Regarding the VBox speed, I see winxp guest is reasonably fast (I even thought, it flies for me). Also, as rklipp notes, we're working on VT-x/AMD-V support, and with it, it is even quicker. Regarding the Additions ISO, you just need to choose Devices->Attach the guest OS Additions ISO image, then agree to download it. It take some time to download it. Also, you can download it manually from (the link to Addition ISO is also on the VBox Netlabs page at, near the last release link).  And then you can put it in the VBox main directory. It should be called VBoxGuestAdditions.iso to be found. (Upd: It downloads it somewhere, but not to the program dir, and in the end the VM crashes. Need to fix that.)

PS: USB 2.0 and 3.0 is available only in commercial version (they require a commercial extpack to be installed, which is not available for OS/2, yet (maybe, in future)). USB 1.0 (OHCI) should work, but raw USB device passthrough is not ready, yet. But you can attach USB mouse or USB harddisk to a VM (you only need to add an USB controller to Storage section, and attach a .vdi to it).

PPS: Also, no need to disable sound, as it uses Null audio driver. So, guests will see the audio card, but the sound will be not output. It should not affect the performance.

Programming / Re: OpenWatcom & GCC
« on: December 09, 2016, 11:47:54 pm »
2Dave Yeo: You need to specify the correct GCC function prototype in Watcom source header, with correct calling convention. GCC is mostly using __cdecl and Watcom expects  __watcall by default. So, you need to specify __cdecl explicitly in prototypes.

Applications / Re: Vbox5.06 beta
« on: November 21, 2016, 03:01:26 am »
2Dave Yeo: It works just fine for me without idl20.dll. The VM is created and started successfully. I don't understood, what is this Guru Meditation about? What you did, exactly? Did you disabled VT-x first?

Applications / Re: Vbox5.06 beta
« on: November 19, 2016, 02:21:57 am »
2pete: Seems so. There's a single "curl" package, but no "libcurl".

I am not sure, but maybe, M$ changed .vhd format, since that. Also, as far as I know, splitting .vhd's to 2GB chunks is an optional feature. OS/2 version of VPC splits them for HPFS compatibility only. But this is not required. VBox seems to not understand splitted .vhd's. It needs them in one piece. Also, I see a 3 GB .vhd in my VM images directory. I took it from OS/2 version of VPC, and I used it with VBox, it had understood it well, and resized to 3 GB successfully, IIRC.  Or, I used that 3 GB .vhd with qemu, not VBox -- don't remember.

Applications / Re: VirtualBox 5.0.6 First Impressions
« on: November 19, 2016, 02:06:03 am »
2roberto: And? What this has to do with Watchcat? And what this has to do with VBox?

Applications / Re: VirtualBox 5.0.6 First Impressions
« on: November 17, 2016, 12:44:12 am »
2Andreas Kohl: It depends on the OS in the VM. Some OS'es setup, like OS/2, don't depend on the host processor, but some of them do (WinXP installs a HAL and kernel based on current CPU). Knoppix (a Debian Linux live CD) is not independent of the current CPU too. I copied VM's with OS/2 and ReactOS between OS/2/Linux/WinXP without any problems.

Pages: 1 [2] 3 4