eComStation includes a new REXX API that enhances and provides new
functionality for REXX applications.

The new API is contained in a DLL that first shipped with eComStation
v1.1 called ECSRXLIB.DLL

The new API provides these new calls to REXX programs and utilities:

rc=ECSLOADFUNCS([version])
[version] name of the variable to store the version number in

rc=ECSDROPFUNCS()

rc=ECSSTARTPROGRAMME(, [parameters], [environment],
[starttype], [startfocus], [startoptions], [cause])
Programme file
[parameters] Parameters for the programme
[environment] Environment variables separated by a |
[starttype] OS2F(ULL)|OS2W(IN)|OS2P(M)|DOSF(ULL)|DOSW(IN)|DE(F AULT)
[startfocus] F(OREGROUND)|B(ACKGROUND)
[startoptions] P(ARENT)|S(HELL)
[cause] Name of the variable to return the failure cause in

rc=ECSCOPY(, , [options], [cause])
A file
[options] A(PPEND)|R(EPLACE)|F(AIL)
[cause] Name of the variable to return the failure cause in

rc=ECSDELETE(, [force], [recoverable], [cause])
A file
[force] F(ORCE)|N(OFORCE)
[recoverable] R(ECOVERABLE)|N(OTRECOVERABLE)
[cause] Name of the variable to return the failure cause in

