From: "Ed Durrant" Received: from [192.168.100.201] (HELO mail.2rosenthals.com) by 2rosenthals.com (CommuniGate Pro SMTP 5.1.16) with ESMTP id 2003588 for os2-wireless_users@2rosenthals.com; Thu, 07 Aug 2008 16:45:04 -0400 Received-SPF: none (secmgr-ny.randr: 61.9.189.137 is neither permitted nor denied by domain of durrant.mine.nu) client-ip=61.9.189.137; envelope-from=edurrant@durrant.mine.nu; helo=nschwmtas01p.mx.bigpond.com; Received: from nschwmtas01p.mx.bigpond.com ([61.9.189.137]) by secmgr-ny.randr with esmtp (Exim 4.43) id 1KRCLr-0006Oq-Gs for os2-wireless_users@2rosenthals.com; Thu, 07 Aug 2008 16:45:03 -0400 Received: from nschwotgx01p.mx.bigpond.com ([121.218.57.225]) by nschwmtas01p.mx.bigpond.com with ESMTP id <20080807204438.YTGB19495.nschwmtas01p.mx.bigpond.com@nschwotgx01p.mx.bigpond.com> for ; Thu, 7 Aug 2008 20:44:38 +0000 Received: from [192.168.100.2] (really [121.218.57.225]) by nschwotgx01p.mx.bigpond.com with ESMTP id <20080807204438.BFCX28620.nschwotgx01p.mx.bigpond.com@[192.168.100.2]> for ; Thu, 7 Aug 2008 20:44:38 +0000 Message-ID: <489B5F42.1010104@durrant.mine.nu> Date: Fri, 08 Aug 2008 06:46:58 +1000 User-Agent: Thunderbird 2.0.0.6 (OS/2/20070731) MIME-Version: 1.0 To: OS/2 Wireless Users Mailing List Subject: Re: [OS2Wireless] MPTS check routine References: In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH PLAIN at nschwotgx01p.mx.bigpond.com from [121.218.57.225] using ID edward.durrant@bigpond.com at Thu, 7 Aug 2008 20:44:37 +0000 X-RPD-ScanID: Class unknown; VirusThreatLevel unknown, RefID str=0001.0A150205.489B5EB6.003F,ss=1,fgs=0 X-Spam-Score: 0.1 (/) X-Spam-Report: 0.1 TW_CF BODY: Odd Letter Triples with CF Dave Saville wrote: > Can someone please remind me what the routine is that checks all the > files messed with by MPTS? > > TIA > > I tend to use laninst.exe in \ibmlan\install and run through the steps, this brings MPTS (actually protocol.ini) and config.sys back in line, then check tcpos2.ini via tcpcfg2 and all should be OK again. Cheers/2 Ed.