To: Joe NYC who wrote (108926 ) 5/1/2000 6:49:00 PM From: pgerassi Read Replies (1) | Respond to of 1572154
Dear Joe: Changing msbackup does not require any loss of reading previous versions. The old code and format should be able to be read by the newer version. If critical data was in this format, you could not read it. This is unacceptable behavior in a backup application. No other backup system does this between versions. How many upgrades have your users went through? How hard do they use the package? The users I referred to used the package day in and day out. These are secretaries and clerks. This has happened to bookkeepers with excel. Where even the import utility does not work and messes up the files so that the only way to get the program to work was to print it out in the old version, input in manually in the new version and then debug any changes needed. This takes many days. All the while, the tasks must be done. I have seen this time and time again with Microsoft. It causes so much lost time and productivity, that many businesses wait 1 to 2 years before changing to find all the "Land Mines" before converting. This is why businesses are beginning to simply say we will stay with what works and "To Heck (expletive changed) with Microsoft". This may hit Microsoft much harder in the future. I agree that for simple tasks, the average users, do not need the high horsepower machines. But the tasks are getting larger. If Microsoft, or any other company, does this with small simple tasks, imagine what they do to very complicated tasks. In some cases, a Microsoft supplied software product simply crashes just for being on 40 days. Things like memory leaks and uninitiated pointers are tolerated. These are the kind of things that crash systems. When someone claims that he can open 15 windows at once on NT and it does not crash, but does just two or three things and shuts their computer off every night, that NT never crashes. This is not a heavy user. On the same system under a UNIX like OS, you can have 10 people opening 20 windows each and running like 10 different large compile runs simultaneously, and this goes on for weeks on end without a single crash, that is what I call a heavy load. I have seen people say that the UNIX system crashed, when it was their PC running X Windows on Windows 98 that crashed. When you can run on a Windows NT platform for six months up all the time (24/7) doing many heavy duty tasks, such as development or high database loads, without a single crash, then I will allow that Windows is virtually crashless. Remember NT is not nor has ever been a multiple concurrent user platform. Citrus and Orange, I believe, have a reworked Windows NT version that does this but, they charge like $10,000 for a 10 user system. Pete