Here's what I posted on logitech forum when I had 355TM and solved few people's problems. Hope this helps someone lol.

Ok guys, my BT mouse and keyboards are finally working as they are supposed to via internal BT.

Here's what you do.

Uninstalll the setpoint you have, don't reboot, and uninstall Widcom crap that came with Dell drivers, dont reboot, go to start and type in msconfig in search. You should now be at system configuration panel, now, go to tools, click on "disable UAC" and click launch. Reboot, install latest Setpoint - Right click it, and run as admin! -setpoint 3.3bt in my case-. Add your devices, and it should work like a charm now!!

what OS were you running? I've done all that before and I have no problems getting my keyboard and mouse to connect and recognize. It even works the way it should for a while. But exiting a game or sometimes just playing a video or MP3, the mouse craps out and is only usable as a 2 button mouse (not even the scroll works). Then I have to open the Device Manager and disable/enable the bluetooth 355+ for it to work again.

BTW, I have no problems what so ever getting it to work properly in WinXP, it's only Vista32 and 64.

Vista. I also had tough time on setpoint with 355 module on my old E1705. It would recognize the buttons after reboot, but wouldn't work in games/after games like yours did.


The solution did provide solutions for some people who had 355, and mine did work for awhile too, but after some programs, I think BT module/drivers crapped out and reinstalled the 2 mouse button thingy and was back to square one.

Try to get 350 (15bucks at Ebay) module, uninstall widcomm. Install setpoint 4.0 beta(link in this thread) It works like a charm with the current M90.

Oh and yes, logitech pisses me off on lack of support on this issue.

yea, I just got fed up with fighting with it. I'm using the dongle for the time being. I really don't know who I should blame for the problem though. Is it a problem with Logitech's drivers not seeing the 355+ properly, is it the 355+ drivers, or is it a problem with Vista itself?

When I spoke to logitech support, they were blaming Vista, but who knows. Think of it as you lost 20 bucks somewhere, and invest it on 350 module. I read someone saying 350 working flawlessly with dinovo set, and was bit skeptical about it since 355 was the newer one etc. Now that I experienced it with 350, I'm with the guy whoever said it. I have no clue why, but 350 and dinovo set works flawlessly. All the key settings work in games etc, and never went wrong since I got the system.

One thing that killed me when I had E1705 with 355 was that I would reboot, all the mouse key worked right after reboot, and I go in games or run 3dmark05, and the setpoint wouldn't even recognize any of the dinovo sets inluding the mouse. I gave up and just used the dongle myself.

When I got the M90, I remembered one guy who said 350 worked well, and gave it a try, and it does work flawlessly with 350. I have no clue why/how though.

okay. I sorta have one from my Dell XPS-M170. Since I wasn't using it in that one I gave the module to a buddy of mine that has an m600. He only uses it to synch his cell phone so I don't think he'd see a difference either way since I've only seen people have problems with logitech mice. I'll get him to swap for a bit and I'll see if the 350 will work properly.
I'll keep everyone posted on this since I know others still come to read this thread, including Dell reps.

which driver versions are you using with your dell 355?

let me know I can post links to newer ones for you to try.

the latest one that's on their site. I go there every day to see if there is anything new. The last release date that they have for the 355+ for vista is January 26th

I am having problems with my e1705 and Microsoft bluetooth keyboard and mouse. The connection goes out every 10 mins or so then comes back after 20-30 seconds. And my mouse backward, forward, scroll wheel go out ocassionally.

Any solutions for this?

that's the same problem that we're all getting. It seems that there's something wrong with the 355 bluetooth module - mainly it sucks A$$. For now I've disabled it in the BIOS and using the bluetooth USB key that came with my Logitech until I hook up with my friend again and get the 350 module back from him.

Bt 355 adapter

ftp://drivers.anycom.com/beta/usb200...-3300-BETA.exe

for windows XP

and

ftp://drivers.anycom.com/beta/usb200...-5100-BETA.exe

for vista.

Both work awsome, don't mind the beta they are WHQL.

nope, doesn't work. I installed them, all works well. Went to play Splinter Cell Double Agent and lost all functionality other than two buttons. No scroll, no nothing. Came out to windows to verify and yup, it's only a two button mouse again.

Did you try the 350 module yet?

naw, not yet. My buddy still has it and I'm still trying to hook up with him again. He moved so we don't see eachother often. I keep bugging him about it though, lol. I'm also in the process of apartment hunting so going out of my way to hook up with him for a module isn't top of my list since it's at least working right with the USB plug. I will keep everyone updated as soon as I do get it back from him though.

Dude, 350 module on Ebay is only 8-9 bucks -.-.