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] 4 5 ... 29
Utilities / Re: architecture/substitute of cmd.exe ?
« on: October 20, 2018, 12:41:52 pm »
Code: [Select]
Purpose:Create loops in batch files.

Format:DO [n | FOREVER]
DO varname = start TO end [BY n ]
DO [WHILE | UNTIL] condition
DO varname IN [@]set

varname : The environment variable that will hold the loop counter, filename, or line from a file.
n, start, end : Integers between 0 and 2,147,483,647 inclusive, or an internal variables or variable functions that evaluate to such a value.
condition : A test to determine if the loop should be executed.
set : A set of values for the variable.
commands : One or more commands to execute each time through the loop. If you use multiple commands, they must be separated by command separators or be placed on separate lines.

File Selection

Supports extended wildcards, ranges, and include lists for the set.


DO can only be used in batch files. It cannot be used in aliases.

DO can be used to create 4 different kinds of loops. The first, introduced by DO n, is a counted loop. The batch file lines between DO and ENDDO are repeated n times. For example:

        do 5
I thought this is standard even for cmd batch processing but seems to be a 4os2 extension.

Anyway even if you don't mind about 4os2 scripts/users it's just irritating for every programmer as probably every scripting or programming language does have a command named do.

Setup & Installation / Re: OS2 Warp Version 3 wont boot from Hard Drive
« on: October 19, 2018, 06:32:36 pm »
IIRC correctly newer IDE / ATA modes need 80pin cables to work reliable. But if you attach a device which is not capable of the higher data rate modes (UDMA 5/6?) then the whole IDE port is switched to the lower speed. So this MAYBE an explanation of what you're seeing. But this is all so long ago and my memory slowly vanish.

Anyway you should clearly see in the BIOS if the disk is detected and in which mode it is operated. Most BIOSes can switch to lower modes too. AFAIR selecting a lower mode (none of the UDMA ones) with 40 pin cables should be possible too.

Utilities / Re: DO.EXE new version commandline utility 1.99
« on: October 19, 2018, 06:26:28 pm »
do is used in REXX and cmd scripts. It's really a bad idea to name a program the same.

Applications / Re: VirtualBox v5.0.51 Testing
« on: October 18, 2018, 05:42:04 pm »
I have no write access to Netlabs' ftp,
FTP write access was disabled long ago. If you want to upload something you have to use WebDAV. The netdrive plugin works well.

Applications / Re: Seamonkey versions
« on: October 18, 2018, 07:55:43 am »
Don't forget to Remove the .; in front of LIBPATH and place it after the  x:\usr\local\lib;x:\usr\lib (or at the end).

Networking / Re: New xwlan beta - please test and give feedback
« on: October 12, 2018, 10:21:37 am »
I've also the impression that the wpa_supplicant is much faster most of the times. BUT not always. Sometimes it needs longer to establish the connection.

DHCP - I didn't see the problem Dough describes here. But I didn't test very much with DHCP since a while. In fact while building and testing new xwlan/wpa_supplicant I switched DHCP off. One thing that comes to mind - I think I've created a ticket long ago about that I think there is a logic error in the original xwlan code. IIRC xwlan fires up dhclient at the same time as wpa_supplicant (before the supplicant has negotiated the connection). If for some currently unknown reason the supplicant takes longer maybe the dhclient has increased it's pause period that much that Dough thinks it never asks and so gets a response. But this is all guessing. Someone has to dig into this. Starting point would be setting wpa_supplicant debug visible with Debuglevel Info and DHCP client Log NOT activated (to see the dhclient window, it is minimized by default, maximize it and see what the dhclient sciprt does).

Networking / Re: New xwlan beta - please test and give feedback
« on: October 11, 2018, 07:01:08 pm »
I've bundled together an intermediate version of wpa_supplicant with beta5 unfortunately. Was a stupid error in the script which packs all together and I didn't have the time for much testing before my travel. So I didn't find it by myself :-(.

I've fixed this and packed beta6. Beside small help file updates (history) it's the same as beta5 except the current wpa_supplicant. Hope the pmprintf.dll dependency is fixed finally.

It also seems that some sort of check needs to be made, to notify the user that something isn't right.
One of the first things I check with every new version is if the properties dialog shows the version for dhclient and wpa_supplicant. A non working wpa_supplicant would be shown in read color. Of course if you compare usability of the whole wlan/lan switching with modern devices/OSes we are years behind. I fear we can never catch up with other systems anymore. Best we can try is to keep it working and ironing out the biggest bugs.

It's also a good idea to start with the standalone application (wlanstat) first instead of the xcenter widget. And read the readme.txt step by step to narrow down problems (current version - Given that the user base with supported wlan devices is very small now and even shrinking I wouldn't bet on much improvement any more.

