Hello,
Thanks for the update and the great information.
I have reviewed this, and, as I'm sure you are aware, it would appear that
the difference is in how the Office Picture Manager registers its file
association in Windows. I have noticed that by modifying the
HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Explorer\FileExt
s\.bmp key, I can control the Windows side registration to associate the
file with OIS. However, OIS does not have the association registered.
When I double click a .bmp file it launches in OIS. Based on this
experience, I assumed that this would resolve your issue, though I
understand more clearly now that it does not.
When I associate .bmp files in OIS, I notice the same keys change as are
demonstrated in your sample script. After this setting is changed, the
.bmp file will be visibly associated in OIS. However, I can change the
file association again in Windows to 'always open' with mspaint, iexplore,
or etc... and have the Windows setting override OIS. At this point OIS
will still display that the .bmp file is associated, though double clicking
the file will launch the other application. This behavior seems
particularly linked to the HKCU keys, especially the Application string.
To test this, I performed these steps.
1. I opened OIS.exe and set it to associate with the .bmp file types. I
could then double-click a .bmp file and it would launch in OIS
2. I reviewed the registry and noticed the HKEY_CLASSES_ROOT\.bmp (default)
string value is set to OISbmpfile
3. In Windows Explorer, I right clicked Open with Choose Program
Paint Always use the selected program...
4. Reviewed the settings in OIS, and noticed that the .bmp setting is still
set to associated
5. Reviewed the HKCU key
HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Explorer\FileExt
s\.bmp key and noticed the string value Application set to mspaint
6. Deleted the Application string and again the file opened with OIS when
double clicked
7. Added the Application string back and set it to OIS.exe and again the
file opened with OIS when double clicked
8. Modified the Application string to mspaint.exe and bmp files again open
with Paint, though OIS still shows the association.
Based on this research, it would appear that the .reg file I suggested
previously should add the necessary keys to associate graphics files with
specific applications in Windows, though they may not show as specifically
associated in OIS. If this was not your experience, I would be curious to
know what did happen when you tested it on your end.
Also from this experiment, it seems that you may want to include the
HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Explorer\FileExt
s\.bmp key in your .reg file and set the Application string value to
ois.exe.
I hope this information is helpful, that you are well rested now, and that
things will go more smoothly for you. Please keep us posted with your
progress, and if you have any more questions I'd be happy to help.
Kindest regards,
Dana
Dana Brash
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.
This and other support options are available he
BCPS:
https://partner.microsoft.com/US/tec...rview/40010469
Others:
https://partner.microsoft.com/US/tec...pportoverview/
If you are outside the United States, please visit our International
Support page:
http://support.microsoft.com/common/international.aspx.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
Thread-Topic: .jpg .gif .bmp file associations gone, upgrade from Office XP
thread-index: AcUUla2VMyIQIUp9Re26Kp2xpYoGDA==
X-WBNR-Posting-Host: 64.1.44.68
From: "=?Utf-8?B?ZmJhcnRyb20=?="
References:
Subject: .jpg .gif .bmp file associations gone, upgrade from Office XP
Date: Wed, 16 Feb 2005 18:09:14 -0800
Lines: 675
Message-ID:
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.office.setup
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.office.setup:10586
X-Tomcat-NG: microsoft.public.office.setup
I am taking the approach to add the registry keys to the transform for the
systems I have not deployed yet. I have a large number of stations that
are
already deployed and I will push the registry change to them using SMS.
The important keys to add are apparently in HKCR. I am using Regmon to
find
out exactly what is changing as I set the File Type in Picture Manager.
For
instance with the jpeg the "HKCR\.jpg" and "HKCR\OISjpegfile"registry
trees
are changing and the
"HKEY_CURRENT_USER\Software\Microsoft\Windows\Cur rentVersion\Explorer\FileE
xt" registry setting is not change by the Picture Manager Process.
Based on my research, here is the regfile that will set .bmp, .gif. .jpe,
.jpeg, .jpg and .png files to open with Picture Manager. Now I have to
get
it into my transform and test it on my VM, but first I need some shut eye.
=======================================
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\.bmp]
@="OISbmpfile"
[HKEY_CLASSES_ROOT\.gif]
@="OISgiffile"
[HKEY_CLASSES_ROOT\.jpe]
@="OISjpegfile"
[HKEY_CLASSES_ROOT\.jpeg]
@="OISjpegfile"
[HKEY_CLASSES_ROOT\.jpg]
@="OISjpegfile"
[HKEY_CLASSES_ROOT\.png]
@="OISpngfile"
[HKEY_CLASSES_ROOT\OISbmpfile]
@="Bitmap Image"
"EditFlags"=hex:00,00,00,00
[HKEY_CLASSES_ROOT\OISbmpfile\DefaultIcon]
\", 3"
[HKEY_CLASSES_ROOT\OISbmpfile\shell]
[HKEY_CLASSES_ROOT\OISbmpfile\shell\Edit]
[HKEY_CLASSES_ROOT\OISbmpfile\shell\Edit\command]
\" /shellEdit \"%1\""
[HKEY_CLASSES_ROOT\OISbmpfile\shell\Open]
[HKEY_CLASSES_ROOT\OISbmpfile\shell\Open\command]
\" /shellOpen \"%1\""
[HKEY_CLASSES_ROOT\OISbmpfile\shell\Preview]
,-550"
[HKEY_CLASSES_ROOT\OISbmpfile\shell\Preview\command]
\" /shellPreview \"%1\""
[HKEY_CLASSES_ROOT\OISgiffile]
@="GIF Image"
[HKEY_CLASSES_ROOT\OISgiffile\DefaultIcon]
\", 2"
[HKEY_CLASSES_ROOT\OISgiffile\shell]
[HKEY_CLASSES_ROOT\OISgiffile\shell\Edit]
[HKEY_CLASSES_ROOT\OISgiffile\shell\Edit\command]
\" /shellEdit \"%1\""
[HKEY_CLASSES_ROOT\OISgiffile\shell\Open]
[HKEY_CLASSES_ROOT\OISgiffile\shell\Open\command]
\" /shellOpen \"%1\""
[HKEY_CLASSES_ROOT\OISgiffile\shell\Preview]
,-550"
[HKEY_CLASSES_ROOT\OISgiffile\shell\Preview\command]
\" /shellPreview \"%1\""
[HKEY_CLASSES_ROOT\OISjpegfile]
@="JPEG Image"
"EditFlags"=hex:00,00,00,00
[HKEY_CLASSES_ROOT\OISjpegfile\DefaultIcon]
\", 1"
[HKEY_CLASSES_ROOT\OISjpegfile\shell]
[HKEY_CLASSES_ROOT\OISjpegfile\shell\Edit]
[HKEY_CLASSES_ROOT\OISjpegfile\shell\Edit\command]
\" /shellEdit \"%1\""
[HKEY_CLASSES_ROOT\OISjpegfile\shell\Open]
[HKEY_CLASSES_ROOT\OISjpegfile\shell\Open\command]
\" /shellOpen \"%1\""
[HKEY_CLASSES_ROOT\OISjpegfile\shell\Preview]
,-550"
[HKEY_CLASSES_ROOT\OISjpegfile\shell\Preview\comman d]
\" /shellPreview \"%1\""
[HKEY_CLASSES_ROOT\OISpngfile]
@="PNG Image"
"EditFlags"=hex:00,00,00,00
[HKEY_CLASSES_ROOT\OISpngfile\DefaultIcon]
\", 4"
[HKEY_CLASSES_ROOT\OISpngfile\shell]
[HKEY_CLASSES_ROOT\OISpngfile\shell\Edit]
[HKEY_CLASSES_ROOT\OISpngfile\shell\Edit\command]
\" /shellEdit \"%1\""
[HKEY_CLASSES_ROOT\OISpngfile\shell\Open]
[HKEY_CLASSES_ROOT\OISpngfile\shell\Open\command]
\" /shellOpen \"%1\""
[HKEY_CLASSES_ROOT\OISpngfile\shell\Preview]
,-550"
[HKEY_CLASSES_ROOT\OISpngfile\shell\Preview\command]
\" /shellPreview \"%1\""
=======================================
"Dana Brash [MSFT]" wrote:
Hi,
Thanks for your response, and I'm sorry to hear that the steps I
provided
did not resolve the issue for you.
I look forward to hearing how things go with Bob's suggested addition.
If
possible, please let me know which of the 3 options you were trying,
what
steps you followed, and what the actual results were. I would be very
happy to continue working on solving this problem with you. Please
provide
me with this further information so that I may continue my research.
Thanks very much!
Sincerely,
Dana Brash
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to
all
Microsoft technology partners in the United States and Canada.
This and other support options are available he
BCPS:
https://partner.microsoft.com/US/tec...rview/40010469
Others:
https://partner.microsoft.com/US/tec...pportoverview/
If you are outside the United States, please visit our International
Support page: http://support.microsoft.com/common/international.aspx.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no
rights.
--------------------
Thread-Topic: .jpg .gif .bmp file associations gone, upgrade from
Office XP
thread-index: AcUUghdR3dNtfosmRqi7ZXay0LwgQg==
X-WBNR-Posting-Host: 64.1.44.68
From: "=?Utf-8?B?ZmJhcnRyb20=?="
References:
Subject: .jpg .gif .bmp file associations gone, upgrade from Office
XP
Date: Wed, 16 Feb 2005 15:49:01 -0800
Lines: 402
Message-ID:
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.office.setup
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
Path: TK2MSFTNGXA01.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFT NGXA03.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.office.setup:10582
X-Tomcat-NG: microsoft.public.office.setup
It didn't work. I am checking into the additional registry keys in
HKEY_Classes_Root that Bob mentioned.
"Dana Brash [MSFT]" wrote:
Hello,
Just want to write in to see if you have opportunity to review my
previous
post. Thanks also to Bob for his contribution.
Please drop me a quick note at your convenience to let me know the
current
status of this issue. If you have any concerns, please do not
hesitate
to
let me know.
Thanks, and have a great day! 
Sincerely,
Dana
Dana Brash
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader
so
that others may learn and benefit from your issue.
================================================== ===
Business-Critical Phone Support (BCPS) provides you with technical
phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week
to
all
Microsoft technology partners in the United States and Canada.
This and other support options are available he
BCPS:
https://partner.microsoft.com/US/tec...rview/40010469
Others:
https://partner.microsoft.com/US/tec...pportoverview/
If you are outside the United States, please visit our International
Support page:
http://support.microsoft.com/default...rnational.aspx.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no
rights.
--------------------
X-Tomcat-ID: 54056339
References:
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
From: (Dana Brash [MSFT])
Organization: Microsoft
Date: Mon, 14 Feb 2005 02:53:39 GMT
Subject: .jpg .gif .bmp file associations gone, upgrade from
Office
XP
X-Tomcat-NG: microsoft.public.office.setup
Message-ID:
Newsgroups: microsoft.public.office.setup
Lines: 294
Path: TK2MSFTNGXA01.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.office.setup:10515
NNTP-Posting-Host: TOMCATIMPORT1 10.201.218.122
Hello,
Thank you for your prompt response, and I apologize for my delayed
response
due to the weekend. I also apologize that I did not fully
understand
your
original concerns and provide a more thorough answer. I have
performed
further research to more thoroughly answer your question.
When Office 2000 or Office XP is upgraded to Office System 2003, the
graphic file extensions associated with Microsoft Photo Editor are
removed
even if the extensions have been re-associated with a different
graphics
file handler. Although Office 2003 installs the Microsoft Office
Picture
Manager, it does not automatically associate the graphics file
extensions
during the installation.
Picture Manager offers the user a choice during the first run by the
user.
Unfortunately, this is by design. It is a limitation in Windows
installer
because it does not know the file association to keep it if it is
associated to something else.
There are several options to manage this scenario. Please choose
the
option that best applies to your needs.
Option 1:
You can re-install Photo Editor on all the systems. This is
essentially
rolling out an office installation through current methods and only
installing the Photo Editor component. To re-install Photo Editor
please
follow the instructions in this link:
http://support.microsoft.com/?id=817095
Option 2:
You can include the necessary registry settings in your MST by
adding
the
keys in CIW to associate the graphics files with the appropriate
applications. I have generated a sample script for you below. You
should
generate your own script following these steps:
1. On a system that is configured with appropriate file
associations,
export the following registry keys to file:
HKEY_CURRENT_USER\Software\Microsoft\Windows\Curr entVersion\Explorer\FileEx
t
s\.bmp
HKEY_CURRENT_USER\Software\Microsoft\Windows\Curr entVersion\Explorer\FileEx
t
s\.gif
HKEY_CURRENT_USER\Software\Microsoft\Windows\Curr entVersion\Explorer\FileEx
t
s\.jpe
HKEY_CURRENT_USER\Software\Microsoft\Windows\Curr entVersion\Explorer\FileEx
t
s\.jpeg
HKEY_CURRENT_USER\Software\Microsoft\Windows\Curr entVersion\Explorer\FileEx
t
s\.jpg
* you can of course add the keys for any other image files you
want
to
associate as well
** to export the keys, open regedit, browse to the key, right
click
and
choose export
2. Copy the resultant .reg file information into one .reg file,
including
the "Windows Registry Editor Version 5.00" line only once at the top.
3. In CIW, on screen 12 of 24, Import the .reg file created in step
#2.
Here is a sample file that I created from my system:
++++++//BEGIN FILE CUT BELOW LINE\\++++++++++++
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Explorer\FileE
x
ts\.bmp]
"Application"="ois.exe"
[HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Explorer\FileE
x
ts\.bmp\OpenWithList]
"a"="mspaint.exe"
"MRUList"="dcba"
"b"="iexplore.exe"
"c"="shimgvw.dll"
"d"="OIS.EXE"
[HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Explorer\FileE
x
ts\.bmp\OpenWithProgids]
"Paint.Picture"=hex(0):
[HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Explorer\FileE
x
ts\.jpg]
[HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Explorer\FileE
x
ts\.jpg\OpenWithList]
"a"="shimgvw.dll"
"MRUList"="ebadc"
"b"="mspaint.exe"
"c"="iexplore.exe"
"d"="msnmsgr.exe"
"e"="OIS.EXE"
[HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Explorer\FileE
x
ts\.jpg\OpenWithProgids]
"jpegfile"=hex(0):
[HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Explorer\FileE
x
ts\.gif]
"Application"="ois.exe"
[HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Explorer\FileE
x
ts\.gif\OpenWithList]
"a"="shimgvw.dll"
"MRUList"="ebadc"
"b"="mspaint.exe"
"c"="iexplore.exe"
"d"="msnmsgr.exe"
"e"="OIS.EXE"
[HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Explorer\FileE
x
ts\.gif\OpenWithProgids]
"giffile"=hex(0):
++++++++++//END FILE CUT ABOVE LINE\\++++++++++++++++
Option 3:
If you have already rolled out the installation and would rather not
re-install office, you can publish a .bat file or implement it as a
login
script to call the .reg file created above. The .bat file should
include
a
line to call the .reg with this syntax:
REGEDIT /S "\\servername\Sharename\name.reg"
Hope this helps!
Sincerely,
Dana Brash
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your
newsreader
so
that others may learn and benefit from your issue.
================================================= ====
Business-Critical Phone Support (BCPS) provides you with technical
phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week
to
all
Microsoft technology partners in the United States and Canada.
This and other support options are available he
BCPS:
https://partner.microsoft.com/US/tec...rview/40010469
Others:
https://partner.microsoft.com/US/tec...pportoverview/
If you are outside the United States, please visit our International
Support page:
http://support.microsoft.com/default...rnational.aspx.
================================================= ====
This posting is provided "AS IS" with no warranties, and confers no
rights.
--------------------
Thread-Topic: .jpg .gif .bmp file associations gone, upgrade from
Office
XP
thread-index: AcUQfDxfDDroTTX1QPawpgjcTHsjow==
X-WBNR-Posting-Host: 64.1.44.68
From: "=?Utf-8?B?ZmJhcnRyb20=?="
References:
Subject: .jpg .gif .bmp file associations gone, upgrade from
Office XP
Date: Fri, 11 Feb 2005 12:57:02 -0800
Lines: 113
Message-ID:
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.office.setup
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.office.setup:10482
X-Tomcat-NG: microsoft.public.office.setup
Your understanding is not correct. After the upgrade, .jpg .gif
.bmp
file
associations gone. Since Photo Editor from Office XP is being
upgraded
to
Picture Manager from Office 2003, these associations should
automatically
be
re-associated to Picture Manager. I am deploying to over 600 users
and
do
not want to manually create the associations for every user.
How do you configure the upgrade install to correctly and
automatically
move
the file association of .jpg, .gif and .bmp from Photo Editor to
Microsoft
Office Picture Manager.
"Dana Brash [MSFT]" wrote:
Hello,
Thank you for posting.
From your post, my understanding of this issue is: After
upgrading
Office
XP to Office 2003, image file associations are no longer
configured
as
you
like. You would like image files other than .jpg to be
associated
with
MS
Office Picture Manager, and to have .jpg files associated with
Photoshop.
If this is not correct, please feel free to let me know.
In order to assiociate image files with MS Office Picture
Manager,
you
can
change these settings in the Picture Manager (by default Start
Programs
Microsoft Office Microsoft Office Tools Microsoft Office
Picture
Manager). When the Picture Manager is opened for the first time,
you
should be prompted with a file association dialog box where you
can
adjust
these settings. If you are not, you can open this dialog from
the
tools
menu (tools File Types). In this dialog, you can associate
image
files
with the picture manager.
To ensure that .jpg files are opened with Adobe Photoshop, you
can
shift
+
right click a file in Windows Explorer, select 'Open with' and
'Choose
Program'. In the Open With dialog box, select Photoshop and tick
the
'Always use the selected program to open this kind of file'
option.
Please let me know if you have any other concerns, or need
anything
else.
Hope this helps!
Sincerely,
Dana Brash
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your
newsreader
so
that others may learn and benefit from your issue.
================================================== ===
Business-Critical Phone Support (BCPS) provides you with
technical
phone
support at no charge during critical LAN outages or "business
down"
situations. This benefit is available 24 hours a day, 7 days a
week
to
all
Microsoft technology partners in the United States and Canada.
This and other support options are available he
BCPS:
https://partner.microsoft.com/US/tec...rview/40010469
Others:
https://partner.microsoft.com/US/tec...pportoverview/
If you are outside the United States, please visit our
International
Support page:
http://support.microsoft.com/default...rnational.aspx.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers
no
rights.
--------------------
Thread-Topic: .jpg .gif .bmp file associations gone, upgrade
from
Office
XP to 2
thread-index: AcUOJ7mGATKdjHMsT22tutGMpYUIsw==
X-WBNR-Posting-Host: 64.1.44.68
From: "=?Utf-8?B?ZmJhcnRyb20=?="
Subject: .jpg .gif .bmp file associations gone, upgrade from
Office
XP
to 2
Date: Tue, 8 Feb 2005 13:47:02 -0800
Lines: 12
Message-ID:
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.office.setup
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFT NGXA03.phx.gbl
Xref: cpmsftngxa10.phx.gbl microsoft.public.office.setup:95265
X-Tomcat-NG: microsoft.public.office.setup
I am upgrading from Office XP to Office 2003. After the
upgrade,
many
users
no longer have file associations for .jpg, .gif and .bmp.
Apparently
"Photo
Editor" has been deleted and replaced by "Microsoft Office
Picture
Manager".
The problem is that Picture Manager is not taking over the file
associations.
I know I could add the registry keys to the transform that would
create
the
association. The problem with this is that Photoshop users want
.jpg
files
to open in Photoshop.
I am looking for a solution where these file types will be
associated
with
Picture Manager if they were previously associated with Photo
Editor
but
not
if they were associated with another application.