rc=ECSCLOSEOBJECT()<br /> <title> Title of the object in the switchlist<br /> <br /> rc=ECSQUERYSWITCHLIST(<variable>)<br /> <variable> Name of the variable to use as stem to return the switchlist<br /> <br /> rc=ECSDELTREE(<file>, [force], [cause])<br /> <file> File to delete<br /> [force] F(ORCE)|N(OFORCE)<br /> [cause] Name of the variable to return the failure cause in<br /> <br /> rc=ECSMAKEPATH(<path>, [cause])<br /> <path> Path to create, either relative or absolute<br /> [cause] Name of the variable to return the failure cause in<br /> <br /> Return code is always 0 (FALSE) or 1 (TRUE)<br /> [cause] is only set if the return code is false<br /> <br /> <br /> Here is some sample code to use these new calls:<br /> <br /> /* Load New eComStation REXX API */<br /> IF LoadECSlib() THEN RETURN 1<br /> LoadRexxUtil:<br /> <br /> IF RxFuncQuery('SysLoadFuncs') <> 0 THEN<br /> DO<br /> IF RxFuncAdd('SysLoadFuncs','RexxUtil','SysLoadFuncs' ) THEN<br /> RETURN 1<br /> CALL SysLoadFuncs<br /> END<br /> RETURN 0<br /> <br /> LoadECSLib:<br /> <br /> IF RxFuncQuery('eCSLoadFuncs') <> 0 THEN<br /> DO<br /> IF RxFuncAdd('eCSLoadFuncs','ECSRXLIB','eCSLoadFuncs' ) THEN<br /> RETURN 1<br /> CALL eCSLoadFuncs<br /> END<br /> RETURN 0<br /> <br /> <br /> This new API provides the REXX programmer enhanced functions and new<br /> functions.<br /> The new eCSCopy() call is one such example that provides the ability to<br /> copy files and overwrite existing ones. Standard OS/2 only allowed this<br /> function using the limited internal OS/2 Copy command. The new<br /> eCSCopy() call dosn't require a new command session to be started and<br /> can take advantabe of dynamic increases in file handles on a per<br /> session basis.<br /> <br /> Another nice addition is the 'cause' parameter which allows more in<br /> depth error reporting from the calls.<br /> <br /> This new REXX API is another example of the great value that you get<br /> with eComStation, making it easier for software developers and users<br /> alike to use there "operating platform of choice"!<br /> <br /> Regards,<br /> <br /> Jeramie Samphere<br /> President,<br /> OS2eCS Organization<br /> <a onclick="_gaq.push(['_trackEvent', 'Outgoing', 'www.os2ecs.org', '']);" rel="nofollow" href="http://www.os2ecs.org" target="_blank">www.os2ecs.org</a><br /> <br /> <!-- google_ad_section_end --> </blockquote> </div> </div> </div> <div class="cleardiv"></div> </div> </div> <div class="postfoot"> <div id="vbseo_vhtml_3"></div> </div> <hr /> </li> <li class="postbitlegacy postbitim postcontainer" id="post_145482"> <div class="posthead"> <div id="vbseo_vhtml_4"></div> </div> <div class="postdetails"> <div class="userinfo"> <div id="vbseo_vhtml_2"></div> </div> <div class="postbody"> <div class="postrow"> <h2 class="title icon"> <!-- google_ad_section_start -->Re: New API included in eComStation<!-- google_ad_section_end --> </h2> <div class="content"> <div id="post_message_145482"> <blockquote class="postcontent restore "> <!-- google_ad_section_start -->Captain's log. On StarDate 9 Apr 2005 00:35:55 -0700 received comm from<br /> <a href="mailto:ecsrulez@os2ecs.org">ecsrulez@os2ecs.org</a> on channel comp.os.os2.misc:<br /> <br /> : eComStation includes a new REXX API that enhances and provides new<br /> : functionality for REXX applications.<br /> <br /> A quick thought; is it really that smart to split and fraction the already too<br /> small tiny OS/2/eCS-market in two camps by introducing and using different<br /> incompatible set of API's?<br /> <br /> Perhaps it really is worth it for the improved functionallity (Linux and Windows<br /> always moves forward with new APIs and driver model enhancements), but on the<br /> other hand I wonder how this will affect the already scarce resources and little<br /> programming talent left?<br /> <br /> Just a question, I'm not saying it's 100% wrong.<br /> <br /> martin törnsten<br /> <br /> --<br /> <a href="mailto:martinot@gmail.com">martinot@gmail.com</a><br /> <!-- google_ad_section_end --> </blockquote> </div> </div> </div> <div class="cleardiv"></div> </div> </div> <div class="postfoot"> <div id="vbseo_vhtml_6"></div> </div> <hr /> </li> <li class="postbitlegacy postbitim postcontainer" id="post_145483"> <div class="posthead"> <div id="vbseo_vhtml_7"></div> </div> <div class="postdetails"> <div class="userinfo"> <div id="vbseo_vhtml_2"></div> </div> <div class="postbody"> <div class="postrow"> <h2 class="title icon"> <!-- google_ad_section_start -->Re: New API included in eComStation<!-- google_ad_section_end --> </h2> <div class="content"> <div id="post_message_145483"> <blockquote class="postcontent restore "> <!-- google_ad_section_start -->On Sat, 9 Apr 2005 11:22:40 UTC, Martin T÷rnsten <martinot@gmail.com><br /> wrote:<br /> <font color="blue"><br /> > Captain's log. On StarDate 9 Apr 2005 00:35:55 -0700 received comm from<br /> > <a href="mailto:ecsrulez@os2ecs.org">ecsrulez@os2ecs.org</a> on channel comp.os.os2.misc:<br /> ><br /> > : eComStation includes a new REXX API that enhances and provides new<br /> > : functionality for REXX applications.<br /> ><br /> > A quick thought; is it really that smart to split and fraction the already too<br /> > small tiny OS/2/eCS-market in two camps by introducing and using different<br /> > incompatible set of API's?<br /> ><br /> > Perhaps it really is worth it for the improved functionallity (Linux and Windows<br /> > always moves forward with new APIs and driver model enhancements), but on the<br /> > other hand I wonder how this will affect the already scarce resources and little<br /> > programming talent left?<br /> ><br /> > Just a question, I'm not saying it's 100% wrong.</font><br /> <br /> Without ongoing developement a system will die.<br /> <br /> A new set of APIs is the base easy developement. Look at the IBM<br /> toolkit! There are a lot of kernel APIs unknown in OS/2 WARP 3 and<br /> OS/2 WARP 4.0.<br /> <br /> You means really that any API to any system should be get frozen for<br /> all time? Then answer please the questions:<br /> <br /> - why got OS/2 WARP4 a lot of new APIs not known in OS/2 WARP3 and why<br /> was WARP3<br /> released with lots of new APIs to OS/2 2.1 and 2.0?<br /> - why gets programming languages new APIs with each new version?<br /> Should be frozen for all time?<br /> <br /> Reality is: when a system is not only in maintenance but developement<br /> state then you will alive new APIs continually. New APIs are the best<br /> way to show up that a system is developed not only maintenced.<br /> <br /> OS/2 WARP4 is out of developement since about a full decade now.<br /> Anything IBM has done in the last decade was only maintenance.<br /> <br /> eCS gets started with the plan to go back to develope state. That<br /> requires that there will be a new set of APIs to use with the new<br /> versions. So be happy that there is developement done to win new users<br /> and not only maintenance to hold long years old current users.<br /> <br /> In your meaning one has even NOT trying to write new applications -<br /> because there are so many DOS applications out that one can never<br /> write new ones.<br /> <br /> As there is Netscape 4.61 there is no need to write and develope a new<br /> WEB broser as this comes with abilities incompatible to old ones.<br /> <br /> You says that there is no need for USB - as OS/2 WARP4 knows nothing<br /> about that. There is no need.... as WARP4 knows nothing about<br /> that........,<br /> <br /> On other hand something times out dayly - other things are coming<br /> really new from scratch - so developement is needed to hold a system<br /> alive. That is what e.g. the eCS REXX APIs are - new functionality you<br /> would use to make lots of things more simple.<br /> <br /> --<br /> Tschau/Bye<br /> Herbert<br /> <br /> Visit <a onclick="_gaq.push(['_trackEvent', 'Outgoing', 'www.ecomstation.de', '']);" rel="nofollow" href="http://www.ecomstation.de" target="_blank">http://www.ecomstation.de</a> the home of german eComStation<br /> eComStation 1.2 Deutsch ist da!<br /> <!-- google_ad_section_end --> </blockquote> </div> </div> </div> <div class="cleardiv"></div> </div> </div> <div class="postfoot"> <div id="vbseo_vhtml_9"></div> </div> <hr /> </li> <li class="postbitlegacy postbitim postcontainer" id="post_145484"> <div class="posthead"> <div id="vbseo_vhtml_10"></div> </div> <div class="postdetails"> <div class="userinfo"> <div id="vbseo_vhtml_2"></div> </div> <div class="postbody"> <div class="postrow"> <h2 class="title icon"> <!-- google_ad_section_start -->Re: New API included in eComStation<!-- google_ad_section_end --> </h2> <div class="content"> <div id="post_message_145484"> <blockquote class="postcontent restore "> <!-- google_ad_section_start -->Herbert Rosenau wrote:<font color="blue"><br /> > On Sat, 9 Apr 2005 11:22:40 UTC, Martin T÷rnsten <martinot@gmail.com><br /> > wrote:<br /> ><br /> ><font color="green"><br /> >>Captain's log. On StarDate 9 Apr 2005 00:35:55 -0700 received comm from<br /> >>ecsrulez@os2ecs.org on channel comp.os.os2.misc:<br /> >><br /> >>: eComStation includes a new REXX API that enhances and provides new<br /> >>: functionality for REXX applications.<br /> >><br /> >>A quick thought; is it really that smart to split and fraction the already too<br /> >>small tiny OS/2/eCS-market in two camps by introducing and using different<br /> >>incompatible set of API's?<br /> >><br /> >>Perhaps it really is worth it for the improved functionallity (Linux and Windows<br /> >>always moves forward with new APIs and driver model enhancements), but on the<br /> >>other hand I wonder how this will affect the already scarce resources and little<br /> >>programming talent left?<br /> >><br /> >>Just a question, I'm not saying it's 100% wrong.</font><br /> ><br /> ><br /> > Without ongoing developement a system will die.<br /> ><br /> > A new set of APIs is the base easy developement. Look at the IBM<br /> > toolkit! There are a lot of kernel APIs unknown in OS/2 WARP 3 and<br /> > OS/2 WARP 4.0.<br /> ><br /> > You means really that any API to any system should be get frozen for<br /> > all time? Then answer please the questions:<br /> ><br /> > - why got OS/2 WARP4 a lot of new APIs not known in OS/2 WARP3 and why<br /> > was WARP3<br /> > released with lots of new APIs to OS/2 2.1 and 2.0?<br /> > - why gets programming languages new APIs with each new version?<br /> > Should be frozen for all time?<br /> ><br /> > Reality is: when a system is not only in maintenance but developement<br /> > state then you will alive new APIs continually. New APIs are the best<br /> > way to show up that a system is developed not only maintenced.<br /> ><br /> > OS/2 WARP4 is out of developement since about a full decade now.<br /> > Anything IBM has done in the last decade was only maintenance.<br /> ><br /> > eCS gets started with the plan to go back to develope state. That<br /> > requires that there will be a new set of APIs to use with the new<br /> > versions. So be happy that there is developement done to win new users<br /> > and not only maintenance to hold long years old current users.<br /> ><br /> > In your meaning one has even NOT trying to write new applications -<br /> > because there are so many DOS applications out that one can never<br /> > write new ones.<br /> ><br /> > As there is Netscape 4.61 there is no need to write and develope a new<br /> > WEB broser as this comes with abilities incompatible to old ones.<br /> ><br /> > You says that there is no need for USB - as OS/2 WARP4 knows nothing<br /> > about that. There is no need.... as WARP4 knows nothing about<br /> > that........,<br /> ><br /> > On other hand something times out dayly - other things are coming<br /> > really new from scratch - so developement is needed to hold a system<br /> > alive. That is what e.g. the eCS REXX APIs are - new functionality you<br /> > would use to make lots of things more simple.<br /> ></font><br /> <br /> I think you misunderstood Martin's point, Herbert. He wasn't saying<br /> that there shouldn't be any new APIs, but that any new API should be<br /> compatible with both "plain" OS/2 and eCS. Jeramie was saying that the<br /> new REXX DLL was only available for eCS - which may or may not be the<br /> case, I don't know.<br /> <br /> Stuart<br /> <!-- google_ad_section_end --> </blockquote> </div> </div> </div> <div class="cleardiv"></div> </div> </div> <div class="postfoot"> <div id="vbseo_vhtml_12"></div> </div> <hr /> </li> <li class="postbitlegacy postbitim postcontainer" id="post_145485"> <div class="posthead"> <div id="vbseo_vhtml_13"></div> </div> <div class="postdetails"> <div class="userinfo"> <div id="vbseo_vhtml_2"></div> </div> <div class="postbody"> <div class="postrow"> <h2 class="title icon"> <!-- google_ad_section_start -->Re: New API included in eComStation<!-- google_ad_section_end --> </h2> <div class="content"> <div id="post_message_145485"> <blockquote class="postcontent restore "> <!-- google_ad_section_start -->Captain's log. On StarDate Sat, 9 Apr 2005 11:49:22 +0000 (UTC) received comm<br /> from "Herbert Rosenau" <os2guy@pc-rosenau.de> on channel comp.os.os2.misc:<br /> <br /> Info posted about eCS specific enhancements (not in IBM OS/2):<br /> <br /> : > : eComStation includes a new REXX API that enhances and provides new<br /> : > : functionality for REXX applications.<br /> <br /> I raised a polite and (IMHO) rather relevant *question* (not any claim):<br /> <br /> : > Perhaps it really is worth it for the improved functionallity (Linux and Windows<br /> : > always moves forward with new APIs and driver model enhancements), but on the<br /> : > other hand I wonder how this will affect the already scarce resources and little<br /> : > programming talent left?<br /> <br /> <br /> You posted incorrect things attributed to me:<br /> <br /> : You means really that any API to any system should be get frozen for<br /> : all time? Then answer please the questions:<br /> <br /> [ snip ]<br /> <br /> : In your meaning one has even NOT trying to write new applications -<br /> : because there are so many DOS applications out that one can never<br /> : write new ones.<br /> <br /> [ snip ]<br /> <br /> : You says that there is no need for USB - as OS/2 WARP4 knows nothing<br /> : about that. There is no need.... as WARP4 knows nothing about<br /> : that........,<br /> <br /> You don't read too well Herbert.<br /> <br /> I'm all for new development. Windows, Linux, *BSD and Mac OS wouldn't be here in<br /> today shape if they wasn't changed and developed with new things. Same goes for<br /> development standards like Java and C#/.NET. It's mostly only a positive thing.<br /> <br /> I'm not against any development of OS/2. Quite the opposite. That's the reason<br /> why I'm generally very positive of SSI and eCS as they (in difference to IBM)<br /> actually do something new with the platform and provide new value. Another big<br /> problem (except new development of the core OS/2) is getting developers to<br /> support it with new and updated applications. That's also very important.<br /> <br /> To have new APIs could be a good thing to increase new and stronger development.<br /> What I (perhaps wrongly) thought about is if this also could be negative if IBM<br /> and SSI starts to fork their base system and API (not just the distribution and<br /> applications provided with it) and pose problems in increased cost and time for<br /> developers to support new API (which might not work on IBM OS/2 versions).<br /> <br /> I might be (and probably are)in error here, but nevertheless I thought it's<br /> still a risk to at least *consider*, both for and against (and perhaps not be<br /> irrelevant to ask about here, but I see it seems to be an issue who shouldn't be<br /> discussed or considered any further thoughts, even if it could be of strategic<br /> nature for future directions OS/2 and eCS takes).<br /> <br /> Sorry for raising the issue.<br /> <br /> martin törnsten<br /> <br /> --<br /> <a href="mailto:martinot@gmail.com">martinot@gmail.com</a><br /> <br /> <!-- google_ad_section_end --> </blockquote> </div> </div> </div> <div class="cleardiv"></div> </div> </div> <div class="postfoot"> <div id="vbseo_vhtml_15"></div> </div> <hr /> </li> <li class="postbitlegacy postbitim postcontainer" id="post_145486"> <div class="posthead"> <div id="vbseo_vhtml_16"></div> </div> <div class="postdetails"> <div class="userinfo"> <div id="vbseo_vhtml_2"></div> </div> <div class="postbody"> <div class="postrow"> <h2 class="title icon"> <!-- google_ad_section_start -->Re: New API included in eComStation<!-- google_ad_section_end --> </h2> <div class="content"> <div id="post_message_145486"> <blockquote class="postcontent restore "> <!-- google_ad_section_start --><br /> samphere, you asshole --> Stop spamming the OS2 news groups for ecs. Its dead product. booby can't pay his taxes, and IBM now sells OS2 for less then booby can buy it.<br /> <br /> PS: If you had a brain, you now where ecsrxlib.dll came from. Its wasn't ecs, and the fact that it was renamed to run under ecs, proves that ecs has modified the code or part of it -->thus proving that ecs is not the same thing as OS2 from IBM.<br /> <br /> <br /> <br /> <br /> <br /> In <1113032155.066605.130770@f14g2000cwb.googlegroups. com>, on 04/09/2005<br /> at 12:35 AM, <a href="mailto:ecsrulez@os2ecs.org">ecsrulez@os2ecs.org</a> said:<br /> <font color="blue"><br /> >eComStation includes a new REXX API that enhances and provides new<br /> >functionality for REXX applications.</font><br /> <font color="blue"><br /> >The new API is contained in a DLL that first shipped with eComStation<br /> >v1.1 called ECSRXLIB.DLL</font><br /> <font color="blue"><br /> >The new API provides these new calls to REXX programs and utilities:</font><br /> <font color="blue"><br /> >rc=ECSLOADFUNCS([version])<br /> >[version] name of the variable to store the version number in</font><br /> <font color="blue"><br /> >rc=ECSDROPFUNCS()</font><br /> <font color="blue"><br /> >rc=ECSSTARTPROGRAMME(<programme>, [parameters], [environment],<br /> >[starttype], [startfocus], [startoptions], [cause]) <programme> Programme<br /> >file<br /> >[parameters] Parameters for the programme<br /> >[environment] Environment variables separated by a |<br /> >[starttype] OS2F(ULL)|OS2W(IN)|OS2P(M)|DOSF(ULL)|DOSW(IN)|DE(F AULT)<br /> >[startfocus] F(OREGROUND)|B(ACKGROUND)<br /> >[startoptions] P(ARENT)|S(HELL)<br /> >[cause] Name of the variable to return the failure cause in</font><br /> <font color="blue"><br /> >rc=ECSCOPY(<source>, <target>, [options], [cause])<br /> ><file> A file<br /> >[options] A(PPEND)|R(EPLACE)|F(AIL)<br /> >[cause] Name of the variable to return the failure cause in</font><br /> <font color="blue"><br /> >rc=ECSDELETE(<file>, [force], [recoverable], [cause])<br /> ><file> A file<br /> >[force] F(ORCE)|N(OFORCE)<br /> >[recoverable] R(ECOVERABLE)|N(OTRECOVERABLE)<br /> >[cause] Name of the variable to return the failure cause in</font><br /> <font color="blue"><br /> >rc=ECSCLOSEOBJECT(<title>)<br /> ><title> Title of the object in the switchlist</font><br /> <font color="blue"><br /> >rc=ECSQUERYSWITCHLIST(<variable>)<br /> ><variable> Name of the variable to use as stem to return the switchlist</font><br /> <font color="blue"><br /> >rc=ECSDELTREE(<file>, [force], [cause])<br /> ><file> File to delete<br /> >[force] F(ORCE)|N(OFORCE)<br /> >[cause] Name of the variable to return the failure cause in</font><br /> <font color="blue"><br /> >rc=ECSMAKEPATH(<path>, [cause])<br /> ><path> Path to create, either relative or absolute<br /> >[cause] Name of the variable to return the failure cause in</font><br /> <font color="blue"><br /> >Return code is always 0 (FALSE) or 1 (TRUE)<br /> >[cause] is only set if the return code is false</font><br /> <br /> <font color="blue"><br /> >Here is some sample code to use these new calls:</font><br /> <font color="blue"><br /> >/* Load New eComStation REXX API */<br /> > IF LoadECSlib() THEN RETURN 1<br /> >LoadRexxUtil:</font><br /> <font color="blue"><br /> >IF RxFuncQuery('SysLoadFuncs') <> 0 THEN<br /> > DO<br /> > IF RxFuncAdd('SysLoadFuncs','RexxUtil','SysLoadFuncs' ) THEN<br /> >RETURN 1<br /> > CALL SysLoadFuncs<br /> > END<br /> >RETURN 0</font><br /> <font color="blue"><br /> >LoadECSLib:</font><br /> <font color="blue"><br /> >IF RxFuncQuery('eCSLoadFuncs') <> 0 THEN<br /> > DO<br /> > IF RxFuncAdd('eCSLoadFuncs','ECSRXLIB','eCSLoadFuncs' ) THEN<br /> >RETURN 1<br /> > CALL eCSLoadFuncs<br /> > END<br /> >RETURN 0</font><br /> <br /> <font color="blue"><br /> >This new API provides the REXX programmer enhanced functions and new<br /> >functions.<br /> >The new eCSCopy() call is one such example that provides the ability to<br /> >copy files and overwrite existing ones. Standard OS/2 only allowed this<br /> >function using the limited internal OS/2 Copy command. The new eCSCopy()<br /> >call dosn't require a new command session to be started and can take<br /> >advantabe of dynamic increases in file handles on a per session basis.</font><br /> <font color="blue"><br /> >Another nice addition is the 'cause' parameter which allows more in depth<br /> >error reporting from the calls.</font><br /> <font color="blue"><br /> >This new REXX API is another example of the great value that you get with<br /> >eComStation, making it easier for software developers and users alike to<br /> >use there "operating platform of choice"!</font><br /> <font color="blue"><br /> >Regards,</font><br /> <font color="blue"><br /> >Jeramie Samphere<br /> >President,<br /> >OS2eCS Organization<br /> ><a onclick="_gaq.push(['_trackEvent', 'Outgoing', 'www.os2ecs.org', '']);" rel="nofollow" href="http://www.os2ecs.org" target="_blank">www.os2ecs.org</a></font><br /> <br /> <br /> <!-- google_ad_section_end --> </blockquote> </div> </div> </div> <div class="cleardiv"></div> </div> </div> <div class="postfoot"> <div id="vbseo_vhtml_18"></div> </div> <hr /> </li> <li class="postbitlegacy postbitim postcontainer" id="post_145488"> <div class="posthead"> <div id="vbseo_vhtml_19"></div> </div> <div class="postdetails"> <div class="userinfo"> <div id="vbseo_vhtml_2"></div> </div> <div class="postbody"> <div class="postrow"> <h2 class="title icon"> <!-- google_ad_section_start -->Re: New API included in eComStation<!-- google_ad_section_end --> </h2> <div class="content"> <div id="post_message_145488"> <blockquote class="postcontent restore "> <!-- google_ad_section_start -->On Sat, 9 Apr 2005 14:20:09 UTC, Martin T÷rnsten <martinot@gmail.com><br /> wrote:<br /> <font color="blue"><br /> > Captain's log. On StarDate Sat, 9 Apr 2005 11:49:22 +0000 (UTC) received comm<br /> > from "Herbert Rosenau" <os2guy@pc-rosenau.de> on channel comp.os.os2.misc:<br /> ><br /> > Info posted about eCS specific enhancements (not in IBM OS/2):<br /> ><br /> > : > : eComStation includes a new REXX API that enhances and provides new<br /> > : > : functionality for REXX applications.<br /> ><br /> > I raised a polite and (IMHO) rather relevant *question* (not any claim):<br /> ><br /> > : > Perhaps it really is worth it for the improved functionallity (Linux and Windows<br /> > : > always moves forward with new APIs and driver model enhancements), but on the<br /> > : > other hand I wonder how this will affect the already scarce resources and little<br /> > : > programming talent left?<br /> ><br /> ><br /> > You posted incorrect things attributed to me:<br /> ><br /> > : You means really that any API to any system should be get frozen for<br /> > : all time? Then answer please the questions:<br /> ><br /> > [ snip ]<br /> ><br /> > : In your meaning one has even NOT trying to write new applications -<br /> > : because there are so many DOS applications out that one can never<br /> > : write new ones.<br /> ><br /> > [ snip ]<br /> ><br /> > : You says that there is no need for USB - as OS/2 WARP4 knows nothing<br /> > : about that. There is no need.... as WARP4 knows nothing about<br /> > : that........,<br /> ><br /> > You don't read too well Herbert.<br /> ><br /> > I'm all for new development. Windows, Linux, *BSD and Mac OS wouldn't be here in<br /> > today shape if they wasn't changed and developed with new things. Same goes for<br /> > development standards like Java and C#/.NET. It's mostly only a positive thing.<br /> ><br /> > I'm not against any development of OS/2. Quite the opposite. That's the reason<br /> > why I'm generally very positive of SSI and eCS as they (in difference to IBM)<br /> > actually do something new with the platform and provide new value. Another big<br /> > problem (except new development of the core OS/2) is getting developers to<br /> > support it with new and updated applications. That's also very important.<br /> ><br /> > To have new APIs could be a good thing to increase new and stronger development.<br /> > What I (perhaps wrongly) thought about is if this also could be negative if IBM<br /> > and SSI starts to fork their base system and API (not just the distribution and<br /> > applications provided with it) and pose problems in increased cost and time for<br /> > developers to support new API (which might not work on IBM OS/2 versions).<br /> ><br /> > I might be (and probably are)in error here, but nevertheless I thought it's<br /> > still a risk to at least *consider*, both for and against (and perhaps not be<br /> > irrelevant to ask about here, but I see it seems to be an issue who shouldn't be<br /> > discussed or considered any further thoughts, even if it could be of strategic<br /> > nature for future directions OS/2 and eCS takes).<br /> ><br /> > Sorry for raising the issue.</font><br /> <br /> As sayed prior IBM has given up developement on OS/2 10 years ago.<br /> There is nothing that will give a split between an IBM OS/2 version<br /> that is younger than 10 years old any OEM OS/2 that will be released<br /> in the next 10 years. But there will be NEW developement on that.<br /> <br /> Incompatibilities? Paalication who would NOT fully runable on OS/2<br /> WARP 4.0 - there are some, even some directed already from IBM. e.g.<br /> compy.exe, xcopy.exe, cmd.exe from OS/2 WARP4.0 and older. They are<br /> unable to handle files > 2GB as introduced with WSoD and WARP 4.51/eCS<br /> 1.0 as they are using APIs not known in WARP4.0 but well known in<br /> WARP4.51 and newer. There are lots of applications released who would<br /> NOT work on OS/2 WARP3.<br /> <br /> multimedia - replaced by eCS alredy - holding something that is NOT<br /> 100% OS/2 multimedia.<br /> WPS: eCS contains some extensions who would NOT work completely on<br /> OS/2 WARP 3 or WARP4.0 because they use APIs not known on them.<br /> filesystems: there are applications not working on WARP3 or WARP4, at<br /> least not legally. Like LVM.EXE<br /> <br /> Time goes on - for ongoing developement is is needed that some new<br /> APIs gets introduced to get what applications needs.<br /> <br /> There are already lots of OEM OS/2's leaving IBM to OEMs. All of them<br /> have OEM extensions inside - and are insofar incompatible to the<br /> standard OS/2 released to public.<br /> <br /> IBM has OS/2 designed to get incompatible to itself! Because it has<br /> lots of OEM specific interfaces inside it - some are well hidden and<br /> never documented to public - some are published widenly.<br /> <br /> In future you will alive that eCS in newer versions will release APIs<br /> to its customers who hare not officially supported by IBM - as IBM has<br /> stopped supporting OS/2.<br /> <br /> And now go to hobbes, please and look around for the many APIs created<br /> from outside IBM already for OS/2. There are lots of DLLs containing<br /> REXX APIs, there are lots of DLLs written for different programming<br /> languages containing APIs for WARP3/4 PM and WPS. Some requires WARP4<br /> - so you can't use them on WARP3 or older.<br /> <br /> Does you already mean that nobody should release an API that does work<br /> with an OS newer than OS/2 1.0?<br /> <br /> Time goes on. An OS/2 in developement gets added new APIs from time to<br /> time - sometimes the release number will chang, sometimes not. Some<br /> dlls gets added to the base system, some other may be released as an<br /> option you have to pay separately, some others will be released as<br /> freeware - in all cases you will need the DLLs when you comes to a<br /> point to use them.<br /> <br /> Stopping developement because IBM may or (surley may not) release a<br /> newer version as the last (WARP 4.52) is stopping developement for it<br /> for ever.<br /> <br /> Look on, eCS is extended since 1.0. It conatins always emx 0.9d<br /> runtime - that makes it absolutely incompatible to IBM OS/2 where that<br /> package is never included in the base system - but any developer can<br /> simply write applications and dlls requiring the emx 0.9d runtime<br /> installed anyway.<br /> <br /> There are many applications delivered as free-, share- or payware who<br /> deliver some DLLs designed to be used by application developers to<br /> bind the solutions into other applications easy. That is done by<br /> documenting the APIs to the dlls and let use them from others. Anybody<br /> who has not the base package installed has no chance to use the<br /> application written by third party.<br /> <br /> Time goes on - developement for eCS and not only for an more than 10<br /> years old, even out of maintenance, base system is needed. Release of<br /> new functionality (APIs) is required to be ready to the future and not<br /> only to the past is required.<br /> <br /> --<br /> Tschau/Bye<br /> Herbert<br /> <br /> Visit <a onclick="_gaq.push(['_trackEvent', 'Outgoing', 'www.ecomstation.de', '']);" rel="nofollow" href="http://www.ecomstation.de" target="_blank">http://www.ecomstation.de</a> the home of german eComStation<br /> eComStation 1.2 Deutsch ist da!<br /> <!-- google_ad_section_end --> </blockquote> </div> </div> </div> <div class="cleardiv"></div> </div> </div> <div class="postfoot"> <div id="vbseo_vhtml_21"></div> </div> <hr /> </li> <li class="postbitlegacy postbitim postcontainer" id="post_145489"> <div class="posthead"> <div id="vbseo_vhtml_22"></div> </div> <div class="postdetails"> <div class="userinfo"> <div id="vbseo_vhtml_2"></div> </div> <div class="postbody"> <div class="postrow"> <h2 class="title icon"> <!-- google_ad_section_start -->Re: New API included in eComStation<!-- google_ad_section_end --> </h2> <div class="content"> <div id="post_message_145489"> <blockquote class="postcontent restore "> <!-- google_ad_section_start -->Hi Jeramie,<br /> <font color="blue"><br /> > This new REXX API is another example of the great value that you get<br /> > with eComStation, making it easier for software developers and users<br /> > alike to use there "operating platform of choice"!</font><br /> <br /> Thats very interesing, thanks for the hint.<br /> <br /> Is this DLL also available for OS/2 users? I'm using eCs for myself on<br /> <br /> different machines, but I would not use routines in my own programs<br /> if they are incompatible to Warp (at least as long as I'm able to use<br /> freely available and more compatible alternatives).<br /> <br /> regards<br /> --<br /> Frank Wochatz<br /> <!-- google_ad_section_end --> </blockquote> </div> </div> </div> <div class="cleardiv"></div> </div> </div> <div class="postfoot"> <div id="vbseo_vhtml_24"></div> </div> <hr /> </li> <li class="postbitlegacy postbitim postcontainer" id="post_145490"> <div class="posthead"> <div id="vbseo_vhtml_25"></div> </div> <div class="postdetails"> <div class="userinfo"> <div id="vbseo_vhtml_2"></div> </div> <div class="postbody"> <div class="postrow"> <h2 class="title icon"> <!-- google_ad_section_start -->Re: New API included in eComStation<!-- google_ad_section_end --> </h2> <div class="content"> <div id="post_message_145490"> <blockquote class="postcontent restore "> <!-- google_ad_section_start -->On Sat, 9 Apr 2005 11:55:49 UTC, Stuart Gray <srtgrayNOT@clara.co.uk><br /> wrote:<br /> <font color="blue"><br /> > Herbert Rosenau wrote:<font color="green"><br /> > > On Sat, 9 Apr 2005 11:22:40 UTC, Martin T÷rnsten <martinot@gmail.com><br /> > > wrote:<br /> > ><br /> > ><font color="darkred"><br /> > >>Captain's log. On StarDate 9 Apr 2005 00:35:55 -0700 received comm from<br /> > >>ecsrulez@os2ecs.org on channel comp.os.os2.misc:<br /> > >><br /> > >>: eComStation includes a new REXX API that enhances and provides new<br /> > >>: functionality for REXX applications.<br /> > >><br /> > >>A quick thought; is it really that smart to split and fraction the already too<br /> > >>small tiny OS/2/eCS-market in two camps by introducing and using different<br /> > >>incompatible set of API's?<br /> > >><br /> > >>Perhaps it really is worth it for the improved functionallity (Linux and Windows<br /> > >>always moves forward with new APIs and driver model enhancements), but on the<br /> > >>other hand I wonder how this will affect the already scarce resources and little<br /> > >>programming talent left?<br /> > >><br /> > >>Just a question, I'm not saying it's 100% wrong.</font><br /> > ><br /> > ><br /> > > Without ongoing developement a system will die.<br /> > ><br /> > > A new set of APIs is the base easy developement. Look at the IBM<br /> > > toolkit! There are a lot of kernel APIs unknown in OS/2 WARP 3 and<br /> > > OS/2 WARP 4.0.<br /> > ><br /> > > You means really that any API to any system should be get frozen for<br /> > > all time? Then answer please the questions:<br /> > ><br /> > > - why got OS/2 WARP4 a lot of new APIs not known in OS/2 WARP3 and why<br /> > > was WARP3<br /> > > released with lots of new APIs to OS/2 2.1 and 2.0?<br /> > > - why gets programming languages new APIs with each new version?<br /> > > Should be frozen for all time?<br /> > ><br /> > > Reality is: when a system is not only in maintenance but developement<br /> > > state then you will alive new APIs continually. New APIs are the best<br /> > > way to show up that a system is developed not only maintenced.<br /> > ><br /> > > OS/2 WARP4 is out of developement since about a full decade now.<br /> > > Anything IBM has done in the last decade was only maintenance.<br /> > ><br /> > > eCS gets started with the plan to go back to develope state. That<br /> > > requires that there will be a new set of APIs to use with the new<br /> > > versions. So be happy that there is developement done to win new users<br /> > > and not only maintenance to hold long years old current users.<br /> > ><br /> > > In your meaning one has even NOT trying to write new applications -<br /> > > because there are so many DOS applications out that one can never<br /> > > write new ones.<br /> > ><br /> > > As there is Netscape 4.61 there is no need to write and develope a new<br /> > > WEB broser as this comes with abilities incompatible to old ones.<br /> > ><br /> > > You says that there is no need for USB - as OS/2 WARP4 knows nothing<br /> > > about that. There is no need.... as WARP4 knows nothing about<br /> > > that........,<br /> > ><br /> > > On other hand something times out dayly - other things are coming<br /> > > really new from scratch - so developement is needed to hold a system<br /> > > alive. That is what e.g. the eCS REXX APIs are - new functionality you<br /> > > would use to make lots of things more simple.<br /> > ></font><br /> ><br /> > I think you misunderstood Martin's point, Herbert. He wasn't saying<br /> > that there shouldn't be any new APIs, but that any new API should be<br /> > compatible with both "plain" OS/2 and eCS. Jeramie was saying that the<br /> > new REXX DLL was only available for eCS - which may or may not be the<br /> > case, I don't know.</font><br /> <br /> Jemramie was saying that the DLL is getting installed with eCS - like<br /> emx 0.9d runtime and others. He say not that it is impossible to get<br /> it from somewhere else.<br /> <br /> Yes, it IS impossible to hold anything that will be released in future<br /> with eCS compatible with WARP4 because WARP4 is outdated since more<br /> than 10 years now - and even IBM itself has released lots of APIs in<br /> WARP4.51 who are incompatible to WARP4.0.<br /> <br /> Fact is that IBM will never release a newer version than WARP4.52,<br /> even as it may (or may not) come out with fixes until Dec. 31. 2006.<br /> Therefor the only chance to get developement is eCS.<br /> <br /> Developement can hold backward compatibility - but will never hold<br /> forward compatibility.<br /> <br /> --<br /> Tschau/Bye<br /> Herbert<br /> <br /> Visit <a onclick="_gaq.push(['_trackEvent', 'Outgoing', 'www.ecomstation.de', '']);" rel="nofollow" href="http://www.ecomstation.de" target="_blank">http://www.ecomstation.de</a> the home of german eComStation<br /> eComStation 1.2 Deutsch ist da!<br /> <!-- google_ad_section_end --> </blockquote> </div> </div> </div> <div class="cleardiv"></div> </div> </div> <div class="postfoot"> <div id="vbseo_vhtml_27"></div> </div> <hr /> </li> <li class="postbitlegacy postbitim postcontainer" id="post_145492"> <div class="posthead"> <div id="vbseo_vhtml_28"></div> </div> <div class="postdetails"> <div class="userinfo"> <div id="vbseo_vhtml_2"></div> </div> <div class="postbody"> <div class="postrow"> <h2 class="title icon"> <!-- google_ad_section_start -->Re: New API included in eComStation<!-- google_ad_section_end --> </h2> <div class="content"> <div id="post_message_145492"> <blockquote class="postcontent restore "> <!-- google_ad_section_start -->On Sat, 9 Apr 2005 14:20:09 UTC, Martin Törnsten <martinot@gmail.com><br /> wrote:<br /> <br /> -> I'm all for new development. Windows, Linux, *BSD and Mac OS wouldn't be here in<br /> -> today shape if they wasn't changed and developed with new things. Same goes for<br /> -> development standards like Java and C#/.NET. It's mostly only a positive thing.<br /> -><br /> -> I'm not against any development of OS/2. Quite the opposite. That's the reason<br /> -> why I'm generally very positive of SSI and eCS as they (in difference to IBM)<br /> -> actually do something new with the platform and provide new value. Another big<br /> -> problem (except new development of the core OS/2) is getting developers to<br /> -> support it with new and updated applications. That's also very important.<br /> -><br /> -> To have new APIs could be a good thing to increase new and stronger development.<br /> -> What I (perhaps wrongly) thought about is if this also could be negative if IBM<br /> -> and SSI starts to fork their base system and API (not just the distribution and<br /> -> applications provided with it) and pose problems in increased cost and time for<br /> -> developers to support new API (which might not work on IBM OS/2 versions).<br /> -><br /> <br /> There aren't going to be any new versions of OS/2 from IBM, so any<br /> further new development has to come from eCS. So long as the new APIs<br /> don't deprecate any older stuff then I don't see any real issue. Yes<br /> if someone writes to the new API functions, then they either have to<br /> make it clear their application will only run on the new system, or<br /> they need to provide a workaround for systems that lack the API.<br /> What's great is that there is still development being done.<br /> <br /> Mark<br /> <br /> --<br /> From the eComStation of Mark Dodel<br /> <br /> <a onclick="_gaq.push(['_trackEvent', 'Outgoing', 'www.os2voice.org', '']);" rel="nofollow" href="http://www.os2voice.org" target="_blank">http://www.os2voice.org</a><br /> Warpstock 2005, Where?/When? Stay tuned to - <a onclick="_gaq.push(['_trackEvent', 'Outgoing', 'www.warpstock.org', '']);" rel="nofollow" href="http://www.warpstock.org" target="_blank">http://www.warpstock.org</a><br /> <!-- google_ad_section_end --> </blockquote> </div> </div> </div> <div class="cleardiv"></div> </div> </div> <div class="postfoot"> <div id="vbseo_vhtml_30"></div> </div> <hr /> </li> <li class="postbitlegacy postbitim postcontainer" id="post_145493"> <div class="posthead"> <div id="vbseo_vhtml_31"></div> </div> <div class="postdetails"> <div class="userinfo"> <div id="vbseo_vhtml_2"></div> </div> <div class="postbody"> <div class="postrow"> <h2 class="title icon"> <!-- google_ad_section_start -->Re: New API included in eComStation<!-- google_ad_section_end --> </h2> <div class="content"> <div id="post_message_145493"> <blockquote class="postcontent restore "> <!-- google_ad_section_start -->In <hnJ1V440825y-pn2-IEZWd7d4Z1dk@athome>, on 04/09/2005<br /> at 04:50 PM, "Frank Wochatz" <frankwochatz@despammed.com> said:<br /> <font color="blue"><br /> >Hi Jeramie,</font><br /> <font color="blue"><font color="green"><br /> >> This new REXX API is another example of the great value that you get<br /> >> with eComStation, making it easier for software developers and users<br /> >> alike to use there "operating platform of choice"!</font></font><br /> <font color="blue"><br /> >Thats very interesing, thanks for the hint.</font><br /> <font color="blue"><br /> >Is this DLL also available for OS/2 users? I'm using eCs for myself on</font><br /> <br /> It was written for the OS2 version of rexx -- it was renamed so it could run on the hacking done to ecs.<br /> <br /> You people seem to think its something integral to OS2. Its rexx -->do you know what that is?<br /> <br /> <br /> <br /> <br /> <font color="blue"><br /> >different machines, but I would not use routines in my own programs if<br /> >they are incompatible to Warp (at least as long as I'm able to use<br /> >freely available and more compatible alternatives).</font><br /> <font color="blue"><br /> >regards</font><br /> <br /> <br /> <!-- google_ad_section_end --> </blockquote> </div> </div> </div> <div class="cleardiv"></div> </div> </div> <div class="postfoot"> <div id="vbseo_vhtml_33"></div> </div> <hr /> </li> <li class="postbitlegacy postbitim postcontainer" id="post_145494"> <div class="posthead"> <div id="vbseo_vhtml_34"></div> </div> <div class="postdetails"> <div class="userinfo"> <div id="vbseo_vhtml_2"></div> </div> <div class="postbody"> <div class="postrow"> <h2 class="title icon"> <!-- google_ad_section_start -->Re: New API included in eComStation<!-- google_ad_section_end --> </h2> <div class="content"> <div id="post_message_145494"> <blockquote class="postcontent restore "> <!-- google_ad_section_start -->In <cLdq6jdb1N4Q-pn2-bKNBFd9dE0ce@localhost>, on 04/09/2005<br /> at 12:03 PM, "Mark Dodel" <madodelNOSPAM@ptd.net> said:<br /> <font color="blue"><br /> >On Sat, 9 Apr 2005 14:20:09 UTC, Martin T÷rnsten <martinot@gmail.com><br /> >wrote:</font><br /> <font color="blue"><br /> >-> I'm all for new development. Windows, Linux, *BSD and Mac OS wouldn't<br /> >be here in -> today shape if they wasn't changed and developed with new<br /> >things. Same goes for -> development standards like Java and C#/.NET.<br /> >It's mostly only a positive thing. -><br /> >-> I'm not against any development of OS/2. Quite the opposite. That's<br /> >the reason -> why I'm generally very positive of SSI and eCS as they (in<br /> >difference to IBM) -> actually do something new with the platform and<br /> >provide new value. Another big -> problem (except new development of the<br /> >core OS/2) is getting developers to -> support it with new and updated<br /> >applications. That's also very important. -><br /> >-> To have new APIs could be a good thing to increase new and stronger<br /> >development. -> What I (perhaps wrongly) thought about is if this also<br /> >could be negative if IBM -> and SSI starts to fork their base system and<br /> >API (not just the distribution and -> applications provided with it) and<br /> >pose problems in increased cost and time for -> developers to support new<br /> >API (which might not work on IBM OS/2 versions). -></font><br /> <font color="blue"><br /> >There aren't going to be any new versions of OS/2 from IBM, so any<br /> >further new development has to come from eCS.</font><br /> <br /> Booby's sales are so low can't pay his annual business taxes, much less pay for development on a product that now costs more then OS2 from IBM.<br /> <br /> Now that you know the facts of life, get out of the OS2 newsgroups with your ecs shilling.<br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> So long as the new APIs<font color="blue"><br /> >don't deprecate any older stuff then I don't see any real issue. Yes if<br /> >someone writes to the new API functions, then they either have to make<br /> >it clear their application will only run on the new system, or they need<br /> >to provide a workaround for systems that lack the API. What's great is<br /> >that there is still development being done.</font><br /> <font color="blue"><br /> >Mark</font><br /> <br /> <br /> <br /> <!-- google_ad_section_end --> </blockquote> </div> </div> </div> <div class="cleardiv"></div> </div> </div> <div class="postfoot"> <div id="vbseo_vhtml_36"></div> </div> <hr /> </li> <li class="postbitlegacy postbitim postcontainer" id="post_145495"> <div class="posthead"> <div id="vbseo_vhtml_37"></div> </div> <div class="postdetails"> <div class="userinfo"> <div id="vbseo_vhtml_2"></div> </div> <div class="postbody"> <div class="postrow"> <h2 class="title icon"> <!-- google_ad_section_start -->Re: New API included in eComStation<!-- google_ad_section_end --> </h2> <div class="content"> <div id="post_message_145495"> <blockquote class="postcontent restore "> <!-- google_ad_section_start --><br /> Hubert, an rexx_dll is not for OS2 only.<br /> <br /> Do try to figure out what you're thinking before posting. Like ecs is not taking a new direction. Sales are so low booby can't pay his annual fees. Its a dead product.<br /> <br /> <br /> <br /> <br /> <br /> <br /> In <wmzsGguTDN6N-pn2-iRQU24OIeQGy@URANUS1.DV-ROSENAU.DE>, on 04/09/2005<br /> at 04:40 PM, "Herbert Rosenau" <os2guy@pc-rosenau.de> said:<br /> <font color="blue"><br /> >On Sat, 9 Apr 2005 14:20:09 UTC, Martin T÷rnsten <martinot@gmail.com><br /> >wrote:</font><br /> <font color="blue"><font color="green"><br /> >> Captain's log. On StarDate Sat, 9 Apr 2005 11:49:22 +0000 (UTC) received comm<br /> >> from "Herbert Rosenau" <os2guy@pc-rosenau.de> on channel comp.os.os2.misc:<br /> >><br /> >> Info posted about eCS specific enhancements (not in IBM OS/2):<br /> >><br /> >> : > : eComStation includes a new REXX API that enhances and provides new<br /> >> : > : functionality for REXX applications.<br /> >><br /> >> I raised a polite and (IMHO) rather relevant *question* (not any claim):<br /> >><br /> >> : > Perhaps it really is worth it for the improved functionallity (Linux and Windows<br /> >> : > always moves forward with new APIs and driver model enhancements), but on the<br /> >> : > other hand I wonder how this will affect the already scarce resources and little<br /> >> : > programming talent left?<br /> >><br /> >><br /> >> You posted incorrect things attributed to me:<br /> >><br /> >> : You means really that any API to any system should be get frozen for<br /> >> : all time? Then answer please the questions:<br /> >><br /> >> [ snip ]<br /> >><br /> >> : In your meaning one has even NOT trying to write new applications -<br /> >> : because there are so many DOS applications out that one can never<br /> >> : write new ones.<br /> >><br /> >> [ snip ]<br /> >><br /> >> : You says that there is no need for USB - as OS/2 WARP4 knows nothing<br /> >> : about that. There is no need.... as WARP4 knows nothing about<br /> >> : that........,<br /> >><br /> >> You don't read too well Herbert.<br /> >><br /> >> I'm all for new development. Windows, Linux, *BSD and Mac OS wouldn't be here in<br /> >> today shape if they wasn't changed and developed with new things. Same goes for<br /> >> development standards like Java and C#/.NET. It's mostly only a positive thing.<br /> >><br /> >> I'm not against any development of OS/2. Quite the opposite. That's the reason<br /> >> why I'm generally very positive of SSI and eCS as they (in difference to IBM)<br /> >> actually do something new with the platform and provide new value. Another big<br /> >> problem (except new development of the core OS/2) is getting developers to<br /> >> support it with new and updated applications. That's also very important.<br /> >><br /> >> To have new APIs could be a good thing to increase new and stronger development.<br /> >> What I (perhaps wrongly) thought about is if this also could be negative if IBM<br /> >> and SSI starts to fork their base system and API (not just the distribution and<br /> >> applications provided with it) and pose problems in increased cost and time for<br /> >> developers to support new API (which might not work on IBM OS/2 versions).<br /> >><br /> >> I might be (and probably are)in error here, but nevertheless I thought it's<br /> >> still a risk to at least *consider*, both for and against (and perhaps not be<br /> >> irrelevant to ask about here, but I see it seems to be an issue who shouldn't be<br /> >> discussed or considered any further thoughts, even if it could be of strategic<br /> >> nature for future directions OS/2 and eCS takes).<br /> >><br /> >> Sorry for raising the issue.</font></font><br /> <font color="blue"><br /> >As sayed prior IBM has given up developement on OS/2 10 years ago. There<br /> >is nothing that will give a split between an IBM OS/2 version that is<br /> >younger than 10 years old any OEM OS/2 that will be released in the next<br /> >10 years. But there will be NEW developement on that.</font><br /> <font color="blue"><br /> >Incompatibilities? Paalication who would NOT fully runable on OS/2 WARP<br /> >4.0 - there are some, even some directed already from IBM. e.g.<br /> >compy.exe, xcopy.exe, cmd.exe from OS/2 WARP4.0 and older. They are<br /> >unable to handle files > 2GB as introduced with WSoD and WARP 4.51/eCS<br /> >1.0 as they are using APIs not known in WARP4.0 but well known in<br /> >WARP4.51 and newer. There are lots of applications released who would<br /> >NOT work on OS/2 WARP3.</font><br /> <font color="blue"><br /> >multimedia - replaced by eCS alredy - holding something that is NOT 100%<br /> >OS/2 multimedia.<br /> >WPS: eCS contains some extensions who would NOT work completely on OS/2<br /> >WARP 3 or WARP4.0 because they use APIs not known on them. filesystems:<br /> >there are applications not working on WARP3 or WARP4, at least not<br /> >legally. Like LVM.EXE</font><br /> <font color="blue"><br /> >Time goes on - for ongoing developement is is needed that some new APIs<br /> >gets introduced to get what applications needs.</font><br /> <font color="blue"><br /> >There are already lots of OEM OS/2's leaving IBM to OEMs. All of them<br /> >have OEM extensions inside - and are insofar incompatible to the<br /> >standard OS/2 released to public.</font><br /> <font color="blue"><br /> >IBM has OS/2 designed to get incompatible to itself! Because it has lots<br /> >of OEM specific interfaces inside it - some are well hidden and never<br /> >documented to public - some are published widenly.</font><br /> <font color="blue"><br /> >In future you will alive that eCS in newer versions will release APIs to<br /> >its customers who hare not officially supported by IBM - as IBM has<br /> >stopped supporting OS/2.</font><br /> <font color="blue"><br /> >And now go to hobbes, please and look around for the many APIs created<br /> >from outside IBM already for OS/2. There are lots of DLLs containing<br /> >REXX APIs, there are lots of DLLs written for different programming<br /> >languages containing APIs for WARP3/4 PM and WPS. Some requires WARP4 -<br /> >so you can't use them on WARP3 or older.</font><br /> <font color="blue"><br /> >Does you already mean that nobody should release an API that does work<br /> >with an OS newer than OS/2 1.0?</font><br /> <font color="blue"><br /> >Time goes on. An OS/2 in developement gets added new APIs from time to<br /> >time - sometimes the release number will chang, sometimes not. Some dlls<br /> >gets added to the base system, some other may be released as an option<br /> >you have to pay separately, some others will be released as freeware -<br /> >in all cases you will need the DLLs when you comes to a point to use<br /> >them.</font><br /> <font color="blue"><br /> >Stopping developement because IBM may or (surley may not) release a<br /> >newer version as the last (WARP 4.52) is stopping developement for it<br /> >for ever.</font><br /> <font color="blue"><br /> >Look on, eCS is extended since 1.0. It conatins always emx 0.9d runtime<br /> >- that makes it absolutely incompatible to IBM OS/2 where that package is<br /> >never included in the base system - but any developer can simply write<br /> >applications and dlls requiring the emx 0.9d runtime installed anyway.</font><br /> <font color="blue"><br /> >There are many applications delivered as free-, share- or payware who<br /> >deliver some DLLs designed to be used by application developers to bind<br /> >the solutions into other applications easy. That is done by documenting<br /> >the APIs to the dlls and let use them from others. Anybody who has not<br /> >the base package installed has no chance to use the application written<br /> >by third party.</font><br /> <font color="blue"><br /> >Time goes on - developement for eCS and not only for an more than 10<br /> >years old, even out of maintenance, base system is needed. Release of<br /> >new functionality (APIs) is required to be ready to the future and not<br /> >only to the past is required.</font><br /> <br /> <br /> <br /> <!-- google_ad_section_end --> </blockquote> </div> </div> </div> <div class="cleardiv"></div> </div> </div> <div class="postfoot"> <div id="vbseo_vhtml_39"></div> </div> <hr /> </li> <li class="postbitlegacy postbitim postcontainer" id="post_145498"> <div class="posthead"> <div id="vbseo_vhtml_40"></div> </div> <div class="postdetails"> <div class="userinfo"> <div id="vbseo_vhtml_2"></div> </div> <div class="postbody"> <div class="postrow"> <h2 class="title icon"> <!-- google_ad_section_start -->Re: New API included in eComStation<!-- google_ad_section_end --> </h2> <div class="content"> <div id="post_message_145498"> <blockquote class="postcontent restore "> <!-- google_ad_section_start -->Hi Herbert,<br /> <br /> I think you have a very theoretical point of view.<br /> <br /> In practice, eCs has to loose if it will be incompatible<br /> to OS/2.<br /> <br /> The reason is that the application development<br /> is nearly at level zero. Ok, there are some free- and<br /> shareware developers, and one or two commercial<br /> companies, and three odinized windows apps<br /> which are working or even not ( I don't count the last<br /> one for productive environments).<br /> <br /> The trouble starts with GRADD under OS/2.<br /> Ok, it is nice to have GRADD-based SNAP for a wide<br /> range of graphic boards, but with GRADD a lot of<br /> applications are not longer usable under OS/2 and<br /> eCs.<br /> <br /> Actually for some of them there is no equivalent<br /> available. With GRADD we have lost some great<br /> and full featured programs like Impos/2 and Microgrfx<br /> Designer.<br /> <br /> And GRADD is only ONE example.<br /> <br /> In latest eCs 1.2 I have to deactivate some things<br /> to run my DCITU software. Fortunately, after days of<br /> searching I've found the system component to deactivate<br /> with some great help here at the news groups.<br /> There is no alternative for DCITU.<br /> <br /> Now I'm waiting for a new eCs version, where apps like<br /> Mesa2 or my own apps will not longer run.<br /> Then I will freeze the previous version and move<br /> to a completely other plattform later.<br /> <br /> The second point is that there are free and OS/2 - eCs<br /> compatible alternatives for above described Rexx API.<br /> It is not a brand new killer feature, there is absolutely no<br /> reason to use such things. Of course it makes it simpler, but<br /> it would be very easy to make such a dll available for<br /> OS/2 users, too. The eCs distributors takes enogh<br /> advantage of free and open source work, so I think this<br /> should not be problem.<br /> <br /> <br /> regards<br /> --<br /> Frank Wochatz<br /> <!-- google_ad_section_end --> </blockquote> </div> </div> </div> <div class="cleardiv"></div> </div> </div> <div class="postfoot"> <div id="vbseo_vhtml_42"></div> </div> <hr /> </li> <li class="postbitlegacy postbitim postcontainer" id="post_145500"> <div class="posthead"> <div id="vbseo_vhtml_43"></div> </div> <div class="postdetails"> <div class="userinfo"> <div id="vbseo_vhtml_2"></div> </div> <div class="postbody"> <div class="postrow"> <h2 class="title icon"> <!-- google_ad_section_start -->Re: New API included in eComStation<!-- google_ad_section_end --> </h2> <div class="content"> <div id="post_message_145500"> <blockquote class="postcontent restore "> <!-- google_ad_section_start -->Interesting post. Personally, I would prefer the 'standard OS/2' method<br /> for security reasons but that's probably a minor point if you alrady<br /> have a hostile REXX-ware running on your system. Your post, however,<br /> seems like you are advocating what you seem to feel is a significant<br /> feature of 'eCS' here in these newsgroups. For what reason are you<br /> doing that? Every one of the handful of readers here has either already<br /> bought 'eCS' or probably never will. If you really want to evangelize<br /> for 'eCS' why not do it somewhere where there might be some people who<br /> are interested? The single biggest thing holding back progress in<br /> 'eCS' is its miniscule user base which seems to be mostly just a small<br /> band of former OS/2 users. Why not reach out to Windows, Mac, and Linux<br /> users rather than spend your time trading posts here with OS/2 users?<br /> Wouldn't that be more helpful to the eCS you seem to like?<br /> <br /> <br /> <a href="mailto:ecsrulez@os2ecs.org">ecsrulez@os2ecs.org</a> wrote:<font color="blue"><br /> > eComStation includes a new REXX API that enhances and provides new<br /> > functionality for REXX applications.<br /> ><br /> > The new API is contained in a DLL that first shipped with eComStation<br /> > v1.1 called ECSRXLIB.DLL<br /> ><br /> > The new API provides these new calls to REXX programs and utilities:<br /> ><br /> > rc=ECSLOADFUNCS([version])<br /> > [version] name of the variable to store the version number in<br /> ><br /> > rc=ECSDROPFUNCS()<br /> ><br /> > rc=ECSSTARTPROGRAMME(<programme>, [parameters], [environment],<br /> > [starttype], [startfocus], [startoptions], [cause])<br /> > <programme> Programme file<br /> > [parameters] Parameters for the programme<br /> > [environment] Environment variables separated by a |<br /> > [starttype] OS2F(ULL)|OS2W(IN)|OS2P(M)|DOSF(ULL)|DOSW(IN)|DE(F AULT)<br /> > [startfocus] F(OREGROUND)|B(ACKGROUND)<br /> > [startoptions] P(ARENT)|S(HELL)<br /> > [cause] Name of the variable to return the failure cause in<br /> ><br /> > rc=ECSCOPY(<source>, <target>, [options], [cause])<br /> > <file> A file<br /> > [options] A(PPEND)|R(EPLACE)|F(AIL)<br /> > [cause] Name of the variable to return the failure cause in<br /> ><br /> > rc=ECSDELETE(<file>, [force], [recoverable], [cause])<br /> > <file> A file<br /> > [force] F(ORCE)|N(OFORCE)<br /> > [recoverable] R(ECOVERABLE)|N(OTRECOVERABLE)<br /> > [cause] Name of the variable to return the failure cause in<br /> ><br /> > rc=ECSCLOSEOBJECT(<title>)<br /> > <title> Title of the object in the switchlist<br /> ><br /> > rc=ECSQUERYSWITCHLIST(<variable>)<br /> > <variable> Name of the variable to use as stem to return the switchlist<br /> ><br /> > rc=ECSDELTREE(<file>, [force], [cause])<br /> > <file> File to delete<br /> > [force] F(ORCE)|N(OFORCE)<br /> > [cause] Name of the variable to return the failure cause in<br /> ><br /> > rc=ECSMAKEPATH(<path>, [cause])<br /> > <path> Path to create, either relative or absolute<br /> > [cause] Name of the variable to return the failure cause in<br /> ><br /> > Return code is always 0 (FALSE) or 1 (TRUE)<br /> > [cause] is only set if the return code is false<br /> ><br /> ><br /> > Here is some sample code to use these new calls:<br /> ><br /> > /* Load New eComStation REXX API */<br /> > IF LoadECSlib() THEN RETURN 1<br /> > LoadRexxUtil:<br /> ><br /> > IF RxFuncQuery('SysLoadFuncs') <> 0 THEN<br /> > DO<br /> > IF RxFuncAdd('SysLoadFuncs','RexxUtil','SysLoadFuncs' ) THEN<br /> > RETURN 1<br /> > CALL SysLoadFuncs<br /> > END<br /> > RETURN 0<br /> ><br /> > LoadECSLib:<br /> ><br /> > IF RxFuncQuery('eCSLoadFuncs') <> 0 THEN<br /> > DO<br /> > IF RxFuncAdd('eCSLoadFuncs','ECSRXLIB','eCSLoadFuncs' ) THEN<br /> > RETURN 1<br /> > CALL eCSLoadFuncs<br /> > END<br /> > RETURN 0<br /> ><br /> ><br /> > This new API provides the REXX programmer enhanced functions and new<br /> > functions.<br /> > The new eCSCopy() call is one such example that provides the ability to<br /> > copy files and overwrite existing ones. Standard OS/2 only allowed this<br /> > function using the limited internal OS/2 Copy command. The new<br /> > eCSCopy() call dosn't require a new command session to be started and<br /> > can take advantabe of dynamic increases in file handles on a per<br /> > session basis.<br /> ><br /> > Another nice addition is the 'cause' parameter which allows more in<br /> > depth error reporting from the calls.<br /> ><br /> > This new REXX API is another example of the great value that you get<br /> > with eComStation, making it easier for software developers and users<br /> > alike to use there "operating platform of choice"!<br /> ><br /> > Regards,<br /> ><br /> > Jeramie Samphere<br /> > President,<br /> > OS2eCS Organization<br /> > <a onclick="_gaq.push(['_trackEvent', 'Outgoing', 'www.os2ecs.org', '']);" rel="nofollow" href="http://www.os2ecs.org" target="_blank">www.os2ecs.org</a><br /> ></font><br /> <br /> <br /> --<br /> Posted with OS/2 Warp 4.52<br /> and IBM Web Browser v2.0.4<br /> <!-- google_ad_section_end --> </blockquote> </div> </div> </div> <div class="cleardiv"></div> </div> </div> <div class="postfoot"> <div id="vbseo_vhtml_45"></div> </div> <hr /> </li> <li class="postbitlegacy postbitim postcontainer" id="post_145509"> <div class="posthead"> <div id="vbseo_vhtml_46"></div> </div> <div class="postdetails"> <div class="userinfo"> <div id="vbseo_vhtml_2"></div> </div> <div class="postbody"> <div class="postrow"> <h2 class="title icon"> <!-- google_ad_section_start -->Re: New API included in eComStation<!-- google_ad_section_end --> </h2> <div class="content"> <div id="post_message_145509"> <blockquote class="postcontent restore "> <!-- google_ad_section_start -->Frank Wochatz wrote:<font color="blue"><br /> > Hi Jeramie,<br /> ><br /> ><font color="green"><br /> >>This new REXX API is another example of the great value that you get<br /> >>with eComStation, making it easier for software developers and users<br /> >>alike to use there "operating platform of choice"!</font><br /> ><br /> ><br /> > Thats very interesing, thanks for the hint.<br /> ><br /> > Is this DLL also available for OS/2 users? I'm using eCs for myself on<br /> ><br /> > different machines, but I would not use routines in my own programs<br /> > if they are incompatible to Warp (at least as long as I'm able to use<br /> > freely available and more compatible alternatives).<br /> ><br /> > regards</font><br /> Hello Frank,<br /> <br /> I'm not aware of this DLL being available for OS/2(its not on Hobbes).<br /> Furthermore, it has been included with eComStation since version 1.1<br /> In developing the installer for<br /> eThemes(<a onclick="_gaq.push(['_trackEvent', 'Outgoing', 'www.os2ecs.org', '/ethemes.html']);" rel="nofollow" href="http://www.os2ecs.org/ethemes.html" target="_blank">http://www.os2ecs.org/ethemes.html</a> I came accross some pretty<br /> serious limitations in copying large numbers of files with REXX's<br /> SysCopyObject or using the standard OS/2 Copy command. Utilizing the New<br /> REXX API included in eComStation (specifically the eCSCopy() call<br /> solved the problem.<br /> <br /> There comes a point when a developer must make some decisions. Do you<br /> continue to struggle trying to make your software run on different<br /> versions, or do you embrace the new standard and move forward? I believe<br /> eComStation is the new standard for OS/2 based applications and is worth<br /> moving forward with. I believe many OS/2 users recognize the value of<br /> eComStation as well. But the real value of eComStation is not just for<br /> existing OS/2 users, but the millions of Windows users who feel forced<br /> into a limiting system and become a slave to maintenance and slews of<br /> Anti-Virus, Aware, Spy ware, and Security issues. Why do they run<br /> Windows? Is it by choice?? No...they are given ONE choice(that is not<br /> choice...Choice is when you have at least three options before you..that<br /> is when you can make a REAL DECISION!)...a reinstalled Windows Operating<br /> System. Therefore they have no choice, they either buy the system with<br /> what they get or they don't buy it!<br /> <br /> In choosing the name of our organization (OS2eCS Organization), we<br /> derived it from the idea that we want to support existing OS/2(the past)<br /> users, but are encouraging users to move forward to eComStation which is<br /> the future! Migrating to eComStation solves 90% of issues people have<br /> running OS/2 apps on new hardware. It is simply ridiculous to spend<br /> countless hours trying to upgrade and patch OS/2(Specifically Warp 4)<br /> rather than spending a few bucks and upgrading to eComStation(unless you<br /> consider your time worthless). But of course eComStation is not just an<br /> upgraded OS/2...Its a supercharged OS/2 with tons of goodies to make<br /> your computer experience powerful and enjoyable!<br /> <br /> This is why we say..."Say eCS, its easy!" <img src="http://fixunix.com/images/smilies/smile.png" border="0" alt="" title="Smile" class="inlineimg" /><br /> <br /> Cheers!<br /> <br /> Jeramie Samphere<br /> President,<br /> OS2eCS Organization<br /> <a onclick="_gaq.push(['_trackEvent', 'Outgoing', 'www.os2ecs.org', '']);" rel="nofollow" href="http://www.os2ecs.org" target="_blank">www.os2ecs.org</a><br /> <!-- google_ad_section_end --> </blockquote> </div> </div> </div> <div class="cleardiv"></div> </div> </div> <div class="postfoot"> <div id="vbseo_vhtml_48"></div> </div> <hr /> </li> <li class="postbitlegacy postbitim postcontainer" id="post_145510"> <div class="posthead"> <div id="vbseo_vhtml_49"></div> </div> <div class="postdetails"> <div class="userinfo"> <div id="vbseo_vhtml_2"></div> </div> <div class="postbody"> <div class="postrow"> <h2 class="title icon"> <!-- google_ad_section_start -->Re: New API included in eComStation<!-- google_ad_section_end --> </h2> <div class="content"> <div id="post_message_145510"> <blockquote class="postcontent restore "> <!-- google_ad_section_start -->Here in comp.os.os2.misc,<br /> "Herbert Rosenau" <os2guy@pc-rosenau.de> spake unto us, saying:<br /> <font color="blue"><br /> >Without ongoing developement a system will die.</font><br /> <br /> While I agree that continued development is a good thing in general, it<br /> isn't strictly necessary. As long as a given platform is able to meet<br /> the needs of its users, it will continue to be viable (with or without<br /> actual growth) to some of its existing users.<br /> <font color="blue"><br /> >OS/2 WARP4 is out of developement since about a full decade now.<br /> >Anything IBM has done in the last decade was only maintenance.</font><br /> <br /> One could argue that the adding of USB support, LVM, JFS, and a number<br /> of other things to OS/2 went well beyond traditional maintenance. :-)<br /> <br /> --<br /> -Rich Steiner >>>---> <a onclick="_gaq.push(['_trackEvent', 'Outgoing', 'www.visi.com', '/~rsteiner']);" rel="nofollow" href="http://www.visi.com/~rsteiner" target="_blank">http://www.visi.com/~rsteiner</a> >>>---> Smyrna, GA USA<br /> OS/2 + eCS + Linux + Win95 + DOS + PC/GEOS + Executor = PC Hobbyist Heaven!<br /> WARNING: I've seen FIELDATA FORTRAN V and I know how to use it!<br /> The Theorem Theorem: If If, Then Then.<br /> <!-- google_ad_section_end --> </blockquote> </div> </div> </div> <div class="cleardiv"></div> </div> </div> <div class="postfoot"> <div id="vbseo_vhtml_51"></div> </div> <hr /> </li> <li class="postbitlegacy postbitim postcontainer" id="post_145511"> <div class="posthead"> <div id="vbseo_vhtml_52"></div> </div> <div class="postdetails"> <div class="userinfo"> <div id="vbseo_vhtml_2"></div> </div> <div class="postbody"> <div class="postrow"> <h2 class="title icon"> <!-- google_ad_section_start -->Re: New API included in eComStation<!-- google_ad_section_end --> </h2> <div class="content"> <div id="post_message_145511"> <blockquote class="postcontent restore "> <!-- google_ad_section_start -->David T. Johnson wrote:<font color="blue"><br /> > Interesting post. Personally, I would prefer the 'standard OS/2' method<br /> > for security reasons but that's probably a minor point if you alrady<br /> > have a hostile REXX-ware running on your system. Your post, however,<br /> > seems like you are advocating what you seem to feel is a significant<br /> > feature of 'eCS' here in these newsgroups. For what reason are you<br /> > doing that? Every one of the handful of readers here has either already<br /> > bought 'eCS' or probably never will. If you really want to evangelize<br /> > for 'eCS' why not do it somewhere where there might be some people who<br /> > are interested? The single biggest thing holding back progress in<br /> > 'eCS' is its miniscule user base which seems to be mostly just a small<br /> > band of former OS/2 users. Why not reach out to Windows, Mac, and Linux<br /> > users rather than spend your time trading posts here with OS/2 users?<br /> > Wouldn't that be more helpful to the eCS you seem to like?</font><br /> <br /> This avenue is being pursued! The foundation needs to be laid first<br /> before the store can be put up! <img src="http://fixunix.com/images/smilies/biggrin.png" border="0" alt="" title="Big Grin" class="inlineimg" /><br /> <br /> <font color="blue"><br /> ><br /> ><br /> > <a href="mailto:ecsrulez@os2ecs.org">ecsrulez@os2ecs.org</a> wrote:<br /> ><font color="green"><br /> >> eComStation includes a new REXX API that enhances and provides new<br /> >> functionality for REXX applications.<br /> >><br /> >> The new API is contained in a DLL that first shipped with eComStation<br /> >> v1.1 called ECSRXLIB.DLL<br /> >><br /> >> The new API provides these new calls to REXX programs and utilities:<br /> >><br /> >> rc=ECSLOADFUNCS([version])<br /> >> [version] name of the variable to store the version number in<br /> >><br /> >> rc=ECSDROPFUNCS()<br /> >><br /> >> rc=ECSSTARTPROGRAMME(<programme>, [parameters], [environment],<br /> >> [starttype], [startfocus], [startoptions], [cause])<br /> >> <programme> Programme file<br /> >> [parameters] Parameters for the programme<br /> >> [environment] Environment variables separated by a |<br /> >> [starttype] OS2F(ULL)|OS2W(IN)|OS2P(M)|DOSF(ULL)|DOSW(IN)|DE(F AULT)<br /> >> [startfocus] F(OREGROUND)|B(ACKGROUND)<br /> >> [startoptions] P(ARENT)|S(HELL)<br /> >> [cause] Name of the variable to return the failure cause in<br /> >><br /> >> rc=ECSCOPY(<source>, <target>, [options], [cause])<br /> >> <file> A file<br /> >> [options] A(PPEND)|R(EPLACE)|F(AIL)<br /> >> [cause] Name of the variable to return the failure cause in<br /> >><br /> >> rc=ECSDELETE(<file>, [force], [recoverable], [cause])<br /> >> <file> A file<br /> >> [force] F(ORCE)|N(OFORCE)<br /> >> [recoverable] R(ECOVERABLE)|N(OTRECOVERABLE)<br /> >> [cause] Name of the variable to return the failure cause in<br /> >><br /> >> rc=ECSCLOSEOBJECT(<title>)<br /> >> <title> Title of the object in the switchlist<br /> >><br /> >> rc=ECSQUERYSWITCHLIST(<variable>)<br /> >> <variable> Name of the variable to use as stem to return the<br /> >> switchlist<br /> >><br /> >> rc=ECSDELTREE(<file>, [force], [cause])<br /> >> <file> File to delete<br /> >> [force] F(ORCE)|N(OFORCE)<br /> >> [cause] Name of the variable to return the failure cause in<br /> >><br /> >> rc=ECSMAKEPATH(<path>, [cause])<br /> >> <path> Path to create, either relative or absolute<br /> >> [cause] Name of the variable to return the failure cause in<br /> >><br /> >> Return code is always 0 (FALSE) or 1 (TRUE)<br /> >> [cause] is only set if the return code is false<br /> >><br /> >><br /> >> Here is some sample code to use these new calls:<br /> >><br /> >> /* Load New eComStation REXX API */<br /> >> IF LoadECSlib() THEN RETURN 1<br /> >> LoadRexxUtil:<br /> >><br /> >> IF RxFuncQuery('SysLoadFuncs') <> 0 THEN<br /> >> DO<br /> >> IF RxFuncAdd('SysLoadFuncs','RexxUtil','SysLoadFuncs' ) THEN<br /> >> RETURN 1<br /> >> CALL SysLoadFuncs<br /> >> END<br /> >> RETURN 0<br /> >><br /> >> LoadECSLib:<br /> >><br /> >> IF RxFuncQuery('eCSLoadFuncs') <> 0 THEN<br /> >> DO<br /> >> IF RxFuncAdd('eCSLoadFuncs','ECSRXLIB','eCSLoadFuncs' ) THEN<br /> >> RETURN 1<br /> >> CALL eCSLoadFuncs<br /> >> END<br /> >> RETURN 0<br /> >><br /> >><br /> >> This new API provides the REXX programmer enhanced functions and new<br /> >> functions.<br /> >> The new eCSCopy() call is one such example that provides the ability to<br /> >> copy files and overwrite existing ones. Standard OS/2 only allowed this<br /> >> function using the limited internal OS/2 Copy command. The new<br /> >> eCSCopy() call dosn't require a new command session to be started and<br /> >> can take advantabe of dynamic increases in file handles on a per<br /> >> session basis.<br /> >><br /> >> Another nice addition is the 'cause' parameter which allows more in<br /> >> depth error reporting from the calls.<br /> >><br /> >> This new REXX API is another example of the great value that you get<br /> >> with eComStation, making it easier for software developers and users<br /> >> alike to use there "operating platform of choice"!<br /> >><br /> >> Regards,<br /> >><br /> >> Jeramie Samphere<br /> >> President,<br /> >> OS2eCS Organization<br /> >> <a onclick="_gaq.push(['_trackEvent', 'Outgoing', 'www.os2ecs.org', '']);" rel="nofollow" href="http://www.os2ecs.org" target="_blank">www.os2ecs.org</a><br /> >></font><br /> ><br /> ></font><br /> <!-- google_ad_section_end --> </blockquote> </div> </div> </div> <div class="cleardiv"></div> </div> </div> <div class="postfoot"> <div id="vbseo_vhtml_54"></div> </div> <hr /> </li> <li class="postbitlegacy postbitim postcontainer" id="post_145515"> <div class="posthead"> <div id="vbseo_vhtml_55"></div> </div> <div class="postdetails"> <div class="userinfo"> <div id="vbseo_vhtml_2"></div> </div> <div class="postbody"> <div class="postrow"> <h2 class="title icon"> <!-- google_ad_section_start -->Re: New API included in eComStation<!-- google_ad_section_end --> </h2> <div class="content"> <div id="post_message_145515"> <blockquote class="postcontent restore "> <!-- google_ad_section_start -->In article <AsDWCpHpvmEN092yn@visi.com>, <a href="mailto:rsteiner@visi.com">rsteiner@visi.com</a> says...<font color="blue"><br /> > Here in comp.os.os2.misc,<br /> > "Herbert Rosenau" <os2guy@pc-rosenau.de> spake unto us, saying:<br /> ><font color="green"><br /> > >Without ongoing developement a system will die.</font><br /> ><br /> > While I agree that continued development is a good thing in general, it<br /> > isn't strictly necessary. As long as a given platform is able to meet<br /> > the needs of its users, it will continue to be viable (with or without<br /> > actual growth) to some of its existing users.<br /> ><font color="green"><br /> > >OS/2 WARP4 is out of developement since about a full decade now.<br /> > >Anything IBM has done in the last decade was only maintenance.</font><br /> ><br /> > One could argue that the adding of USB support, LVM, JFS, and a number<br /> > of other things to OS/2 went well beyond traditional maintenance. :-)<br /> ><br /> ></font><br /> As long as the needs of those existing users don't change. When you sit<br /> down and work out how many customers have such static needs coupled with<br /> the lack of development, it is relatively easy to see why the OS/2 user<br /> base has fallen to such a degree.<br /> --<br /> --------------------------------------<br /> David H. McCoy<br /> <br /> <br /> --------------------------------------<br /> <!-- google_ad_section_end --> </blockquote> </div> </div> </div> <div class="cleardiv"></div> </div> </div> <div class="postfoot"> <div id="vbseo_vhtml_57"></div> </div> <hr /> </li> <li class="postbitlegacy postbitim postcontainer" id="post_145516"> <div class="posthead"> <div id="vbseo_vhtml_58"></div> </div> <div class="postdetails"> <div class="userinfo"> <div id="vbseo_vhtml_2"></div> </div> <div class="postbody"> <div class="postrow"> <h2 class="title icon"> <!-- google_ad_section_start -->Re: New API included in eComStation<!-- google_ad_section_end --> </h2> <div class="content"> <div id="post_message_145516"> <blockquote class="postcontent restore "> <!-- google_ad_section_start -->David H. McCoy wrote:<font color="blue"><br /> > In article <AsDWCpHpvmEN092yn@visi.com>, <a href="mailto:rsteiner@visi.com">rsteiner@visi.com</a> says...<br /> ><font color="green"><br /> >>Here in comp.os.os2.misc,<br /> >>"Herbert Rosenau" <os2guy@pc-rosenau.de> spake unto us, saying:<br /> >><br /> >><font color="darkred"><br /> >>>Without ongoing developement a system will die.</font><br /> >><br /> >>While I agree that continued development is a good thing in general, it<br /> >>isn't strictly necessary. As long as a given platform is able to meet<br /> >>the needs of its users, it will continue to be viable (with or without<br /> >>actual growth) to some of its existing users.<br /> >><br /> >><font color="darkred"><br /> >>>OS/2 WARP4 is out of developement since about a full decade now.<br /> >>>Anything IBM has done in the last decade was only maintenance.</font><br /> >><br /> >>One could argue that the adding of USB support, LVM, JFS, and a number<br /> >>of other things to OS/2 went well beyond traditional maintenance. :-)<br /> >><br /> >></font><br /> ><br /> > As long as the needs of those existing users don't change. When you sit<br /> > down and work out how many customers have such static needs coupled with<br /> > the lack of development, it is relatively easy to see why the OS/2 user<br /> > base has fallen to such a degree.</font><br /> <br /> It's the apps stupid!!! ;-). I can run a Commodore 64 today, or an<br /> Amiga, or an Atari ST or (add platform here) but the consumer drives the<br /> mass market and it ain't in those platforms. I could go off on a<br /> diatribe about competition being perfect only when a fully informed<br /> consumer exists (if you think the majority of consumers are fully<br /> informed about their options you're nuts) and therefore the computer<br /> operating system market is not in perfect competition, but I won't. No<br /> major software houses develop for OS/2 and OS/2 software isn't sold at<br /> major retailers. OS/2 is in maintance mode now with features requested<br /> by current customers with enough clout being added. It's pretty simple,<br /> if somebody wants to use OS/2 they are free to. If they want to be<br /> delusional and believe that IBM is going to push it and start trying to<br /> get developers writing for it let them be delusional. For the longest<br /> time I hoped that something would happen in the OS/2 landscape that<br /> would make it viable again but that's not the way the market works.<br /> What are you rallying against David? This group used to be good for a<br /> yuck and occasionaly intersting information about OS/2 but not so much<br /> anymore.<br /> <!-- google_ad_section_end --> </blockquote> </div> </div> </div> <div class="cleardiv"></div> </div> </div> <div class="postfoot"> <div id="vbseo_vhtml_60"></div> </div> <hr /> </li> </ol> <div class="separator"></div> <div class="postlistfoot"> </div> </div> <div id="below_postlist" class="noinlinemod below_postlist"> <a rel="nofollow" href="http://fixunix.com/newreply.php?p=145516&noquote=1" class="newcontent_textcontrol" id="newreplylink_bottom" ><span>+</span> Reply to Thread</a> <div id="pagination_bottom" class="pagination_bottom"> <form action="http://fixunix.com/os2/43337-new-api-included-ecomstation-3.html" method="get" class="pagination popupmenu nohovermenu"> <input type="hidden" name="t" value="43337" /><input type="hidden" name="s" value="b94f66ca8a186c586358708656a5cf7c" /> <span><a href="javascript://" class="popupctrl">Page 1 of 4</a></span> <span class="selected"><a href="javascript://" title="Results 1 to 20 of 67">1</a></span> <span><a href="http://fixunix.com/os2/43337-new-api-included-ecomstation-2.html" title="Show results 21 to 40 of 67">2</a></span> <span><a href="http://fixunix.com/os2/43337-new-api-included-ecomstation-3.html" title="Show results 41 to 60 of 67">3</a></span> <span class="separator">...</span> <span class="prev_next"><a rel="next" href="http://fixunix.com/os2/43337-new-api-included-ecomstation-2.html" title="Next Page - Results 21 to 40 of 67"><img src="http://fixunix.com/images/pagination/next-right.png" alt="Next" /></a></span> <span class="first_last"><a href="http://fixunix.com/os2/43337-new-api-included-ecomstation-4.html" title="Last Page - Results 61 to 67 of 67">Last<img src="http://fixunix.com/images/pagination/last-right.png" alt="Last" /></a></span> <ul class="popupbody popuphover"> <li class="formsubmit jumptopage"><label>Jump to page: <input type="text" name="page" size="4" /></label> <input type="submit" class="button" value="Go" /></li> </ul> </form> </div> </div> <div class="navlinks"> <strong>«</strong> <a href="http://fixunix.com/os2/45191-re-why-wont-ecs-install-my-machine.html" >Re: Why won't eCS install on my machine?</a> | <a href="http://fixunix.com/os2/45192-re-papyrus.html" >Re: Papyrus</a> <strong>»</strong> </div> <div id="thread_info" class="thread_info block"> </div> <div id="ad_global_above_footer"> <div align="center"> <script type='text/javascript'> GA_googleFillSlot("FixUnix-Bottom"); </script> </div> </div> <div id="footer" class="floatcontainer footer"> <form action="http://fixunix.com/forum.php" method="get" id="footer_select" class="footer_select"> </form> <ul id="footer_links" class="footer_links"> <li><a href="mailto:webmaster@fixunix.com" rel="nofollow" accesskey="9">Contact Us</a></li> <li><a rel="nofollow" href="http://fixunix.com/">Unix Linux Forum</a></li> <li><a rel="nofollow" href="http://fixunix.com/privacy_policy.php">Privacy Statement</a></li> <li><a rel="nofollow" href="http://fixunix.com/os2/43337-new-api-included-ecomstation.html#top" onclick="document.location.hash='top'; return false;">Top</a></li> </ul> <script type="text/javascript"> <!-- // Main vBulletin Javascript Initialization vBulletin_init(); //--> </script> </div> </div> <div class="below_body"> <div id="footer_time" class="shade footer_time">All times are GMT. The time now is <span class="time">06:25 PM</span>.</div> <div id="footer_copyright" class="shade footer_copyright"> Powered by <a onclick="_gaq.push(['_trackEvent', 'Outgoing', 'www.vbulletin.com', '']);" rel="nofollow" href="http://www.vbulletin.com" id="vbulletinlink">vBulletin™</a> Version 4.1.3 <br />Copyright © 2014 vBulletin Solutions, Inc. All rights reserved. <br /><!-- google_ad_section_start(weight=ignore) -->Content Relevant URLs by vBSEO 3.6.0 ©2011, Crawlability, Inc.<!-- google_ad_section_end --> </div> <div id="footer_morecopyright" class="shade footer_morecopyright"> <img src="http://fixunix.com/cron.php?rand=1414175100" alt="" width="1" height="1" border="0" /> Maintained by <a onclick="_gaq.push(['_trackEvent', 'Outgoing', 'infnx.com', '']);" href="http://infnx.com">Infnx</a> </div> </div> <script type="text/javascript"> //<![CDATA[ var vbseo_jshtml = new Array(); vbseo_jshtml[0] = "<ol> </ol>"; vbseo_jshtml[1] = " <span class=\"postdate old\"> <span class=\"date\">10-02-2007 <span class=\"time\">12:29 AM</span></span> </span> <span class=\"nodecontrols\"> <a name=\"post145481\" href=\"http://fixunix.com/os2/43337-new-api-included-ecomstation.html#post145481\" class=\"postcounter\">#1</a><a id=\"postcount145481\" name=\"1\"></a> </span> "; vbseo_jshtml[2] = " <div class=\"username_container\"> <div class=\"popupmenu memberaction\"> <a rel=\"nofollow\" class=\"username offline \" href=\"http://fixunix.com/members/unix.html\" title=\"unix is offline\"><strong><!-- google_ad_section_start(weight=ignore) -->unix<!-- google_ad_section_end --></strong></a> </div> <img class=\"inlineimg onlinestatus\" src=\"http://fixunix.com/images/statusicon/user-offline.png\" alt=\"unix is offline\" border=\"0\" /> </div> <span class=\"usertitle\"> Junior Member </span> <hr /> <dl class=\"userinfo_extra\"> <dt>Join Date</dt> <dd>Sep 2009</dd> <dt>Posts</dt> <dd>0</dd> </dl> <div class=\"imlinks\"> </div> "; vbseo_jshtml[3] = " <div class=\"textcontrols floatcontainer\"> <span class=\"postcontrols\"> <img style=\"display:none\" id=\"progress_145481\" src=\"http://fixunix.com/images/misc/progress.gif\" alt=\"\" /> <a id=\"qrwq_145481\" class=\"newreply\" href=\"http://fixunix.com/newreply.php?do=newreply&p=145481\" rel=\"nofollow\"><img id=\"quoteimg_145481\" src=\"http://fixunix.com/clear.gif\" alt=\"Reply With Quote\" /> Reply With Quote</a> </span> <span class=\"postlinking\"> </span> </div> "; vbseo_jshtml[4] = " <span class=\"postdate old\"> <span class=\"date\">10-02-2007 <span class=\"time\">12:29 AM</span></span> </span> <span class=\"nodecontrols\"> <a name=\"post145482\" href=\"http://fixunix.com/os2/43337-new-api-included-ecomstation.html#post145482\" class=\"postcounter\">#2</a><a id=\"postcount145482\" name=\"2\"></a> </span> "; vbseo_jshtml[5] = " <div class=\"username_container\"> <div class=\"popupmenu memberaction\"> <a rel=\"nofollow\" class=\"username offline \" href=\"http://fixunix.com/members/unix.html\" title=\"unix is offline\"><strong><!-- google_ad_section_start(weight=ignore) -->unix<!-- google_ad_section_end --></strong></a> </div> <img class=\"inlineimg onlinestatus\" src=\"http://fixunix.com/images/statusicon/user-offline.png\" alt=\"unix is offline\" border=\"0\" /> </div> <span class=\"usertitle\"> Junior Member </span> <hr /> <dl class=\"userinfo_extra\"> <dt>Join Date</dt> <dd>Sep 2009</dd> <dt>Posts</dt> <dd>0</dd> </dl> <div class=\"imlinks\"> </div> "; vbseo_jshtml[6] = " <div class=\"textcontrols floatcontainer\"> <span class=\"postcontrols\"> <img style=\"display:none\" id=\"progress_145482\" src=\"http://fixunix.com/images/misc/progress.gif\" alt=\"\" /> <a id=\"qrwq_145482\" class=\"newreply\" href=\"http://fixunix.com/newreply.php?do=newreply&p=145482\" rel=\"nofollow\"><img id=\"quoteimg_145482\" src=\"http://fixunix.com/clear.gif\" alt=\"Reply With Quote\" /> Reply With Quote</a> </span> <span class=\"postlinking\"> </span> </div> "; vbseo_jshtml[7] = " <span class=\"postdate old\"> <span class=\"date\">10-02-2007 <span class=\"time\">12:29 AM</span></span> </span> <span class=\"nodecontrols\"> <a name=\"post145483\" href=\"http://fixunix.com/os2/43337-new-api-included-ecomstation.html#post145483\" class=\"postcounter\">#3</a><a id=\"postcount145483\" name=\"3\"></a> </span> "; vbseo_jshtml[8] = " <div class=\"username_container\"> <div class=\"popupmenu memberaction\"> <a rel=\"nofollow\" class=\"username offline \" href=\"http://fixunix.com/members/unix.html\" title=\"unix is offline\"><strong><!-- google_ad_section_start(weight=ignore) -->unix<!-- google_ad_section_end --></strong></a> </div> <img class=\"inlineimg onlinestatus\" src=\"http://fixunix.com/images/statusicon/user-offline.png\" alt=\"unix is offline\" border=\"0\" /> </div> <span class=\"usertitle\"> Junior Member </span> <hr /> <dl class=\"userinfo_extra\"> <dt>Join Date</dt> <dd>Sep 2009</dd> <dt>Posts</dt> <dd>0</dd> </dl> <div class=\"imlinks\"> </div> "; vbseo_jshtml[9] = " <div class=\"textcontrols floatcontainer\"> <span class=\"postcontrols\"> <img style=\"display:none\" id=\"progress_145483\" src=\"http://fixunix.com/images/misc/progress.gif\" alt=\"\" /> <a id=\"qrwq_145483\" class=\"newreply\" href=\"http://fixunix.com/newreply.php?do=newreply&p=145483\" rel=\"nofollow\"><img id=\"quoteimg_145483\" src=\"http://fixunix.com/clear.gif\" alt=\"Reply With Quote\" /> Reply With Quote</a> </span> <span class=\"postlinking\"> </span> </div> "; vbseo_jshtml[10] = " <span class=\"postdate old\"> <span class=\"date\">10-02-2007 <span class=\"time\">12:29 AM</span></span> </span> <span class=\"nodecontrols\"> <a name=\"post145484\" href=\"http://fixunix.com/os2/43337-new-api-included-ecomstation.html#post145484\" class=\"postcounter\">#4</a><a id=\"postcount145484\" name=\"4\"></a> </span> "; vbseo_jshtml[11] = " <div class=\"username_container\"> <div class=\"popupmenu memberaction\"> <a rel=\"nofollow\" class=\"username offline \" href=\"http://fixunix.com/members/unix.html\" title=\"unix is offline\"><strong><!-- google_ad_section_start(weight=ignore) -->unix<!-- google_ad_section_end --></strong></a> </div> <img class=\"inlineimg onlinestatus\" src=\"http://fixunix.com/images/statusicon/user-offline.png\" alt=\"unix is offline\" border=\"0\" /> </div> <span class=\"usertitle\"> Junior Member </span> <hr /> <dl class=\"userinfo_extra\"> <dt>Join Date</dt> <dd>Sep 2009</dd> <dt>Posts</dt> <dd>0</dd> </dl> <div class=\"imlinks\"> </div> "; vbseo_jshtml[12] = " <div class=\"textcontrols floatcontainer\"> <span class=\"postcontrols\"> <img style=\"display:none\" id=\"progress_145484\" src=\"http://fixunix.com/images/misc/progress.gif\" alt=\"\" /> <a id=\"qrwq_145484\" class=\"newreply\" href=\"http://fixunix.com/newreply.php?do=newreply&p=145484\" rel=\"nofollow\"><img id=\"quoteimg_145484\" src=\"http://fixunix.com/clear.gif\" alt=\"Reply With Quote\" /> Reply With Quote</a> </span> <span class=\"postlinking\"> </span> </div> "; vbseo_jshtml[13] = " <span class=\"postdate old\"> <span class=\"date\">10-02-2007 <span class=\"time\">12:29 AM</span></span> </span> <span class=\"nodecontrols\"> <a name=\"post145485\" href=\"http://fixunix.com/os2/43337-new-api-included-ecomstation.html#post145485\" class=\"postcounter\">#5</a><a id=\"postcount145485\" name=\"5\"></a> </span> "; vbseo_jshtml[14] = " <div class=\"username_container\"> <div class=\"popupmenu memberaction\"> <a rel=\"nofollow\" class=\"username offline \" href=\"http://fixunix.com/members/unix.html\" title=\"unix is offline\"><strong><!-- google_ad_section_start(weight=ignore) -->unix<!-- google_ad_section_end --></strong></a> </div> <img class=\"inlineimg onlinestatus\" src=\"http://fixunix.com/images/statusicon/user-offline.png\" alt=\"unix is offline\" border=\"0\" /> </div> <span class=\"usertitle\"> Junior Member </span> <hr /> <dl class=\"userinfo_extra\"> <dt>Join Date</dt> <dd>Sep 2009</dd> <dt>Posts</dt> <dd>0</dd> </dl> <div class=\"imlinks\"> </div> "; vbseo_jshtml[15] = " <div class=\"textcontrols floatcontainer\"> <span class=\"postcontrols\"> <img style=\"display:none\" id=\"progress_145485\" src=\"http://fixunix.com/images/misc/progress.gif\" alt=\"\" /> <a id=\"qrwq_145485\" class=\"newreply\" href=\"http://fixunix.com/newreply.php?do=newreply&p=145485\" rel=\"nofollow\"><img id=\"quoteimg_145485\" src=\"http://fixunix.com/clear.gif\" alt=\"Reply With Quote\" /> Reply With Quote</a> </span> <span class=\"postlinking\"> </span> </div> "; vbseo_jshtml[16] = " <span class=\"postdate old\"> <span class=\"date\">10-02-2007 <span class=\"time\">12:29 AM</span></span> </span> <span class=\"nodecontrols\"> <a name=\"post145486\" href=\"http://fixunix.com/os2/43337-new-api-included-ecomstation.html#post145486\" class=\"postcounter\">#6</a><a id=\"postcount145486\" name=\"6\"></a> </span> "; vbseo_jshtml[17] = " <div class=\"username_container\"> <div class=\"popupmenu memberaction\"> <a rel=\"nofollow\" class=\"username offline \" href=\"http://fixunix.com/members/unix.html\" title=\"unix is offline\"><strong><!-- google_ad_section_start(weight=ignore) -->unix<!-- google_ad_section_end --></strong></a> </div> <img class=\"inlineimg onlinestatus\" src=\"http://fixunix.com/images/statusicon/user-offline.png\" alt=\"unix is offline\" border=\"0\" /> </div> <span class=\"usertitle\"> Junior Member </span> <hr /> <dl class=\"userinfo_extra\"> <dt>Join Date</dt> <dd>Sep 2009</dd> <dt>Posts</dt> <dd>0</dd> </dl> <div class=\"imlinks\"> </div> "; vbseo_jshtml[18] = " <div class=\"textcontrols floatcontainer\"> <span class=\"postcontrols\"> <img style=\"display:none\" id=\"progress_145486\" src=\"http://fixunix.com/images/misc/progress.gif\" alt=\"\" /> <a id=\"qrwq_145486\" class=\"newreply\" href=\"http://fixunix.com/newreply.php?do=newreply&p=145486\" rel=\"nofollow\"><img id=\"quoteimg_145486\" src=\"http://fixunix.com/clear.gif\" alt=\"Reply With Quote\" /> Reply With Quote</a> </span> <span class=\"postlinking\"> </span> </div> "; vbseo_jshtml[19] = " <span class=\"postdate old\"> <span class=\"date\">10-02-2007 <span class=\"time\">12:29 AM</span></span> </span> <span class=\"nodecontrols\"> <a name=\"post145488\" href=\"http://fixunix.com/os2/43337-new-api-included-ecomstation.html#post145488\" class=\"postcounter\">#7</a><a id=\"postcount145488\" name=\"7\"></a> </span> "; vbseo_jshtml[20] = " <div class=\"username_container\"> <div class=\"popupmenu memberaction\"> <a rel=\"nofollow\" class=\"username offline \" href=\"http://fixunix.com/members/unix.html\" title=\"unix is offline\"><strong><!-- google_ad_section_start(weight=ignore) -->unix<!-- google_ad_section_end --></strong></a> </div> <img class=\"inlineimg onlinestatus\" src=\"http://fixunix.com/images/statusicon/user-offline.png\" alt=\"unix is offline\" border=\"0\" /> </div> <span class=\"usertitle\"> Junior Member </span> <hr /> <dl class=\"userinfo_extra\"> <dt>Join Date</dt> <dd>Sep 2009</dd> <dt>Posts</dt> <dd>0</dd> </dl> <div class=\"imlinks\"> </div> "; vbseo_jshtml[21] = " <div class=\"textcontrols floatcontainer\"> <span class=\"postcontrols\"> <img style=\"display:none\" id=\"progress_145488\" src=\"http://fixunix.com/images/misc/progress.gif\" alt=\"\" /> <a id=\"qrwq_145488\" class=\"newreply\" href=\"http://fixunix.com/newreply.php?do=newreply&p=145488\" rel=\"nofollow\"><img id=\"quoteimg_145488\" src=\"http://fixunix.com/clear.gif\" alt=\"Reply With Quote\" /> Reply With Quote</a> </span> <span class=\"postlinking\"> </span> </div> "; vbseo_jshtml[22] = " <span class=\"postdate old\"> <span class=\"date\">10-02-2007 <span class=\"time\">12:29 AM</span></span> </span> <span class=\"nodecontrols\"> <a name=\"post145489\" href=\"http://fixunix.com/os2/43337-new-api-included-ecomstation.html#post145489\" class=\"postcounter\">#8</a><a id=\"postcount145489\" name=\"8\"></a> </span> "; vbseo_jshtml[23] = " <div class=\"username_container\"> <div class=\"popupmenu memberaction\"> <a rel=\"nofollow\" class=\"username offline \" href=\"http://fixunix.com/members/unix.html\" title=\"unix is offline\"><strong><!-- google_ad_section_start(weight=ignore) -->unix<!-- google_ad_section_end --></strong></a> </div> <img class=\"inlineimg onlinestatus\" src=\"http://fixunix.com/images/statusicon/user-offline.png\" alt=\"unix is offline\" border=\"0\" /> </div> <span class=\"usertitle\"> Junior Member </span> <hr /> <dl class=\"userinfo_extra\"> <dt>Join Date</dt> <dd>Sep 2009</dd> <dt>Posts</dt> <dd>0</dd> </dl> <div class=\"imlinks\"> </div> "; vbseo_jshtml[24] = " <div class=\"textcontrols floatcontainer\"> <span class=\"postcontrols\"> <img style=\"display:none\" id=\"progress_145489\" src=\"http://fixunix.com/images/misc/progress.gif\" alt=\"\" /> <a id=\"qrwq_145489\" class=\"newreply\" href=\"http://fixunix.com/newreply.php?do=newreply&p=145489\" rel=\"nofollow\"><img id=\"quoteimg_145489\" src=\"http://fixunix.com/clear.gif\" alt=\"Reply With Quote\" /> Reply With Quote</a> </span> <span class=\"postlinking\"> </span> </div> "; vbseo_jshtml[25] = " <span class=\"postdate old\"> <span class=\"date\">10-02-2007 <span class=\"time\">12:29 AM</span></span> </span> <span class=\"nodecontrols\"> <a name=\"post145490\" href=\"http://fixunix.com/os2/43337-new-api-included-ecomstation.html#post145490\" class=\"postcounter\">#9</a><a id=\"postcount145490\" name=\"9\"></a> </span> "; vbseo_jshtml[26] = " <div class=\"username_container\"> <div class=\"popupmenu memberaction\"> <a rel=\"nofollow\" class=\"username offline \" href=\"http://fixunix.com/members/unix.html\" title=\"unix is offline\"><strong><!-- google_ad_section_start(weight=ignore) -->unix<!-- google_ad_section_end --></strong></a> </div> <img class=\"inlineimg onlinestatus\" src=\"http://fixunix.com/images/statusicon/user-offline.png\" alt=\"unix is offline\" border=\"0\" /> </div> <span class=\"usertitle\"> Junior Member </span> <hr /> <dl class=\"userinfo_extra\"> <dt>Join Date</dt> <dd>Sep 2009</dd> <dt>Posts</dt> <dd>0</dd> </dl> <div class=\"imlinks\"> </div> "; vbseo_jshtml[27] = " <div class=\"textcontrols floatcontainer\"> <span class=\"postcontrols\"> <img style=\"display:none\" id=\"progress_145490\" src=\"http://fixunix.com/images/misc/progress.gif\" alt=\"\" /> <a id=\"qrwq_145490\" class=\"newreply\" href=\"http://fixunix.com/newreply.php?do=newreply&p=145490\" rel=\"nofollow\"><img id=\"quoteimg_145490\" src=\"http://fixunix.com/clear.gif\" alt=\"Reply With Quote\" /> Reply With Quote</a> </span> <span class=\"postlinking\"> </span> </div> "; vbseo_jshtml[28] = " <span class=\"postdate old\"> <span class=\"date\">10-02-2007 <span class=\"time\">12:29 AM</span></span> </span> <span class=\"nodecontrols\"> <a name=\"post145492\" href=\"http://fixunix.com/os2/43337-new-api-included-ecomstation.html#post145492\" class=\"postcounter\">#10</a><a id=\"postcount145492\" name=\"10\"></a> </span> "; vbseo_jshtml[29] = " <div class=\"username_container\"> <div class=\"popupmenu memberaction\"> <a rel=\"nofollow\" class=\"username offline \" href=\"http://fixunix.com/members/unix.html\" title=\"unix is offline\"><strong><!-- google_ad_section_start(weight=ignore) -->unix<!-- google_ad_section_end --></strong></a> </div> <img class=\"inlineimg onlinestatus\" src=\"http://fixunix.com/images/statusicon/user-offline.png\" alt=\"unix is offline\" border=\"0\" /> </div> <span class=\"usertitle\"> Junior Member </span> <hr /> <dl class=\"userinfo_extra\"> <dt>Join Date</dt> <dd>Sep 2009</dd> <dt>Posts</dt> <dd>0</dd> </dl> <div class=\"imlinks\"> </div> "; vbseo_jshtml[30] = " <div class=\"textcontrols floatcontainer\"> <span class=\"postcontrols\"> <img style=\"display:none\" id=\"progress_145492\" src=\"http://fixunix.com/images/misc/progress.gif\" alt=\"\" /> <a id=\"qrwq_145492\" class=\"newreply\" href=\"http://fixunix.com/newreply.php?do=newreply&p=145492\" rel=\"nofollow\"><img id=\"quoteimg_145492\" src=\"http://fixunix.com/clear.gif\" alt=\"Reply With Quote\" /> Reply With Quote</a> </span> <span class=\"postlinking\"> </span> </div> "; vbseo_jshtml[31] = " <span class=\"postdate old\"> <span class=\"date\">10-02-2007 <span class=\"time\">12:29 AM</span></span> </span> <span class=\"nodecontrols\"> <a name=\"post145493\" href=\"http://fixunix.com/os2/43337-new-api-included-ecomstation.html#post145493\" class=\"postcounter\">#11</a><a id=\"postcount145493\" name=\"11\"></a> </span> "; vbseo_jshtml[32] = " <div class=\"username_container\"> <div class=\"popupmenu memberaction\"> <a rel=\"nofollow\" class=\"username offline \" href=\"http://fixunix.com/members/unix.html\" title=\"unix is offline\"><strong><!-- google_ad_section_start(weight=ignore) -->unix<!-- google_ad_section_end --></strong></a> </div> <img class=\"inlineimg onlinestatus\" src=\"http://fixunix.com/images/statusicon/user-offline.png\" alt=\"unix is offline\" border=\"0\" /> </div> <span class=\"usertitle\"> Junior Member </span> <hr /> <dl class=\"userinfo_extra\"> <dt>Join Date</dt> <dd>Sep 2009</dd> <dt>Posts</dt> <dd>0</dd> </dl> <div class=\"imlinks\"> </div> "; vbseo_jshtml[33] = " <div class=\"textcontrols floatcontainer\"> <span class=\"postcontrols\"> <img style=\"display:none\" id=\"progress_145493\" src=\"http://fixunix.com/images/misc/progress.gif\" alt=\"\" /> <a id=\"qrwq_145493\" class=\"newreply\" href=\"http://fixunix.com/newreply.php?do=newreply&p=145493\" rel=\"nofollow\"><img id=\"quoteimg_145493\" src=\"http://fixunix.com/clear.gif\" alt=\"Reply With Quote\" /> Reply With Quote</a> </span> <span class=\"postlinking\"> </span> </div> "; vbseo_jshtml[34] = " <span class=\"postdate old\"> <span class=\"date\">10-02-2007 <span class=\"time\">12:29 AM</span></span> </span> <span class=\"nodecontrols\"> <a name=\"post145494\" href=\"http://fixunix.com/os2/43337-new-api-included-ecomstation.html#post145494\" class=\"postcounter\">#12</a><a id=\"postcount145494\" name=\"12\"></a> </span> "; vbseo_jshtml[35] = " <div class=\"username_container\"> <div class=\"popupmenu memberaction\"> <a rel=\"nofollow\" class=\"username offline \" href=\"http://fixunix.com/members/unix.html\" title=\"unix is offline\"><strong><!-- google_ad_section_start(weight=ignore) -->unix<!-- google_ad_section_end --></strong></a> </div> <img class=\"inlineimg onlinestatus\" src=\"http://fixunix.com/images/statusicon/user-offline.png\" alt=\"unix is offline\" border=\"0\" /> </div> <span class=\"usertitle\"> Junior Member </span> <hr /> <dl class=\"userinfo_extra\"> <dt>Join Date</dt> <dd>Sep 2009</dd> <dt>Posts</dt> <dd>0</dd> </dl> <div class=\"imlinks\"> </div> "; vbseo_jshtml[36] = " <div class=\"textcontrols floatcontainer\"> <span class=\"postcontrols\"> <img style=\"display:none\" id=\"progress_145494\" src=\"http://fixunix.com/images/misc/progress.gif\" alt=\"\" /> <a id=\"qrwq_145494\" class=\"newreply\" href=\"http://fixunix.com/newreply.php?do=newreply&p=145494\" rel=\"nofollow\"><img id=\"quoteimg_145494\" src=\"http://fixunix.com/clear.gif\" alt=\"Reply With Quote\" /> Reply With Quote</a> </span> <span class=\"postlinking\"> </span> </div> "; vbseo_jshtml[37] = " <span class=\"postdate old\"> <span class=\"date\">10-02-2007 <span class=\"time\">12:29 AM</span></span> </span> <span class=\"nodecontrols\"> <a name=\"post145495\" href=\"http://fixunix.com/os2/43337-new-api-included-ecomstation.html#post145495\" class=\"postcounter\">#13</a><a id=\"postcount145495\" name=\"13\"></a> </span> "; vbseo_jshtml[38] = " <div class=\"username_container\"> <div class=\"popupmenu memberaction\"> <a rel=\"nofollow\" class=\"username offline \" href=\"http://fixunix.com/members/unix.html\" title=\"unix is offline\"><strong><!-- google_ad_section_start(weight=ignore) -->unix<!-- google_ad_section_end --></strong></a> </div> <img class=\"inlineimg onlinestatus\" src=\"http://fixunix.com/images/statusicon/user-offline.png\" alt=\"unix is offline\" border=\"0\" /> </div> <span class=\"usertitle\"> Junior Member </span> <hr /> <dl class=\"userinfo_extra\"> <dt>Join Date</dt> <dd>Sep 2009</dd> <dt>Posts</dt> <dd>0</dd> </dl> <div class=\"imlinks\"> </div> "; vbseo_jshtml[39] = " <div class=\"textcontrols floatcontainer\"> <span class=\"postcontrols\"> <img style=\"display:none\" id=\"progress_145495\" src=\"http://fixunix.com/images/misc/progress.gif\" alt=\"\" /> <a id=\"qrwq_145495\" class=\"newreply\" href=\"http://fixunix.com/newreply.php?do=newreply&p=145495\" rel=\"nofollow\"><img id=\"quoteimg_145495\" src=\"http://fixunix.com/clear.gif\" alt=\"Reply With Quote\" /> Reply With Quote</a> </span> <span class=\"postlinking\"> </span> </div> "; vbseo_jshtml[40] = " <span class=\"postdate old\"> <span class=\"date\">10-02-2007 <span class=\"time\">12:29 AM</span></span> </span> <span class=\"nodecontrols\"> <a name=\"post145498\" href=\"http://fixunix.com/os2/43337-new-api-included-ecomstation.html#post145498\" class=\"postcounter\">#14</a><a id=\"postcount145498\" name=\"14\"></a> </span> "; vbseo_jshtml[41] = " <div class=\"username_container\"> <div class=\"popupmenu memberaction\"> <a rel=\"nofollow\" class=\"username offline \" href=\"http://fixunix.com/members/unix.html\" title=\"unix is offline\"><strong><!-- google_ad_section_start(weight=ignore) -->unix<!-- google_ad_section_end --></strong></a> </div> <img class=\"inlineimg onlinestatus\" src=\"http://fixunix.com/images/statusicon/user-offline.png\" alt=\"unix is offline\" border=\"0\" /> </div> <span class=\"usertitle\"> Junior Member </span> <hr /> <dl class=\"userinfo_extra\"> <dt>Join Date</dt> <dd>Sep 2009</dd> <dt>Posts</dt> <dd>0</dd> </dl> <div class=\"imlinks\"> </div> "; vbseo_jshtml[42] = " <div class=\"textcontrols floatcontainer\"> <span class=\"postcontrols\"> <img style=\"display:none\" id=\"progress_145498\" src=\"http://fixunix.com/images/misc/progress.gif\" alt=\"\" /> <a id=\"qrwq_145498\" class=\"newreply\" href=\"http://fixunix.com/newreply.php?do=newreply&p=145498\" rel=\"nofollow\"><img id=\"quoteimg_145498\" src=\"http://fixunix.com/clear.gif\" alt=\"Reply With Quote\" /> Reply With Quote</a> </span> <span class=\"postlinking\"> </span> </div> "; vbseo_jshtml[43] = " <span class=\"postdate old\"> <span class=\"date\">10-02-2007 <span class=\"time\">12:29 AM</span></span> </span> <span class=\"nodecontrols\"> <a name=\"post145500\" href=\"http://fixunix.com/os2/43337-new-api-included-ecomstation.html#post145500\" class=\"postcounter\">#15</a><a id=\"postcount145500\" name=\"15\"></a> </span> "; vbseo_jshtml[44] = " <div class=\"username_container\"> <div class=\"popupmenu memberaction\"> <a rel=\"nofollow\" class=\"username offline \" href=\"http://fixunix.com/members/unix.html\" title=\"unix is offline\"><strong><!-- google_ad_section_start(weight=ignore) -->unix<!-- google_ad_section_end --></strong></a> </div> <img class=\"inlineimg onlinestatus\" src=\"http://fixunix.com/images/statusicon/user-offline.png\" alt=\"unix is offline\" border=\"0\" /> </div> <span class=\"usertitle\"> Junior Member </span> <hr /> <dl class=\"userinfo_extra\"> <dt>Join Date</dt> <dd>Sep 2009</dd> <dt>Posts</dt> <dd>0</dd> </dl> <div class=\"imlinks\"> </div> "; vbseo_jshtml[45] = " <div class=\"textcontrols floatcontainer\"> <span class=\"postcontrols\"> <img style=\"display:none\" id=\"progress_145500\" src=\"http://fixunix.com/images/misc/progress.gif\" alt=\"\" /> <a id=\"qrwq_145500\" class=\"newreply\" href=\"http://fixunix.com/newreply.php?do=newreply&p=145500\" rel=\"nofollow\"><img id=\"quoteimg_145500\" src=\"http://fixunix.com/clear.gif\" alt=\"Reply With Quote\" /> Reply With Quote</a> </span> <span class=\"postlinking\"> </span> </div> "; vbseo_jshtml[46] = " <span class=\"postdate old\"> <span class=\"date\">10-02-2007 <span class=\"time\">12:30 AM</span></span> </span> <span class=\"nodecontrols\"> <a name=\"post145509\" href=\"http://fixunix.com/os2/43337-new-api-included-ecomstation.html#post145509\" class=\"postcounter\">#16</a><a id=\"postcount145509\" name=\"16\"></a> </span> "; vbseo_jshtml[47] = " <div class=\"username_container\"> <div class=\"popupmenu memberaction\"> <a rel=\"nofollow\" class=\"username offline \" href=\"http://fixunix.com/members/unix.html\" title=\"unix is offline\"><strong><!-- google_ad_section_start(weight=ignore) -->unix<!-- google_ad_section_end --></strong></a> </div> <img class=\"inlineimg onlinestatus\" src=\"http://fixunix.com/images/statusicon/user-offline.png\" alt=\"unix is offline\" border=\"0\" /> </div> <span class=\"usertitle\"> Junior Member </span> <hr /> <dl class=\"userinfo_extra\"> <dt>Join Date</dt> <dd>Sep 2009</dd> <dt>Posts</dt> <dd>0</dd> </dl> <div class=\"imlinks\"> </div> "; vbseo_jshtml[48] = " <div class=\"textcontrols floatcontainer\"> <span class=\"postcontrols\"> <img style=\"display:none\" id=\"progress_145509\" src=\"http://fixunix.com/images/misc/progress.gif\" alt=\"\" /> <a id=\"qrwq_145509\" class=\"newreply\" href=\"http://fixunix.com/newreply.php?do=newreply&p=145509\" rel=\"nofollow\"><img id=\"quoteimg_145509\" src=\"http://fixunix.com/clear.gif\" alt=\"Reply With Quote\" /> Reply With Quote</a> </span> <span class=\"postlinking\"> </span> </div> "; vbseo_jshtml[49] = " <span class=\"postdate old\"> <span class=\"date\">10-02-2007 <span class=\"time\">12:30 AM</span></span> </span> <span class=\"nodecontrols\"> <a name=\"post145510\" href=\"http://fixunix.com/os2/43337-new-api-included-ecomstation.html#post145510\" class=\"postcounter\">#17</a><a id=\"postcount145510\" name=\"17\"></a> </span> "; vbseo_jshtml[50] = " <div class=\"username_container\"> <div class=\"popupmenu memberaction\"> <a rel=\"nofollow\" class=\"username offline \" href=\"http://fixunix.com/members/unix.html\" title=\"unix is offline\"><strong><!-- google_ad_section_start(weight=ignore) -->unix<!-- google_ad_section_end --></strong></a> </div> <img class=\"inlineimg onlinestatus\" src=\"http://fixunix.com/images/statusicon/user-offline.png\" alt=\"unix is offline\" border=\"0\" /> </div> <span class=\"usertitle\"> Junior Member </span> <hr /> <dl class=\"userinfo_extra\"> <dt>Join Date</dt> <dd>Sep 2009</dd> <dt>Posts</dt> <dd>0</dd> </dl> <div class=\"imlinks\"> </div> "; vbseo_jshtml[51] = " <div class=\"textcontrols floatcontainer\"> <span class=\"postcontrols\"> <img style=\"display:none\" id=\"progress_145510\" src=\"http://fixunix.com/images/misc/progress.gif\" alt=\"\" /> <a id=\"qrwq_145510\" class=\"newreply\" href=\"http://fixunix.com/newreply.php?do=newreply&p=145510\" rel=\"nofollow\"><img id=\"quoteimg_145510\" src=\"http://fixunix.com/clear.gif\" alt=\"Reply With Quote\" /> Reply With Quote</a> </span> <span class=\"postlinking\"> </span> </div> "; vbseo_jshtml[52] = " <span class=\"postdate old\"> <span class=\"date\">10-02-2007 <span class=\"time\">12:30 AM</span></span> </span> <span class=\"nodecontrols\"> <a name=\"post145511\" href=\"http://fixunix.com/os2/43337-new-api-included-ecomstation.html#post145511\" class=\"postcounter\">#18</a><a id=\"postcount145511\" name=\"18\"></a> </span> "; vbseo_jshtml[53] = " <div class=\"username_container\"> <div class=\"popupmenu memberaction\"> <a rel=\"nofollow\" class=\"username offline \" href=\"http://fixunix.com/members/unix.html\" title=\"unix is offline\"><strong><!-- google_ad_section_start(weight=ignore) -->unix<!-- google_ad_section_end --></strong></a> </div> <img class=\"inlineimg onlinestatus\" src=\"http://fixunix.com/images/statusicon/user-offline.png\" alt=\"unix is offline\" border=\"0\" /> </div> <span class=\"usertitle\"> Junior Member </span> <hr /> <dl class=\"userinfo_extra\"> <dt>Join Date</dt> <dd>Sep 2009</dd> <dt>Posts</dt> <dd>0</dd> </dl> <div class=\"imlinks\"> </div> "; vbseo_jshtml[54] = " <div class=\"textcontrols floatcontainer\"> <span class=\"postcontrols\"> <img style=\"display:none\" id=\"progress_145511\" src=\"http://fixunix.com/images/misc/progress.gif\" alt=\"\" /> <a id=\"qrwq_145511\" class=\"newreply\" href=\"http://fixunix.com/newreply.php?do=newreply&p=145511\" rel=\"nofollow\"><img id=\"quoteimg_145511\" src=\"http://fixunix.com/clear.gif\" alt=\"Reply With Quote\" /> Reply With Quote</a> </span> <span class=\"postlinking\"> </span> </div> "; vbseo_jshtml[55] = " <span class=\"postdate old\"> <span class=\"date\">10-02-2007 <span class=\"time\">12:30 AM</span></span> </span> <span class=\"nodecontrols\"> <a name=\"post145515\" href=\"http://fixunix.com/os2/43337-new-api-included-ecomstation.html#post145515\" class=\"postcounter\">#19</a><a id=\"postcount145515\" name=\"19\"></a> </span> "; vbseo_jshtml[56] = " <div class=\"username_container\"> <div class=\"popupmenu memberaction\"> <a rel=\"nofollow\" class=\"username offline \" href=\"http://fixunix.com/members/unix.html\" title=\"unix is offline\"><strong><!-- google_ad_section_start(weight=ignore) -->unix<!-- google_ad_section_end --></strong></a> </div> <img class=\"inlineimg onlinestatus\" src=\"http://fixunix.com/images/statusicon/user-offline.png\" alt=\"unix is offline\" border=\"0\" /> </div> <span class=\"usertitle\"> Junior Member </span> <hr /> <dl class=\"userinfo_extra\"> <dt>Join Date</dt> <dd>Sep 2009</dd> <dt>Posts</dt> <dd>0</dd> </dl> <div class=\"imlinks\"> </div> "; vbseo_jshtml[57] = " <div class=\"textcontrols floatcontainer\"> <span class=\"postcontrols\"> <img style=\"display:none\" id=\"progress_145515\" src=\"http://fixunix.com/images/misc/progress.gif\" alt=\"\" /> <a id=\"qrwq_145515\" class=\"newreply\" href=\"http://fixunix.com/newreply.php?do=newreply&p=145515\" rel=\"nofollow\"><img id=\"quoteimg_145515\" src=\"http://fixunix.com/clear.gif\" alt=\"Reply With Quote\" /> Reply With Quote</a> </span> <span class=\"postlinking\"> </span> </div> "; vbseo_jshtml[58] = " <span class=\"postdate old\"> <span class=\"date\">10-02-2007 <span class=\"time\">12:30 AM</span></span> </span> <span class=\"nodecontrols\"> <a name=\"post145516\" href=\"http://fixunix.com/os2/43337-new-api-included-ecomstation.html#post145516\" class=\"postcounter\">#20</a><a id=\"postcount145516\" name=\"20\"></a> </span> "; vbseo_jshtml[59] = " <div class=\"username_container\"> <div class=\"popupmenu memberaction\"> <a rel=\"nofollow\" class=\"username offline \" href=\"http://fixunix.com/members/unix.html\" title=\"unix is offline\"><strong><!-- google_ad_section_start(weight=ignore) -->unix<!-- google_ad_section_end --></strong></a> </div> <img class=\"inlineimg onlinestatus\" src=\"http://fixunix.com/images/statusicon/user-offline.png\" alt=\"unix is offline\" border=\"0\" /> </div> <span class=\"usertitle\"> Junior Member </span> <hr /> <dl class=\"userinfo_extra\"> <dt>Join Date</dt> <dd>Sep 2009</dd> <dt>Posts</dt> <dd>0</dd> </dl> <div class=\"imlinks\"> </div> "; vbseo_jshtml[60] = " <div class=\"textcontrols floatcontainer\"> <span class=\"postcontrols\"> <img style=\"display:none\" id=\"progress_145516\" src=\"http://fixunix.com/images/misc/progress.gif\" alt=\"\" /> <a id=\"qrwq_145516\" class=\"newreply\" href=\"http://fixunix.com/newreply.php?do=newreply&p=145516\" rel=\"nofollow\"><img id=\"quoteimg_145516\" src=\"http://fixunix.com/clear.gif\" alt=\"Reply With Quote\" /> Reply With Quote</a> </span> <span class=\"postlinking\"> </span> </div> "; for(var vi=0;vi<vbseo_jshtml.length;vi++) if(fetch_object("vbseo_vhtml_"+vi))fetch_object("vbseo_vhtml_"+vi).innerHTML = vbseo_jshtml[vi]; window.orig_onload = window.onload; window.onload = function() { var cpost=document.location.hash.substring(1);var cpost2='';if(cpost){ var ispost=cpost.substring(0,4)=='post';if(ispost)cpost2='post_'+cpost.substring(4);if((cobj = fetch_object(cpost))||(cobj = fetch_object(cpost2))){cobj.scrollIntoView(true);}else if(ispost){cpostno = cpost.substring(4,cpost.length);if(parseInt(cpostno)>0){location.replace('http://fixunix.com/showthread.php?p='+cpostno);};} } if(typeof window.orig_onload == "function") window.orig_onload(); } //]]> </script> </body> </html>