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 ... 6 7 [8] 9 10 ... 24
106
Applications / Re: Mounting a VDI image as a drive
« on: January 04, 2019, 10:14:24 pm »
2Martin: Why not  use fat32.ifs or loop.add driver supplied with it? Fat32.ifs can mount FAT/FAT32/exFAT
disk images on a subdirectory on another FAT/FAT32/exFAT drive. Also, with help of loop.add block device
driver, it is possible to mount any file system, having an IFS driver for OS/2, on a drive letter. The disk images
can be raw ones (floppy images, CD/DVD ISO images, or any VM disk images, like .vhd/.vdi/.vmdk/.qcow/etc
-- for details, see fat32.inf file). Note that this feature is still in development. Currently, there are problems
with mounting file systems other than FAT/FAT32/exFAT/iso9660. These listed are mounted fine. JFS/HPFS
are mounted successfully, but there are problems with using strat2/strat3 in loop.add driver. So, you can
view directory listings, but if you try to copy something bigger than 1 MB, you can see a hang when cache
is flushed. But FAT/FA32/exFAT/CDFS work fine as they use strat1 only.

For reading/writing different VM disk images, fat32.ifs and loop.add uses a special qemuimg.dll library I ported
from QEMU. The library is loaded by cachef32.exe daemon, and executes read/write/open/close requests, issued
by fat32.ifs or loop.add, and returns results back.

Note that currently, there is a bug in this library, which causes to show trash is some subdirectories. This is
currently not fixed.

107
Applications / Re: Shared folders IFS for VBox Additions, the test version
« on: December 24, 2018, 06:13:10 pm »
2Martin: No, this is Knut's version of OS/2 additions. I told Knut that my version is almost ready,
then he immediately flushed his last version (previously unpublished). It appears that he had almost
working version, but did not committed it to official repository, until now. My version is based on
his early version, which was available in Oracle's repository. I thought, it was abandoned.

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).

108
Applications / Re: Creating archive > 4GiB from script
« on: December 02, 2018, 05:39:50 am »
2Bogdan:

> I only know about the private Github company. Does it mean that BWW offers a similar service for the public?

What do you mean? Most Github projects are opensource and provide sources and binaries
for free, including BWW. So, BWW repos are public, not private (only commercial sources are not
public, like InJoy, for example).

>>> Sorry we are in 2018 now, I cannot see any reason for a fork of 10 year old code, where created binary packages don't follow the terms of the licence agreement and additionally are incomplete or break compatibility in different ways.

>>    Do you think that fork is something bad? Anybody can fork any software with opensource license,
 and add his own enhancements.

>... under the restrictions of the licence agreement and the copyright. But that depends on local law.

InfoZIP seems to be under BSD-like license. BWW provide packages under the same license. So, what
terms they don't follow?

>>  Moreover, forks are encouraged with git, where multiple repositories
with the same program exist, and they may copy changes from one to another.

>git is only a version control software that encourages nobody. I don't know about a special AI improvement or module that would offer this feature.

Git and GitHub makes it easy to create and merge forks. Forks are just a convenient way to create
modified versions of sources. Fork doesn't denote anything bad. So, there's nothing bad that BWW
created a fork. This fork could be in the future merged into an original version, but this requires time.

> InfoZip releases of zip or unzip don't require any patches. They built on native OS/2 supported environments or can be cross-compiled from other development environments.

These patches are old and InfoZip cannot thoroughly test the OS/2 code with newer versions. Simply
because they don't use OS/2 for everyday  use. So, they can break something in new versions, without
noticing it. That's why newer versions can cointain bugs (related to combination of old OS/2 patches
with newer InfoZip code). So, this require fixes, which is done by BWW. So, no wonder if they require
modifications.

The OS/2 patches to InfoZip are very old, they were created by Kai Uwe Rommel in 90'ths. And I doubt
that this code was updated much by InfoZip.

>> Also, there are some enhancements like kLIBC symlinks support. I doubt that this feature present in
InfoZip version.

> Please provide the necessary information so I can answer the question. Do you mean symbolic links? The Zip format is from the PC DOS world and has only limited support for UNIX features. Hard link and symbolic link support can be provided with UNIX Extra Field, but seems to be useless for non-UNIX environments. Who wants to restore UNIX device names under OS/2?

This is you are kidding, or serious?  Yes, symbolic links. Don't you know that kLIBC contains symlink support?
No, it is not useless on non-UNIX environment. It is very useful in case you backup/restore your UNIX ports tree.
This tree contains many symlinks in /@unixroot/usr/bin subdirectory, for example. I suspect that you'll not like
if after restoring the UNIXROOT from backup, your symlinks are broken? And yes, InfoZIP contains support for
symlinks on UNIX environments (the same as ACL and EA's support on OS/2 platform), so, it can be desirable
to have symlinks support on kLIBC too. This is one reason for creating patches to original version.

>>Did you tried to build InfoZip yourself?

>I cannot count the platforms and different C compilers here, but mostly C/370 or the AIX C set.

So, you didn't tried to build the OS/2 version, ok.

>Which version of OpenWatcom was utilised? I remember of building it 20 years ago with Watcom C compiler for OS/2 and NT with the supplied makefile from an OS/2 hosted environment.

I used OW 1.9 I mean that there were some problems with calling a 16-bit API from netapi.dll for OS/2
ACL support. OW is good with building 16<->32 bits thunks, at least, I was able to create 16-bit wrappers for
32-bit DLL (a FS utility DLL from fat32.ifs, for example). So, this should work, though, I was unable to build
wrappers for ACL code in zip.exe. That's why I wonder how this was worked around in GCC builds. Maybe, they
just dropped the ACL code. I don't know.

109
Applications / Re: Creating archive > 4GiB from script
« on: December 02, 2018, 12:57:01 am »
2Bogdan:

> It's quite easy, these builds seem to be from a private codebase and not released officially by Infozip.

They are not private. They are publicly available from BWW GitHub.

> Sorry we are in 2018 now, I cannot see any reason for a fork of 10 year old code, where created binary packages don't follow the terms of the licence agreement and additionally are incomplete or break compatibility in different ways.

Do you think that fork is something bad? Anybody can fork any software with opensource license,
and add his own enhancements. Moreover, forks are encouraged with git, where multiple repositories
with the same program exist, and they may copy changes from one to another. Original OS/2 patches
from InfoZip are very old, and InfoZip can easily break the OS/2 version themself. I doubt they do
OS/2 version testing very much. So, there can be bugs. To fix these bugs, BWW needs extra patches.
Also, there are some enhancements like kLIBC symlinks support. I doubt that this feature present in
InfoZip version.

Binaries don't follow the license agreement? What do you mean? Both sources and binaries are
publicly available...

> I agree, applying some 2 minute patches to a 10 year old zip release can be very time-consuming. So there is no time left for compatibility checking any more or a functional test at all.

Why do you think it is 2-minute patches? Did you tried to build InfoZip yourself? I tried to build it
with OpenWatcom. It was very old version, and making the old OS/2 ACL patch work was very
hard. (There were some problems with calling 32-to-16-bit thunks. As some 16-bit API from
netapi.dll was called. I wonder how they work this around with 32-bit GCC build).

110
Applications / Re: Shared folders IFS for VBox Additions, the test version
« on: November 30, 2018, 03:39:35 pm »
2ivan:

Quote
ftp://osfree.org/upload/vbox/vbox-os2-i386-v5.0.51.zip

?

This is the latest available version.There is also the older official version 5.0.6 of VBox on Herwig's page.
Not sure, what do you need for "AMD Ryzen G" processor. Never had such processor. And I doubt
that other VBox versions are available. The required dependencies are described here:

Quote
http://trac.netlabs.org/vbox/

PS: Why do you need the version with all the dependencies? Manually picking all versions of all required
libs is not recommended because it is tricky and causes library versions conflicts, which can cause problems.
It is recommended to have a single version of each library in the system, to avoid situation, when different
programs want different versions of a library, and thus, crashes happen. Also, having a single library in the system
consumes less memory. This is very important on a 32-bit system, which is limited with the < 4 GB limit
of its address space. To achieve this, there is a package manager, like yum. It should care about all
dependencies, updating each library to the latest version, and all programs being dependent from the
same version of each library. So, why not just use the package manager as it's designed?

PPS: For AMD Ryzen processors (not sure about "Ryzen G"), Arca OS kernels was not known to work/boot
ok. Though, on unofficial OS/4 kernels, there are some users which had successfully using OS/4 kernel
with AMD Ryzen processors (though, I'm not sure about what Ryzen variants they are). But it makes sense
to contact OS/4 developers and try being a tester. Also, as a bonus of an OS/4 kernel, you'd have a
possibility to use hardware virtualization (AMD-V/VT-x) with OS/2 version of VBox. This is an unfinished
feature, yet, but it is mostly working. I am even able to run OS/2 guest on top of OS/2 host.

111
Applications / Re: Shared folders IFS for VBox Additions, the test version
« on: November 23, 2018, 09:48:28 pm »
Hm, but I cannot reproduce your situation on my machine. I have OS/2 or Linux
hosts, and OS/2 guest. On OS/2 host, I set "archive" bit in DOS file attributes, but
via a shared folder, I see this bit cleared on that file. You seem to have Windows
host (is it true?), and see "archive" bit set on some files via shared folders. Too bad,
I have no windows on my test machine :( I have WinXP host on a third machine, though.

112
Applications / Re: Shared folders IFS for VBox Additions, the test version
« on: November 23, 2018, 06:51:01 pm »
2Moritz:

> Files/directories skipped/repeated twice

I have no idea why they could repeat twice, but they can be skipped because file
attributes are not matched. Maybe, they have hidden/system/readonly/archive
attributes set? Can you check which attributes these files/directories have? DOS
could skip files with system/hidden/readonly attributes. You could try removing
these attributes with FC/2 and see. You can also try Norton/Volkov Commander/
DOS Navigator -- they should not skip files with special attributes set.

PS: Indeed, as it can be seen, your files have "archived" bit cleared, except for
those two "sav_*.ice" files. So, it's because of this.

113
Applications / Re: Shared folders IFS for VBox Additions, the test version
« on: November 23, 2018, 05:40:17 pm »
PS: This is in DOS (command.com):

Quote

The volume label in drive L is os2l.
Directory of L:\TMP

0075_01  TRP      5866  14.11.18 13:51
3        10  <DIR>      23.12.15 23:45
acpi-3   22.    129939  23.12.15 23:39
acpi-man ger    118667   4.08.08 19:48
acpi-too kit    241070  14.12.15 10:23
acpi     psd    220275  28.11.13 11:02
acpi32   dll     15631  28.11.13 11:00
acpi4    bpd    112959  20.12.15 22:56
acpi4    rar    109184  23.12.15 22:29
AcpiInfo dat    452032  24.12.15  1:31
AcpiLstI fo.     37748  24.12.15  1:31
AcpiMana er.    201794  12.03.07 17:12
AcpiMana er.      2822  24.12.15  1:31
addition     <DIR>      12.11.18 11:32
addition .zi    692493  12.11.18  9:50
dos      txt        40  23.11.18 16:51
DosSysCt _IP     22112  18.11.16 22:12
freeShar dMe     14385   7.01.16 14:58
g        img  33162240  30.09.17  6:22
gnufu    dll     24445  31.03.98 18:22
gnuintl  dll      6203  31.03.98 18:22
o        img 181485568  29.09.17  8:58
PMGPI    DLL    248446  16.10.01 13:31
PMGPI    txt    117246   7.03.17 18:45
VBoxAddi ion   1422919  17.11.18 18:26
VBoxAddi ion   2818048  20.11.18 15:54
VBoxAddi ion   1519757  21.11.18  2:34
yum_save tx-     12815  21.05.17  7:53
yum_save tx-     20325   3.04.18 23:31
yum_save tx-     20325   3.04.18 23:33
                     0                 
      31 file(s)  223235866 bytes used
                 371965952K bytes free


The same directory shown in 4OS/2:

Quote

 Volume in drive L is os2l       
 Directory of  L:\tmp\*

23.11.18  16:54         <DIR>        0   _H__D  .
23.11.18  16:52         <DIR>        0   _H__D  ..
23.12.15  23:45         <DIR>        0   ____D  3.10
12.11.18  11:32         <DIR>        0   ____D  additions
                              0      0   _____   
23.11.18  16:54              38      0   _____  4os2.txt
14.11.18  13:51           5 866      0   _____  0075_01.TRP
23.12.15  23:39         129 939      0   _____  acpi-3.22.03.rar
 4.08.08  19:48         118 667      0   _____  acpi-manager-20070312.zip
14.12.15  10:23         241 070      0   _____  acpi-toolkit-3.22.zip
28.11.13  11:02         220 275      0   _____  acpi.psd
20.12.15  22:56         112 959      0   _____  acpi4.bpd
23.12.15  22:29         109 184      0   _____  acpi4.rar
28.11.13  11:00          15 631      0   _____  acpi32.dll
24.12.15   1:31         452 032      0   _____  AcpiInfo.dat
24.12.15   1:31          37 748      0   _____  AcpiLstInfo.lst
12.03.07  17:12         201 794      0   _____  AcpiManager.exe
24.12.15   1:31           2 822      0   _____  AcpiManager.log
12.11.18   9:50         692 493      0   _____  additions.zip
18.11.16  22:12          22 112      0   _____  DosSysCtl_IPI.exe
 7.01.16  14:58          14 385      0   _____  freeSharedMem.exe
30.09.17   6:22      33 162 240      0   _____  g.img
31.03.98  18:22          24 445      0   _____  gnufu.dll
31.03.98  18:22           6 203      0   _____  gnuintl.dll
29.09.17   8:58     181 485 568      0   _____  o.img
16.10.01  13:31         248 446      0   _____  PMGPI.DLL
 7.03.17  18:45         117 246      0   _____  PMGPI.txt
17.11.18  18:26       1 422 919      0   _____  VBoxAdditions-os2-x86-5.0.51.r183.zip
20.11.18  15:54       2 818 048      0   _____  VBoxAdditions-os2-x86-5.0.51.r184.iso
21.11.18   2:34       1 519 757      0   _____  VBoxAdditions-os2-x86-5.0.51.r184.zip
21.05.17   7:53          12 815      0   _____  yum_save_tx-2017-05-21-07-53nopywb.yumtx
 3.04.18  23:33          20 325      0   _____  yum_save_tx-2018-04-03-23-33cvthgo.yumtx
 3.04.18  23:31          20 325      0   _____  yum_save_tx-2018-04-03-23-315o16h2.yumtx
     223 235 352 bytes (212MB) in 29 files and 4 dirs

     223 297 536 bytes (212MB) allocated
 307 888 103 424 bytes (286GB) free

As can be seen above, the names shown are the same for "yum_save tx-", "VBoxAddi ion",
but the files are different. Also, as it can be seen, "addition" ("additions" in fact) subdirectory
is shown here. Both listings contain 29 files and 2 directories.

114
Applications / Re: Shared folders IFS for VBox Additions, the test version
« on: November 23, 2018, 05:01:50 pm »
2Moritz:

Interesting effect that it displays some files twice. Are you sure they are the same?
Maybe, this is two different files with long name, truncated to the same short name?
 I don't have this on my VM. Also, directories are shown ok in my case.

PS: File names in DOS are not yet ready, because file name translation short <-> long
is to be implemented, yet.

115
Comments, Suggestions & Questions / Re: OS2 on emulation machine
« on: November 21, 2018, 08:50:19 pm »
Yes, debugging some drivers in a VM, or debugging any other software in a VM. For example,
I developed my live CD/bootflash partially in a VM. The boot CD has options for enabling VBox
additions, or VPC additions, so it can be very comfortably run in a VM. The CD/flash is very
handy to test some software setups in VM's. If someone interested, I could give a link here.

116
Applications / Re: Shared folders IFS for VBox Additions, the test version
« on: November 21, 2018, 12:07:52 am »
2Martin:

Quote
It seems to me that ArcaOS 5.0.3 installs the  14.200_W kernel when you have only once processor/core. I installed this VM with only one core, any tip to update/change to the 14.201_SMP from the kernel that I have is welcome.

Just search \os2image for SMP kernel (It should be in \os2image\debug\smp, I think).

117
Applications / Re: Shared folders IFS for VBox Additions, the test version
« on: November 20, 2018, 09:44:09 pm »
I uploaded a new version:

Quote
ftp://osfree.org/upload/vbox/additions/VBoxAdditions-os2-x86-5.0.51.r184.zip

Now WPS Drives object should work ok, as I implemented creating the empty EA's
structure. Also, I fixed FS_VERIFYUNCNAME, so it now should work, when two UNC
IFS-es are installed. The "dir \\vboxsrv\sharename" now works ok with CMD.EXE.
Previously, this command gave an error.

118
Applications / Re: Shared folders IFS for VBox Additions, the test version
« on: November 20, 2018, 08:49:19 pm »
2Martin Iturbide:

Quote
1) It does not auto-mount with "start /n vboxservice.exe" on startup.cmd. I had to run like "VBoxSFAttach w: OS2Temp" to mount the drive. Was an auto-mount supposed to happen, or did I get it wrong? I have no problem adding "VBoxSFAttach w: OS2Temp" on the startup.cmd.

Is your \programs\VBox directory on PATH? If not, you need to specify the full path:

Quote
start /n c:\programs\vbox\VBoxService.exe

It automounts ok on mine, and several other users machines. Did you checked the
"Auto-mount" checkbox in shared folder settings?

Quote
2) It is "Read only" I can not copy a file from and to the same mounted drive using 4OS2 or CMD. (but the good thing is that now CMD sees the files and I can copy those to other drives like C:).

Do you have "read only" checkbox set on your shared folder in VM settings? If so, remove it. The "copy" command does not yet work ok, as I already mentioned above. e/ae editors should work. I have no problems saving files with them.
Note that read only shared folders are not tested at all -- used r/w ones only so far.

Quote
3) WPS integration is not working.
    a) I open e.exe and looked at the W: drive and worked (E Running W.png)
    b) I open W: from the "Drives" icon and get a OS2KRNL trap (See OS2KRNL- Trap.png or video)

