Intellitype (Microsoft keyboard driver) conflict with Dell keyboard driver

Hunter,

I use a Dell external keyboard and a Microsoft Bluetooth IntelliMouse, but run it on the Dell supplied ALPS Drivers.

My thought on how to install IntelliPoint without disrupting the ALPS Drivers (which IntelliPoint would remove) is
to use Control Panel; System, Hardware tab and Hardware Profiles. You would follow that by going into Device Manager
and select "Do not use this device in the current hardware profile (disable)" for each 'profile'.

Here you can set up as many "Profiles" as you want but I would try one with MS Keyboard and one without.

I would expect it would take a reboot to change and you can set it to use a 'default profile' after a
specified number of 'choose' seconds on bootup. My system does switch itself between 'Docked' and
'Un-Docked' without re-boot, automatically.

As a general rule: "Only One Driver can control a hardware device" and two communication devices cannot
share the same 'Port'. I know the way around the second 'rule' but have never tried the "Driver conflict"
issue as there is nothing on IntelliPoint that I need or want to have.

We would all be interested to know if the "Different Hardware Profile" idea works for you.

The thing is (for example) my Logitech mouse and the trackpad work fine as the trackpad is PS2 and the mouse is USB.  The Logitech drivers are even nice enough to tell you on install that a PS2 trackpad was detected and that the drivers are only installing for USB so as not to conflict.  I had hoped that either Dell would do what it takes to work with Microsoft or mebbe Microsoft had a similar feature that just wasn't automatically done as the Logitech did.  I guess while Microsoft seems to make the better ergo keyboard (the new ergo 4000), their drivers still create a vacuum.

- Hunter

Hunter,

The Fn functions you mention are controled either by Dell Notebook Software or Dell QuickSet, are those installed and operating?

My Device Manager shows two Keyboards, one "Standard 101/102-Key or Microsoft Natural PS/2 Keyboard" as well as a "HID Keyboard Device"
and I don't even know which is for what, but they both have Microsoft Drivers with no "Dell Drivers" involved.

The Mice and other pointing devices list an ALPS Touch Pad as well as a HID-compliant Device, there is an ALPS Control Console that
has a lot of settings and features missing from a generic PS2 mouse. My main gain with IntelliPoint would be control over the
"Side-Scroll" portion of the Wheel, but I would then lose the ALPS Console with (among a lot more settings) the ALPS "Auto-Scroll"
that I can set to activate by IntelliMouse and provides better scroll control (vertical & horizontal) than the Wheel.
DragLock can only be locked with the touchpad, but it can then be dragged and released by the IntelliMouse.

Art

Hunter,

Long, long ago, (Win98) there had been some program/utilities that were needed at times but caused problems with other programs when installed,
best solution for that had been to monitor the installs with CleanSweep and have CS remove them with a compressed backup copies. I had also
dealt with conflicts by using two different copies of the Registry.

Then, anytime I wanted one of those 'problematic programs' CleanSweep would restore it in about a minute and then remove it again when I was
done with it. I have not run into this 'conflict' with WinXP, but if I did, I would try to manage it with "Hardware Profiles" as Norton's
version of CleanSweep is not as slick, quick and reliable as QuarterDeck's had been.

After a Microsoft UpDate to Service Pack 2, I had lost a lot of the Fn 'functions' and it took a reinstall of Dell QuickSet to get them back.

Strange things happen at times with Programs, install of the Dell/Widcomm Bluetooth Stack/Driver will cause a momentary 'on-screen' notification
when 'CapsLock' is turned on/off and if that is bothersome to anyone, a Registry Modification will stop it. No idea why DBTW would have anything
to do with CapsLock notifications?

You might Email Microsoft's Support for your Keyboard, your fix might be as 'simple' as a Registry Edit. To get an idea on this, create a copy
of your Registry when Fn's were functional and install that copy (with a new current Registry Copy saved) after the MS Keyboard had blocked them.
WARNING fooling with Registry can render your Operating System In-Operable, use utmost caution when going there!!!

Your experience with SetPoint is encouraging. I had given up on Logitech ever introducing an "All-Terrain" Laser Mouse for Bluetooth and got
the IntelliMouse (which I love, but it is not 'Laser') and LOOK at what Logitech has NOW

That is where I would go if I had your sort of problem, put the IntelliType on eBay and buy the MX5000 on eBay at the same time, again Use Caution!

Art