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 ... 4 5 [6] 7 8 ... 24
wrc should be version from the yum repository, not from your version of OpenWatcom. You should install gcc-wrc. Please install all
build time dependencies from here:

iasl  vboxtools\os2x86\bin\iasl.exe   (533548)

What is 533548? This does not seem to be a valid date. I'm using the version


It is in my d:\ecs\bin directory. I can share it with you if you need. It should be on PATH when you're running configure.

Kbuild: Linking VBoxPython2_7
weakld error: Unresolved symbol (UNDEF)  '_yydebug'.
The symbol is rferenced by-.

I have no out\os2-x86\release\object\VboxDTraceCmd\src\VBox\ExtPacks\VBoxDtrace\generated\ directory in my
build at all. What is your kBuild version BTW? Mine is:

kmk -v

kmk - kBuild version 0.1.9998 (r118688303)
Built Jul 26 2017 20:41:48

Something is wrong in your environment.

2rklipp: Can you show which "rc" and "iasl" versions do you have? What "which wrc", "which  iasl" commands say? Start them and show
which versions they show?

2R.M. Klippstein: I'm compiling with both MCP2 and eCS 2.2, and I see no problems. VBoxACPI -- what do you mean? IASL errors?
RC error? Hm. Is it somewhere complained about that error already? I don't remember what's the problem already. A week ago,
I compiled the VBox sources in eCS 2.2 VM under Linux host -- no problems, all build time dependencies were the latest from the Netlabs-exp
repository. I don't have ArcaOS, so no idea. Maybe, you're using Netlabs-rel?

PS: in r199, only Additions were updated, so you'll not get any advantages compiling all VBox sources.

It is ramboot for being independent from a file system from which it is booting. All files are located on an on-disk file system. Only a minumum number of files load from ramdisk. So, it is a full OS/2 installation. Though, it is stripped-down a bit, to fit to 300 MB. But I have a full-fledged OS/2 on a flash stick too, so you can enhance it if you wish. For details, read readme.eng file.

2Rich Walsh: My most used plugins for Netdrive are FTP and ISOFS plugins. I have no SMB shares in my flat, so
nothing to test on. At least, when FTP plugin is active, It shows 0 in DosFindFirst. Also, I checked ISOFS plugin,
it shows 0 too.

2Rich Walsh:
Yes,  indeed. I created the test example for DosFindFirst, and now see that different IFS'es return the following results:

HPFS - 4
JFS - 0
FAT32 - 0
CDFS - 4
NDFS32 - 0

So yes, original IBM's IFS-es return 4, you're right

2Rich Walsh & Lars Erdmann:

vboxfs.ifs was created looking at fat32.ifs and ramfs.ifs. So, they should behave similar way. Looking at fat32.ifs, I see:
1) In FS_PATHINFO and FS_FILEINFO: filestatus.cbList = sizeof(filestatus.cbList); (i.e., 4 for one ULONG).
2) In FS_FINDFIRST worker,

