IntelliType 6.2.1 (the latest release I've been able to find) has a
very nasty bug when used with Excel 2004 under Leopard. I'm running a
MacBook Pro (Core 2 Duo 2.33GHz, 3G RAM). At work, I have an external
monitor, Microsoft Natural Ergonomic Keyboard 4000 and Microsoft
Compact Optical Mouse. When typing in Excel 2004 on my Microsoft
keyboard, one of four things happens:
1. Works normally (about 90% of the time).
2. After typing the first character in a cell, keyboard goes seemingly
dead -- no keys work, not even escape (built-in keyboard on my MacBook
also does not work when this happens)-- but if you click the mouse in
another cell, keyboard works again.
3. Same as #2, but even clicking the mouse does not restore the
keyboard. Use the mouse to quit Excel (mouse still works fine) and
relaunch; Excel and keyboard are back to normal.
4. In event #2 or #3, there is a slim chance (I'd say 10% chance) that
Excel quits. No, scratch that -- EVERYTHING quits. Screen goes blue for
a second, then desktop picture reappears. All programs you had running
are spontaneously closed. Anything you had set to launch at startup
launches, as if the computer has just started up. It's as if the Finder
has unexpectedly quit and relaunched, but it takes all other running
apps down with it. Very, very bad.
I can almost guarantee this is something to do with the IntelliType
driver because if I just use Excel with the built-in keyboard on my
MacBook Pro (like when I'm on the road), the program never quits like
this. It's only when I'm using Excel *and* the Microsoft keyboard. I
can also say it happens in no program other than Excel (I use the
keyboard constantly in Thunderbird, Safari, iCal -- no problems). FYI,
I have the latest Office 2004 patch (11.3.9) and all the latest Leopard
updates (as of this writing, that's QuickTime 7.3/iTunes 7.5).
I would note that IntelliType 6.2.1's do***entation only lists sup****t
up to 10.4, so it's not technically endorsed for Leopard yet anyway.
IntelliPoint 6.2.2 specifically lists 10.5 compatibility, but there is
no matching IntelliType 6.2.2 yet that I know of.
On 2007-11-08 13:13:19 -0500, JE McGimpsey <jemcgimpsey@[EMAIL PROTECTED]
> said:
> In article <1194541669.640982.282850@[EMAIL PROTECTED]
>,
> Ralph <odaba****anr@[EMAIL PROTECTED]
> wrote:
>
>> WTF.
>
> Yup. Being an early adopter does have it's disadvantages. Sucks, and one
> can hope that there will be a fix from one manufacturer or the other
> (after they agree on whose fault it is).
>
> But I'm surprised by your apparent surprise. When a company develops and
> tests an OS-dependent driver on one version of an OS (made by a
> different company), why would anyone find it surprising that the driver
> doesn't work perfectly when you change the OS?
>
> Perhaps Apple should have been more careful to make sure that Leopard
> worked with existing MS drivers, but I don't know what the cost-benefit
> ratio for that would be...
>
> AFAICT, MS is still only advertising that its drivers are compatible
> with OS X 10.2.x-10.4.x.
|
