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 - Herwig Bauernfeind

Pages: 1 [2] 3
Applications / Re: Firefox 45.5 Install issues
« on: May 28, 2017, 02:07:54 pm »
I have to address some statements in this discussion:

OS/2's human package manager

Why does OS/2 rely on a human package manager? Because its architecture is from the early 1990ies. No need for automatic package managers back then.

However: It is quite arrogant to assume that all other OS maintainers (no matter whether these are the Linux, Windows, FreeBSD, whoever guys) are rather dim and incompetent to create such beasts for other OSes when in reality they were not needed. 201x software (especially bigger programs) are simply too complex for a manual approach.

Firefox 45 is a 2016 piece of software: The problems to get all DLLs together are not OS/2 specific - all the other OSes got package managers to do that job. NOBODY on other OSes asks for specific DLL requirements to be manually downloaded "somewhere" and copied into specific locations - the question for that (unless for specific research purposes) would be considered plain stupid and obsolete.

The RPM/YUM port is an attempt driven by bitwise works and Arca Noae to close this gaping hole in the OS/2 architecture.


If you want to run software the 1990ies way on a 1990ies OS, please use software from the 1990ies - an automatic package manager would not really be required then.

If you want to run software from the 201x on a 1990ies OS, please do as the ones who DO THE WORK on that stuff suggest. We know what we are doing and why we are doing it the way we do it.

If you do not want to do it the suggested way - you are free to do so. You just need to do A LOT OF RTFM and use PMDLL as a tool to overcome the arising difficulties...

Maybe it is time for you to review your point of view. But please don't steal our time by asking 1990ies questions in 2017. They have been solved - use RPM/YUM - that IS the solution.

It's a disadvantage of lacking competition.

It looks like you are suffering from blatant illusions. I wish the OS/2 market and community was big enough to make competion a healthy option to get the best alternative solution for a problem. The reality is, that the main problem is, to get enough manpower to complete ONE solution for a single problem.

Discussions whether there would have been other (possibly better) solution is senseless - there is simply nobody who will create it.

Critisizing certain aspects of current software (OS and application) is absolutely valid and welcome - however make sure you got a viable alternative solution at hand, a simple rant just is not good enough.

Applications / Re: VirtualBox 5.0.6 First Impressions - follow up
« on: May 28, 2017, 12:47:12 pm »
Does Win 7 work inside vbox with os/2 host?

1. Win 7 works in VBox 5.0.6 for OS/2 and can be installed within a VM of VBox 5.0.6 for OS/2.
Shared sound does not work, shared clipboard does not work.

Networking DOES work for Win 7 guests. Make sure you choose the "Intel NIC for servers" as the network adapter reflected into the VM. It is a known issue that not all other NICs work.

2.) Win 7 can be made to work inside VBox 1.6 for OS/2. You have to create an appropriate .vdi image on VBox for Win and use that in Vbox 1.6 for OS/2. You have to use older guest additions (those for Vbox 2.1.2), not the latest ones. Shared sound does not work, shared clipboard does not work.

Networking works for Win 7 guests using the AMD C579 NIC and driver (not included in Win 7!). The Intel NICs do not work.

In general stability of the whole machine is better with 5.0.6 and the guest runs a lot faster in 5.0.6.

Applications / Re: Firefox 45 Installation
« on: May 21, 2017, 12:46:29 pm »
libjpeg-turbo and hunspell have been moved to release repo by Silvan already.

Applications / Re: Firefox 45 Installation
« on: May 20, 2017, 05:28:28 pm »
The "missing" libraries are in the netlabs/experimental repo.

It looked like we would not make it for WSE, that is why these libraries were not moved to release repo.

2 possibilities: Add netlabs/experimental to your repolist or wait until monday or tuesday when the libraries will be moved to release.

Networking / Re: Copying SAMBA users and groups
« on: February 20, 2017, 07:08:53 am »
While Pauls comment is right, it omits the essential /samba/private directory.

