Windows 7 and 5.4.1

[Kevin Crist]

We have a pc that was upgraded from XP SP3 to Windows 7. We have CL 5.4.1 and it installed fine on the new pc but cant see the Network Monitor (screenshot attached) is there any settings that need to be done for this?

Thanks.

Topic

[David Barr]

Try increasing the amount of memory that the JVM can use.

Add this line to the [general] section of the client.ini file:

jvm_args=-Xmx512M

[Russ Ross]

We have Cloverleaf 5.6rev2, which installed but didn’t work much at all under Windows 7 similar to what you described for Cloverleaf 5.4 running under Windows 7.

I would expect an earlier version like Cloverleaf 5.4 to have the same or more trouble working under Windows 7.

Also, be aware earlier releases of Cloverleaf running under Windows 7 aren’t supported by Lawson even if you get them to sort of work.

Finally I did run across a cloverltech post indicating someone had figured out how to get Cloverleaf 5.6rev2 to mostly work under Windows 7.

I followed their lead and did get Cloverleaf 5.6rev2 installed and mostly working under Windows 7 at first glance.

At least it looks promising enough I’m coordinating having my PC migrated to Windows 7 and will be trying it for a while before converting the rest of the integration team.

Here is the URL describing the steps I followed in case you are interested in seeing if you might have any success getting Cloverleaf 5.4 to work under Windows 7.

<a href="https://usspvlclovertch2.infor.com/viewtopic.php?t=5706&#8243; class=”bbcode_url”>https://usspvlclovertch2.infor.com/viewtopic.php?t=5706

Russ Ross
RussRoss318@gmail.com

[Charlie Bursell]

It depends on which version of Windows 7 you use.  We, the Implementers, have been running every version of Cloverleaf since 5.4 under Windows 7 Professional with no problem.

However it is for personal use only.  I don’t think it would be much use as a production server with several external clients.

I made no changes to my Windows 7 at all when installing.  In earlier Revs I had to copy the changed files manually or change the install.cmd script since it did not like Windows 7.

Russ is correct however.  When you install on a non-supported box you are more or less on your own  😀

[Author]

Replies