In message , "dennis@home"
writes


"Graeme" wrote in message
...

Followed the setup instructions (which also involved buying a USB DVD
drive for the Tosh, to read the D-Link manual which is on CD), and
using the built in Tosh and D-Link software, I can see the D-Link
access point from the Tosh, but cannot connect. Keep getting the
error message 'Another Vendor's Application is controlling the
wireless adaptor', but what application?

Anyone successfully connected a Tosh netbook in similar circumstances?

You made the error of installing the software off the cd.

Yes, I did wonder about that. The D-Link thing came with a huge sticker
saying :

STOP! Insert CD First.

Uninstall it and start again without making the error.
(You may need to use system restore to roll it back a bit.)

The netbook is almost brand new, so I suppose I could set it back to
'brand new'.

Windows can find the wireless network without any of the cr@p that
comes on the cds.

You will want to log into the AP and set security once it is working.

BTW are you sure its an access point?
most are routers.

It is described as Wireless G Access Point, model DAP-1160, suitable for
use as an Access Point, AP Client, Bridge, Bridge with AP, Repeater,
WISP Client Router or WISP Repeater.
--
Graeme

Graeme wrote:

Yes, I did wonder about that. The D-Link thing came with a huge sticker
saying :

STOP! Insert CD First.

Uninstall it and start again without making the error.
(You may need to use system restore to roll it back a bit.)


The CD supplied with the access point would have had software intended
to configure the wireless point NOT anything to do with configuring your
wireless adaptor on your laptop.


The netbook is almost brand new, so I suppose I could set it back to
'brand new'.

Windows can find the wireless network without any of the cr@p that
comes on the cds.

This following is pure Dennis.


You will want to log into the AP and set security once it is working.

BTW are you sure its an access point?
most are routers.


It is described as Wireless G Access Point, model DAP-1160, suitable for
use as an Access Point, AP Client, Bridge, Bridge with AP, Repeater,
WISP Client Router or WISP Repeater.

Back to the laptop, forget ConfigFree for the moment. That looks merely
like some convienience software for swapping settings for different
locations and their available internet connections be they wireless or
cabled. It's not a wifi driver.

If you look in device manager from control panel. i.e.
http://aps2.toshiba-tro.de/kb0/HTD7201PO000SR01.htm

You'll find the make of the wireless network adaptor. Either Atheros or
Intel I think. The utility software that you want to select and make the
connection is the following.

Intel - Intel(R) PROSet for Wireless
Atheros - Wireless Lan Client Manager

Either should be found from the programs menu and could be the 'other'
driver that MS (and also ConfigFree) are complaining about.

--
Adrian C

"Adrian C" wrote in message
...
Graeme wrote:

Yes, I did wonder about that. The D-Link thing came with a huge sticker
saying :

STOP! Insert CD First.

Uninstall it and start again without making the error.
(You may need to use system restore to roll it back a bit.)


The CD supplied with the access point would have had software intended to
configure the wireless point NOT anything to do with configuring your
wireless adaptor on your laptop.


SSID, encryption, etc.

dennis@home wrote:


The CD supplied with the access point would have had software intended
to configure the wireless point NOT anything to do with configuring
your wireless adaptor on your laptop.


SSID, encryption, etc.


Really?


--
Adrian C

"Adrian C" wrote in message
...
dennis@home wrote:


The CD supplied with the access point would have had software intended
to configure the wireless point NOT anything to do with configuring your
wireless adaptor on your laptop.


SSID, encryption, etc.


Really?

There isn't much point in having a wizard that sets encryption, etc. on a
WAP that doesn't set it on the PC.


--
Adrian C

dennis@home wrote:

SSID, encryption, etc.


Really?

There isn't much point in having a wizard that sets encryption, etc. on
a WAP that doesn't set it on the PC.


Wow. Tell me, with the plethora of different wireless chipsets possible
on a PC, and the random fact that the user may be using Microsoft
wireless configuration OR something else, and different operating
systems - exactly how is a setup disc wizard FOR THE WAP going to set up
encryption on the PC?

--
Adrian C

"Adrian C" wrote in message
...
dennis@home wrote:

SSID, encryption, etc.


Really?

There isn't much point in having a wizard that sets encryption, etc. on a
WAP that doesn't set it on the PC.


Wow. Tell me, with the plethora of different wireless chipsets possible on
a PC, and the random fact that the user may be using Microsoft wireless
configuration OR something else, and different operating systems - exactly
how is a setup disc wizard FOR THE WAP going to set up encryption on the
PC?


What makes you think they don't all store the data in the same place?
What makes you think there isn't a standard set of library calls to
manipulate them?
Can you name a card/driver combination where things like the "net" commands
and "ipconfig" don't work?

In message , Adrian C
writes

Intel - Intel(R) PROSet for Wireless
Atheros - Wireless Lan Client Manager

Either should be found from the programs menu and could be the 'other'
driver that MS (and also ConfigFree) are complaining about.

I think we're making progress. Found the Atheros settings under
Programs, and told it to let Windows take over. Windows confirms the
D-Link is connected, but is stuck, 'acquiring network address'. I start
work in ten minutes, so will try again later.
--
Graeme

Graeme wrote:
In message , Adrian C
writes

Intel - Intel(R) PROSet for Wireless
Atheros - Wireless Lan Client Manager

Either should be found from the programs menu and could be the 'other'
driver that MS (and also ConfigFree) are complaining about.

