So it would seem like it would be easier for a badly behaving application
that makes the system choke and freeze up as it opens up 25-1000 files to
just set the registry hack as opposed to fixing their code to write a better
shell handler.
As such, it wouldn't seem to make any sense whatsoever to have a registry
override... which is probably why there isn't one. =\
If you don't like this behavior, request your application vendor to support
more modern shell file handlers. They're not too tough to write and they
make your system run better and be more responsive. Win-win. Duct-taping
together bad practices isn't the best plan. =\
If you want the right thing to happen, ask your application vendor to fix
their code.
If you want the wrong thing to happen, complain to official Microsoft
support.
Otherwise, there's no way that I'm aware of to force the shell to use the
old problematic method, sorry.
-Zach
--
Speaking for myself only.
See
http://zachd.com/pss/pss.html for some helpful WMP info.
This posting is provided "AS IS" with no warranties, and confers no rights.
--
"lforbes" <guest@xxxxxx-email.com> wrote in message
news:dc26cba16a6680bcd2b1a983f95f892d@xxxxxx-gateway.com...
Quote:
>
> 'zachd [MSFT Wrote: Quote:
>> ;610133']To others: the definitive differential in the file opening
>> experience is based upon the application's shell association type.
>> Legacy handlers are limited to 15 selections by default for performance
>> reasons. Applications using modern shell association methods will not
>> have this limitation.
>>
>> No, that's part of WYSIWII. What You Select Is What Is Invoked. The
>> Open
>> With menu item only supports one selection, so it would be incorrect to
>> make
>> it available.
>>
>> OK: I had previously respected your difference of opinion by pointing
>> out
>> that this behavior is by design for legacy style associations, and that
>> if
>> you disagree with the current implementation, your best resource would
>> be
>> actual Product Support where you could attempt to garner support for an
>> update of some sort. I think we've run the gamut from determining the
>> behavior, explaining the behavior, and a possible resolution to the
>> behavior, so I think we're likely done here.
>>
>> -Zach
>
> Zach, is there not a registry hack for this? I have been a network tech
> for 25 years so I would consider myself an expert in the Dos/Windows OS
> environment. I have managed every OS since Dos first came out.
>
> Vista is the first OS where I couldn't believe how much they "dumbed"
> it down. I have not deployed it in my network as it is just so
> ridiculously simplified that it will not be a good replacment for XP.
>
> I do a lot of website design and often have to open more than 25 100k
> jpeg thumbnails. The reason that MS took away this ability in Vista
> baffles me. What was the reason given? It cannot possibly be performance
> as I have been doing this on XP since Pentium I's with 128MB Ram. With
> XP it would just warn you and that was that.
>
> What on earth is considered a 'legacy app'? I am running Adobe
> Fireworks CS3 written for Vista and that won't open more than 15 jpgs
> with the context menu.
>
> Microsoft Office 2007 won't let me open a .doc and a .docx at the same
> time regardless of the fact they are both SET to default to Office 2007.
>
> Please tell me there is a registry change for this.
>
>
> --
> lforbes