View Single Post
  #9  
Old August 15th 07, 01:05 AM posted to microsoft.public.windowsme.setup
Mike M
External Usenet User
 
Posts: 2,047
Default Visual Basic Scripting Support

D$$n spellchucker - or rather typist!

"whereby theY force users to upgrade to 5.7 and just tough luck for those
with operating systems noT supported by the new version."

As for Microsoft losing sight of their original customers I suspect that
it is more and more caring not one jot about anyone other than their major
accounts. In my view Microsoft long ago gave up on their home and soho
users preferring that these users solely deal with the big OEMs. Not that
the OEMs care either once they've shifted their box. I'm not sure I'll be
around long enough to see it but feel that Microsoft is already on a
downward slope which is getting steeper and steeper. The last thing I
want to see is Web 2.0 and the likes of Google take over and I for one
want to retain the applications I use on my systems rather than do
everything via a browser which probably means that some form of 'nix is
perhaps going to be the only way forward - either that or get a Mac vbg.

BTW I reported the broken download link in KB303107. Others are also
complaining about the withdrawal of Windows Scripting 5.6 and asking why
they are being forced to install v5.7 if 5.6 gets broken for any reason.
--
Mike


Mart wrote:

Mike wrote :-

This appears to me to be yet another
short-sighted action by Microsoft ....


and sadly, perhaps they are losing sight of their original customers
too, judging by the take-up of (retail) Vista. Not particularly
brilliant, according to press reports. My PC magazines seem to be
sniffing around Linux and other OS's as a credible alternatives more
recently.