Comments on: installing client access version V5R2M0 on windows 7 64 bit http://itknowledgeexchange.techtarget.com/itanswers/installing-client-access-version-v5r2m0-on-windows-7-64-bit/ Fri, 24 May 2013 16:35:04 +0000 hourly 1 By: tomliotta http://itknowledgeexchange.techtarget.com/itanswers/installing-client-access-version-v5r2m0-on-windows-7-64-bit/#comment-97173 tomliotta Thu, 29 Sep 2011 00:21:08 +0000 #comment-97173 When he installed on Win7-64, green screen sessions came right up – no issues.
It was ODBC that was a problem (which we use heavily).

If the OS has the interfaces used by the programming, the programming should work. A telnet client is probably (relatively) easy. It’s little more than establishing a socket and relaying characters to and from the display and keyboard.

But a remote database connection requires quite a bit more. (Note that Microsoft has never really supplied an ODBC client to SQL Server for the AS/400 platform, and the AS/400 finds it fairly easy to support old versions of software after upgrading the OS. Apparently, MS thinks ODBC clients are not trivial.) How many times have drivers of various kinds needed to be updated/replaced after a Windows upgrade? The underlying rules are changed by the new OS.

When going from 32-bit to 64-bit, it’s even more complicated (on Windows).

How about running WinXP in a VM? Then install iSeries Access on WinXP.

Tom

]]> By: donethat http://itknowledgeexchange.techtarget.com/itanswers/installing-client-access-version-v5r2m0-on-windows-7-64-bit/#comment-97166 donethat Wed, 28 Sep 2011 21:21:47 +0000 #comment-97166 I verified: no special software installed on either XP or Win 7 (32 or 64) machines.

We just take the giant IBM install and run it.

]]> By: woodengineer http://itknowledgeexchange.techtarget.com/itanswers/installing-client-access-version-v5r2m0-on-windows-7-64-bit/#comment-97151 woodengineer Wed, 28 Sep 2011 15:57:49 +0000 #comment-97151 I am working from memory here but as I recall we had do a one-time install of a piece of software from IBM based on the hardware where the Client Access upgrade would be installed – either the 32-bit or the 64-bit version of the program.

According to IBM, the extra program had to be installed prior to installing the upgrade.

]]> By: donethat http://itknowledgeexchange.techtarget.com/itanswers/installing-client-access-version-v5r2m0-on-windows-7-64-bit/#comment-97111 donethat Tue, 27 Sep 2011 16:13:55 +0000 #comment-97111 Here is a little more detail…
When he installed on Win7-64, green screen sessions came right up – no issues.
It was ODBC that was a problem (which we use heavily).
After downgrading to Win7-32, V5R2 CA ODBC worked straight away.
We have 2 Win7-32 PCs running V5R2 CA identically to our XP machines.
Unfortunately I don’t know what causes the XCOPYFILE-2 error you are referring to. We install from CD…maybe you are trying to install from the AS400 or a network server?

]]> By: tomliotta http://itknowledgeexchange.techtarget.com/itanswers/installing-client-access-version-v5r2m0-on-windows-7-64-bit/#comment-97071 tomliotta Mon, 26 Sep 2011 19:53:15 +0000 #comment-97071 You were probably lucky getting such an old version to install on Win7. See the Using IBM i Access with Windows OSs for supported combinations.

Perhaps installing XP Mode on your PC will give you some success.

Tom

]]> By: donethat http://itknowledgeexchange.techtarget.com/itanswers/installing-client-access-version-v5r2m0-on-windows-7-64-bit/#comment-97062 donethat Mon, 26 Sep 2011 17:42:18 +0000 #comment-97062 Bad news. My network guy worked very hard on getting V5R2 CA installed on Win 7-64.
He’s a talented guy & put in a lot of effort but no-go.
Had to downgrade to Win 7-32.

]]>