From: "Ed Durrant" <os2-wireless_users@2rosenthals.com>
Message-ID: <45E0A945.6070709@bigpond.net.au>
Date: Sun, 25 Feb 2007 08:08:21 +1100
User-Agent: Thunderbird 1.5.0.9 (OS/2/20061223)
MIME-Version: 1.0
To: OS/2 Wireless Users Mailing List <os2-wireless_users@2rosenthals.com>
Subject: Re: [OS2Wireless]Re: TP Utilities
References: <list-926560@2rosenthals.com>
In-Reply-To: <list-926560@2rosenthals.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Ed Durrant wrote:
> Dave Saville wrote:
>> On Sat, 24 Feb 2007 15:24:52 +1100, Ed Durrant wrote:
>>
>>> However the current DOS utilities can be run from an OS/2 dos box - 
>>> these are here with instructions on how to run under OS/2 :
>>>
>>> http://www-307.ibm.com/pc/support/site.wss/MIGR-4ZFPEG.html
>>
>> And you install it on ECS how? The exe on that page won't run in a 
>> DOS box. And the destructions don't work - the Device Driver install 
>> wants a source.........................
>>
> The instructions are how to run the utilities under OS/2, if you are 
> saying they won't run in a DOS box under eComStation, that may suggest 
> that something has changed in eCS - I suggest you raise a support 
> ticket with Serenity Systems on this point - you might also check the 
> eComStation site to see if they have a copy of TP utilities that work 
> under eCS.
>
> Cheers/2
>
> Ed.
>
Reading other replies, and re-reading your original e-mail, I realise 
you are looking to add the "windows extras" utilities, which will never 
work as such under OS/2, eCS or Linux - for example IBM connections is 
definately Windoze only.

Also the file unpacking - this is not uncommon, however as stated in 
another reply, you can use ODIN or simpler Innowin to run the self 
extracting win32 executable. A few years back, the opposite was the 
case, IBM used a self extracting OS/2 executable for all drivers, which, 
since Windows NT and Windows 2000 supported 16bit commandline OS/2 
executables, was fine, until Micro$oft removed this support from Windows 
XP !

In general, you'll need to look for equivalents of the utilities you 
require from OS/2 coders, I don't believe you'll get the Windoze ones to 
work, even under ODIN.

Cheers/2

Ed.