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

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

3
Programming / Re: Rexx Socket / SMTP
« on: May 07, 2019, 02:13:50 am »
It's not SMTP, but my IMAPADD script demonstrates how to use IMAP via REXX to add a message to the remote mail server.
http://www.altsan.org/programming/rexx/index.html#imapadd

I used to use it to have PMMail copy all incoming messages to my IMAP account.

So, PMMail already can use IMAP, instead of POP3??? Your script should write an email message into
an IMAP folder. But how could it help with sending emails with SMTP?

4
Programming / Re: Rexx Socket / SMTP
« on: May 07, 2019, 02:08:51 am »
2David Graser: REXXCURL is an interface to cURL, and cURL is for HTTP (including https). How could it
help with SMTP over SSL?

As far as I can see, newer versions of PMMail use stunnel for SMTP over SSL. So, we could use it too
for the same purpose.

5
Hardware / Re: T420 and Intel 5100 Wifi
« on: April 01, 2019, 01:30:07 pm »
2Jochen Schaefer: Yes, I know. But there are patched BIOS'es which have supported cards whitelist disabled. With my older X61T laptop, I had BIOS already patched with its previous owner. Need to check if a patched BIOS exists for T420, of course. Some info on this should be available at http://www.thinkwiki.org. So, 5100 is whitelisted?

IIRC, the half-sized slot is intended for 3g/4g WWAN cards, or for SSD's. It has PCI-express lines missing, only USB lines present. Full-size slot additionally supports PCI-express cards (like wifi ones).

Did you tried to install a 3G WWAN card into T420? Does T420 have a SIM card slot somewhere? X61T has it under the same cover where DIMM memory modules are installed. But I don't see the SIM slot under similar cover in T420.

6
Hardware / Re: T420 and Intel 5100 Wifi
« on: April 01, 2019, 10:45:47 am »
Hi all.

I bought T420 too, it was one month ago. Almost all devices are working with eCS 2.2, except wifi (my T420 has Intel PRO/Wireless 6205 a/g/n, 8086:0085 wifi card installed). Also, Intel HDA sound is semi-working (sometimes, I hear a startup sound during the boot, and sometimes I don't. I use uniaud from eCS 2.2 distribution. unimix sometimes says that it successfully set the sound volume, but sometimes it says "Failed")

For a wifi, I found a winxp driver, but I did not tamed it yet to work under GenMac. System just hangs on netbind.exe during the boot. Also, I tried to make it work with the Intel PRO/Wireless 4965 a/g/n driver. So far, driver loads ok, the log output in lantran.log is ok, but the MAC address shown is all zeroes. Also, XWLAN widget says It does not see any wifi card. So, I did not achieved any success with it so far. Gigabit LAN is working ok with e1000e driver, though. (I patched a table in the genm32.os2 driver accordingly, so GenMac now knows about my new card and which winxp driver it should use for it)

So, 5100 is still being sold? Good choice, I think (if so). I also have 4965 card on my older Thinkpad X61 Tablet, so I planned to swap wifi adapters on X61T and T420, but buying 5100 could be a better idea.

7
Programming / Re: Can an application be started and run in monoprocessor?
« on: February 28, 2019, 05:42:04 pm »
P.S.:
> It is possible to implement it on IBM's kernels with ACPI.PSD, but I see no interest from ArcaNoae for that to be implemented.

On OS/4 kernels, it works with any PSD. Tested successfully with os4apic.psd, os2apic.psd and acpi.psd. On IBM's kernels, it is possible to use ACPI.PSD, or implement this feature locally in VBoxDrv.sys driver, or create a special helper driver for that, in theory.

8
Programming / Re: Can an application be started and run in monoprocessor?
« on: February 28, 2019, 04:32:41 pm »
2Doug Bissett:

> I have been using Virtual Box 5.0.6, for a while now. It runs okay, but uses HUGE amounts of lower shared memory space.

You could try marking VirtualBox DLL's for loading into high memory, then it will use less lower one. For that, I made a highmem.cmd script. It uses highmem.exe from OpenOffice distribution for marking DLL's for loading into high memory, so you need it too. The same could be done with XUL.DLL from Mozilla, it helped me a lot. Unfortunately, not all DDL's like if they are loaded into high memory, so use it with care. It can hang your machine if used incorrectly.

2Doug Clark:

> I am using vbox 5.0.51 and it runs pretty well - except for having to pause for about 20 seconds or so between starting vbox and starting a virtual machine.

VirtualBox VM's communicate with the VBox Selector window via remote procedure call (specifically, for sending the VM screenshots for previews. So, you can try to ease your life with VBox by disabling preview updates. Just right-click on the preview window and set a "Update disabed" checkbox). Or, you could try closing the Selector window, or run VBox from the OS/2 window as "VirtualBox --startvm <vm_name>". Or, better use "VBoxSDL -s <vm_name>". The problem with PM lockups when starting the VM are present in Qt frontend, only. SDL frontend is free from it. So, you can try to set up the VM parameters in the selector window, then close it, and run a VM without the selector.

> It appears that Vbox doesnt run os/2 clients = at least that is the message I get trying to install OS/2 on vbox on a Windows 7 host. Virtual PC version 5 runs OS/2 clients just fine, on an OS/2 host. It works very will on my ECS 2.x box with a pentium 4 with 2 gb of memory circa 2001 or so. But  VirtualPC does not run on my AMD 4 core machine.

VBox runs OS/2 clients, but only with hardware virtualization enabled. Pentium 4 machines doesn't have hardware virtualization support, the same is for my Athlon 64 (1-core, socket 939- based). VirtualPC runs fine on my Athlon 64, though. Did not experimented with it on SMP machines, though (I'm unsure, but it seems, I ran VirtualPC on a Core2Duo, without any problems. Need to check.)

