Sax and dotty not working in windows 7 64bit
![sax and dotty not working in windows 7 64bit sax and dotty not working in windows 7 64bit](https://veterinariaonline.com.ar/wp-content/uploads/2019/08/Incurin_tcm55-33233.jpg)
I also recommend going into the "regedit" program and looking up the existing default values for these and adjusting the file to suit your own needs that way.
![sax and dotty not working in windows 7 64bit sax and dotty not working in windows 7 64bit](https://images.drivereasy.com/wp-content/uploads/2018/08/img_5b7a8387d8ba7.jpg)
You will also want to edit this file to include the extensions YOU want to affect, and delete the ones here that you don’t work with regularly. I made an additional string entry for myself that gives me a backup-copy of that string in case I ever want to put it back, like this: C extension key, the original default value was "VisualStudio.c.10.0". My initials are "vw" so this new default value is set up so that it cannot clash with any new Multi-Edit releases.įor the. "orig_default_value_vw"="VisualStudio.c.10.0" I went to the extent to save the original values on some keys so I can put them back if ever needed. Or simply to make sure that the two systems on which I use Multi-Edit are identical.Ĭaution: examine these keys closely, as if you don’t have VisualStudio 10.0 installed, some of these values will be different.
Sax and dotty not working in windows 7 64bit install#
REG file so that I can easily install it AGAIN next time I re-build a system. And remember that on Windows7 64-bit, if you kept the default directory, it is going to have a "(x86)" in it, like this:
![sax and dotty not working in windows 7 64bit sax and dotty not working in windows 7 64bit](https://u.jimcdn.com/cms/o/s01bc8bbf3a78df54/emotion/crop/header.jpg)
If you have your Multi-Edit installed on D: drive instead of C:, then change the drive letter. If you use the below, edit the execution path to match your own. Meanwhile, I have devised my own solution that I will share with everyone. Both of the above worked perfectly under Windows XP, and I wish that the fabulous Multi-Edit team would fix this one for us Windows7 users, as I think it would well take less than a day to fix. In my world, this is a rather important production-hindering bug, and suspect it is just a permissions issue adding keys to the registry? Because I don’t see the keys at all (thought I am not sure which ones I should be looking for). Tools > Customize > File extensions > pick_extension > Edit > Associate to Desktop Shell Tools > Customize > File extensions > Create "Edit with Multi-Edit" shell extensionĭefinitely DOES NOT work on either my Windows7 32-bit nor my Windows7 64-bit system. I recently migrated my desktop and laptop development computers from Windows XP to Windows 7 (one 64-bit and one 32-bit) and ran into a bug that SOUNDS similar, although I have tested on both systems, and Hi Clay, and all those who are also affected by this bug.