Hi,
I'm quoting inline with ">", else this will take all night.
>let's read your messages again,
Wow, that's different from the usual russian statement "You don't understand. I repeat.".
>we can't claim the scout of os2.org site.
Where did all that news come from if not you? Someone at os2.org invented it?
And nevertheless: If you write *1* _good_ announcement, that would be no problem. What you write is a bunch of information without form and structure.
>Read the official announcement "ACPI 3.17 + ACPI tools", ignore unofficial.
How can I differentiate this? And why should I?
Also, if you create CENTRALIZED information, I can simply ignore everything and go the one-and-only website that has all relevant information.
>If no official messages then unofficial news are useful.
Huh? Didn't you say I should ignore them?
>Again, we appreciate the efforts of os2.org news scouts.
>Today there are extra news, tomorrow only official message is published.
And the after, you send out the useful one?
All this wouldn't be a problem if you had *1* website that explains things well. For END-USERS.
Hold it, hold it! I know: You don't see problems here...
> 2) you requested for All-in-one package - ACPI Heavy package is available.
> Users which are testing ACPI since 2005 are using ACPI Fast Upgrade .wpi
How should I know that this package is only for people already testing ACPI if I am _NEW_ to testing ACPI and YOU didn't tell me anywhere! We don't have crystal balls over here, bring me one from Russia next time...
> 3) "one-click" approach doesn't work.
Let's face it - you either simply don't know how to do it or you just want to avoid the extra mile.
Or you don't understand what I mean. Maybe I should repeat.
> As I said, every user has own PC model, specific problems.
> That's why every user should read the documentation.
No problem for me if there is a structured documentation in ONE place suitable for END-USERS.
You are brilliant in explaining what people should do...
> 4) "operating system is delivered as 1 package" - yes, and not all users are successful to install eCS,
(which is of course a problem of these people, not those making the operating system...)
>they have many troubles. That's why they are reading eCSFAQ brochure + call to support service
Yeah, brochure: Instead of writing the brochure you should write more code and save that brochure.
Or save time from brochure writing to clean up your web pages, do more support work, whatever.
Is that brochure delivered with eCS so people can read it when they see an error happen?
I don't think so. So what you do when people have a problem is handing them out a brochure?
>. The same with ACPI. One package is not enough, you need additional book (223 pages)
> + contact support service.
You aren't selling these books by any chance, do you?
How long did it take to write these books by the way?
And: One package _could_ be enough if everything is contained. *I* don't see a problem here
> 5) "I don't want to learn this because I don't want to know how it works."
> ACPI fully changes old OS/2 system, so every user should load additional kilobytes of knowledge to the head.
Let me ask you: When you look at your watch - are you interested in how it was built and how it internally works or are you mostly only interested in knowing what the time is? I know that eCS and ACPI may be your microcosmos but for other people, it is only a tool. They use it to achieve something different (e.g. writing an email). They certainly don't use it for understanding how ACPI works.
> 6) you write me how to write announcements. "if.. then.. url.." - yes,
That exactly is your problem: It is "if.. then.. url.." only from a high level. Take a close look.
> you repeat the structure of our announcements.
Maybe. But my announcement is better and yours is crap, therefore we are talking about it here.
Yours is a mess of cluttered and shattered pieces of information that only partly fit together. Here is a tip:
- Print your announcement on A4 paper
- Take a second sheet of paper
- Take a scissor and cut a 3cm x 10cm rectangular hole into the 2nd sheet
- Put the sheet with the hole above your announcement, and watch:
Everything that is intended for 1 specific target group needs to fit into that rectangle, otherwise it is bad structure.
Up yours, marketing man.
> There were announcements for every version + additional announcements in eCo Software
> newsletters + additional announcements of utils/special tests.
Which leads us back to the "mess"/"mass" of announcement whose existence you denied...
> We tried all kinds of announcements: "What is ACPI, .. Whatsnew: .., Join or die, .. We need your help.."
>- we are doing this since 2005. I don't see problems here.
Well, the problem is that you are trying since 2005. But no, you don't need help. Everythings is just brilliant.
> 7) We distribute the messages among 15-20 eCS/OS/2 sites.
> Yes, we submit the announcement directly via os2world.com web-form.
Except that you don't follow up when something apparently doesn't work.
That is just the same f***ing story you told last time when you screamed at us and we simply didn't get your message!
People are not monitoring 24/24 if someone posted something... sometimes things fail. Don't put the blame on us.
And frankly, when I submit a news item and it isn't published witin 1 hour, I simply try again. f that fails too, I leave a mail to the webmaster.
>

Yes, ACPI Heavy requires eCo Software runtime.
> eCS 2.0 is equipped with eCo Software runtime.
I have 2.0rc6a here. There is "some" eCo Software runtime on it, yes. But apparently _not_ all that is needed.
I repeat: This is not my problem, I didn't package the WPI.
> All other users should download the latest version from the homepage of the runtime.
Oops, sorry. I think I overlooked that information in your announcements... oh, no, wait:
It simply wasn't mentioned. That explains.
> It should be distributed from 1 site, else the users will use old/illegal versions.
Well you know, looking at what you packed into the WPI even distribution from 1 site will not really be of help...
> the link to the runtime is published at the homepage of ACPI. I don't see problems here.
Of course not, since you don't understand how to write a useful announcement - shall I repeat?
'nite.
Thomas