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 - Andi B.

Pages: [1] 2 3 ... 24
Setup & Installation / Re: RAM disk ... offtopic HPFS386
« on: April 19, 2018, 08:16:12 pm »
I've in config.sys

IFS=m:\IBM386FS\HPFS386.IFS /A:*

And a few notes like -
"REM ! EARLYMEMINIT=TRUE   unreming may be needed for JFS chkdsk on large volumes but does not work with HPFS386"
"REM ! HPFS386 does not work anymore with VIRTUALADDRESSLIMIT=2048 - too less memory, going back to VA = 1536"

Internet / Re: Firefox and Traps
« on: April 12, 2018, 01:19:31 pm »
Additionally to Lars statement about kernel internals it's simply a waste of memory (= scare resource given todays applications) when 'same' dlls are loaded more then once via LIBPATHSTRICT.

Practical experiments showed me that you can easily bring down OS/2 when playing with LIBPATHSTRICT and BEGINLIBPATH.

Internet / Re: Firefox and Traps
« on: April 12, 2018, 09:04:02 am »
One suggestion is to use cmd files to set up your environment for all your servers. Something like, and this is guess work about your programs,
set PATH=c:\weasel;%PATH%

Adjusting as needed for your various services. This should help with DLL hell

This may help for some situations. But I fear in Bens case it will make things worse. LIBPATHSTRICT and BEGINLIBPATH opens another can of worms. Limited resources (for todays needs) our OS can provide and handle is one of them. The list of services Ben wants to run is much over the limit LIBPATHSTRICT can work reliable IMHO. My advice is using LIBPATHSTRICT only for a single or two applications if really needed (running SM and FF in parallel for testing purposes). Not in any case for more than a few programs.

Ben has duplicate/wrong dlls. Probably spread all over his drives. He need to clean up this mess. One thing he can do is use f.i. DataSeeker (or another search tool which searches all drives) and search for every single dll FF needs with 'Search all drives' selected. And rename/delete all duplicates on all drives. Tools which only check the LIBPATH for dublicates (XWP or 'which' f.i.) do not help in Bens case as he has the .; in the LIBPATH and fear he does not want to delete it from there.

Internet / Re: Firefox and Traps
« on: April 11, 2018, 03:52:10 pm »
I did try it and it made some difference.

Which proved you have old dlls on your system. Anyway no big problem for FF if you set the .; correct. Now the second obvious question - do you have all needed dlls for your FF version? To be more precise did you enable netlabs exp repository or do you use an older FF version which does not need the exp dlls?

Internet / Re: Firefox and Traps
« on: April 11, 2018, 02:52:11 pm »
I think you did not show your LIBPATH in this thread nor said if you tried the .; after the unixroot directories. It does not matter if ANPM put it to the front. You can overwrite this or instruct ANPM to not change the correct setting (= after the unixroot dirs or at the end). IMHO putting .; in front of unixroot dirs was the wrong decision. The discussion about is in AN bugtracker. You never know if the 'right' dlls (for FF) are loaded if you do not set you LIBPATH correct (= unixroot dirs in front) in config.sys.

The other thing is if you want different Mozilla builds (FF, SM, Thunderbird, ...) running in parallel you HAVE to use LIBPATHSTRICT/BEGINLIBPATH. Simplest way is with RUN. Even if you close one application it's a good idea to check if it is really closed f.i. with TOP.

If I got it right you could not manage to run even one application (FF) immediately after boot. Most probably reason for such behavior is wrong or missing dlls. Newest SM/FF needs dlls from exp repositories I think.

Internet / Re: Firefox and Traps
« on: April 01, 2018, 07:36:56 pm »
I think that I will just rename my remaining dll folders temporarily, copy across the dll folders from another machine
Install all required dlls with ANPM or yum and make sure that your LIBPATH in config.sys starts with the %UNIXROOT% folders. MOVE THE .; ENTRY after the x:\USR\LOCAL\LIB;x:\USR\LIB; entries. Unfortunately ANPM do not do this for you.

Hardware / Re: How to find or extract a Postscript printer driver?
« on: March 25, 2018, 12:39:24 pm »
OTOH, the Generic Postscript (Enhanced) driver built in to PSPRINT usually works quite well. It supports colour, duplex, high resolutions, and a good set of standard paper sizes.
IIRC this driver does not allow less than 12.x mm margin form paper boarders. This was the reason why I started playing with importing ppd files some time ago. Is this quite true? Or do I mix things up here?

That may well be true, but it's a pretty specialized requirement for non-photo printers (most of which aren't Postscript anyway) and I'm Michael hasn't mentioned needing such a thing.
It's very common for printers to have minimum margins of 4-6mm. At least that's true for all the postscript printers I used the last two decades. And I need that very much.

You are right this is a bit OT in this thread. But as it has gotten your attention and this is a forum not the bug tracker ;-) I hope you can fix this for future releases. Thx.

