RunningClarion 6.3 on windows Server 2019 - does it work?

Hi all - Not very Familiar with Clarion - New here and was looking for some advice - we have a customer that runs a 3rd party application on Clarion - they are using Clarion 6.3 on a windows 2019 server.
I have come across some threads that say Clarion 6.3 can’t run-on 64-bit OS due to the 16-bit parts of it - is this true?

Is there some sort of documentation from SoftVelocity that gives requirements and recommendations?

The Support for the 3rd party application say Clarion 6.3 is fine to Run on windows 2019 Server - but my concern is that this app has not been moved on to newer versions of Clarion first of all - The customer also has continuous issues with their server, and it needs to be rebooted daily due to frozen applications and menus etc.

You need to distinguish between the Clarion 6.3 development environment and the resultant programs.

The C6 IDE, being 16 bit, will not run natively on 64bit OS. Some people set up a VM for this, while others run a Clarion6 setup within a later 32bit version of Clarion (like the current C11.1 but in theory anything from C7 or later).

However apps CREATED by C6 are 32bit so they run fine on 64bit OS,

I hope that clarifies things.

It is a long time ago now but I seem to remember there was a combination of characters that would give the “appearance” of a lockup. There were a couple of free solutions for this which would prevent it happening. Have a search for " Alt -Lockup Fix For Clarion 6", If you have no luck I will see what I can find tomorrow.

Hello, you don’t say what type of database the application is using.
If it is one of the “ISAM” database, like the TopSpeed or Clarion Drivers, then you will need to deal with SMB3 on the new server. This will significantly impact performance when running the program over the network, but avoids corrupting the database files.
If you are using a SQL database then this is not an issue.
You can tell if you are using the TopSpeed database if there are data files with .TPS extension in the folder where the program runs. The Clarion data files have a .DAT extension.

Thanks for the response - will take a look at the Alt-Lock fix you mentioned

Hi - thanks for taking the time to respond - they are running Topspeed - The database as well as the third party application all run on a windows 2019 server terminal server(TSPLUS) - 16 users connect directly and work on the server directly. as this is the case - I Dont think SMB would be an issue?

In a previous gig, we used Faux Max to take care of that lockup. It uses a little bit of screen real estate, and looks a little funky, but it helped to reduce support issues. Download Clarion Templates and Tools from Icetips Alta LLC

Or, maybe there was an additional template for the lockup.

The fauxmax solved the issue of a whole lot of maximize boxes. Not sure if it helped with the lockup.

Correct. In the setup you describe SMB is not a factor.

A Clarion 6.3 application is (compiled/linked as) a 32-bit program, so it would run on a 64-bit Windows computer, including a 64-bit Windows Server 2019. And run okay with TSplus using tps files.
Somebody gave me several Clarion 6.3 applications awhile ago and to my surprise I was able to easily get them to compile with Clarion 11 (converted as Clarion 11 applications). They are still 32-bit programs, but they run just fine on 32-bit Windows Server using TSplus. -Bob

And they’d run just fine on 64 bit Windows Server as well.

Thought this was a duplicated thread but its not.

Did you try any of the suggestions in this thread?

If the server is playing up Id go through all the event ID’s and address those first. You might find some false positives which MS acknowledge as FP’s, then start tracking what the machine is doing into the lead up to a freeze. Obviously check all drivers and the bios as well. Ive had windows servers run for weeks without any problem until a windows update forced a reboot, they should still be reliable. Memory leaks can be an issue but that can show quite quickly and I think there is a memory leak app checker around.