From: "Kris Steenhaut" Received: from mxout4.mailhop.org ([63.208.196.168] verified) by 2rosenthals.com (CommuniGate Pro SMTP 5.0.9) with ESMTP id 619895 for os2-wireless_users@2rosenthals.com; Thu, 14 Dec 2006 03:53:19 -0500 Received: from mxin2.mailhop.org ([63.208.196.176]) by mxout4.mailhop.org with esmtp (Exim 4.51) id 1GumL4-000GfB-UT for os2-wireless_users@2rosenthals.com; Thu, 14 Dec 2006 03:53:15 -0500 Received: from outmx015.isp.belgacom.be ([195.238.4.87]) by mxin2.mailhop.org with esmtp (Exim 4.51) id 1GumL4-000Dwk-Cd for os2-wireless_users@2rosenthals.com; Thu, 14 Dec 2006 03:53:14 -0500 Received: from outmx015.isp.belgacom.be (localhost [127.0.0.1]) by outmx015.isp.belgacom.be (8.12.11.20060308/8.12.11/Skynet-OUT-2.22) with ESMTP id kBE8quRq031745 for ; Thu, 14 Dec 2006 09:52:57 +0100 (envelope-from ) Received: from [192.168.2.102] (61.5-201-80.adsl-dyn.isp.belgacom.be [80.201.5.61]) by outmx015.isp.belgacom.be (8.12.11.20060308/8.12.11/Skynet-OUT-2.22) with ESMTP id kBE8qrNO031707; Thu, 14 Dec 2006 09:52:54 +0100 (envelope-from ) Message-ID: <458110DC.2030200@kolibrieweg.eu> Date: Thu, 14 Dec 2006 09:52:44 +0100 Organization: CFM$-FC (Coalition for Micro$oft-Free Computing) User-Agent: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.8.0.8) Gecko/20061110 SeaMonkey/1.0.6 MIME-Version: 1.0 To: OS/2 Wireless Users Mailing List Subject: Re: [OS2Wireless]Re: Wireless on an IBM T-40 References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mail-Handler: MailHop by DynDNS X-Originating-IP: 195.238.4.87 X-Spam-Score: -0.6 (/) altownsend wrote: > Is this the "Location Profile"? Which shows as TiggerCat or is that where I am connected to? > > ?? > I have the D-Link Wireless Network Name as TiigerCat > We can be pretty sure it isn't. > If I am wrong where do I find the name for the name of the wireless device > > If there is one, in the Windows device list (or whatever the name is). > This name shows in an "IBM Access Conections" window > > T-40 is running WindowsXP > > If Windy hasn't automagically installed the driver etc... etc..., this only can mean, take your pick: - or the laptop hasn't an inbuild wireless device (device = hardware) - or due to some miracolous miracle Windy hasn't detected the device and hence not installed the device driver etc... etc... If the first, purchase a cheap PCMCIA card (cardbus type) that comes with Windy drivers in the box. If the second, prior to anything you'll have to look for the name of the wireless inbuild device (= hardware) in the TP's manual. Was Windy XP the OS the laptop originally came with? Bottom line: wireless connection between your TP and your routier is a Windy affair and nothing but a Windy affair. -- Groeten uit Gent, Kris