Hardware / Re: How to find or extract a Postscript printer driver?
« on: March 22, 2018, 09:08:18 am »
OTOH, the Generic Postscript (Enhanced) driver built in to PSPRINT usually works quite well. It supports colour, duplex, high resolutions, and a good set of standard paper sizes.
IIRC this driver does not allow less than 12.x mm margin form paper boarders. This was the reason why I started playing with importing ppd files some time ago. Is this quite true? Or do I mix things up here?

Networking / Re: Test build wpa_supplicant v2.7
« on: March 18, 2018, 10:09:16 am »
I amended my .conf with ap_scan=2, this helped, works now

Good to hear. The .conf file is full of documentation. Honestly I've to say I do not understand what all the options are good for. I only enabled the build to allow .conf file cause someone asked it long ago in a ticket IIRC. I never used it by myself and so can do only very limited testing. This is one reason why I asked here for testers.

Feel free to open an issue at if you find any problem with the supplicant or here I guess you need to login there for doing that. No promise that anyone is fixed especially things I can not test. But sometimes even tickets opened years ago get fixed eventually :)

Networking / Re: Test build wpa_supplicant v2.7
« on: March 14, 2018, 01:49:22 pm »
Hi Andi, thanks for the update.
The readme.os2 needs updating to refer to where ArcaOS stores its wpa_supplicant.exe, namely x:\sys\apps\xwps\plugins\xcenter\xwlan
Thanks for the input.

After rebooting (is this needed? Perhaps add to readme.os2)
No. New wpa_supplicant is used whenever a new connection (profile) is established.

right clicking shows I'm now using wpa_supplicant v2.2 (eCS-v1) which I have to assume is correct.
Unfortunately this is wrong. Your version is what I supplied with xwlan3.12. The new one should identify itself with 'v2.7 (OS/2-v2beta)....'

Seems you didn't not copy it into the correct directory. Check 'right-click - properties - tab 'WPA supplicant' version and path'. Be aware wlanstat uses a different directory than the xwlan widget.

Networking / Test build wpa_supplicant v2.7
« on: March 13, 2018, 03:53:07 pm »
I've made a test build of the newest wpa_supplicant code and uploaded it to

It can be used together with current xwlan builds. From the readme.os2 -
Code: [Select]
BetaTester installation intructions
- replace installed wpa_supplicant.exe with the included one
When using xwlan widget wpa_supplicant is usually found in
When using the standalone wlanstat then in .\xwlan\.
- check if the new version is used by xwlan/wlanstat
right-click - properties - tab 'WPA supplicant' check version and path
- connect to wpa protected networks and post your findings at correspondending
thread at
- you can also test wpa_supplicant with a .conf file. F.i. set up a profile
with no security, switch on wireless and start wpa_supplicant manually
(f.i. wpa_supplicant.exe -i lan1 -cwpa_supplicant.conf)

If someone want to test feel free to post your findings here. If you're using the xcenter widget (in contrary to the standalone wlanstat.exe), be sure your ALT-F1 boot works or you've a working maintenance partition. I once saw a hang on my T60 at bootup of the xwlan widget with teh new wpa_supplicant.

Have fun.

Events / Re: IRC speakup with BWW this Saturday (3 of March)!
« on: March 07, 2018, 09:04:32 am »
Is there a summary of that somewhere? Didn't find anything at

Applications / Re: Curious about these old patches
« on: March 05, 2018, 07:01:38 pm »
I used newcalls years ago for systems with flash memory instead of a harddisk. I don't think it's very useful/necessary nowadays with SSD.

Comments, Suggestions & Questions / Re: Censorship complaints
« on: February 26, 2018, 01:41:12 pm »
And we should all remember the differences in languages and cultures represented here can make statements come across harsher than perhaps intended.
All true. But as Lars stated above this is not the case with ak120/Andreas Kohl. We the German native speakers know
  • it's not a language problem (if you read his statements you know he is very very good in English compared to most of the other Germans/Austrians/Swiss here)
  • it's not a cultural problem (maybe some very slight damage given by the long ago punishment in Eastern Germany. But all other Ex-DDR guys I know handle that much better)
  • it's a personal problem with him which drives people crazy even in the German forum
  • he's very often offtopic and gives irrelevant inputs (constantly talks about ancient hard-/software no one else uses since ages nor the thread starter does)
  • constantly wants to demonstrate he, and only he, is right and knowledgeable
On the other hand he has some very deep knowledge in some fields and sometimes (unfortunately not very often) gives very valuable information.

Article Discussions / Re: AN changing USB driver stack to 32-bit
« on: January 28, 2018, 08:46:10 pm »
Andi, you write about testers but the problem is just what are they testing on?
Where is the problem here? I guess if testers were paid by AN or by any other individual or company they will test what they get paid for. Otherwise they will test what they are interested in and with hardware they have.

If you want better support for your individual hardware you can open tickets in the bugtracker. If you want even better support I guess AN is happy to take your money and will invest in better support for your specific hardware. But it's up to AN to decide on that.

Pages: [1] 2 3 ... 24