I think we're making progress. Found the Atheros settings under
Programs, and told it to let Windows take over. Windows confirms the
D-Link is connected, but is stuck, 'acquiring network address'. I start
work in ten minutes, so will try again later.

Ok, so you have recognised the link, but DHCP is not set up correctly.


That may in fact be something you need to configure on the WAP.

On Sep 4, 9:11*pm, Graeme wrote:
In message , "dennis@home"
writes



"Graeme" wrote in message
...

Anyone successfully connected a Tosh netbook in similar circumstances?

You made the error of installing the software off the cd.

Yes, I did wonder about that. *The D-Link thing came with a huge sticker saying :

STOP! *Insert CD First.

Ha, that was your first mistake ... !

Uninstall it and start again without making the error.
(You may need to use system restore to roll it back a bit.)

The netbook is almost brand new, so I suppose I could set it back to
'brand new'.

Windows can find the wireless network without any of the cr@p that comes on the cds.

That depends on the wireless card and if it has a standard chipset.
Anything from Netgear, D-Link or 3com should be ok, and recognised by
windows.

As has been said, de-install your card software (but not the drivers)
and windows should pick it up and use the Wireless Zero software.

Only default to the card makers software if windows can't drive it.

There's loads out there on the web for and against WZC.

e.g. http://www.smallbusinesscomputing.co...le.php/3577111

Cheers,

Paul.

On Fri, 4 Sep 2009 15:19:28 -0700 (PDT), zymurgy
wrote:

Windows can find the wireless network without any of the cr@p that comes on the cds.

That depends on the wireless card and if it has a standard chipset.
Anything from Netgear, D-Link or 3com should be ok, and recognised by
windows.

The chipset doesn't come into it. If it's transmitting the right kind
of wireless (and it will be) the computer will be able to pick it up.
The software provided on the computer will be fine.

Standard procedure with all this sort of gear is to ignore the
software provided. Connect to a computer with a network cable. Find
the address of the device from the manual. Typically it will be
192.168.0.1 or 192.168.1.1 Type it into your web browser, in the
same way as you'd type a www. address. There may be a default logon
and password. Typically some combination of "admin", "user" and
"password". Again the manual will tell you.

Once you're into the device's control panel (which looks and acts just
like a web page) make any necessary settings. For an access point the
only changes you'll probably need to make from the defaults is to
choose a network name and set a password (so that neighbours and
passers-by can't access your connection).

Typically it will be
192.168.0.1 or 192.168.1.1 Type it into your web browser, in the
same way as you'd type a www. address. There may be a default logon
and password. Typically some combination of "admin", "user" and
"password". Again the manual will tell you.

Correction - those are typical router addresses. An access point will
be different. Maybe 50 or 254 as the final number.

In uk.d-i-y, Graeme wrote:
In message , "dennis@home"
writes


"Graeme" wrote in message news:yqhs3YehyVo
...

Followed the setup instructions (which also involved buying a USB
DVD drive for the Tosh, to read the D-Link manual which is on CD),
and using the built in Tosh and D-Link software, I can see the D-
Link access point from the Tosh, but cannot connect. Keep getting
the error message 'Another Vendor's Application is controlling the
wireless adaptor', but what application?

Anyone successfully connected a Tosh netbook in similar circumstances?

You made the error of installing the software off the cd.

Yes, I did wonder about that. The D-Link thing came with a huge
sticker saying :

STOP! Insert CD First.

Yes, but presumably that wasn't in the laptop. Or was it? Normally you'd
install the D-Link software on a wired network PC. Then you'd use the
web browser on that PC to configure the WAP over the wired network. (You
don't need a crappy CD to do that, but that's another story). There's no
need to install any D-Link software on the laptop. Unless you use the
laptop to configure its own access point, which I suspect would be
confusing and inconvenient to say the least.

So:

Wired PC: install CD if you must, use your web browser to configure the
WAP (passwords, etc).

Laptop: don't install CD, use either Toshiba's software or Windows'
software, and whichever you get working first, stick with it. You should
be able to find Toshiba's software in the Start Menu, and when you start
that software you should see a check box "Allow Windows to manage this
connection" or similar. I'd check that box and see how I got on.

Lastly, take heart from the fact that this is all par for the course.

--
Mike Barnes

In message , Mike Barnes
writes

Lastly, take heart from the fact that this is all par for the course.

Not sure if I can help at all, but I just pop in to say that I'm the
owner of an earlier Toshiba NB100. Mine runs Ubuntu and I ran into a
whole heap of problems caused by my Linux inexperience with what to
answer to the questions that Ubuntu updates asked. A later version of
Ubuntu cured almost all of the mistakes I'd made, and I now really like
the little machine.

There are some Toshiba Europe forums for these machines eg

http://forums.computers.toshiba-euro...spa?forumID=94

which might give specific advice.

I certainly installed no software, just connected to my router. But the
wireless access point needs to be configured to pass through the dhcp
settings and DNS from the router transparently, and that's where you
need to have the software installed somewhere wired to set up the access
point.

I've done this using a second router as a WAP and it can be very
confusing.
--
Bill

In message , Mike Barnes
writes

Wired PC: install CD if you must, use your web browser to configure the
WAP (passwords, etc).

Mike, this is where I'm confused. Why do I need to bring a wired PC
into the equation? All I want to do is make the net book connect
wirelessly.

Lastly, take heart from the fact that this is all par for the course.

grin
--
Graeme