Networking / Re: New xwlan beta - please test and give feedback
« on: October 04, 2018, 11:32:20 am »
Strange. I reopened the ticket #49. Will look at it when I'm back. Thx for testing.

Networking / Re: New xwlan beta - please test and give feedback
« on: October 03, 2018, 07:52:21 am »
There is an undocumented dependency on PMPRINTF.
Even with beta5? My own checks with pmdll assured me that I've fixed that. But YMMV.

Networking / New xwlan beta - please test and give feedback
« on: October 02, 2018, 09:21:58 pm »
I've uploaded the new beta5 of xwlan.
I want to ask people who have a wireless NIC supported by genmac to test this version. I've made significant changes in a lot of places to improve some code and in debug message handling. I've cross checked all changes numerous times and think I did not break anything. Hope it works for others too the same as the latest versions. Or better.

Included is wpa_supplicant from current official code repository and Spanish language files.

Before I concentrate on other topics I wanted to assure all my current changes works as designed (do not break any functionality of previous versions).

Btw. you can create tickets or post here. Don't be offended when I can not answer questions the next week. I've to meet some sharks. But I'll be back afterwards :-)

Utilities / Re: architecture/substitute of cmd.exe ?
« on: October 01, 2018, 03:47:49 pm »
IMHO it's easier to take 4os2 sources and add and additional pm to overcomes the 8k character restriction. That's what TakeCommander did but unfortunately we do not have the sources. Some left overs are still in place though. In fact I started this with my 4os2 sources. I think it's easier to add a pm window to 4os2 than adding all the commands to an existing pm program like ME. Of course I'm biased ;)

Anyway the restrictions are the same. You have to redirect (or dup) stdin/stdout/stderr which makes the whole thing even more incompatible to standard cmd.exe. Regardless if you take 4os2 or your editor as base. Remember people even complain about 4os2 to cmd compatibility although it's nearly perfect.

For me Jonathan Pollards cmd replacement is useless cause we do not have the sources. And as I understand he is not willing to open source it. Beside that I did not found any good reason why I should learn his different syntax.

Beside JPs cmd replacement there are build in cmd shells (sort of) in VisualSlickEdit, NEDPM, LarsenCommander, ...? At least the VS implementation overcomes the 8k character limit. But it does not support ANSI colors. And I guess does have some resource problems (using it much for huge compile tasks makes it slow). And we do not have sources too. Maybe the NEDPM implementation is better. Hope aschn will comment on that here.

Multimedia / Re: [SBAWED2] Getting an old audio card working.
« on: September 21, 2018, 03:04:53 pm »
I think they only do not provide new/refreshed drivers for ISA cards and they do not spend time in supporting questions about. That makes sense to me cause if you're still using such ancient system with ISA cards you probably run an older version of OS/2 anyway. You need ArcaOS mainly for new hardware which requires ACPI and AHCI. Such systems do not provide ISA slots since many years.

AFAIK there is no OS driver needed to support ISA cards. So there is nothing to left out. You got the drivers for your old ISA card anyway when you bought them. And if the card ever worked with OS/2 on a specific system, I'm pretty sure it will do the same with ArcaOS.

and it is used for connecting to "legacy" hardware such as health monitoring chips on modern motherboards.
I do not know a single health sensor which is connected via ISA. They are usually on the SMI (I²C) or integrated in some chipset. Managed by PCI registers or older ones by legacy port I/O. So you need a driver which knows the commands for the sensor and the I/O port where it is connected. But that's not ISA.

Multimedia / Re: [SBAWED2] Getting an old audio card working.
« on: September 21, 2018, 01:54:50 pm »
What has changed sine then is that Arca Noae has removed ISA support from their system...
What do you mean by that? What specifically was removed?

General Discussion / Re: Open Source / 2
« on: September 20, 2018, 04:01:16 pm »
That API is huge, probably 50x more complex than it needs to be.
Needs to be for what? I'm pretty sure the complexity isn't there for it's own sake. Maybe you only didn't understand fully for what it's good for?

Something that is very PM in nature and function, but doesn't include the full API?
IMHO then it's no PM. It's another graphic engine with limited functionality. Zero applications and no GUI. Or do you think WPS and SOM runs on your lightweight version? What is the benefit compared to our working PM. I fore myself hardly see any need for such thing.

Applications / Re: SmartGit - Problem with File Mode (Modified (File Mode))
« on: September 17, 2018, 09:43:38 am »
I've read somewhere about 'core.autocrlf' setting 'true' is recommended for Win. Would this be a better option then fileMode? Or does it not work for us?

Pages: 1 2 [3] 4 5 ... 29