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 ... 7 8 [9] 10 11 ... 24
121
Applications / Re: Shared folders IFS for VBox Additions, the test version
« on: November 17, 2018, 01:33:44 pm »
2Mauro: Is it indeed the version r179? Its version of vbxgradd.dll should load ok, it's fixed.
Though, VBoxService fix was in r180, so I didn't uploaded the fix, yet. So VBoxService.exe
should be non-working, yet. But no need to try the old version anymore, I'm already uploading
the newer version, r183, try it instead:

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

This version contains more fixes. Both vbxgradd.dll and VBoxService.exe now are
working. SO, shared clipboard should work too.

Also, now I fixed UNC pathnames, so, it now should work if any other UNC IFS is
installed, except for vboxsf.ifs (like the IFS from Peer/LAN Server).

Also, a new feature is added: If \os2\boot\vboxsf.cfg file is present, having lines
like the following:

Quote
share1       <driveletter1>
...
shareN       <driveletterN>

Then drive letters can be pinned. If vboxsf.cfg file is not present, a first available drive
letter is used.

122
Applications / Re: Shared folders IFS for VBox Additions, the test version
« on: November 16, 2018, 04:15:09 am »
2Mauro:

> means a latest version than the one attached at the beginning of this thread?

I updated the link in the first message of this thread. And the message itself, so that it
contains the actual information. So, you need to reupload it and try.

123
Applications / Re: Shared folders IFS for VBox Additions, the test version
« on: November 15, 2018, 09:59:39 am »
2Doug Bissett:

Quote
I finally found some time to try this. First, I don't like the way it is packaged. It is difficult to easily transfer the files to the final locations, but I am sure you can do better (possibly by packaging it as an RPM, or WPI, package). Even a ZIP file, that could be unzipped over the boot drive, would be better (of course, that assumes that files are where they are expected to be). I don't know how you would handle the LIBC stuff though. That should be done with ANPM (RPM/YUM) anyway.

I put it into the ISO image for easier mounting under a VM. So, you mount the ISO image under your
OS/2 VM and copy files to respective directories. Just copy them by your file manager. I use FC/2 for
that. In the future, I plan to create also an RPM package for it, so it could be easily installed from the
yum repository. So, I plan to distruibute  the additions by two ways: 1) As an usual additions ISO
2) As an RPM package. This sould be more convenient. RPM is better for newer OS/2 installations,
which have UNIX ports installed. If they are not installed, it's better to use the ISO image.

It's better to handle kLIBC dependencies with RPM, but in case RPM is not present in your system,
it can be copied manually from the ISO. Also, each RPM package has the same files zipped. So, you
can use a ZIP file as a third installation method.

Quote
It is MUCH better. At least I get, what appears to be, good information when I do DIR in CMD.EXE, or 4OS/2. Even a DOS or WinOS2 window works, within the limits of what DOS does. I still do not get anything, but a blank folder, when opening the WPS drive object, and that folder does not close properly, every time.