I d suggest to use the builtin archive feature of b4smb.cmd - look into this file, it has a feature to take a complete Samba configuration snapshot upon each start.

The complete config is saved into a ZIP file, ready to be unzipped in a new environement.

In case the new server resides in a different place, make sure to change the paths in smb.conf accordingly.

Hope it helps,

Next question, when new version of Java?
Scheduled after next Firefox 45 (in the works) and Qt 5.x.

We had the number of our bank account always on our contact page at
from the very start of bitwise works in April 2012.

Kind regards,
Herwig B.
CFO bww bitwise works GmbH.

Applications / Re: REXX libraries 1.1.1 (from Samba 1.3)
« on: December 15, 2016, 07:44:15 am »
A few thoughts:

Seeing a server but not its shares: This may be a result of disabling the guest account and/or denieing browsing rights to it.

EVFSGUI shows in which user context the browsing is done. Usually it tries both, context of the logged in user and guest. In case there is no login, the context will be guest only.

The guest account is mandatory.

Applications / Re: REXX libraries 1.1.1 (from Samba 1.3)
« on: December 14, 2016, 11:17:04 am »
I had that running in a test env some time in the past - however that is long gone (tdb stuff made everything other stall for a long time :-( ).

While some Samba/CUPS info ist definitely on my todo-list, it simply does not exist yet.

As soon as I start this will be my starting point

Applications / Re: REXX libraries 1.1.1 (from Samba 1.3)
« on: December 13, 2016, 11:12:12 am »
@David McKenna: Looks like you are missing the smbprint.exe utility. It wasn't included, sscc however assumes, it is there. Sorry, here it is:

Rx4Smb.WPI has been updated once more yesterday (really updated outdated pr2utill.dll)

We accidentally disabled winbind building some time ago.
Here is the winbind package

Applications / Re: REXX libraries 1.1.1 (from Samba 1.3)
« on: December 11, 2016, 10:40:23 am »

no excuse needed ;-) Netlabs host many projects and Adrian still provides access rights. However the work behind most of the stuff is doen by bitwisers.

Regarding winbindd.exe - we did not put it in as it is completely untested. The same applies to its companion wbinfo.exe.

We have built both files, so I can but them into a separate package.


Applications / Re: REXX libraries 1.1.1 (from Samba 1.3)
« on: December 10, 2016, 07:07:01 am »
I have put up a (final) updated WPI for rx4smb.wpi

- updated pr1util from 1.64 to Paul Ratcliffes last 1.65
- added Alex Taylor VROBJEX.DLL as it is used by all the Samba GUI Tools

Just a sidenote: All efforts to provide the updated Samba Server package were done by bitwise works.

Applications / Re: REXX libraries 1.1.1 (from Samba 1.3)
« on: December 09, 2016, 07:07:04 pm »
b4smb.cmd is just a "plugin" - a script just run before Samba. No change intended there AFAIR.

Applications / Re: REXX libraries 1.1.1 (from Samba 1.3)
« on: December 09, 2016, 07:10:13 am »
what you see are genuine TCP/IP problems, not Samba.

Please note:
2.) the nmbd stuff (which is responsible for browsing and "seeing" stuff is cached in various buffers in various machines - changing the IP of a running server ist asking for troubles - I know that from my own (test) setups. I may take some time until an IP change has spread to every machine on a network.

Applications / Re: REXX libraries 1.1.1 (from Samba 1.3)
« on: December 09, 2016, 07:04:52 am »
Regarding the rx4smblib directories on OS/2 (and later ArcaOS)
- Rather sooner than later this will be available as a rpm/yum package and therefore end up in %unixroot%\usr\lib, however we do not endores to put stuff manually there.
- I suggest to put them in \os2\apps\dll or \os2\dll on "pure" OS/2 4.52 systems for now.

As for the version number of vrobj.dll: Watcom couldn't really decide which version number scheme to use - 2.14 = 2.1d (d being 4th in a b c d). Both schemes are found within the product. The 900k version is not lxlited, but otherwise correct.

Pages: 1 [2] 3