[bsoplinger1]

Dumb question time...

Around about kext 9 or 10 you forgot to include the small bit of code that would read the prefs and apply them so the kext didn't remember its settings after a reboot. So there was a separate PS2PreferencesSetter or somesuch to add and copy to the location in the plist.

Should I still be using that extra bit or just copying the current version of the prefpane one page 1?

I'm still struggling with the 'after a restart everything is hosed' issue.

Also, the difections on page 10, pointed to by the page 1 entry try to unzip the pref_andHelper (don't have the exact name) and then copy that but there hasn't been one of those for awhile now.

[meklort]

Originally Posted by bsoplinger1

Dumb question time...

Around about kext 9 or 10 you forgot to include the small bit of code that would read the prefs and apply them so the kext didn't remember its settings after a reboot. So there was a separate PS2PreferencesSetter or somesuch to add and copy to the location in the plist.

Should I still be using that extra bit or just copying the current version of the prefpane one page 1?

I'm still struggling with the 'after a restart everything is hosed' issue.

Also, the difections on page 10, pointed to by the page 1 entry try to unzip the pref_andHelper (don't have the exact name) and then copy that but there hasn't been one of those for awhile now.

It's included in the one up there. The naming is changed because the launch agent plist isn't included in the same zip file.
If changing a pref pane value temporarily fixes it, try manually running the preference setter app (but not as root). (see location in previous post). If you can't, that means it isn't there or you didn't chmod + x it.

Originally Posted by mrichardin

Hi,

OK, I removed everything as per instruction, then installed the kext using kext helper, and installed the .plist and prefpanes using shell instructions instead of double clicking. It worked before I rebooted. After reboot, the kext:driver seems not active anymore as the prefpanes has no action on the keypad behaviour. Seems like the setter deactivate the driver ? ecause when the setter is not working (double click installation) then the driver and the prefpanes are both working. I now have to install the kext after each reboot...??

I can't install the driver using the shell scripts you provided as the /Extra doesn't not exist on my OSx distrib.

Marc.

Try doing the above. The setter app won't disable the kext, if anything it just wont initialize it (but you can then use the pref pane to do that). If changing a value in the pref pane doesn't work, then I don't know what the problem is.
The location of the kext doesn't matter, it can be anywhere. What matters is where the setter app is.

[EdZ]

Originally Posted by EdZ

I'd installed the touchpad driver and it was working fine with two-finger scrolling. I then installed the logitech control panel (for my MX revolution), and two-finger scrolling stopped working. I uninstalled and re-installed the touchpad drivers, but still no two-finger scrolling. The prefpane also appears to no longer have any effect on touchpad sensitivity or clicking, even after the re-install.

Tried re-installing with the new kext, still not working. I hope that full mouse support and full touchpad support aren't mutually exclusive.

[meklort]

Originally Posted by EdZ

Tried re-installing with the new kext, still not working. I hope that full mouse support and full touchpad support aren't mutually exclusive.

It shouldn't matter. What might be the problem is that the preference pane and helper app's cannot find the ps2 driver anymore to initialize it. I'll try installing the microsoft mouse drivers and see if I can get it working for that (or if there is a problem).

[mrichardin]

If changing a pref pane value temporarily fixes it, try manually running the preference setter app (but not as root).

Hi,Running it under my user from
/System/Library/Pref.../PS2.../Contents/Resources

I got : (it's chmoded +x and owned by root:wheel)

PS2PreferenceSetter [345:10b] IORegistryEntrySetCFProperties returned on error.

Any idea what that means in your code ?

Thanks,
Marc.

[meklort]

Originally Posted by mrichardin

Hi,Running it under my user from
/System/Library/Pref.../PS2.../Contents/Resources

I got : (it's chmoded +x and owned by root:wheel)

PS2PreferenceSetter [345:10b] IORegistryEntrySetCFProperties returned on error.

Any idea what that means in your code ?

Thanks,
Marc.

That means that it found the kext in memory, but when it tried to send the preferences to it, something happened (but I don't know what). It could mean that the preference file is corrupt, or that the kext doesn't support that method (which it does).
Try deleting the preference file ~/Library/Preferences/com.meklort.ps2.preferences.plist, then reset the preference with the preference pane, and then rerun the helper app. If that doesn't work, then there probably a driver conflict in the system (such as the old trackpad kext being loaded).

[popophobia]

I got : (it's chmoded +x and owned by root:wheel)

PS2PreferenceSetter [345:10b] IORegistryEntrySetCFProperties returned on error.

I got the same error when trying to run it as user. But no error when running as root. I think there is some problem with the permission. Will try to redo the whole thing.

[apparissus]

I got this error as well; deleting the preferences .plist seems to fix it, though it took a couple of tries once.

[bsoplinger1]

Originally Posted by apparissus

I got this error as well; deleting the preferences .plist seems to fix it, though it took a couple of tries once.

Deleting prefs fixed it for me also, which leads to 2 thoughts:

1) Add a "rm ~/Library/Preferences/com.mer..." to the list of commands on page 10 so that any install will start with creating a new preference file since the old one will be removed.

2) Something, perhaps related with sleep, manages to corrupt the preference file. Perhaps the PS2PreferenceSetter (if I got the name right) can determine if the pref file is 'bad' and use (and also write out) a default set of values until the why of the corrupted preferences is found?

[meklort]

Originally Posted by bsoplinger1

Deleting prefs fixed it for me also, which leads to 2 thoughts:

1) Add a "rm ~/Library/Preferences/com.mer..." to the list of commands on page 10 so that any install will start with creating a new preference file since the old one will be removed.

2) Something, perhaps related with sleep, manages to corrupt the preference file. Perhaps the PS2PreferenceSetter (if I got the name right) can determine if the pref file is 'bad' and use (and also write out) a default set of values until the why of the corrupted preferences is found?

It probably become corrupt because of the new preference pane. When the plist is corrupt, it just doesn't initialize the kext, so it uses the default setting which is movement only.
If it does become corrupt, deleting it and regenerating it will always work (I could have the helper automatically delete the preference plist if it becomes corrupt, but the user would still have to reconfigure them manually).