Does this also apply to normal users not being able to save to disk the file that they are viewing?
In my lab environment, normal users cannot save acrobat documents that they are viewing. They can click on a link and view the document but can't save it?!? I, on the other hand, as administrator, can save the documents so Adobe must be doing something wrong.
I suppose another solution would be to save the document by right-clicking it while using a browser, but the web site (a WebCT implementation) uses convoluted javascript links...
That's my gripe with Acrobat... that and the fact that it loads a zillion plug-ins that I don't need!
1. The user who wishes to install Firefox to D:\Program Files\Firefox must first navigate to D:\Program Files and then press "Make New Folder", click on the created folder named "New Folder", rename this folder "Mozilla Firefox", and then select this Folder.
*Note*: this is unlike any other Windows installer.
If you installed your system to D:\ (which I often do), your program files also default to D:\Program Files, and Firefox would default to D:\Program Files\Mozilla Firefox, make the exercise you described unnecessary.
3. Other installers automatically create a named installation folder, and users expect Firefox to do the same thing.
What I'm hearing is that this isn't so much a Mozilla or Firefox bug but an assumption (right or wrong) of users because there is no consistency between all installers.
This may be true, but I would point out that installers today are much better than what we had years ago. Back when each program would install itself everywhere on your hard drive, edit a few of your ini files, and then autoexec.bat and config.sys for good measure.
Honestly, it shouldn't have even been a question and was just the result of poor research or caving to troll pressure. Grow up children.
I agree. There were many more important questions that weren't touched upon that could have been instead of this user error/bug.
If this really is a widespread problem then arguably Firefox or any application shouldn't be allowed to do the install or uninstall. Everything to do with package management should be handled Windows (as is the case with RPM).
Furthermore, to protect users from themselves (even those who think the are advanced) there are zero installation options.... i.e. you either install it or you don't, no choosing where you'd like to go today.
Then, if you have anyone to blame, blame Microsoft.
This is the stupidest decision I have ever heard. They are practicly driving everyone with 2000 and lower over to firefox. It's like giving a present to one child, naturaly the other will be pissed as shit and not like the parent. Microsoft is digging themselves a hole, not only in the browser world but also Operating System.
I'm also surprised that they won't make IE 7 available to 2000. Since XP and now Win2003 Server are minor upgrades to 2000 (5.1 and 5.2 respectively) one would assume it would not be too much more work to "port" it to Windows 2000.
One might also reasonably assume that since they will likely continue to issue critical fixes to IE 6 on Windows 2000, Microsoft could actually $ave money on security by having one current supported browser.
The question is will they take any steps to separate IE from the OS?
They would have gains in the security by doing so, but at the expense of possibly losing their strangle hold on what 95% of users use to browse the web. (I wonder which is more important to Microsoft?)
From a sys admin perspective tying the browser to the OS scares me. I'll patch it up completely (critical, important patches) but I'm always wary of IE updates because it a partial OS update too... what system files does IE want to poke around with? And what will break?
Lastly, why are they turning their backs on Windows 2000? Surely they can make IE 7 available to that OS too... if Win5.2 (Win2003 Server) and 5.1 (WinXP) can get it, surely Win5.0 (Win2000) should be able to.
I understand you experienced some problems because you didn't understand the install procedure but that's not the fault of Mozilla or Firefox.
The custom install option states it is for experienced users, if you managed to install to the root of the program folders you certainly are not such a user.
Your "misconception" #1 is misleading since Firefox will install to D:\Program Files\Mozilla Firefox by default if your system drive is the D drive (not only from a custom install to D: as you imply).
And for "misconception #3", well people who don't read deserve what they get.
Slashdot Mirror
In my lab environment, normal users cannot save acrobat documents that they are viewing. They can click on a link and view the document but can't save it?!? I, on the other hand, as administrator, can save the documents so Adobe must be doing something wrong.
I suppose another solution would be to save the document by right-clicking it while using a browser, but the web site (a WebCT implementation) uses convoluted javascript links...
That's my gripe with Acrobat... that and the fact that it loads a zillion plug-ins that I don't need!
If you installed your system to D:\ (which I often do), your program files also default to D:\Program Files, and Firefox would default to D:\Program Files\Mozilla Firefox, make the exercise you described unnecessary.
3. Other installers automatically create a named installation folder, and users expect Firefox to do the same thing.
What I'm hearing is that this isn't so much a Mozilla or Firefox bug but an assumption (right or wrong) of users because there is no consistency between all installers.
This may be true, but I would point out that installers today are much better than what we had years ago. Back when each program would install itself everywhere on your hard drive, edit a few of your ini files, and then autoexec.bat and config.sys for good measure.
-sp-
I agree. There were many more important questions that weren't touched upon that could have been instead of this user error/bug.
If this really is a widespread problem then arguably Firefox or any application shouldn't be allowed to do the install or uninstall. Everything to do with package management should be handled Windows (as is the case with RPM).
Furthermore, to protect users from themselves (even those who think the are advanced) there are zero installation options.... i.e. you either install it or you don't, no choosing where you'd like to go today.
Then, if you have anyone to blame, blame Microsoft.
I, for one, wonder what in the world I did with a computer before the internet (or at least before I started using it... ~1995).
-sp-
I'm also surprised that they won't make IE 7 available to 2000. Since XP and now Win2003 Server are minor upgrades to 2000 (5.1 and 5.2 respectively) one would assume it would not be too much more work to "port" it to Windows 2000.
One might also reasonably assume that since they will likely continue to issue critical fixes to IE 6 on Windows 2000, Microsoft could actually $ave money on security by having one current supported browser.
-sp-
They would have gains in the security by doing so, but at the expense of possibly losing their strangle hold on what 95% of users use to browse the web. (I wonder which is more important to Microsoft?)
From a sys admin perspective tying the browser to the OS scares me. I'll patch it up completely (critical, important patches) but I'm always wary of IE updates because it a partial OS update too... what system files does IE want to poke around with? And what will break?
Lastly, why are they turning their backs on Windows 2000? Surely they can make IE 7 available to that OS too... if Win5.2 (Win2003 Server) and 5.1 (WinXP) can get it, surely Win5.0 (Win2000) should be able to.
-sp-
Sorry, this is not a bug.
I understand you experienced some problems because you didn't understand the install procedure but that's not the fault of Mozilla or Firefox.
The custom install option states it is for experienced users, if you managed to install to the root of the program folders you certainly are not such a user.
Your "misconception" #1 is misleading since Firefox will install to D:\Program Files\Mozilla Firefox by default if your system drive is the D drive (not only from a custom install to D: as you imply).
And for "misconception #3", well people who don't read deserve what they get.
-sp-