Resolved Shrink to fit default!

Through hours of scouring posts and finding minimal fixes from MS, I
discovered the Outlook printing "hotfix" adds a reg key:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet
Explorer\Main\FeatureControl\FEATURE_STF_Scale_Min]
"pst.exe"=dword:00000064
changing the print default to 100%
Since our business uses some apps that use the IE7 browser to print from,
add: iexplore.exe"=dword:00000064 as another value defaults printing to 100%
in this app. Recently another program printing option (for ID cards) was
defaulting to shrink to fit even though it appeared it was using the browser.
After conversation with the vendor found that it was using a Crystal wrapper
(exe) through the browser as the print call. So it too was fixed (set back to
100% as default) once entering it into that reg key. <sigh> SO if this theory
is correct most applications that use in part the browser and call some form
of proprietary executable might just respond to this "fix"

I hope this helps others :)

PA
Wed May 07 16:02:24 PDT 2008

Previous discussions in this newsgroup about Shrink To Fit and Outlook or
Outlook Express:
http://groups.google.com/group/microsoft.public.internetexplorer.general/search?hl=en&group=microsoft.public.internetexplorer.general&q=%22shrink+to+fit%22+%2B+outlook
--
~Robear Dyer (PA Bear)
MS MVP-IE, Mail, Security, Windows Desktop Experience - since 2002
AumHa VSOP & Admin http://aumha.net
DTS-L http://dts-l.net/

Vixen wrote:
> Through hours of scouring posts and finding minimal fixes from MS, I
> discovered the Outlook printing "hotfix" adds a reg key:
> [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet
> Explorer\Main\FeatureControl\FEATURE_STF_Scale_Min]
> "pst.exe"=dword:00000064
> changing the print default to 100%
> Since our business uses some apps that use the IE7 browser to print from,
> add: iexplore.exe"=dword:00000064 as another value defaults printing to
> 100% in this app. Recently another program printing option (for ID cards)
> was defaulting to shrink to fit even though it appeared it was using the
> browser. After conversation with the vendor found that it was using a
> Crystal wrapper (exe) through the browser as the print call. So it too was
> fixed (set back to 100% as default) once entering it into that reg key.
> <sigh> SO if this theory is correct most applications that use in part the
> browser and call some form of proprietary executable might just respond to
> this "fix"
>
> I hope this helps others :)