Code: ("C") [Select]
                     if (!f32Parms.fEAS || !HAS_EAS( pDir->fEAS ))
                        /* HACK: what we need to return here
                           is the FEALIST size of the list
                           that would be produced by usGetEmptyEAs !
                           for the time being: just tell the user
                           to allocate some reasonably sized amount of memory
                        pfFind->cbList = 0;
                        rc = usGetEASize(pVolInfo, pFindInfo->pInfo->rgClusters[0], NULL,
                                         szLongName, &pfFind->cbList);
                        if (rc)
                           /* HACK: what we need to return here
                              is the FEALIST size of the list
                              that would be produced by usGetEmptyEAs !
                              for the time being: just tell the user
                              to allocate some reasonably sized amount of memory
                           pfFind->cbList = 0;
                        rc = 0;

so, in absence of EA's, it returns cbList = 0; Yes, I looked primarily at FS_FINDFIRST. Rich, you seem to be right.
At least, FS_FILEINFO and FS_PATHINFO do thye same.

    So, the problem is with something other.

That may be true, but returning 0 in cblist is still incorrect. Write a simple test program and point it to a file on a JFS, HPFS, or even FAT drive to confirm this. BTW... AN's version of FAT32 also returns 4.

Yes, but the error occurs when FS_FINDFIRST (but not FS_FILEINFO / FS_PATHINFO) is called. It returns 0 in cbList in both vboxfs.ifs and fat32.ifs. Though, I see no problems at all
with fat32.ifs.

Quote from: mauro
Now, since I like very much  systems on a self-bootable USB stick, and also said that OS2 W4 cannot support itself such capability, I created a self-bootable fully installed Ubuntu 18.04 USB stick, and setted an autostart command for the OS2 Warp 4.5 guest machine (updated as above described) cloned and moved from the initial Win10 host system to the Linux VirtualBox application there.

OS/2 can boot from a flash stick. For that, I created the Universal OS/2 Boot disk (based on my FreeLDR bootloader). It can boot from any medium,
like CD, flash stick or a partition on a hard disk. It is available from here: (the latest version is from Oct 21, 2016).

The disk exists for about 10 years. For installing onto the CD disk, you need to create an ISO image (just start tools/rambtcd.cmd script. Mkisofs
is included). To boot from a flash stick, or a hard disk partition, you need to copy contents of the ZIP archive to the root directory, and write a boot
block and MBR. For that, there is the installer in "tools/freeinst". Also, if your disk is FAT/FAT32/exFAT, then you can use "sysinstx" with fat32.ifs.
(it installs FreeLDR bootblock too). fat32.ifs supports FAT/FAT32/exFAT. And FreeInst supports more file systems: FAT/FAT32/HPFS/JFS.

If boot block and MBR are written correctly, FreeLDR should boot into its menu. From the menu, you should select the required options: Language
(LANG=en_US or ru_RU), video driver (GENGRADD/Panorama or SNAP. GENGRADD and SNAP SE are included. Panorama can be added easily by an eCS/ArcaOS owner), video resolution, kernel, boot loader, etc. If no options selected, it will boot into PM/WPS with GenGRADD and 800x600 resolution, kernel is 14.104a. Also, OS/2 kernel and QSINIT are included. Please, read details in readme.eng file.

PS: OS/2 can boot into three configurations:
1) Textmode with TShell

There are also options to boot DOS from a diskette, or chainload different GRUB versions (GRUB legacy, GRUB4DOS, GRUB2).

Quote from: Rich Walsh
Just to confirm: if your IFS receives a request for the total size of all EAs (FIL_QUERYEASIZE), and you want to indicate that their are no EAs, are you returning '4' (and not '0')? Returning zero is the most common coding error when handling EAs.

What do you mean? cbList field? It is always returned to be 0. (It is so in vboxfs.ifs, fat32.ifs and ramfs.ifs/emsfs.ifs). Why it should be 4?

I used the working code from fat32.ifs as a template, so it should work. I see no problems with displaying disks with Drives WPS object
in fat32.ifs. So, the problem is with something other.

OS/2 host? It works, isn't it? OS/2 guest over OS/2 host with hardware-assisted virtualization works fine on my machines, too.

BTW, I released a new r199 version of VBox Additions today:


Many fixes were added, including timestamp fixes: now "touch" utility gives the current time as a timestamp
for affected files. "Make" utility no more loops around, so that, building sources with "make" should work
correctly. Also, I adjusted returned file listings, so file find operation (with DosFindFirst/Next API's) no more
returns an empty filename, so now "copy" command works correctly in both CMD and 4OS/2. Also, now
ZIP and WIC utilities work correctly, so that I was able to create ZIP and WarpIN archives over a shared
folder. Also, I fixed some traps and memory leaks, so now I was able to check out VBox and fat32.ifs and
osFree sources, and build them over a shared folder without any problems. VBox sources take about
1 GB of space on disk, and compile for about 6-8 hours in a VBox machine under a Linux host. So,
no memory leaks occured that time and everything was built without problems. Git and Svn clients
work fine over a shared folder too.

So, I'll appreciate any testing.

PS: This version also has fixed wildcard matching, the DOS way (instead of the UNIX way).

PPS: Now timestamps are adjusted to local timezone. For that, TZ environment variable in config.sys
is parsed to calculate a time zone offset. Time zone offset calculating is done in VBoxService.exe
"Timesync" service, and set a "timezone" field in Global infoseg (via DosSetDateTime/DosGetDateTime
API's). Currently, only simple syntax like "TZ=MSK-3" works. (I'll implement a full timezone parser in the future)

PPPS: Also, I implemented logging to OS/4 / QSINIT / ArcaLDR log buffer. There are unfinished docs (README
and DEBUG documents) added. Please read DEBUG doc for details on debugging techinques (using the log
buffer etc.).

Quote from: mauro
Quote from: Valery Sedletski
    So, now we have two versions of OS/2 additions -- mine and Knut's. Mine has some features,
    missing in Knut's version (his version has non-working WPS Drives object, for example. And
    automount won't work, only manual mount. Plus no drive letter pinning support).

Hi Valery, did someone else than me reported he has issue for shared folder to be handled in wps, as advised you some posts before? No problem with fc/2, but in wps it shows as an empty drive even if it contains some folder and file,
Virtual machine is OS2 Warp 4.5 with your Guest Additions

I have mostly implemented returning empty EA list in some IFS functions, so, in theory, WPS should show a folder listing in "Drives" object.
In practice, it shows it sometimes, and sometimes it shows a "No objects were found that matched the specified match criteria" dialog. Some
other problem occurs. No idea yet, why. Need to look at it closer. If you try to open a WPS window from FC/2 with Ctrl-W, it often works, but
if you try opening the root directory of a shared folder from Launchpad->Drives->..., then it fails often.

Hi, Martin.

> It would be great if both streams can be merged together, but sometimes it is hard to make two developers agree in his way of doing things.

The two versions are very different, so no way to merge them. And I want a bit different features, which are unlikely to be implemented by Knut
and Oracle. And it seems, Knut does not like to include other people's code. (Look at BWW and their libc fork called libcn -- the same situation).

Yes, with netw4x32.sys (dated Oct 13, 2007, size 2206976 bytes) from GenMU distribution, I got the same Eric reported:
a zero MAC address, and device is not detected by XWLAN/WPA supplicant (though, IP address is
assigned and it answer to pings). I also tried a newer version of netw4x32.sys windoze driver (size
10287984 bytes), which should support Intel 6205, but it hangs when netbind.exe is loading.
So, I ended up buying a Intel 5100 from Aliexpress (just ordered it). It should work with my T420
laptop. Also, I bought Ericsson F3507g 3G card + GPS (which worked fine in OS/2 with my older
X61T laptop).

Hardware / Re: M.2 Question
« on: May 23, 2019, 09:56:49 pm »
At least, NVMe requires special drivers for each OS, they are incompatible with AHCI (other similar standard).
So, it is impossible to use under OS/2, unless someone will write a driver. From the last Warpstock I heard that AN
plans to write a NVMe driver.

Pages: 1 ... 4 5 [6] 7 8 ... 24