Yes, CMD/4OS2/DOS session should work now, but WPS still doesn't, as all required DosFindFirst
options are implemented, except for FIL_QUERYEASFROMLIST[L]. It requires more work, as I should
properly return an empty FEALIST structure (which contains an empty EA'S) for WPS to be working.
DOS also requires more work, as I need to implement filename translation short <-> long, as it's
done by FAT32.IFS. So, some long file names are not yet accessible to DOS/Win16 programs.

Quote
In CMD.EXE, I cannot copy a file to another drive. It says that it cannot find the specified drive (not clear on which drive, the source, or the target). Copying a file to a new name on the source drive (no drive letters used) seems to work okay, but it said that 2 files were copied. I don't see a second file. Deleting the copied file works.

Yes, I know about that, too. The "copy" and "cp" commands still don't work as required. It tries
to create a destination file and returns "File not found" error. Need to fix this too.

Quote
I am not sure what to make of vbxgradd.dll. I did not change the line in CONFIG.SYS, but the file is locked, so I assume that your replacement gengradd.dll is using it. I don't notice any difference in the video stuff.

What do you mean, you left GENGRADD in config.sys as is, but VBXGRADD is used, and
locked? You can check which GRADD driver is loaded by looking into \os2\install\gradd.log.

PS: I also fixed VBoxService.exe, so it no more quits after mounting all shared folders. So,
shared clipbord should work now. I also will add an option to explicitly assign drive letters
to shared folders, instead of using the first available ones. Will release it soon.

124
Applications / Re: Shared folders IFS for VBox Additions, the test version
« on: November 14, 2018, 10:16:28 am »
2Mauro:

> -non need to modify the Startup.cmd file, I just copied a shadow of VBoxService.exe  in the Startup folder contained inside OS/2 System utilities, it does its job.

Yes, this should work both ways. No big difference.

No need to comment the

Quote
set gradd_chains=c1

line, and add it again. The position of that line in config.sys doesn't matter. So, you returned
gengradd.dll back? As I said, with lhe latest version, vbxgradd.dll should work too. It is better
because it is faster and it provides support for extra video modes, as Martin said about adding
the 1920x1080x32 mode.

And no need to rename gengradd.dll and panogrex.dll files. You only need to comment the respective
config.sys lines out.

125
Applications / Re: Shared folders IFS for VBox Additions, the test version
« on: November 14, 2018, 06:59:21 am »
2Martin Iturbide: I updated to 5.2.22 too, but it didn't helped (I have VBox under Linux on my
laptop. Maybe, it's working for you because you have Windows). It seems, if the host key is
Right Ctrl, it doesn't work. But when I tried to change it to Right Alt, it worked. so, it finally
works for me.

Shared clipboard doesn't work because VBoxService.exe quits after it has shared folders mounted.
Shared clipboard service is a part if it. So, I need to fix VBoxService first.

126
Applications / Re: Shared folders IFS for VBox Additions, the test version
« on: November 13, 2018, 05:38:57 pm »
2Martin Iturbide: Yes, this works for me too, just tried. Switched to full screen successfully, but can't
switch back because the Host key doesn't work for some reason in VBox version 5.2.20 (Linux host).
Too bad. Needed to kill the VM.

127
Applications / Re: OS/2 for Power PC and the Thinkpad 860
« on: November 13, 2018, 03:49:13 pm »
There are some articles about OS/2 PPC in Michal Necasek's blog:

http://www.os2museum.com/wp/category/powerpc/

He also has the PowerPC hardware (a desktop system).

Also, there is an OS/2 PPC CD's uploaded at archive.org.

128
Setup & Installation / Re: VirtualBox Easy OS/2 Setup
« on: November 13, 2018, 03:28:09 pm »
2Bogdan Szmalcownik: I have read about ddinstall in pddref.inf from IBM DDK. As far as I can see,
:SYSINI option allows to modify INI entries. Though, I don't see an option to get a current value
of an INI entry, and modify it (I need to add one DLL to the end of SYS_DLLS list, not only replace
the all existing entries to my entry).

And :SYSINI seems to be only for adding PM video drivers.

Also, I need an option to comment some "set" and "device=..." lines out in config.sys, and replace
them by my lines. But I only see :CONFIG option which appears to ignore existing config.sys lines
and leave them as is.

And I don't see any option to modify startup.cmd file from an .ddp profile. So, it seems, the
possibilities offered by ddinstall are limited. So, I think, it's better to provide two options:

1) Create an .rpm package for additions, so it could be automatically installed to the guest
system from network. This option is very convenient if you have UNIX ports installed, like
in newer eCS 2.2 and ArcaOS systems.

2) Create an usual Additions ISO, with all required files, including the kLIBC DLL's, plus a
REXX script to automate installation. Also, it's possible to use a WarpIN package, instead of
a REXX script, and put it to Additions ISO too.