> I THINK it is possible to install OS/2 on the MS version of Virtual PC that is available for Windows 7. However the menu item for attaching/using a floppy drive has been removed, so it is a pain to use floppies with the MS version of Virtual PC. You apparently can do it, but it requires running a VB script and I never could get it to actually use an USB attached floppy; only floppy images.

You can try VPC 2004 or VPC 2007 from MS, I used the former to run OS/2 successfully without any problems, and IIRC, it can use floppies without problems too.

2Dave Yeo:

> Vbox needs hardware virtualization to run OS/2, enable VT-x/AMD-V under System-->Acceleration, which means you need a CPU (and BIOS and OS) that supports it. If you're using a P4, it won't work. Not sure about your AMD machine  but OS/2 itself doesn't support it so no running OS/2 on vbox with an OS/2 host.

Hardware virtualization works fine under OS/2 host (and OS/2 guest runs fine on OS/2 host. If you interested, I can post screenshots here :)), but only on OS/4 kernels at the moment. Though it is under development, it is generally working. For hardware virtualization, VBox needs a feature to run code on all CPU's in parallel in sync (the feature is called "CPU rendez-vous"). This feature is missing on IBM's kernels. OS/4 kernels has this feature available with a new KEE calls. It is possible to implement it on IBM's kernels with ACPI.PSD, but I see no interest from ArcaNoae for that to be implemented. (ACPI.PSD from Pavel Shtemenko had some function for CPU rendez-vous, but it was removed in version by David Azarevicz). And I will support IBM's kernels only in case it will be financed properly (either by ArcaNoae, or by interested community members). Unfortunately, I see no interest in this from ArcaNoae. VBox was funded by XEU a bit, but the funds are almost ended and the work requires more funding. So, for now, if you want hardware virtualization support in OS/2, use OS/4 kernel.

9
Applications / Re: PMMail - COMCAST - secure tunnel
« on: January 05, 2019, 01:26:20 am »
So, it still doesn't support IMAP, and HTML and national codepages? If so, then it's a lot of work.
Who will do it? Moreover, it isn't open source. Who will work on a closed-source project, does this
work feasible? Personally, I'd not invest my time into a closed-source project :(

Why it uses stunnel? Why not use OpenSSL libs instead, so no dirty workarounds like manual
port mappings remote <-> local?

PS: I moved to Seamonkey mail/Thunderbird long time ago, because of lack of IMAP support
and codepages+HTML. Now a days, it's a real problem.

10
Applications / Re: Mounting a VDI image as a drive
« on: January 04, 2019, 11:05:16 pm »
2Martin: Everything is documented in fat32.inf. If it is  JFS, then no way to extract files from the image currently.
As I said, JFS uses strat3, so it doesn't work currently. But FAT/FAT32/exFAT/CDFS will work.

You need to use current version of fat32.ifs, and add the

Quote
basedev=loop.add

statement to your config.sys. Then use f32mount utility to mount the image, like this:

Quote
f32mount <path_to_image> /block /p:<partition_number>

PS: You can mount JFS, and may be, copy some small file from it, but if you'll try something
bigger, it will hang.
PPS: the "/block" parameter means mounting to a block device (i.e., a drive letter). After you
used the drive letter, you can "eject" it like any other removable. If you use mounting to a directory
on another FAT/FAT32/exFAT drive as a mountpoint, you use path to that directory, instead of
"/block" word. To unmount the image, use the same "f32mount" command you used for mounting,
with "/d" appended.

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

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

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

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

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

Pages: [1] 2 3 ... 18