Office Picture Manager opens slowly

My Office Picture Manager become very slow to open, what to do?

All file paths that are open are stored in this file OIScatalog.cag, so Network paths and other paths may no longer exist, causing a Delay when opening Picture Manager, now what to do?

Windows, Windows XP

1. Go to File OIScatalog.cag that is in your LOCAL Profile %\Documents and Settings\\LocalSettings\Application Data\Microsoft\OIS%

2. Look for "MRU PATH" and Delete all paths that no longer exist

Windows Vista

1. Go to File OIScatalog.cag that is in your LOCAL Profile %\Users\\AppData\Local\Microsoft\OIS%

2. Look for "MRU PATH" and Delete all paths that no longer exist

Links:

http://techblog.johnner.com/2005/11/microsoft-office-picture-manager-opens.html

http://msmvps.com/blogs/officept/archive/2006/04/09/office-picture-manager-very-slow-to-open.aspx

Comments

Post a Comment

Popular posts from this blog

Graylog - an easy solution for log management

Image
Recently, I was researching for opensource log management tools. I had only two requirements. Log Search and Log analytics. A lot of posts in the internet suggested me to use an ELK stack. But, I wanted to do something different. I found graylog as an alternative to ELK. One can setup and run it in minutes. It uses mongodb, elastic search and graylog server. Here is the login page: grylog provides different options to stream logs into graylog server. I used the simple UDP listener and forwarded logs from multiple devices into this listener. Next step is to create dashboards using the search. Here is the search page: Once search is done, you can add the widgets to a dashboard. The dashboard will help you to get the summary of your devices at one shot. It is also possible to generate alerts on different conditions. More here: https://www.graylog.org/
Read more

Comparing C and Go Lang - My first impression

Of late we are hearing a lot about go lang (https://golang.org/). I was also curious about this. I wanted to run some experiments with go and C. As expected, the experiment was started with "hello world". Here is the C code that I have used: ------------------------------------------------ #include "stdio.h" int main(int argc, char** argv) {    printf("hello, world\n");    return 0; } ------------------------------------------------ Corresponding go code is: ------------------------------------------------ package main import "fmt" func main() {     fmt.Printf("hello, world\n") } ------------------------------------------------ Well, both of them look simple. But I was astonished after creating the exe file. Below are the sizes of exe files created by C ( 51k ) and Go( 2MB ) 06/03/2016  03:41 PM            51,712 hello_c.exe 06/03/2016  03:37 PM         2,434,560 hello...
Read more