Again, clean install, running 7 ultimate on 7 computers and not a single bluescreen on any computer since the beta was released. But despite that I am persisting with 7, I still think it is a major disappointment. One of my kids is begging me to let him go back to Vista (seriously) coz of compatability issues with steam games. And I spent many hours struggling with compatability issues myself, but it's about 90% working now.
I had to put Vista dual boot back on one box here for a roommate who didn't want to give up his 1701AD game. He only goes there to play the game. Something to consider. It doesn't affect your Win7 at all, just add a partition and install Vista. Keep a backup image and you never have to reinstall either again.Again, clean install, running 7 ultimate on 7 computers and not a single bluescreen on any computer since the beta was released. But despite that I am persisting with 7, I still think it is a major disappointment. One of my kids is begging me to let him go back to Vista (seriously
That's more the fault of the applications developers who have had plenty of time to get their stuff working with Win 7.
Even the software I'm working on now has Windows 7 support, including actual Windows 7 features such as Jump Lists. See...
Twitpic - Share photos on Twitter
So much of the incompatibility we see is simply caused by developers not following the rules when writing the applications.
Microsoft provide information on the methods for interfacing with the operating systems and where the OS expects certain files to be stored.
Certain developers ignore this and write things their own way - it works with the OS so no problem.
Until the next OS
When Microsoft develops a new Operating System and needs, for technical reasons, to change these entry points or locations, It includes code to handle the older locations. Of course the badly written software assumes everything is where it used to be and promptly crashes
A similar situation exists with the need for programs to run as admin - it is easier to write a program assuming that it will have access to everything. On XP, where most uses were admin and security wast basically not used on files and folders, this worked.
When vista arrived you end up with the need to run a something like a desktop publisher as admin - causing the UAC prompt to trigger. This was of course "all Microsoft and Vista's fault".
Unfortunately we also have some developers who treat a change of operating system as a chance to make money by choosing to not supply updates for their products but new chargeable products. This applies to both software and hardware (which explains a lot of driver problems)
So much of the incompatibility we see is simply caused by developers not following the rules when writing the applications.
Microsoft provide information on the methods for interfacing with the operating systems and where the OS expects certain files to be stored.
Certain developers ignore this and write things their own way - it works with the OS so no problem.
Until the next OS
When Microsoft develops a new Operating System and needs, for technical reasons, to change these entry points or locations, It includes code to handle the older locations. Of course the badly written software assumes everything is where it used to be and promptly crashes
A similar situation exists with the need for programs to run as admin - it is easier to write a program assuming that it will have access to everything. On XP, where most uses were admin and security wast basically not used on files and folders, this worked.
When vista arrived you end up with the need to run a something like a desktop publisher as admin - causing the UAC prompt to trigger. This was of course "all Microsoft and Vista's fault".
Unfortunately we also have some developers who treat a change of operating system as a chance to make money by choosing to not supply updates for their products but new chargeable products. This applies to both software and hardware (which explains a lot of driver problems
Well said and true statement about developers not updating so they can sell the new and improved version.
Iggy in the cool part of Arizona.....
Well said Barman58
I have a HP scanner, probably seven years old but like new. I use a scanner maybe once a month. HP will not support it with a driver, and i tried everyway i new to install it with no luck. They expect me to through the scanner away and buy new. We are in a through away society anymore. My little mini rant
Smitty
I don;t buy HP anything any more because if that. I had a ONE YEAR OLD Hp color printer when Vista came out and they refused to support that.
I /almost/ gave up on M-Audio fo rthe same reason, they even argued with me on their forum. But when I pointed out that MUTO and other manufacturers already had Vista drivers that worked during the beta they shut up. Now this time around they have been MUCH more proactive about drivers, supporting most everything they have, including years old stuff. (Though oddly not the ONE midi box I own and that has to be the easiest driver to maintain Grr....)
Start Menu option can be improvized more ! Also booting time . ( i know booting time depends on the system specs ) , however they should come up with some solution . .
I remember reading that many developers were being lazy and referring to HKLM registry calls instead of HKCU calls. Apparently that is one of the reasons that was causing many of the UAC prompts when the programs were run on Vista.So much of the incompatibility we see is simply caused by developers not following the rules when writing the applications.
Microsoft provide information on the methods for interfacing with the operating systems and where the OS expects certain files to be stored.
Certain developers ignore this and write things their own way - it works with the OS so no problem.
Until the next OS
When Microsoft develops a new Operating System and needs, for technical reasons, to change these entry points or locations, It includes code to handle the older locations. Of course the badly written software assumes everything is where it used to be and promptly crashes
A similar situation exists with the need for programs to run as admin - it is easier to write a program assuming that it will have access to everything. On XP, where most uses were admin and security wast basically not used on files and folders, this worked.
When vista arrived you end up with the need to run a something like a desktop publisher as admin - causing the UAC prompt to trigger. This was of course "all Microsoft and Vista's fault".
Unfortunately we also have some developers who treat a change of operating system as a chance to make money by choosing to not supply updates for their products but new chargeable products. This applies to both software and hardware (which explains a lot of driver problems
