Yay operator error.
Originally posted by: bsobel
The Advance edit dialog that existed in Windows XP has been removed: http://pixma.damnmachine.com/wp-content/uploads/2007/04/advanced_tn.jpg
Ok, I honestly didn't know that dialog was there in XP. But I just brought it up in both XP and the Vista associations dialog. Looks like you can't easily edit the icon for an application or add additional verbs.
Where you really using the functionality, and if so, for what. It does seem the default behaviour of browsing for and selecting an application covers the needs of 99.9% of the user base.
Bill
Originally posted by: 13Gigatons
Originally posted by: bsobel
The Advance edit dialog that existed in Windows XP has been removed: http://pixma.damnmachine.com/wp-content/uploads/2007/04/advanced_tn.jpg
Ok, I honestly didn't know that dialog was there in XP. But I just brought it up in both XP and the Vista associations dialog. Looks like you can't easily edit the icon for an application or add additional verbs.
Where you really using the functionality, and if so, for what. It does seem the default behaviour of browsing for and selecting an application covers the needs of 99.9% of the user base.
Bill
It's used a lot for repairing systems that have had their associations screwed up either from crashes or viruses. For instance when the .exe, .bat, etc where improperly associated with Media Center instead of 'application', you could not launch anything. Under XP this could be fixed easily.
I would say it's used 1000 times per year to fix a system that's been screwed up.
It's used a lot for repairing systems that have had their associations screwed up either from crashes or viruses. For instance when the .exe, .bat, etc where improperly associated with Media Center instead of 'application', you could not launch anything. Under XP this could be fixed easily.
Originally posted by: Smilin
Wow, ok. I've been working on computers for decades and I've never once seen associations alone get screwed up by crashes. If a nasty crash clobbers a registry there is no way that damage is going to be confined soley to file associations and no where else. I've fixed more registry's than I can count and this just doesn't happen. If I found a goofed up file association due to some crash I would view it as merely the tip of the iceberg and start looking for a replacement hive.
Any deliberate malicious alterations to say the CMD association are also fixed by hand and not through an advanced file associations dialog. In many cases an AV vendor simply provides a cleanup tool. If it's something more involved like say root kit removal you flatten the system.
This is your latest argument regarding the file associations dialog? Keep it around for that reason? "Used 1000 times per year" is an utter crock. Back that fact up. This whole argument regarding the file associations has gotten ludicrous. Logical rational thinking and *facts* brought us around to the point where "user error" was the culprit and now this nuttiness has appeared out of nowhere to provide some escape route.
You've yet to even admit that Firefox associations can be altered. How far are you willing to take this just to avoid admiting that you were wrong?
Thanks for the feedback everyone. There are a lot of good points here.
The decision to remove the advanced file associations tab was a difficult one. There were a number of problems facing it that made it a candidate for removal.
1. It had a number a cross hive issues that worked over HKCU and HKLM which caused a lot of problems with the new UAC framework.
2. It is very low traffic UI
3. Most of the functionality is available other places
4. There were many instances of users getting themselves into trouble using the advanced UI because it was just a glorified registry editor. In most cases if you mess something up in the advanced UI there is no recovery path.
The most common usage we found for this UI was IT admins trying to go in and fix file associations from some piece of malware. In vista, both UAC and Windows defender help solve this problem. <--- LOL :roll:
[
In addition the UI is not well suited for that task. Ultimately we want to ship something that provides a better experience for tweaking the underlying pieces of file associations while helping the user not hose the registry.
We are still working on what the best release mechanism will be for this functionality.
I absolutely understand the problem with unistalling Firefox, but this has also been a long standing problem that has existed in previous versions of the OS. This issue is fixed if you run IE or another browser. The other browser should detect some of the keys it cares about aren't there give you the option to set it as the default. This will fix the problems of FF removing keys.
Ultimately, we want a framework where there is a easy way to delegate file\protocol assocaitons at unistall so there is a gracefull hand off. The new default programs hand off is a part of that foundation but we still have a ways to go.
cheers,
Ed
The most common usage we found for this UI was IT admins trying to go in and fix file associations from some piece of malware. In vista, both UAC and Windows defender help solve this problem. <--- LOL :roll:
In addition the UI is not well suited for that task. Ultimately we want to ship something that provides a better experience for tweaking the underlying pieces of file associations while helping the user not hose the registry.
Originally posted by: 13Gigatons
Under Windows XP it's used 1000 times a year and I'm sticking by that. You may not tweak your system as much but others do. Sometimes to fix problems and sometimes to add and edit things.
Agian Firefox associations COULD NOT BE FIXED using any of the Windows Vista dialog boxes that are provided. It didn't work, I'll repeat that agian, IT DID NOT WORK. I used a third party app to resolve the BUG. I suppose you will tell me that Vista is perfect and has no bugs?
Originally posted by: loup garou
Looks fine to me.
Reinstall Firefox, something is obviously fvcked up.
I'll translate for you: Nobody used it. That's what juktar, bsobel, and I have pretty much been saying.From Microsoft:
2. It is very low traffic UI
...again as everyone has said.. This includes the functionality you say you are after.3. Most of the functionality is available other places
...As I told you earlier. Wanna be power users like that "advanced" title on the dialog they are working in. Real power users would use regedit. Just because you know where the dipstick is once you raise the hood doesn't mean you belong there. Typical users? See #34. There were many instances of users getting themselves into trouble using the advanced UI because it was just a glorified registry editor. In most cases if you mess something up in the advanced UI there is no recovery path.
The most common usage we found for this UI was IT admins trying to go in and fix file associations from some piece of malware. In vista, both UAC and Windows defender help solve this problem. In addition the UI is not well suited for that task. Ultimately we want to ship something that provides a better experience for tweaking the underlying pieces of file associations while helping the user not hose the registry.
We are still working on what the best release mechanism will be for this functionality.
I absolutely understand the problem with unistalling Firefox, but this has also been a long standing problem that has existed in previous versions of the OS. This issue is fixed if you run IE or another browser. The other browser should detect some of the keys it cares about aren't there give you the option to set it as the default. This will fix the problems of FF removing keys.
Ultimately, we want a framework where there is a easy way to delegate file\protocol assocaitons at unistall so there is a gracefull hand off. The new default programs hand off is a part of that foundation but we still have a ways to go.
Originally posted by: bsobel
The most common usage we found for this UI was IT admins trying to go in and fix file associations from some piece of malware. In vista, both UAC and Windows defender help solve this problem. <--- LOL :roll:
Have you offered any evidence to the contrary?
A lot of users will just turn off UAC because they will find it annoying and it's only effective in some cases when it's on anyways. Windows Defender well it seems to have a rather poor detection rate: http://www.pcworld.com/article/id,128660/article.html
In addition the UI is not well suited for that task. Ultimately we want to ship something that provides a better experience for tweaking the underlying pieces of file associations while helping the user not hose the registry.
That just reiterates what we've been saying and refutes what you posted.
No it doesn't, it just means that admin's that know what there doing can use the dialog box and won't make a mistake while average joe's could screw it up. It's also an excuse for why Vista didn't ship with a replacement dialog.
Originally posted by: Smilin
Originally posted by: 13Gigatons
Under Windows XP it's used 1000 times a year and I'm sticking by that. You may not tweak your system as much but others do. Sometimes to fix problems and sometimes to add and edit things.
Agian Firefox associations COULD NOT BE FIXED using any of the Windows Vista dialog boxes that are provided. It didn't work, I'll repeat that agian, IT DID NOT WORK. I used a third party app to resolve the BUG. I suppose you will tell me that Vista is perfect and has no bugs?
mebe since you keep using caps, repeated characters, underlines, boldface and all that it's what it takes to get through to you. I'll give it a shot.. :disgust:
IT CAN BE FIXED using the Windows Vista dialog boxes. HERE IS HOW YOU DO IT:
Originally posted by: loup garou
Looks fine to me.
Reinstall Firefox, something is obviously fvcked up.
Why do you still think that this is a Vista bug?
Your Firefox was not installed right. You've already been shown in this thread with screenshots that it works perfectly fine. Your Firefox install was broken. Reinstall. If still no worky, get Firefox support. The Vista dialog boxes are capable of doing exactly what you are trying to do. Ooops, sorry... The Vista dialog boxes are capable of doing exactly what you are trying to do. ..there.
I'll translate for you: Nobody used it. That's what juktar, bsobel, and I have pretty much been saying. That's his opinion and yours.From Microsoft:
2. It is very low traffic UI
...again as everyone has said.. This includes the functionality you say you are after.3. Most of the functionality is available other places
...As I told you earlier. Wanna be power users like that "advanced" title on the dialog they are working in. Real power users would use regedit. Just because you know where the dipstick is once you raise the hood doesn't mean you belong there. Typical users? See #34. There were many instances of users getting themselves into trouble using the advanced UI because it was just a glorified registry editor. In most cases if you mess something up in the advanced UI there is no recovery path.
The most common usage we found for this UI was IT admins trying to go in and fix file associations from some piece of malware. In vista, both UAC and Windows defender help solve this problem. In addition the UI is not well suited for that task. Ultimately we want to ship something that provides a better experience for tweaking the underlying pieces of file associations while helping the user not hose the registry.
Note he said "trying to go in and fix", "the UI is not well suited for that task" etc. Follow earlier advice given to you instead:
"Any deliberate malicious alterations to say the CMD association are also fixed by hand and not through an advanced file associations dialog. In many cases an AV vendor simply provides a cleanup tool. If it's something more involved like say root kit removal you flatten the system. "
I think he's basically saying that folks like you keep trying to be Uber and fix this with an "Advanced" dialog then end up jacking your system up.
If you bust something in that dialog do you even know how to restore your registry? You're not even sure what keys it's changing so how could you? These aren't in control sets so lastknowngood won't save you. Know how to restore the whole thing?
We are still working on what the best release mechanism will be for this functionality.
I absolutely understand the problem with unistalling Firefox, but this has also been a long standing problem that has existed in previous versions of the OS. This issue is fixed if you run IE or another browser. The other browser should detect some of the keys it cares about aren't there give you the option to set it as the default. This will fix the problems of FF removing keys.
Ultimately, we want a framework where there is a easy way to delegate file\protocol assocaitons at unistall so there is a gracefull hand off. The new default programs hand off is a part of that foundation but we still have a ways to go.
What? What did he say? "This will fix the problems of FF removing keys?" You mean FireFox's uninstaller jacks things up and doesn't put them back the way they were? The problem "existed in previous versions of the OS?" Nice. Clearly a Vista bug :roll:
How many times have you been told in this thread alone that Windows Vista allows you to do the things you are trying to do? It allows you to make the changes with Firefox that you desire. You've been shown actual screenshots of it working!
It just so happens that Firefox's installer screwed up and didn't make the proper changes. Reinstall Firefox or contact their tech support. The fact that you used your 3rd party app to fix things is not an indication of a problem with Vista. Know what else would have fixed it? Reinstalling Firefox or calling their tech support. Know what would not have fixed it? Calling MS tech support. They would have told you to (wait for it..) Reinstall Firefox or call their tech support.
Everyone else is able to get this to work on Vista. Apparently it works on Vista.
You're just mad because, for all the world to see, you blogged about how Vista is broken when it turns out you just didn't know what you were doing.
No Vista problem here.Originally posted by: 13Gigatons
I'll give it to you in steps since you STILL are missing the point:
1. Firefox not acting as default browser even though it should be.
No Vista problem here.2. Re-installing Firefox several times does NOT fix the problem and it does NOT appear like this: http://pics.bbzzdd.com/users/werk/defaults.JPG ....cannot manually force it to appear.
Sounding like a broken record but the proof is there...3. Vista dialog boxes are unable to set Firefox as default, protocols http, https and ftp are listed but cannot be changed.
No Vista problem here.Originally posted by: loup garou
Looks fine to me.
You can do everything you are trying to do...4. Notice advance edit dialog is MISSING.
No Vista problem here.Originally posted by: loup garou
Looks fine to me.
Glad your 3rd party app fixed your Firefox problem.5. Install third party app and quickly fix the problem. [/b]
You mean "few if any" of you right? ...The point still remains that the advance edit dialog box was very useful for some of us. Sometimes you don't want to crawl through the registry and that little dialog was a easy and quick way to add, edit and fix things. It always worked in Windows XP and the third party app works great in Vista.
You also mean it was something that does nothing beyond regedit but provides a way for wannabe power users to get themselves into trouble...From Microsoft:
2. It is very low traffic UI
...it also provides nothing that would have helped in this situation if your Firefox installer worked correctly.From Microsoft:
4. There were many instances of users getting themselves into trouble using the advanced UI because it was just a glorified registry editor.
I am not the slightest bit interested in whatever you are babbling about now.I also think Vista can be improve in dozens of ways, like why in details mode full row select cannot be disabled ?
Nobody here has said Vista is perfect. Please provide a quote on that. Vista is capable of doing what you asked (it has been proven to you). You just seem hell bent on blaming Vista for what is obviously a Firefox installer issue. Your inability to admit your mistake seems to indicate that you think of yourself as perfect. So sad 🙁Many here think vista is perfect and always works perfect and if it fails then it's simply a reflection on the user. I'm sorry but that just makes me laugh. 🙂
Originally posted by: 13Gigatons
I'll give it to you in steps since you STILL are missing the point:
1. Firefox not acting as default browser even though it should be.
2. Re-installing Firefox several times does NOT fix the problem and it does NOT appear like this: http://pics.bbzzdd.com/users/werk/defaults.JPG ....cannot manually force it to appear.
3. Vista dialog boxes are unable to set Firefox as default, protocols http, https and ftp are listed but cannot be changed.
4. Notice advance edit dialog is MISSING.
5. Install third party app and quickly fix the problem.
The point still remains that the advance edit dialog box was very useful for some of us. Sometimes you don't want to crawl through the registry and that little dialog was a easy and quick way to add, edit and fix things. It always worked in Windows XP and the third party app works great in Vista.
I also think Vista can be improve in dozens of ways, like why in details mode full row select cannot be disabled ?
Many here think vista is perfect and always works perfect and if it fails then it's simply a reflection on the user. I'm sorry but that just makes me laugh. 🙂
Originally posted by: bsobel
Smilin, I think this thread is done and ready to be locked. He simply wants to argue and I dont think any amount of rational (or irrational 🙂) discussion is going to change that.
Originally posted by: 13Gigatons
I received a email saying Smilin works for MICROSOFT so I'm not going to argue with him anymore since he's being paid to troll for his company.
Originally posted by: 13Gigatons
I received a email saying Smilin works for MICROSOFT so I'm not going to argue with him anymore since he's being paid to troll for his company.
Please vacate your own thread.Originally posted by: 13Gigatons
I received a email saying Smilin works for MICROSOFT so I'm not going to argue with him anymore since he's being paid to troll for his company.
Meh, don't overestimate my inside knowledge. I'm not on that team (nor is your TAM). Thinking there would be no service pack over the entire life of the product is pretty silly. I'm kinda surprised there's an argument about it. I've no idea what the plans or release dates are though. I can't give you Dave's number either so don't ask.
No, your poll still sucks.
It has no option for "running now just fine"
It also has no real option for "never" which if you knew crap about software and operating systems would be the real answer. Do you have any clue whatsoever how many bugs are sitting in Windows, Mac OS, OSX, Linux, Unix, OS/400 etc etc???
These have so many moving parts that there will always...repeat...always..be something wrong with them. There are bugs in Windows 3.1 that were never corrected. It would be utterly impractical to get a perfect OS **and** have innovation. If you can't wrap your head around this then you don't know a lot about computers.
You are a troll and a little speck of poop. Stop making these retarded threads so people with real discussion and troubleshooting questions can get some use out of the forums
*sigh*
Not a Vista bug.
If you try to run it with hardware and drivers that aren't fully supported on Vista then you'll have problems.
Same thing with XP MCE.
/shrug
You're taking your XP MCE hardware and loading Vista on it. Might work, might not. If it does, cool. Build a Vista box from the ground up and things are fine. Buy an OEM that's all preloaded with fully supported Vista hardware and things are fine. This is the same song and dance we had with XP, 2000 etc..
It's nice when the stuff you bought just before Vista released works but really it was still released before Vista with drivers that say XP so it's not guaranteed. With some luck your hardware vendors will provide some better drivers. They aren't oblidged to though.
I'm partially in the same boat too. I've got arguably the best non-DX10 card available right now. meh. I knew what I was getting into. I'll move to DX-10 at a later date.
Stop putting sugar in the gas tank and remember to change your oil.
I ran a single XP install for it's entire lifespan through several motherboards and other upgrades and never had the issues you're describing.
Note that sporadic failed boots are the sign of hardware problems, often power supply. Not the OS. The same set of instructions are running in the OS each time you boot. They do not simply behave one way one time and another some other time.
Yeah for it's time that was quite possibly one of the greatest OSs ever written. I hope history judges Vista the same.
Not understanding why DX10 doesn't run on XP shows a lack of knowledge. Ranting about it makes you look like a noob.
Me? Been running Vista RTM since November...getting close to 6 months now. No showstoppers here. Works great and makes XP feel really dated now that I'm used to it. It cracks me up when people tell me what my Vista experience is like.
This happens every update. People come out of the woodwork saying it caused their mom to get cancer. When people get down to root cause it always turns out to be something other than the update. You going to really tell me that mouse pointer code is causing utilities to vanish into thin air, USB problems??? Give me a break.
The #1 cause of this FUD: People apply MS or 3rd party updates then fail to reboot. A problem sits like a timebomb in the pendingfilerename regkey and then when they pull down an MS update that requires a reboot, BAM! The update gets blamed when really a reboot by itself would have cause the same problem. #2 cause: corruption on the filesystem sitting underneath files required for boot. Apply an update, BAM! The update gets blamed when really a reboot by itself would have caused the same problem.
How do I know this? I used to be on the team that took the failed update calls. We didn't guess (like the monkey's you are quoting), we found ROOT CAUSE. EVERY time. Simply telling a customer to remove a security update was NOT an option. Not fixing the case was NOT an option
Not single complaint or criticsim from Smilin...always the user or hardware is to blame. As someone who has used Microsoft software for many years, I can say with 100% confidence that it has bugs.
Originally posted by: bsobel
Not single complaint or criticsim from Smilin...always the user or hardware is to blame. As someone who has used Microsoft software for many years, I can say with 100% confidence that it has bugs.
What an extremely slimey post. Did you read what you quoted?
"It also has no real option for "never" which if you knew crap about software and operating systems would be the real answer. Do you have any clue whatsoever how many bugs are sitting in Windows, Mac OS, OSX, Linux, Unix, OS/400 etc etc???
These have so many moving parts that there will always...repeat...always..be something wrong with them. There are bugs in Windows 3.1 that were never corrected. It would be utterly impractical to get a perfect OS **and** have innovation. "
This statement is in direct conflict to your statement of "always the user or hardware is to blame. As someone who has used Microsoft software for many years, I can say with 100% confidence that it has bugs"
I strongly suggest you let this thread just die, you are not (in any way) helping yourself by your above post.
It shows how hostile he is to anybody criticizing Microsoft Software. It's always "you suck" you "speck of poop".
Originally posted by: bsobel
It shows how hostile he is to anybody criticizing Microsoft Software. It's always "you suck" you "speck of poop".
a) Changing the argument once again. You stated that he said it's never the OS's fault. However, in your quote (that I requoted) I even showed you were he said the OS DOES have bugs. Since your statement was factually incorrect, your now trying to claim a different reason for your quote.
b) You picked two threads out of thousands to make your point. Smilin is one of the best posters in this forum. All I've seen you do is change your story as your comments are proven false.
c) I ask you again what you hope to gain from prolonging this thread.
You still won't admit that a feature was removed that some users found useful. You dismiss this as that nobody needed the feature and that we should all just be happy with what Microsoft has provided because it's perfect.