511
Comments, Suggestions & Questions / Re: Ecomstation 2.0 GA
« on: 2009.04.23, 22:42:20 »
As I see it, standing on the sideline looking in, there appears to be no co-ordination of the effort to get a GA out!
The base OS is OS/2 - which works.
Daniela has solved most of the drive problems.
Most common network cards have drivers.
Paul has given us a uniaud driver for the most common audio chipsets.
What is left that is important? ACPI and WiFi drivers.
So there are two areas to be worked on, ACPI and WiFi, to get a full working OS out of the door. Where is the hold up? Who is co-ordinating the effort? If no one then why not?
For both ACPI and WiFi there is a very reasonable amount of material available in the linux community, can much of this be applied to OS/2 like the uniaud project and others that Paul and others have ported for us? Or has the development of these essential parts degenerated to an ego pumping exercise? If this is the case then new developers should be found that will work in the project and see it to a successful conclusion.
Until the problems with ACPI and WiFi are solved all other tweeks should be relegated to secondary status to allow a working GA out to customers.
As it stands OS/2, through the medium of eCS and its long delay, is being relegated to an also-ran hobby OS - which I resent.
Since way back when OS/2 v2.1 arrived I have encouraged others to use OS/2. At the moment I am prevented from doing so because of the very limited availability of copies on places like eBay.
If Daniela, Paul and a few others can produce a wealth of drivers and programs in the time it has taken to get a part working ACPI layer ready - I must ask what is the problem? and will there ever be a GA of eCS?
The project co-ordinator need to come forward and give a truthful statement about what is going on before ALL credibility is lost, as I lost out on getting OS/2 into a small organisation today because I didn't have enough spare copies of OS/2 available.
The base OS is OS/2 - which works.
Daniela has solved most of the drive problems.
Most common network cards have drivers.
Paul has given us a uniaud driver for the most common audio chipsets.
What is left that is important? ACPI and WiFi drivers.
So there are two areas to be worked on, ACPI and WiFi, to get a full working OS out of the door. Where is the hold up? Who is co-ordinating the effort? If no one then why not?
For both ACPI and WiFi there is a very reasonable amount of material available in the linux community, can much of this be applied to OS/2 like the uniaud project and others that Paul and others have ported for us? Or has the development of these essential parts degenerated to an ego pumping exercise? If this is the case then new developers should be found that will work in the project and see it to a successful conclusion.
Until the problems with ACPI and WiFi are solved all other tweeks should be relegated to secondary status to allow a working GA out to customers.
As it stands OS/2, through the medium of eCS and its long delay, is being relegated to an also-ran hobby OS - which I resent.
Since way back when OS/2 v2.1 arrived I have encouraged others to use OS/2. At the moment I am prevented from doing so because of the very limited availability of copies on places like eBay.
If Daniela, Paul and a few others can produce a wealth of drivers and programs in the time it has taken to get a part working ACPI layer ready - I must ask what is the problem? and will there ever be a GA of eCS?
The project co-ordinator need to come forward and give a truthful statement about what is going on before ALL credibility is lost, as I lost out on getting OS/2 into a small organisation today because I didn't have enough spare copies of OS/2 available.