I think it's working. So besides commenting the console event init stuff which uses a function not present in mono, I had to compile lapper with the symbol MONOSQLITE so it would use Mono.Data.SqliteClient instead of System.Data.SQLite .
Perhaps in the future you could make two releases? One for windows and one for linux (mono)
Additionally I installed libmono-i18n4.0-all which installed a whole lot more libs for mono which helped a bit too with some other problems. Not sure why I hadn't done that before...
I can provide a bit updated code tomorrow (it's late now and i might do some more tweaks), allowing you to easily create the two version if you want.
@alau07 could you try lapper again on your host?
EDIT - hmm found some more problems. Might take until tomorrow before they're fixed.
EDIT - I wonder if this could be avoided, maybe with a startup param or config variable that enables console events or not. In my case I'd disable them and this piece of code wouldn't have to run.
Maybe I should install VS again .. hmm.
pff ... have updated the os and mono and everything, but still the same issue. Seems mono doesn't know about 1251. But apparently it is supposed to know "windows-1251" (even though 1251 in the functions below should work according to docs).
I wonder if it's possible for you to create a test version with the following change? Would like to try.
I've dumped some Lapper traffic where you can see:
17:03:03.879720 - Lapper sends ISP_ISI with the correct admin password
17:03:03.881793 - LFS sends ISP_VER in reply (so everything should be ok, yet I don't see this in the LFS console )
and then some more data is exchanged before Lapper hangs up right after sending ISP_TINY + TINY_NCN (17:03:04.015324).
So this is pretty weird. In which cases does Lapper report that the admin password is incorrect?
The logs don't tell us much unfortunately.
Via the LFS console I'm seeing Lapper connect, and disconnect basically immediately:
and that's all
We're using the latest Lapper v220.127.116.11
I'll keep trying to find out what's going on. Though I wonder if there could be a bit more debug for the log files.
Another thing I noticed is that Lapper doesn't seem to send an init packet at all. Otherwise the console output would have shown "InSim : version 7 requested - using 7" after "InSim - TCP : LFSLapper", but there's no such line.
I assume the message "InSim guest closed : LFSLapper" means Lapper actively closed the connection.
Does that give you guys any hints?