On Tue, Feb 9, 2010 at 20:07, Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx> wrote:
Ugh. ÂNo it isn't. ÂIt's at most V5R3 to V5R4, which is an overnight
upgrade. ÂTry switching from 2003 to 2008.
Or are you TRYING to be obtuse?
No, you're trying to make a point which isn't valid - higher hardware
requirements on an OS that was released in 2008, versus one that was
released in 2003 are perfectly acceptable and valid. I can't run V6R1
on a Model 270 either - and that's perfectly okay.
2008 R2, which is a major release (not a service pack, it requires a
2008 R2 license), does not have higher hardware requirements than
2008.
And while V5R3 may install on a 170, it's not a good idea to do so.
Bad vendor, NOTHING to do with the OS.
Yep. So if your upgrade from 2003 to 2008 wasn't painless, you know
who to blame. I've never had issues with OS upgrades with Microsoft
products - it's always the third party products that are programmed by
idiots.
Example ONE: When Microsoft killed VB6, everything had to be rewritten.
Give me a break.
When IBM killed BASIC, everything had to be rewritten. The basic
compiler doesn't pass ANZOBJCVN.
Our legacy software package which still used 5250 (discontinued in
2000, i believe), was still written in BASIC. Yep, it does convert to
V6R1 because we can compile it on V6R1, but in the same way, VB6
applications still run on 64bit Windows 7.
There is a lot of crap and a lot of shittyness in the Microsoft world,
but acting like everything IBM does is perfect doesn't help you.
Doesn't help if your machine isn't supported.
Yeah, i can't run V6R1 on my model 170 either, so what? It's not supported.
Did you ever read a "Memo to user"? It's just as complicated, just
because it lasts all the options you have.
You said it was simple. ÂThe page disagrees. ÂDon't blame me, it's one
of your guys who said it.
It IS simple if you know what you're doing. When i look at an RPG
manual, even the basic stuff looks very complex to me. Because i don't
know the basics of RPG.
The blog post you mentioned tried to give you an option for every
scenario, of which most don't apply to you.
And that's why I stay out of these conversations. ÂI'm done here.
Continue to tell us how Windows is as easy as i5/OS, Lukas. ÂIt's cheap,
but it ain't easy. ÂYou get what you pay for.
I think i explicitly stated that Windows is only cheap if you don't
license it correctly. Even in reply to one of your posts.
What annoys me about the IBM i apologists here is that you can't deal
with criticism of your system - for every bad Windows application,
it's Microsoft's fault. But when something on the i doesn't work
correctly, you blame the vendor. The latter makes a lot of sense, but
apparently it's not something you do on Windows, because blaming
Microsoft is easier.
midrange.com