E.exe is not the WPS drives object. It is Drives object did not work. File dialog should work. But now I
added support for WPS Drives object, will upload a new version soon. From your trap screen it is
hard to tell where it trapped. Somewhere in the kernel. You'll need to retest with the newer version
(I'll upload it soon).

119
Applications / Re: Shared folders IFS for VBox Additions, the test version
« on: November 18, 2018, 04:33:30 pm »
2Mauro:

So, you have all video modes in the list. I have no display selected here at all. Yes, these
modes are shown by VBox VESA BIOS. I have the same. What else do you want?

No 16x9 value? Then add it with VBoxManage command, as Martin did before.

120
Applications / Re: Shared folders IFS for VBox Additions, the test version
« on: November 17, 2018, 06:15:12 pm »
2Mauro:

Yes, as it was written above, if you have the \usr\lib\*.dll files already installed, no need to install them
again, just ensure they're latest version.

Quote
And, opened C:\OS2\INSTALL\GRADD.LOG  I found the following:
20181117T155005 VMAN:ProcessGraddList(): Module VBXGRADD loaded successfully

So, it loaded ok. Did you checked System Setup->System->Screen ? Does it show all
usual video modes? If so, enable the video mode you need and reboot.

Pages: 1 ... 6 7 [8] 9 10 ... 24