|
>From: Leif Svalgaard [mailto:leif@xxxxxxxx] >...by forcing the user into the upgrade cycle by >tying hardware and software upgrades,... How does MS "force" the user to upgrade. In fact I'd argue that an iSeries user is more forced to upgrade than an MS user. Given the size of the PC hardware market it would be easy (and cheap) for me to buy the hardware I need to run DOS 6.22 today. Try to buy the hardware needed to run V2R2. To run a production machine you need to be able to support hardware failures. I can do that in a PC environment by buying new hardware to run my OS at a cost effective price, how do I do that in an iSeries environment? -Walden PS. Obviously, I can't use the new features w/o upgrading, but a user's desire to use a new feature isn't MS "forcing" the user to upgrade, it's the user opting to upgrade. ------------ Walden H Leverich III President Tech Software (516) 627-3800 x11 (208) 692-3308 eFax WaldenL@xxxxxxxxxxxxxxx http://www.TechSoftInc.com Quiquid latine dictum sit altum viditur. (Whatever is said in Latin seems profound.) -----Original Message----- From: Leif Svalgaard [mailto:leif@xxxxxxxx] Sent: Tuesday, May 13, 2003 11:08 AM To: Midrange Systems Technical Discussion Subject: Re: V5R2 Quality - Notes from the field needed From: Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx> > However, I thought that one of the fundamental ideas of OS/400 was that you > could slip new hardware underneath the operating system without disturbing > it. I thought the horizontal and vertical microcode was supposed to allow > exactly this sort of thing. Haven't we had processor upgrades before that > didn't require an upgrade to a new version of the operating system? > > Just wondering. Because if you're saying each new version of hardware > requires new software, then OS/400 has lost one of the major benefits that I > (evidently mistakenly) thought it had. > IBM has discovered that Microsoft makes money (and lots of it) by forcing the user into the upgrade cycle by tying hardware and software upgrades, so IBM wants to try that too. _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.