quote:
Originally posted by ShawnZ
in fact, i'll start, because i caught this skimming through the thread:
- vista doesn't have 16-bit support
you're a newb, and here's why: it does. 64-bit doesn't, but no 64-bit version of windows has ever had 16-bit support. and on that note, the 16-bit compatibility in 32-bit vista is just as good as it always has been in every windows version, because it hasn't been changed since XP.
I dont like quoting myself:
quote:
And again you should give me the impression that you dont know about Vista by saying that Vista runs 16-bit programs when it does not; It has very limited compatibility for 16 bit programs and is not supported at all on 64 bit processors running 64 bit Windows Vista
I said the exact same thing you just said....WHats your point?
quote:
one of the strangest things I've heared lately....
If there are better solutions, then go working at Microsoft. I bet they will pay millions if you have a better solution for all their ActiveXs which they STILL use to this day (for example: MSIE and many many MANY other NATIVE programs).
Yes but dont you see a trend? Less and less everyday ActiveX DLLS or VB6 or whatever your oldschool ways are, are used. .NET for example is being pushed as the "next great thing" and developers should enbrace it (sorry for sounding like Steve).
quote:
FYI, there are still a lot of problems with drivers, that is actually one of the main reasons why SP1 is not yet released to everybody! (which will soon change, but anyways).
FYI, SP1 has not been released to everyone because a bug in a previous build (this is where you are clearly mistaken) was present. The bug was that when SP1 was installed several drivers needed uninstallation and installation again before they properlly worked in Vista. This, AFAIK, has been fixed.
quote:
One of the reason IS that Vista doesn't accept them. Some APIs are not in Vista anymore. And how do you know Vista is "more effecient" in handling its API functions? You have the source of both XP and Vista and you can interpret it?
Those APIs that have been removed arent because Microsoft decided to fuck some developers; They were removed because other functions possibly replaced them with a more effecient and better way of handling and interpreting data.
quote:
Some things ARE NOT possible anymore in Vista. It would be nice if you also accept that fact.
If something IS possible in Vista also, I'm sure the developers (or somebody else) will update their stuff, if it needs to be updated in the first place. But some things are simply NOT possible.
I think you are mistaken. Ill give you a example:
Previous versions of Windows: a + a + b + b = c
Vista: (a * 2) + (b * 2) = c
So you are correct that certain things cant be done in Vista BUT they can be done a different way and more effecient.
quote:
Talking about twisting words, djeez.... Who of us said he should shutout Vista users?
What part of me said that he should shutout XP users?
quote:
He might know a thing or two about how Microsoft's OS functions?
Why? Because he is a MSDN subscriber and he has a Vista beta? That makes no sense
quote:
If you read up on some MSDN articles you would, for example, also know about the driver problems in Vista.
Wouldnt a driver problem be in the KB?
quote:
You love Vista, fine.
I dont love Vista nor am I a fanboy. I just hate it when people say that XP is better. Thats a stupid statement. I have had a way better experience with Vista than XP.
quote:
You haven't got any problems with Vista, even more fine and congrats... But some people do, and some people aren't even able to get Vista. And some things can only be done on XP... Those are also facts...
But Im willing to bet that 99% of those problems are not Microsoft's fault. If it was MS's fault, then wouldnt we all have those similar bugs on are system? Like I said, my ride has been smooth sailing.
quote:
I hate that too.
Its official. The world is coming to a end. Me and cookie agree on something.
/ 
