Like a lot of people who frequent this forum, the service pack caused me to lose my icons for ".ufo" files in my system. I have resolved that problem by doing a series of registry tweaks but in my haste I releted the extension from my folder options/file types menu. The result is a mixed result. On the one hand photoimpact no longer crashes upon loading and I do have a permanent ".ufo" icon for that file type. the downside is that I am no longer able to view thumbnails for any of my .ufo files. Does anyone know of a way that I can get this back? I would really prefer to do something through the registry as opposed to a reinstall seeing as how it has taken me so long to adjust my settings to how I can use them comfortably. I should mention that I use photoimpact exclusively as an editor and I would not want to change my current file associations which allow me to preview images through picture & fax viewer (just seems unnecessary to have to load photoimpact every time i want to view a full-sized pic).
I appreciate any help you can give me on this. I really use this program a lot but I have to admit that this is the most buggy of any of the releases I have used thus far. I just need it to work correctly and this one problem I'm facing is the final hurdle in using the program error-free.
.ufo not displaying thumbnails
-
ponsonbybritt
fixed!!
nevermind. I thought this would have been a lot more complicated than it was. anyways, if this ever becomes a problem for anyone in the future, this is how I fixed it. run "regedit" and go into HKEY_CLASSES_ROOT\.ufo to make changes. Oddly enough, my registry already had an entry there but knowing it wasn't working, I deleted the .ufo string. I have a second computer with photoimpact 11 on it so all I did was copy the string from the working computer to the one where it wasn't working by right-clicking on it and pressing "export". voila! problem solved.
If this of value to anyone else out there, here is a snapshot of the information to recreate the string manually.
If this of value to anyone else out there, here is a snapshot of the information to recreate the string manually.
-
heinz-oz
I'm glad that this worked for you. You are a very courageous person. To muck around in the registry, like you have, can have disastreous consequences. It is very easy, too easy in fact, to corrupt the registry, ending up with a PC which won't even boot up anymore.
I'm not saying that you don't know what you are doing but, surely, some people reading your post don't.
I think I speak for all responsible people on this board: If you are unfamiliar with tinkering in the registry, don't. You may render your system useless. At the very least, back up your registry first, export the current registry key and import it back after you made your changes.. Before you do anything, make sure you know the process to restore your registry after a corruption and, NO, I'm not talking about the famous "System Restore". If you corrupt your registry, you will not even be able to get this far.
I'm not saying that you don't know what you are doing but, surely, some people reading your post don't.
I think I speak for all responsible people on this board: If you are unfamiliar with tinkering in the registry, don't. You may render your system useless. At the very least, back up your registry first, export the current registry key and import it back after you made your changes.. Before you do anything, make sure you know the process to restore your registry after a corruption and, NO, I'm not talking about the famous "System Restore". If you corrupt your registry, you will not even be able to get this far.
-
ponsonbybritt
I completely agree with you on that. By no means did i intend for people to start messing around with their registries unwittingly. In fact, the reason why I posted the screenshot was to clarify what exactly I had done and where. Even though most of the experiences I have had working with the system registry have not yielded results quite as cataclysmic as a full-on system failure, even slight changes made to the wrong things can create minor, albeit very annoying effects on a system.
As I stated before, I really am a fan of ulead and I have been using their products since photoimpact 3.2 (or something around there) that I bought along with my very first pc. I love the customizeable interface they put in with recent versions because I find it very aggravating to have to search through multiple submenus for many of the features I use. With PI11, I seem to be facing a LOT of problems though and from what I have read in this forum, those problems are hardly unique. Is there any word on a photoimpact 12, or possibly a new service pack or build for PI11 that will address these problems?
As I stated before, I really am a fan of ulead and I have been using their products since photoimpact 3.2 (or something around there) that I bought along with my very first pc. I love the customizeable interface they put in with recent versions because I find it very aggravating to have to search through multiple submenus for many of the features I use. With PI11, I seem to be facing a LOT of problems though and from what I have read in this forum, those problems are hardly unique. Is there any word on a photoimpact 12, or possibly a new service pack or build for PI11 that will address these problems?