> I have a D-link blue tooth USB adapter. DBT-120.
>
> XPE with SP1.
>
> The drivers installed properly after FBA, no errors at all. But when
> I plug in the device the software can't find the BT device, nor the
> power light on the adapter comes on. But it does work on the XP pro.
>
> I was wondering if it is because SP1 doesn't support bluetooth stack?
> Or am I missing some USB components / some thing else to get this to
> work.
> jj,
>
> This is probably USB related problem.
>
> Go to device manager and see if you have all USB (EHCI, UHCI) drivers installed and functional.
> Or check setupapi.log.
>
> Regarding the Bluetooth. Since it is working on your XPP then it can be configured to work on XPe also.
>
> Best regards,
> Slobodan
>
> "jj3000" <jeremy_ho@my-deja.com> wrote in message news:3ed9e158.0409281506.350ffff8@posting.google.c om...> > I have a D-link blue tooth USB adapter. DBT-120.
> >
> > XPE with SP1.
> >
> > The drivers installed properly after FBA, no errors at all. But when
> > I plug in the device the software can't find the BT device, nor the
> > power light on the adapter comes on. But it does work on the XP pro.
> >
> > I was wondering if it is because SP1 doesn't support bluetooth stack?
> > Or am I missing some USB components / some thing else to get this to
> > work.
> Is this a problem with the lack of Bluetooth stack on XPe SP1?It should not be, since you have third-party drivers and services that you said that you already installed. They are intended for
> Hi, I have made sure in the windows\system32\drivers directory, the
> usbuhci, ehci, ohci sys files are present.
>
> But this did not help the situation any. When the USB BT dongle is
> plugged in, it simply does not light up or detect a new device. The
> Device manager does refresh though during this though, but I could not
> find what has changed.
>
> My next step is to install XP Pro on this specific computer board to
> see if it works to isolate that it's not a USB hardware problem. It
> worked fine on the desktop computers we have tried.
>
> The installation of the linksys/widcomm drivers went successfully,
> however after the installation the device simply isn't detected.
>
> Is this a problem with the lack of bluetooth stack on XPe SP1?
> Although it seem like it is still a USB problem.
>
> Thanks in advnace.
>
> "Slobodan Brcin \(eMVP\)" <sbrcin@ptt.yu> wrote in message news:<Ou0r4IcpEHA.648@tk2msftngp13.phx.gbl>...> > jj,
> >
> > This is probably USB related problem.
> >
> > Go to device manager and see if you have all USB (EHCI, UHCI) drivers installed and functional.
> > Or check setupapi.log.
> >
> > Regarding the Bluetooth. Since it is working on your XPP then it can be configured to work on XPe also.
> >
> > Best regards,
> > Slobodan
> >
> > "jj3000" <jeremy_ho@my-deja.com> wrote in message news:3ed9e158.0409281506.350ffff8@posting.google.c om...> > > I have a D-link blue tooth USB adapter. DBT-120.
> > >
> > > XPE with SP1.
> > >
> > > The drivers installed properly after FBA, no errors at all. But when
> > > I plug in the device the software can't find the BT device, nor the
> > > power light on the adapter comes on. But it does work on the XP pro.
> > >
> > > I was wondering if it is because SP1 doesn't support bluetooth stack?
> > > Or am I missing some USB components / some thing else to get this to
> > > work.
> Hi jj3000,
>
> I have a Sitecom USB Bluetooth dongle that also works with the widcomm
> drivers. I had a lot of troubles getting this damn thing to start too.
> This is how I'm able to get it going:
>
> 1. Try to get to the control panel on your XPE machine (with the dongle
> installed) and start the 'new hardware wizard'. It will look for PnP
> devices, but will not find any. After this select 'I have already installed
> the hardware', select from list, and you will see all hardware devices that
> are found on your system. Now, check if you see a USB device that has this
> exclemation mark with it. (Drivers that aren't correctly intalled) Select
> this device and go on with the wizard. The wizard will not install anything
> and reports back with 'success' immediately. If you now close the wizard,
> the system will detect the dongle and ask you for the drivers. Just point
> the system to the correct driver files. (Check System32\drivers dir,
> System32 and the folder in the "Program Files" that has the widcomm software
> installed. In this folder, you will find a subfolder which has a bin-folder,
> with additional .sys files and so on)
> 2. If you get this ok, go to the control panel and double click the
> 'bluetooth' item. On the last tabpage of this control panel applet, you will
> see if the widcomm drivers are able to identify your dongle. If ok, proceed
> to step 3.
> 3. If this is ok, try double clicking the Bluetooth item on your desktop.
> This will start the initial wizard which lets you detect any bluetooth
> devices in the neighbourhood and pair with them. If this wizard does not
> show, you'll have to start it up using the cmd command line tool by typing
> rundll32.exe BtWizard.dll,ShowWizard
> The ShowWizard parameter is case sensitive, watch out.
> 4. If you are not able to start the bluetooth initial wizard, and you have
> to use the command line equivalent I have shown you in step 3, you will not
> have access to the Bluetooth Neighbourhood neither on the desktop and on 'My
> Computer'. This will not allow you for example to start a Bluetooth Serial
> Port that you had installed right after pairing the device that offers this
> serial port. To get this Serial Port running, see step 5.
> 5. If you need a service that a bluetooth device in your neighbourhood
> offers, start the wizard again with the command line tool, and select the
> second option on the wizard. (something like "I know the service I want to
> use, look for devices that offer this service") Now look for the device,
> select it, next... And now you need to check the 'Start Service' or
> something like that. This will make a connection to the service on your BT
> device and automatically start it right after this wizard. Now you don't
> need to go the the Bluetooth Neighourhood to start the service manually.
> This 'Start Automatically' option is NOT included if you use the first
> option of the wizard to pair to a device. (However, if you still need to
> perform the first option of the wizard becaus you have to pair with the
> device, do not select any services after pairing using this first option,
> just start the wizard again and use option 2 to link to the service and
> start it.)
> If you have linked to the service like I described here, you will not need
> to do this again.
>
> I know, it's not a pretty sight, but it works for my setup.
>
> good luck, and please give some feedback on your progress. I would like to
> know if I'm not alone with this issue.
>
> regards,
> Sven
> Thanks for the suggestions!
>
> I have an update. I used a XPe image that I got from our computer
> board supplier, and the driver install successfully and the USB device
> is working on that image.
>
> The difference is that their image comes up with "file needed" to
> prompt you for a couple of .sys files during the install wizard, and
> you would browse it to your extracted driver directory and it would
> work fine.
>
> On my build of XPe it would skip it completely. Any idea what I am
> missing?
>
>
>
> "Sven Meirsman" <Sven.Meirsman_NoSpam@cronos.be> wrote in message news:<#sLKlwGqEHA.596@TK2MSFTNGP11.phx.gbl>...> > Hi jj3000,
> >
> > I have a Sitecom USB Bluetooth dongle that also works with the widcomm
> > drivers. I had a lot of troubles getting this damn thing to start too.
> > This is how I'm able to get it going:
> >
> > 1. Try to get to the control panel on your XPE machine (with the dongle
> > installed) and start the 'new hardware wizard'. It will look for PnP
> > devices, but will not find any. After this select 'I have already installed
> > the hardware', select from list, and you will see all hardware devices that
> > are found on your system. Now, check if you see a USB device that has this
> > exclemation mark with it. (Drivers that aren't correctly intalled) Select
> > this device and go on with the wizard. The wizard will not install anything
> > and reports back with 'success' immediately. If you now close the wizard,
> > the system will detect the dongle and ask you for the drivers. Just point
> > the system to the correct driver files. (Check System32\drivers dir,
> > System32 and the folder in the "Program Files" that has the widcomm software
> > installed. In this folder, you will find a subfolder which has a bin-folder,
> > with additional .sys files and so on)
> > 2. If you get this ok, go to the control panel and double click the
> > 'bluetooth' item. On the last tabpage of this control panel applet, you will
> > see if the widcomm drivers are able to identify your dongle. If ok, proceed
> > to step 3.
> > 3. If this is ok, try double clicking the Bluetooth item on your desktop.
> > This will start the initial wizard which lets you detect any bluetooth
> > devices in the neighbourhood and pair with them. If this wizard does not
> > show, you'll have to start it up using the cmd command line tool by typing
> > rundll32.exe BtWizard.dll,ShowWizard
> > The ShowWizard parameter is case sensitive, watch out.
> > 4. If you are not able to start the bluetooth initial wizard, and you have
> > to use the command line equivalent I have shown you in step 3, you will not
> > have access to the Bluetooth Neighbourhood neither on the desktop and on 'My
> > Computer'. This will not allow you for example to start a Bluetooth Serial
> > Port that you had installed right after pairing the device that offers this
> > serial port. To get this Serial Port running, see step 5.
> > 5. If you need a service that a bluetooth device in your neighbourhood
> > offers, start the wizard again with the command line tool, and select the
> > second option on the wizard. (something like "I know the service I want to
> > use, look for devices that offer this service") Now look for the device,
> > select it, next... And now you need to check the 'Start Service' or
> > something like that. This will make a connection to the service on your BT
> > device and automatically start it right after this wizard. Now you don't
> > need to go the the Bluetooth Neighourhood to start the service manually.
> > This 'Start Automatically' option is NOT included if you use the first
> > option of the wizard to pair to a device. (However, if you still need to
> > perform the first option of the wizard becaus you have to pair with the
> > device, do not select any services after pairing using this first option,
> > just start the wizard again and use option 2 to link to the service and
> > start it.)
> > If you have linked to the service like I described here, you will not need
> > to do this again.
> >
> > I know, it's not a pretty sight, but it works for my setup.
> >
> > good luck, and please give some feedback on your progress. I would like to
> > know if I'm not alone with this issue.
> >
> > regards,
> > Sven
> Hi JJ,
>
> You would like to add component "Add Hardware Control Panel"?
>
> Anyhow check setupapi.log for missing files. And provide them in appropriate folders in XPe image. This way you won't need "Add
> Hardware Control Panel" to ask you for files (actually you won't need Add Hardware Control Panel).
>
> Best regards,
> Slobodan
>
> "jj3000" <jeremy_ho@my-deja.com> wrote in message news:3ed9e158.0410061143.44359419@posting.google.c om...> > Thanks for the suggestions!
> >
> > I have an update. I used a XPe image that I got from our computer
> > board supplier, and the driver install successfully and the USB device
> > is working on that image.
> >
> > The difference is that their image comes up with "file needed" to
> > prompt you for a couple of .sys files during the install wizard, and
> > you would browse it to your extracted driver directory and it would
> > work fine.
> >
> > On my build of XPe it would skip it completely. Any idea what I am
> > missing?
> >
> >
> >
> > "Sven Meirsman" <Sven.Meirsman_NoSpam@cronos.be> wrote in message news:<#sLKlwGqEHA.596@TK2MSFTNGP11.phx.gbl>...> > > Hi jj3000,
> > >
> > > I have a Sitecom USB Bluetooth dongle that also works with the widcomm
> > > drivers. I had a lot of troubles getting this damn thing to start too.
> > > This is how I'm able to get it going:
> > >
> > > 1. Try to get to the control panel on your XPE machine (with the dongle
> > > installed) and start the 'new hardware wizard'. It will look for PnP
> > > devices, but will not find any. After this select 'I have already installed
> > > the hardware', select from list, and you will see all hardware devices that
> > > are found on your system. Now, check if you see a USB device that has this
> > > exclemation mark with it. (Drivers that aren't correctly intalled) Select
> > > this device and go on with the wizard. The wizard will not install anything
> > > and reports back with 'success' immediately. If you now close the wizard,
> > > the system will detect the dongle and ask you for the drivers. Just point
> > > the system to the correct driver files. (Check System32\drivers dir,
> > > System32 and the folder in the "Program Files" that has the widcomm software
> > > installed. In this folder, you will find a subfolder which has a bin-folder,
> > > with additional .sys files and so on)
> > > 2. If you get this ok, go to the control panel and double click the
> > > 'bluetooth' item. On the last tabpage of this control panel applet, you will
> > > see if the widcomm drivers are able to identify your dongle. If ok, proceed
> > > to step 3.
> > > 3. If this is ok, try double clicking the Bluetooth item on your desktop.
> > > This will start the initial wizard which lets you detect any bluetooth
> > > devices in the neighbourhood and pair with them. If this wizard does not
> > > show, you'll have to start it up using the cmd command line tool by typing
> > > rundll32.exe BtWizard.dll,ShowWizard
> > > The ShowWizard parameter is case sensitive, watch out.
> > > 4. If you are not able to start the bluetooth initial wizard, and you have
> > > to use the command line equivalent I have shown you in step 3, you will not
> > > have access to the Bluetooth Neighbourhood neither on the desktop and on 'My
> > > Computer'. This will not allow you for example to start a Bluetooth Serial
> > > Port that you had installed right after pairing the device that offers this
> > > serial port. To get this Serial Port running, see step 5.
> > > 5. If you need a service that a bluetooth device in your neighbourhood
> > > offers, start the wizard again with the command line tool, and select the
> > > second option on the wizard. (something like "I know the service I want to
> > > use, look for devices that offer this service") Now look for the device,
> > > select it, next... And now you need to check the 'Start Service' or
> > > something like that. This will make a connection to the service on your BT
> > > device and automatically start it right after this wizard. Now you don't
> > > need to go the the Bluetooth Neighourhood to start the service manually.
> > > This 'Start Automatically' option is NOT included if you use the first
> > > option of the wizard to pair to a device. (However, if you still need to
> > > perform the first option of the wizard becaus you have to pair with the
> > > device, do not select any services after pairing using this first option,
> > > just start the wizard again and use option 2 to link to the service and
> > > start it.)
> > > If you have linked to the service like I described here, you will not need
> > > to do this again.
> > >
> > > I know, it's not a pretty sight, but it works for my setup.
> > >
> > > good luck, and please give some feedback on your progress. I would like to
> > > know if I'm not alone with this issue.
> > >
> > > regards,
> > > Sven
> Thanks. I am able to make it work now by changing from minlogon to
> windows logon only. Whenever it is using minlogon, it does not work.
>
> (actually, I'm using explorer shell + min logon), But I disable the
> windows logon after the dependency check.
>
> Any idea why it is this way?
>
> "Slobodan Brcin \(eMVP\)" <sbrcin@ptt.yu> wrote in message news:<#Wj6r59qEHA.644@tk2msftngp13.phx.gbl>...> > Hi JJ,
> >
> > You would like to add component "Add Hardware Control Panel"?
> >
> > Anyhow check setupapi.log for missing files. And provide them in appropriate folders in XPe image. This way you won't need "Add
> > Hardware Control Panel" to ask you for files (actually you won't need Add Hardware Control Panel).
> >
> > Best regards,
> > Slobodan
> >
> > "jj3000" <jeremy_ho@my-deja.com> wrote in message news:3ed9e158.0410061143.44359419@posting.google.c om...> > > Thanks for the suggestions!
> > >
> > > I have an update. I used a XPe image that I got from our computer
> > > board supplier, and the driver install successfully and the USB device
> > > is working on that image.
> > >
> > > The difference is that their image comes up with "file needed" to
> > > prompt you for a couple of .sys files during the install wizard, and
> > > you would browse it to your extracted driver directory and it would
> > > work fine.
> > >
> > > On my build of XPe it would skip it completely. Any idea what I am
> > > missing?
> > >
> > >
> > >
> > > "Sven Meirsman" <Sven.Meirsman_NoSpam@cronos.be> wrote in message news:<#sLKlwGqEHA.596@TK2MSFTNGP11.phx.gbl>...
> > > > Hi jj3000,
> > > >
> > > > I have a Sitecom USB Bluetooth dongle that also works with the widcomm
> > > > drivers. I had a lot of troubles getting this damn thing to start too.
> > > > This is how I'm able to get it going:
> > > >
> > > > 1. Try to get to the control panel on your XPE machine (with the dongle
> > > > installed) and start the 'new hardware wizard'. It will look for PnP
> > > > devices, but will not find any. After this select 'I have already installed
> > > > the hardware', select from list, and you will see all hardware devices that
> > > > are found on your system. Now, check if you see a USB device that has this
> > > > exclemation mark with it. (Drivers that aren't correctly intalled) Select
> > > > this device and go on with the wizard. The wizard will not install anything
> > > > and reports back with 'success' immediately. If you now close the wizard,
> > > > the system will detect the dongle and ask you for the drivers. Just point
> > > > the system to the correct driver files. (Check System32\drivers dir,
> > > > System32 and the folder in the "Program Files" that has the widcomm software
> > > > installed. In this folder, you will find a subfolder which has a bin-folder,
> > > > with additional .sys files and so on)
> > > > 2. If you get this ok, go to the control panel and double click the
> > > > 'bluetooth' item. On the last tabpage of this control panel applet, you will
> > > > see if the widcomm drivers are able to identify your dongle. If ok, proceed
> > > > to step 3.
> > > > 3. If this is ok, try double clicking the Bluetooth item on your desktop.
> > > > This will start the initial wizard which lets you detect any bluetooth
> > > > devices in the neighbourhood and pair with them. If this wizard does not
> > > > show, you'll have to start it up using the cmd command line tool by typing
> > > > rundll32.exe BtWizard.dll,ShowWizard
> > > > The ShowWizard parameter is case sensitive, watch out.
> > > > 4. If you are not able to start the bluetooth initial wizard, and you have
> > > > to use the command line equivalent I have shown you in step 3, you will not
> > > > have access to the Bluetooth Neighbourhood neither on the desktop and on 'My
> > > > Computer'. This will not allow you for example to start a Bluetooth Serial
> > > > Port that you had installed right after pairing the device that offers this
> > > > serial port. To get this Serial Port running, see step 5.
> > > > 5. If you need a service that a bluetooth device in your neighbourhood
> > > > offers, start the wizard again with the command line tool, and select the
> > > > second option on the wizard. (something like "I know the service I want to
> > > > use, look for devices that offer this service") Now look for the device,
> > > > select it, next... And now you need to check the 'Start Service' or
> > > > something like that. This will make a connection to the service on your BT
> > > > device and automatically start it right after this wizard. Now you don't
> > > > need to go the the Bluetooth Neighourhood to start the service manually.
> > > > This 'Start Automatically' option is NOT included if you use the first
> > > > option of the wizard to pair to a device. (However, if you still need to
> > > > perform the first option of the wizard becaus you have to pair with the
> > > > device, do not select any services after pairing using this first option,
> > > > just start the wizard again and use option 2 to link to the service and
> > > > start it.)
> > > > If you have linked to the service like I described here, you will not need
> > > > to do this again.
> > > >
> > > > I know, it's not a pretty sight, but it works for my setup.
> > > >
> > > > good luck, and please give some feedback on your progress. I would like to
> > > > know if I'm not alone with this issue.
> > > >
> > > > regards,
> > > > Sven
> I lost you about what is working.
>
> Bluetooth or "Add Hardware Wizard"?
> I thought that you are trying to make BT work?
>
> Regards,
> Slobodan
>
> "jj3000" <jeremy_ho@my-deja.com> wrote in message news:3ed9e158.0410070933.248815b8@posting.google.c om...> > Thanks. I am able to make it work now by changing from minlogon to
> > windows logon only. Whenever it is using minlogon, it does not work.
> >
> > (actually, I'm using explorer shell + min logon), But I disable the
> > windows logon after the dependency check.
> >
> > Any idea why it is this way?
> >
> > "Slobodan Brcin \(eMVP\)" <sbrcin@ptt.yu> wrote in message news:<#Wj6r59qEHA.644@tk2msftngp13.phx.gbl>...> > > Hi JJ,
> > >
> > > You would like to add component "Add Hardware Control Panel"?
> > >
> > > Anyhow check setupapi.log for missing files. And provide them in appropriate folders in XPe image. This way you won't need "Add
> > > Hardware Control Panel" to ask you for files (actually you won't need Add Hardware Control Panel).
> > >
> > > Best regards,
> > > Slobodan
> > >
> > > "jj3000" <jeremy_ho@my-deja.com> wrote in message news:3ed9e158.0410061143.44359419@posting.google.c om...
> > > > Thanks for the suggestions!
> > > >
> > > > I have an update. I used a XPe image that I got from our computer
> > > > board supplier, and the driver install successfully and the USB device
> > > > is working on that image.
> > > >
> > > > The difference is that their image comes up with "file needed" to
> > > > prompt you for a couple of .sys files during the install wizard, and
> > > > you would browse it to your extracted driver directory and it would
> > > > work fine.
> > > >
> > > > On my build of XPe it would skip it completely. Any idea what I am
> > > > missing?
> > > >
> > > >
> > > >
> > > > "Sven Meirsman" <Sven.Meirsman_NoSpam@cronos.be> wrote in message news:<#sLKlwGqEHA.596@TK2MSFTNGP11.phx.gbl>...
> > > > > Hi jj3000,
> > > > >
> > > > > I have a Sitecom USB Bluetooth dongle that also works with the widcomm
> > > > > drivers. I had a lot of troubles getting this damn thing to start too.
> > > > > This is how I'm able to get it going:
> > > > >
> > > > > 1. Try to get to the control panel on your XPE machine (with the dongle
> > > > > installed) and start the 'new hardware wizard'. It will look for PnP
> > > > > devices, but will not find any. After this select 'I have already installed
> > > > > the hardware', select from list, and you will see all hardware devices that
> > > > > are found on your system. Now, check if you see a USB device that has this
> > > > > exclemation mark with it. (Drivers that aren't correctly intalled) Select
> > > > > this device and go on with the wizard. The wizard will not install anything
> > > > > and reports back with 'success' immediately. If you now close the wizard,
> > > > > the system will detect the dongle and ask you for the drivers. Just point
> > > > > the system to the correct driver files. (Check System32\drivers dir,
> > > > > System32 and the folder in the "Program Files" that has the widcomm software
> > > > > installed. In this folder, you will find a subfolder which has a bin-folder,
> > > > > with additional .sys files and so on)
> > > > > 2. If you get this ok, go to the control panel and double click the
> > > > > 'bluetooth' item. On the last tabpage of this control panel applet, you will
> > > > > see if the widcomm drivers are able to identify your dongle. If ok, proceed
> > > > > to step 3.
> > > > > 3. If this is ok, try double clicking the Bluetooth item on your desktop.
> > > > > This will start the initial wizard which lets you detect any bluetooth
> > > > > devices in the neighbourhood and pair with them. If this wizard does not
> > > > > show, you'll have to start it up using the cmd command line tool by typing
> > > > > rundll32.exe BtWizard.dll,ShowWizard
> > > > > The ShowWizard parameter is case sensitive, watch out.
> > > > > 4. If you are not able to start the bluetooth initial wizard, and you have
> > > > > to use the command line equivalent I have shown you in step 3, you will not
> > > > > have access to the Bluetooth Neighbourhood neither on the desktop and on 'My
> > > > > Computer'. This will not allow you for example to start a Bluetooth Serial
> > > > > Port that you had installed right after pairing the device that offers this
> > > > > serial port. To get this Serial Port running, see step 5.
> > > > > 5. If you need a service that a bluetooth device in your neighbourhood
> > > > > offers, start the wizard again with the command line tool, and select the
> > > > > second option on the wizard. (something like "I know the service I want to
> > > > > use, look for devices that offer this service") Now look for the device,
> > > > > select it, next... And now you need to check the 'Start Service' or
> > > > > something like that. This will make a connection to the service on your BT
> > > > > device and automatically start it right after this wizard. Now you don't
> > > > > need to go the the Bluetooth Neighourhood to start the service manually.
> > > > > This 'Start Automatically' option is NOT included if you use the first
> > > > > option of the wizard to pair to a device. (However, if you still need to
> > > > > perform the first option of the wizard becaus you have to pair with the
> > > > > device, do not select any services after pairing using this first option,
> > > > > just start the wizard again and use option 2 to link to the service and
> > > > > start it.)
> > > > > If you have linked to the service like I described here, you will not need
> > > > > to do this again.
> > > > >
> > > > > I know, it's not a pretty sight, but it works for my setup.
> > > > >
> > > > > good luck, and please give some feedback on your progress. I would like to
> > > > > know if I'm not alone with this issue.
> > > > >
> > > > > regards,
> > > > > Sven
|
|
LinkBack | Thread Tools | Display Modes |
 |
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| bluetooth devices | mtgb | Windows Vista Hardware & Devices | 0 | 12-16-2006 01:19 PM |
| Missing Bluetooth Devices in Control Panel | Iwona | Windows Vista Hardware & Devices | 0 | 08-04-2006 06:28 PM |
| No Bluetooth Devices in Control Panel | Iwona | Windows Vista Hardware & Devices | 0 | 08-04-2006 06:26 PM |
| Bluetooth Devices Control Panel applet missing | Ken | Windows XP Configuration & Management | 2 | 07-22-2004 11:13 PM |
| Bluetooth Devices | Rod P. | Windows XP Device Drivers | 2 | 12-21-2003 08:17 PM |
Linear Mode
Posts: n/a