129
Applications / Re: Shared folders IFS for VBox Additions, the test version
« on: November 13, 2018, 02:25:29 pm »
Hi all

I uploaded a new build of VBox OS/2 Additions to my ftp:

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

For convenience, I built them as an ISO image, so it can be easily attached to the VM.
All additions binaries (except for vbxgradd.dll and VboxMouse.sys, for which sources
are unavailable) now contain buildlevel information. I also included the readme from
the Oracle additions (though, it is a bit not in sync with current state, and I need to
write my own readme in the future) and all required DLL's from kLIBC (in case they
are missing in your system. If they are present, use the versions from your system,
but update from repository, first).

Also, things that were fixed in this version include correct handling of directory listings
in CMD.EXE and 4OS/2 (though, FIL_QUERYEASFROMLIST[L] option in DosFindFirst
is not yet working. I need to generate correct FEALIST structure with empty EA's for
WPS Drives object to be working correctly).

Also, I noticed an error in previous version, which was fixed too: I renamed gengradd.dll
from official Oracle Additions to vbxgradd.dll, but forgot to change the internal module
name to VBXGRADD too (it remained to be GENGRADD as is). So, I discovered that
vbxgradd.dll failed to load in fact. So, it falled back to gengradd or vgagradd (if gengradd
is unavailable). So, this is why Mauro got VGA mode with 16 colors. He has no gengradd.dll
in his system, but has vgagradd.dll, so it was loaded as a fallback.

Also, new features include support for UNC pathnames. So, paths like

Quote
\\vboxsrv\shared_folder_name\path\to\somefile

or

Quote
\\vboxsvr\shared_folder_name\path\to\somefile

now are working. Though, it appears that an UNC IFS can be only one in the system, so
if you have ifs=netwksta.200 from Peer/LAN Server installed, only last UNC IFS in config.sys
will work. So, currently, you need to comment out the second IFS, if you want to try this.

2Mauro: So, you have VGAGRADD loaded. So, update to the new version, it should work now.
It looks like you had amouse.sys and VBoxMouse.sys loaded at the same time, that's why you
had a trap. All other your settings seem to be ok. I only don't know why you have this error:

Quote
https://ibb.co/k9CYQA

I dont have it in my system. I only see an empty drive for each shared folder I have. No errors
at all.

2Martin Iturbide: It's best to use VBXGRADD. SNAP or Panorama work in VESA mode anyway.
So, they should be slow. VBXGRADD seems to call VBox video functions from host directly, so it
should be better. Though, I don't know exactly what it does as I don't have its sources. And previously,
I had vbxgradd failing to load, and gengradd was loaded instead, but I did not noticed the difference
between vbxgradd and gengradd until Mauro said he has started in VGA mode.

2Doug Bissett: So, now I have CMD.EXE working. So, WPS should be working soon too.

PS: I updated the first message of this topic, now it contains the latest link to binaries,
and some new tips.

