Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.databases.paradox    |    To crash or not to crash, asks Borland    |    9,834 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 8,481 of 9,834    |
|    Rodney Wise to Delfo Perozziello    |
|    Re: Vista compatibility ??    |
|    26 Apr 07 11:24:06    |
      From: NSpamPlease_rodney1@bellsouth.net              "Delfo Perozziello" wrote:              > And can we tell at our customer that ours application work well only on       > xpsp2 ??       >       ================              If you do, it will be the beginning of the end of your application.       Customers who get that response from software vendors will immediately begin       looking for a solution.... one that will run (without issues) on the most       current OS. I know.... I've sold DOS only applications all the way up to       Windows 2000. By this time, new customers were simply saying no to DOS only       applications and existing customers were saying that if the application was       not updated to run on the most current OS, they were going to shop around       for something that does.... and they did.              Hopefully, there will be an answer to the current Paradox/Vista issues.       Either through our own collective efforts, Corel or MS.... or some       combination of the same. I think I remember reading somewhere that Corel       was going to release an updated Vista compatible version of Paradox... but       this means that Paradox developers who "prefer" an earlier version of       Paradox (for what ever reason) will be forced to migrate to the newer       version.              Paradox is by far, not the only software being impacted by Vista. If enough       complaints are heard by MS, possibly a new Service Pack release will correct       many, if not all, of these issues.              But I do remember reading, a while ago, about how MS has historically spent       a lot of money in an effort to keep their new OS's as backward compatible as       possible and the man who was the driving force behind this core philosophy       had left MS (retired).... the new guy in charge didn't share his same       philosophy and did not want to spend the required resources to keep newer MS       OS's "as compatible" with older legacy applications. As I recall, he wanted       to "move on" and abandon the code that allowed for all the compatibility       because it added to the size of the OS, added complex problems involving       security and bugs... and it slowed the OS performance. By ignoring       backward compatibility, he was essentially saying, here is where we're       going... if you don't come with us, you will be left behind.... period.       That means that every time MS comes out with a new OS, developers will be       looking at some serious and costly re-writes.... and having to support       several different versions of their own applications... one for each MS OS       Version. I think this is a big mistake for MS.... especially when there       are so many viable alternatives to MS OS's which are finally gaining       widespread acceptance in the industry.              Hopefully, the combination of a loud cry of foul from the public and slow       Vista sales will be enough of a wake up call to cause MS to take another       look at this new direction and correct it.                     --       ...        `·.¸¸.·´¯`·.¸¸.·´¯`·-> rodney              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca