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 2432349 for virtualized_ecs_users@2rosenthals.com; Sun, 23 May 2010 03:04:03 -0400 Received: from secmgr-va.2rosenthals.com ([162.83.95.194] helo=mail2.2rosenthals.com) by secmgr-ny.randr with esmtps (TLSv1:AES256-SHA:256) (Exim 4.43) id 1OG5E9-0004bM-0x for virtualized_ecs_users@2rosenthals.com; Sun, 23 May 2010 03:04:02 -0400 Received: from nskntmtas02p.mx.bigpond.com ([61.9.168.140]:42244) by mail2.2rosenthals.com with esmtp (Exim 4.69) (envelope-from ) id 1OG5Dz-0000ln-2s for virtualized_ecs_users@2rosenthals.com; Sun, 23 May 2010 03:03:52 -0400 Received: from nskntotgx02p.mx.bigpond.com ([58.164.10.17]) by nskntmtas02p.mx.bigpond.com with ESMTP id <20100523070348.KIUK1693.nskntmtas02p.mx.bigpond.com@nskntotgx02p.mx.bigpond.com> for ; Sun, 23 May 2010 07:03:48 +0000 Received: from [192.168.100.2] (really [58.164.10.17]) by nskntotgx02p.mx.bigpond.com with ESMTP id <20100523070348.MHBZ2010.nskntotgx02p.mx.bigpond.com@[192.168.100.2]> for ; Sun, 23 May 2010 07:03:48 +0000 X-CTCH-RefID: str=0001.0A020203.4BF8D358.0084,ss=1,fgs=0 Message-ID: <4BF8D3B5.4020103@durrant.mine.nu> Date: Sun, 23 May 2010 17:05:25 +1000 User-Agent: Thunderbird 2.0.0.23 (OS/2/20090822) MIME-Version: 1.0 To: Virtualized eCS Users Mailing List Subject: Re: [Virtualized eCS] Printer support 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 nskntotgx02p.mx.bigpond.com from [58.164.10.17] using ID edward.durrant@bigpond.com at Sun, 23 May 2010 07:03:47 +0000 X-RPD-ScanID: Class unknown; VirusThreatLevel unknown, RefID str=0001.0A090201.4BF8D354.00BF,ss=1,fgs=0 Doug Bissett wrote: > On 2010-05-23, at 11:54:47, Ed Durrant wrote: > >> Doug Bissett wrote: >> >>> >>> >> So you are saying you have been able to get the Windoze WiFi drivers to >> see the WiFi hardware in the host system via the virtual switch? >> > > Actually it should be possible to use the WiFi link, BUT windows guest > only sees the virtual wired link supplied by the Virtual Switch > software. It knows nothing about the WiFi that eCS can use. WiFi is > nothing more than a cable replacement between a NIC and something else > (usually a wireless router). Think of it as a ............. > So are you saying it's seeing the cable NIC then? I thought when using the virtual switch, it still saw the virtualised NIC - DEC 24440 or something (or in later versions optionally an Intel E100 NIC) - so are you saying that the windows OS running under VPC/2 sees the actual NIC hardware in the host machine and does not go via the OS/2 NIC drivers? > No, that doesn't work. It *may* be possible to do that, if the virtual > machine software could be made to expose the actual hardware to the > guest software, but it currently doesn't do that. All that the guest > sees is the virtual cabled NIC. At the other end of that "cable", the > "physical" link to the router can be a WiFi link, but the guest knows > nothing about that. > > OK, so it's as I thought it worked then, nothing new here, just that you can access network attached devices (including printers) from within the virtual machine and use windows printers drivers to print to the network printers from the Windows OS. > > Cheers/2 Ed Please checkout my podcasts at: http://eComStationAustralia.podbean.com or via iTunes To subscribe - click this: http://eComStationAustralia.podbean.com/feed