130
Applications / Re: Shared folders IFS for VBox Additions, the test version
« on: November 11, 2018, 02:25:52 am »
PS: BTW, I fixed FIL_QUERYEASIZEL now, so file listings in CMD.EXE and some versions of 4OS/2
are working now. The problem was very simple. It was a oNextEntryOffset field in the beginning of
FILEFINDBUF4L structure. DosFindFirst returns it, but an IFS should omit it, it is added later by the
kernel. It was returned by FIL_QUERYEASIZEL, but was ommited by FIL_QUERYEASIZE, so the
latter worked, and the former didn't work. Now FIL_QUERYEASFROMLIST/FIL_QUERYEASFROMLISTL
are in the queue. Should be fixed soon. (The layout of data returned by these two options is the
most complex, so it's harder to implement it).

131
Applications / Re: Shared folders IFS for VBox Additions, the test version
« on: November 11, 2018, 01:21:56 am »
2Doug Bissett:

Quote
I avoid anything that even hints that it is like a NORTON program. Many years ago, when antivirus was a new thing, I found that NORTON was causing more problems than it fixed, or prevented. From what I have seen, over the years, that hasn't changed. Clones, of course, should not have those problems, but I avoid them anyway.

Norton causing problems? I did not saw any problems with Norton. So, what do you mean? So, is there any alternative
for Norton clones? Do you think that using a bare command line is better and more efficient? I doubt that.

Quote
BTW, 4OS/2 doesn't display directory information (for a shared drive) any better than CMD.EXE does (that is, no file names). At least CMD.EXE formats what is shown, in a more readable way. I find the 4OS/2 DIR to be distracting, on normal directory displays. I do hope that you an come up with something that works better than what SAMBA does.

??? My version displays directory listings fine. I'm using 4OS/2 OSE, osFree version. Maybe, your version is different
and it uses different switches for DosFindFirst?

My version of 4OS/2 uses FIL_QUERYEASIZE == 2, and FC/2 uses FIL_STANDARDL == 11. command.com
and Volkov Commander in a DOS session use FIL_STANDARD == 1. These do work.

CMD.EXE uses FIL_QUERYEASIZEL == 12, WPS uses FIL_QUERYEASFROMLIST == 3 -- these won't
work, yet.

PS: just checked another version of 4OS/2 (version 4OS2 3.08.3-shl), it uses FIL_QUERYEASIZEL,
like CMD.EXE. So, it doesn't display file names too. Probably, you have the same problem.

132
Setup & Installation / Re: VirtualBox Easy OS/2 Setup
« on: November 10, 2018, 02:09:08 pm »
AFAIK, ddinstall cannot modify INI files,
This should be possible by adding a section :OS2INI to the DDP.

Oh, that's good. So, it looks like everything can be installed with ddinstall only.

Quote
Quote
but this could be done from REXX.
REXX has to be installed first. So it will not work early at installation time. But an option for OS/2 <2.1.

Why do you need it early at installation time? It can be installed after the completion of installation,
and it is done always this way. Why OS/2 < 2.1 ??? Do OS/2 versions older that 2.1 miss ddinstall?
But yes, ddinstall can be used at any time -- so you're right

Quote
Quote
(I plan to move shared clipboard code to a DLL loadable from SYS_DLLS, so VBoxService
no more contains PM-related code, so I could move VBoxService.exe from startup.cmd to a run=... line in
config.sys).
There are enough other solutions for clipboard sharing that will work with a wider range of virtualized OS/2 products. The current additions require files that are simply not available on a fresh install and do not work under most versions of OS/2.

Other solutions for clipboard sharing? What do you mean? I know only about one program
written by dink, it has versions for OS/2 and win32, only. But what to do in case of Linux or
any other less widely used OS?

Current VBox Additions use KEE API's, that's why they require Aurora-level kernel. So yes, it will
not work with Merlin, or older OS'es. I don't like this too. But that's how VBox works. The drivers
from OS/2 additions are built with GCC and should be 32-bit. Writing 32-bit drivers for older OS-es
has big issues. Drivers from the additions use VBox runtime. It's problematic to use VBox runtime
in 16-bit drivers. So, no way.

Which files that are not available at fresh install are used by the Additions? Do you mean, kLIBC/libcx/
gcc runtime? Yes, of course, they are required, as VBox (including the additions) is built with GCC+NASM.
So, these files are required. But this cannot be avoided. No way to build the Additions with Watcom,
currently. Anyway, it's easy to install kLIBC/libcx/libgcc in a freshly-installed system. The additions
depend on a small number of libs, indeed. Here's the list:

Quote
libc066.dll
gcc1.dll
libcx0.dll

Nothing more is required, I only omitted standard OS/2 DLL's like tcpip32.dll, pmwin.dll, doscalls.dll.

133
Setup & Installation / Re: VirtualBox Easy OS/2 Setup
« on: November 10, 2018, 08:21:29 am »
2Bogdan Szmalcownik: Yes, I completely forgot about ddinstall.exe. But the required things are not only add
device=... and ifs=... lines to config.sys, but also comment out some other unneeded lines. I'm not sure
if ddinstall can add "set" lines, and replace some lines with another lines. Also, possibly, in the future, modification
of os2.ini will be required, to add some DLL to SYS_DLLS list. AFAIK, ddinstall cannot modify INI files, but this
could be done from REXX. (I plan to move shared clipboard code to a DLL loadable from SYS_DLLS, so VBoxService
no more contains PM-related code, so I could move VBoxService.exe from startup.cmd to a run=... line in
config.sys).

134
Applications / Re: Shared folders IFS for VBox Additions, the test version
« on: November 10, 2018, 07:43:23 am »
2Doug Bissett:

Quote
They are "extras", and neither one is a "must have". IMO. They are not part of OS/2, they are added later. I usually install 4OS/2, but I never use it. I haven't even thought about FC/2, for a number of years. I wasn't impressed with it then, and I see no good reason to try it now.

OS/2 without FC/2 and 4OS/2 is non-usable. CMD.EXE has a lot of limitations, and it does even not support
command autocomplete. It has only basic  required features. So, 4OS/2 should be used instead. It is free,
open source and no reason not to use it by default. It was included into eCS by default too.

WPS is not at all intended to be a file manager. It only serves as a convenient program launcher, using a desktop.
Copying files with WPS is slow and inefficient. So, it anyway requires an external file manager. But GUI file managers
like Larsen Commander and File Manager/2 are even less usable that Norton Commander clones, like File Commander/2
is. FC/2 has very optimized and convenient hotkeys and using it instead of GUI file managers is far more efficient.

And FC/2 can be started from command line, when booting into Recovery Choices menu. So, it is very useful
and convenient for system repair too. In my opinion, Norton-like file managers are most usable ones, so I use
File Commander/2 and Dos Navigator/2 in OS/2, Volkov Commander, DOS Navigator and Norton Commander
in DOS, Midnight Commander under Linux, and Far Manager is the best under Windows.

Quote
There are a few ways to do that. I find it easiest, to just copy the VDI file, and copy it back if something goes wrong. Snapshots are too permanent, and end up taking up space in my backups. Export/Import has a few problems too, like converting VDI files to VMDK files, which work okay, but if I wanted VMDK files, I would have made the disk image use that format initially. I am not saying that either method is wrong, or bad, I am just saying that copying the VDI file is easier.

Snapshots can be deleted, if not required anymore. And the space used by them can be freed by compacting
the disk image. There is a "compact disk image" feature for that.

2Mauro:

Quote
Valery, afaik,  you can resume from a snapshot only once you are in the working system, so it is not for a non-booting system recovery.

You can restore from a snapshot any time. You can do it with VBoxManage:

Quote
https://www.vleeuwen.net/2012/12/virtualbox-snapshots-using-the-cli

Also, IIRC, this is possible to do the same from GUI. Just start the VM and "restore from a snapshot"
can be choosen from its menu.

135
Applications / Re: Shared folders IFS for VBox Additions, the test version
« on: November 08, 2018, 12:24:29 am »
2Doug Bissett: Yes, file listings in WPS Drives object and CMD.EXE doesn't work yet. Use 4OS/2 and FC/2 for now.
Anyway, FC/2 and 4OS/2 are not "extras" but are "must have" programs. Of course, it should work in standard
programs like CMD.EXE and WPS, but not all at once. It will work later. It is just easier to make FIL_STANDARD
and FIL_STANDARDL DosFindFirst options work first. WPS does also require EA's to work, it seems. But no EA's
support in VBox, AFAIK. So, it is more difficult to make WPS and CMD.EXE working. But it will work later.

PS: Yes, agree with the 3rd paragraph, too. What I could add here is except for backing up the .vdi file,
or exporting it to .ova and then reimporting, in case of problems, there is also a snapshots feature in VBox. You
can take a snapshot of a VM (just like checkpoints in windows restore), then revert to any checkpoint.

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