Jump to content


  • Content count

  • Joined

  • Last visited

About kkrull

  • Rank
    InsanelyMac Protégé
  1. Jeff, Thanks for your help on this. I have been stuck for a month. For anyone else working on this, from safe mode I could not see the \class\ folder but if I performed a 'find' for InputRemapperFilter then regedit would open it and I could see it. I assume you removed the \Services\InputRemapperFilter\ entries, but left the \Enum\HID\VID_0461&PID_4D01\ and \Enum\HID\VID_05AC&PID_021A&MI_00\ entries in which there are subkey values called 'ActiveService' set to InputRemapperFilter
  2. My latest thinking is to try a registry cleaner, maybe one that is smart enough to return the mouse and keyboard drivers to something functional after inputremapperfilter is removed and the machine is restarted in repair mode. The problem is that in general registry cleaners are not smart enough to realize that they are in repair mode and they clean the repair mode registry instead of letting the user clean the broken windows directory. Anyone have experience with this?
  3. Ok, so I missed uninstalling InputRemapper before I installed Windows 7 RC. Now I can't uninstall it. I can't sucessfully remove it. And it crashes Windows. I have put an enormous amount of time into trying to repair the computer, manually uninstall, fix the registry, install new drivers, learn devcon, start and stop services, etc. You may think that I should just reinstall but unfortunately I have some very expensive software that must be de-authorized so I really need to get the OS working one last time before I reformat the OS. Any advice?
  4. kkrull

    InputRemapper 1.0.04 Windows RC 1 (7100)

    Cut your losses and reinstall. I have spent more than ten hours on this and cannot find a work around to get input remapper uninstalled after Win 7 RC. I should have done it before.
  5. I have not been able to get Input Remapper working on my MacBook Air. The function key and the eject key do not seem to be recognized. I have tried this with the default keyboard driver and the Apple keyboard driver. I am running Vista x64, but I would think that the issue would exist on x86 as well. Any ideas? Anyone have XP or Vista in either bit version and have Input Remapper installed on the Air?
  6. kkrull

    Triplebooting rEFIt into Vista by default

    Linux. Looks like if you use setup tripleboot the most common way you will get Linux first by using that switch. I would be interested if anyone gets a different result.
  7. Has anyone tried the lecacyfirst switch on rEFIt? Will it boot Linux or Vista first?
  8. kkrull

    32-bit/64-bit Vista?

    I had the Vista x64 verison running fine nine months ago but couldn't get the Atheros wireless drivers for x64 and went back to x86. This has since been fixed. Over the upcoming year end holiday I will be reinstalling everything and will switch to Vista x64. I expect there to be issues with advanced bluetooth profiles, which is ok. Also, since Vista won't run unsigned drivers on x64, an old scanner and printer will need to be discarded, which is probably overdue anyway. I don't expect any application trouble. Go for x64.
  9. kkrull

    Bluetooth Fix

    I got this working and have long since forgotten how. I do know that as of year ago I had to... modify the .inf file to get Windows out of bluetooth HID mode download CSR software to enable advanced profiles work around windows forgetting where all the default .inf files were (probably won't happen to you) I stuck with the Microsoft stack. I tried the others and didn't care for them.
  10. kkrull

    Multiboot x4?

    The three OS limit is a firmware drive partition limit, so if you are willing to install the fourth OS to a CD (LiveCD Linux or PE Windows) or if you are willing to install to ExpressCard flash memory (like eFilm exprescard to SDHC adapter) then you can have a pretty easily removable fourth OS that boots from rEFIt and has its OS its own partition. Just follow the standard triple boot procedures and then add your fourth OS (probably XP or Linux). Alternatively you can put XP on the same partition as Vista if you install it into a folder other than c:\windows (where Vista goes) and use a non-standard program files directory and non-standard user directory. I would not recommend this unless you have done it before and as an added drawback you will have to navigate both the graphical EFI boot menu and the character based windows boot loader menu. Setting up three OSs on rEFIt was more than I cared to learn.
  11. I have a rEFIt triple booting pre-Santa Rosa Macbook Pro and I recieved a blank boot screen in Vista after the above automatic update rebooted. OSX and linux continued to boot fine. Looks like it was fixed pretty quickly in rev 3 of the update. http://support.microsoft.com/Default.aspx?kbid=941649. Makes me wonder what happened to the rev 1 users. Keep your install\repair disks handy if you have automatic updates turned on.
  12. kkrull

    Input Remapper 1.0.02 Beta

    I had Input Remapper 1.0.01 running on a CoreDuo MacBook with Vista Ultimate 32 bit. I had some problems keeping the settings, but usually it ran fine. I have not been able to get version 1.0.02 working properly on this configuration.
  13. In 32 bit Vista I see two for me as a user and one more SYSTEM process if I select "show processes from all users"... InputRemapper.x86.exe SYSTEM 660K Input Remapper Runtime InputRemapper.x86.exe SYSTEM 740K Input Remapper Runtime InputRemapper.x86.exe (user) 956K Input Remapper Runtime
  14. I have a new Macbook Pro running 32 bit Vista and the latest build of Input Remapper does not see the eject key. I can't manually create a new key binding because it doesn't see the keypress. Also the default mappings for that key do not do anything when the key is pressed. I have reinstalled the apple keyboard driver and re-uninstalled that driver and then reinstalled input remapper but it never works. Great program, but I think something got broken along the way.
  15. This driver works fine for me in Vista Ultimate on a Macbook Pro. I would have expected the remote to function slightly differently in Windows Media Player as the pause and play/resume works as start and stop and the up and down arrows scroll up and down the playlist (you still have to select or 'play' the file) and the forward and back buttons do not move forward and back in the playlist. Still - awesome job.