Sign in to follow this  
  • entries
    10
  • comments
    16
  • views
    10555

All Hail Microsoft!

Sign in to follow this  

429 views

... Yeah ... Right ...

As some may know, Microsoft have two sets of users for their money making. Customers, and Companies/Developers. They make a massive amount of money from customers over businesses. When Microsoft developed Vista, they decided to make the OS secure and user friendly. At the same time, since developers and customers are polar opposites, Microsoft royally screwed over the developers ... The following is case and point.

Blizzard's official response to installing and using WOW on Vista is that you must do one of two things.

1. Install WOW outside of the Program Files directory. Most customers are hesitant to that change as it is different from previous windows versions. Thus you lose some customers there.

2. Install as normal, but follow this 18 step instructions to allow ALL USER ACCOUNTS on the computer FULL AND COMPLETE access to the WOW folder and sub folders. This is a major security breach. And, on most Vista installations, after setting the security, vista still will not a let you do updates there!

Now, why do Vista users have special instructions while XP users do not? One word ... Microsoft!

All modern software uses an internet patching process to update their software "on the fly". This allows companies to update their software quickly, in case there is a bug or if a criminal found a weakness ... This is STANDARD practice, it's a no brainer.

Microsoft decided to go against the world, and prevent this from happening by locking down the OS. Why? Customers generate more money for the company then developers.

I recieved a new computer that came with Vista Home Premium AKA Sub Windows XP Pro. Developing on it is a nightmare. I'm wiping the computer clean, and installing XP Professional on the bugger, it's faster, safer, and more user AND developer friendly.

What about DX10 games? I only know of one that I was slightly interested in, Halo 3. But after awhile, I realized that the Halo series is the literal rock bottom of the FPS genre. People still laugh when they hear that name .. Poor Bungie.

So all and all? Mirage will support Windows XP. If you have Vista, I will provide some simple instructions on installation, but you have to be on your own. Vista is still in Alpha Testing, and is not meant for public consumption.


Which reminds me. I need to change the "forums" link on the site to "Community', and point it to http://www.miragecore.com. Spoon will be in charge of that site and forums. This will leave me to do the programming, while he takes care of the community.
Sign in to follow this  


4 Comments


Recommended Comments

I own plenty of videogames that install into Program Files, have auto-update software, and have absolutely no problems running on Vista - and no, I didn't follow any special instructions or apply any special updates to run this way, and the majority of the games I'm thinking of are pre-Vista games.

Allowing programs to write to Program Files was already not recommended on previous versions of Windows, they've just decided to enforce it now. They've also set up the system so that the majority of programs which try to do this will transparently have their input and output directed elsewhere in the filesystem.

Don't blame Microsoft for the fact that Blizzard apparently did a shitty job with their WOW updater.

Quote:
People still laugh when they hear that name .. Poor Bungie.
Yes, poor Bungie, with their incredibly popular game that reportedly made $170m in it's first 24 hours of sales. I'm personally of the opinion that there's nothing particularly special about the game itself, but it is very well polished, pretty fun to play and has a massive fan-base.

Quote:
Mirage will support Windows XP. If you have Vista, I will provide some simple instructions on installation, but you have to be on your own.
Why don't you just develop your software properly (I observe once again that it was already recommended with XP that software not write to Program Files without good reason and that installers/updaters can do so perfectly fine (albeit with a UAC prompt) if properly written) and not potentially exclude users of what will eventually be the dominant desktop OS? In your previous entry you mentioned planning for the future, and this seems to go well and truly against that - unless you're planning to have your game developed and released extremely quickly you're going to be targetting a diminishing market share.

Quote:
Original post by Reddox
Microsoft royally screwed over the developers ... The following is case and point.
A few counters:

Share this comment


Link to comment
You are seriously short-sighted in your rant here.

First of all, Microsoft actually makes more money from businesses than it does from consumers. You don't wanna know how many consumer OS installations are pirated, and the gross of the license income that Microsoft generates are produced by servers, server licenses and business license for the desktop OSes. Sure, us developers are clearly outnumbered by consumers, but Visual Studio Professional is about 3 times more expensive that Vista, and then we're ignoring the fact that a lot of business software uses SQL Server on the background too.

Next, Microsoft clearly did a good thing by isolating the Program Files folder. You can still access the files there, except you need to provide a manifest to your auto-updater stating it needs Administrator privileges, because it wants to write to the Program Files folder.

Why it's protected? To stop malicious programs from writing themselfs to that location, deleting files from other programs or to have other programs write their clutter into the program files folder.

As said, learn to write your software properly. I'm a professional developer, and we managed to migrate over to Vista without too much trouble, including porting parts of our OpenGL over(Which gave us problems in the first place).

So please, instead of blaming it on Microsoft(or Apple for that matter, but that's irrelevant in this situation), blame it on yourself.

Share this comment


Link to comment
Well, thanks for the comments, but experience is what drove me to write the post.

1. The manifest is a gimmick, sometimes it works sometimes it doesn't.

2. Yep, people are really laughing is such a horrible game. :) I mean, you can
even compare it to quake 1, and Halo is nowhere polish, let alone the horrible slowness that game runs at (and it's not the fps).

3. Yeah, ever been a government programmer? Especially a Mainframe one? Products are test, and test, and tested continuously to make sure there are no bugs. Especially when it can cost the government hundreds of thousands of dollars, if not more. So to counter your statement, it is being developed properly.

4. This rant as well as ones in my other posts are based on professional experience. As posted, there are clear reasons why Microsoft did a major screwup with Vista. The blame is placed where it belongs.

I understand people have different opinions and experience. My rants are based on my as well as others experience. And it's one of the reason why my day job is going to skip Vista all together. It is not out of testing phase, and is clearly not ready for the public.

If Microsoft was to create a reliable OS that can be developed on (Like XP) with Vista, then there wouldn't be so many problems. But as it is ... Google is your friend :)

However, with the above being said, and your comments, etc. I will give it another shot at home. Maybe I can find some sort of stability in Vista from a developer's point of view.

Work is still another story ;)

~~ Thanks for the posts ~~

Share this comment


Link to comment
Quote:
Original post by Reddox
1. The manifest is a gimmick, sometimes it works sometimes it doesn't.
Works perectly when written correctly, I've never encountered a correctly authored manafiest that has mot worked as intended, and I challenge you to offer any reasonable explanation (given that the manifest is software parsed) why a correctly written manifest should ever be interpretted incorrectly.

Quote:
2. Yep, people are really laughing is such a horrible game. :) I mean, you can even compare it to quake 1, and Halo is nowhere polish, let alone the horrible slowness that game runs at (and it's not the fps).
Not any significant number of people, it's a ridiculously popular game; if you think otherwise you're incredibly out of touch with actual gamers. For the record it runs perfectly smoothly on every computer I've tried to run it on, and apart apart from one friend (who was running Halo 2 on a system which did not by a long shot meet the minimum recommended system requirements) it runs perfectly fine on the majority of systems I've tried to run the game on.

Quote:
3. Yeah, ever been a government programmer? Especially a Mainframe one? Products are test, and test, and tested continuously to make sure there are no bugs. Especially when it can cost the government hundreds of thousands of dollars, if not more. So to counter your statement, it is being developed properly.
Actually, yes, what's your point? The software I've developed while working for the government works for Vista just as well as for that which doesn't, and you shouldn't be taking any position you have or have previously held as an excuse for writing bad software. Microsoft have been providing documentation on how to correctly write your software for years and are continuing to do so, and it's entirely not their fault if you choose to ignore that.

Share this comment


Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now