Re: Use of .WSX file types...

From: Administrator (JUNK_it_at_nmb.gov_FREE)
Date: 07/15/04 

Date: Thu, 15 Jul 2004 04:01:03 -0700

Update (to confuse things further, or to clear them up?)...

Last night, using one of the affected computers, logging in as someone else (same PC and DOMAIN but different user) and the WorkSaver program worked. Meaning you click the link, the file auto-opens, requested file is returned to you.

Logging back in as the regular, normal user, and the links no longer work...

On the other two computers, it is across all three login types (local admin, domain admin, and domain users).

Can this be an ACTIVE DIRECTORY glitch (again)... I have utterly no idea! AD is so convoluted and repetitive that I can't make use of it. When I enable something it kills something else.

  Must be a better metaphor for editing AD schema... I have ideas on this!

Is there a way to reset AD to it's default state? Some little app, some checkbox, some button, maybe a special prayer to Uncle Bill (I've heard that a properly formatted prayer to him takes the form of a $250 CC charge)?

ARGH... 

-- 
IT Administrator (Old Fogie)
"zachd [ms]" wrote:
> 
> I don't know anything about 833828, and so wouldn't feel comfortable 
> speaking to it.
> 
> Really, though: what does the registry hive for .wsx's progid look like? 
> I'd look at the reg dump if you had it...
> 
> It sounds like the association was just reset- it should be easy enough to 
> reset that...
> 
> -Z
> -- 
> (speaking for myself and doing this in my free time)
> See http://www.zachd.com/pss/pss.html for some helpful WMP info.
> Following up to your post with the resolution is good netiquette.
> This posting is provided "AS IS" with no warranties, and confers no rights.
> All e-mail to this account will bounce or be deleted - *use the newsgroups*.
> --
> "Administrator" <JUNK_it@nmb.gov_FREE> wrote in message 
> news:2F0244EB-B47E-48BA-959F-B66829379072@microsoft.com...
> >
> > So, will uninstalling KB833828 really crash my whole system?
> >
> > It might be worth it to fix this problem, then use a generic media player 
> > after that.
> > One of the affected systems is the #2 person here and he's very upset over 
> > this, another is my computer.
> >
> > All three systems were recently reformatted for one reason or another...
> >
> > -- 
> > IT Administrator (Old Fogie)
> >
> >
> > "zachd [ms]" wrote:
> >
> >>
> >> What are .wsx files?
> >>
> >> So HKEY_CLASSES_ROOT\.wsx points to what?  What's under what it points 
> >> to?
> >>
> >> -Zach
> >> -- 
> >> (speaking for myself and doing this in my free time)
> >> See http://www.zachd.com/pss/pss.html for some helpful WMP info.
> >> Following up to your post with the resolution is good netiquette.
> >> This posting is provided "AS IS" with no warranties, and confers no 
> >> rights.
> >> All e-mail to this account will bounce or be deleted - *use the 
> >> newsgroups*.
> >> --
> >> "Administrator" <Administrator@discussions.microsoft.com> wrote in 
> >> message
> >> news:3BD95D78-8F49-408C-B2BA-79724C81FBBC@microsoft.com...
> >> > We already have an application that uses the .WSX file extension, used 
> >> > to
> >> > be that you clicked on the file and the app would run (like it does 
> >> > with a
> >> > .DOC, etc.).
> >> >
> >> > After the last Media Player v9 update/patch, when you click on a .WSX 
> >> > it
> >> > now asks you what you want to do with it.  Just like you had right 
> >> > clicked
> >> > on it and selected "Save Target As"...
> >> >
> >> > I've reviewed the registry and all .WSX entries point towards the 
> >> > correct
> >> > executable (and are set by the app install program), still it doesn't
> >> > work.
> >> >
> >> > What do I need to do to make this work again, and this isn't the only
> >> > computer suffering from it.  I've attempted to re-associate the file 
> >> > type
> >> > with the app but it didn't help.
> >> >
> >> > I'm at a loss!
> >> >
> >> > -- 
> >> > IT Administrator (Old Fogie)
> >>
> >>
> >> 
> 
> 
>