Curious if anyone has deployed an EXE on Linux or a Windows Emulator such as WINE. The program accesses primarily TPS files, and a few MSSQL tables. The IT manager that wants to try this configuration is also concerned about the TPS files locking.
Thanks,
Mark
Hi Mark
It’s worth experimenting. TPS files are no more likely to lockup under wine than they are Windows. My own approach is that if the TPS files are to be shared (on a network or terminal server) then the IP Server/Driver is the way to go.
You can also use XRDP on Linux if you need a terminal server and don’t want to use TS Plus or Citrix etc
Cheers
Rohan
I Posted this on 23rd of June 2023 in comp.lang.clarion
Hi All
Just an FYI.
Extending the life of a couple of older family laptops I installed a Linux Distro Q4OS (32 bit using the Trinity Light Weight desktop) because it has a Windows Like UI. https://q4os.org/
I was curious to see what WINE was capable of running.
Clarion IP Server - Yes ( accessible internally and externally of the device)
Clarion Appbroker - Yes (had to change the ports. accessible internally and externally of the device)
Clarion Anyscreen - No (the netmanager and netsetup “sort of work”)My programme;
BackOffice uses a mix of local TPS and IP Server - capable of accessing the local IP server and an external Ip server
PrintServer - running as a task - no issue communicating with an external IP server and printing to network printers.
So my conclusion is that I wouldn’t bother using a Q4OS Pc/Laptop for server activities (it was interesting to see what works and what doesn’t though) but it works fine as a client device as well as a general use PC - something for the back pocket that may be useful
cheers
Rohan
You certainly use Linux as a file server with Samba, that’s well established. This is the way most small NAS systems work.
It’s been a couple of years since I tried WINE. My experimentation has been mixed, and It changes depending on the Wine version and the Clarion version as to how much works.
I’ve also wanted ODBC access which is somewhat harder to acheive. Mostly programs run, so I’d suggest trying and seeing how it goes
I’ve tested one of our systems on Wine several times, and it works perfectly connecting to MSSQL databases in our case. The only issue we had was that the system wouldn’t start, obviously, because it was missing a DLL. The problem was that it didn’t warn us at all. Not a single message.
I am not as fond of the IP driver. I used it in my application for several years. Although the driver is mostly reliable it is not as reliable is I needed. The biggest issue is how the ip driver handles any disconnections etc. Where i need network access I have turned to web services. They are easy to create and easy to consume. It does take a re-write. Something else to add to the mix.
Hi Jeff
I’ve found the IP driver very reliable over the years. There are a couple of “tweaks” and a bit of extra code that I’ve written in my applications that manage disconnections - especially my printserver/manager - it tests for the IP server and restarts if it’s not there after NN seconds - this is an issue regardless of what is written. If the server is not there (due to restart or whatever) then it’s not there. Because the printserver/manager is not generally running on the server it’s better to write some code to handle the server’s “disappearance”. Saves a lot of support issues.
Horses for courses. The IPdriver/server works for me. The WINE exercise was.. “I wonder what happens if…”