Dirtsand Early 2018

[J'Kla]

Well it appears I am at a dead end with this I have that Windows 7 Machine working but it is now the only one Windows 10 is dead in the water for my LAN dirtsand.

Like I say the plClient.exe is the one provided for the Destiny shard and it has the same failure on Destiny or my own dirtsand shard

So I am going to start a new investigation to try and make Noob compatible instructions for a MOSS shard.

[Deledrius]

Well it appears I am at a dead end with this I have that Windows 7 Machine working but it is now the only one Windows 10 is dead in the water for my LAN dirtsand.

Your dirtsand server isn't running in Windows, so that's not the culprit.

So I am going to start a new investigation to try and make Noob compatible instructions for a MOSS shard.

Welcome to a whole new set of problems.

[J'Kla]

I know dirtsand is not running on Windows but the plClient is.

And yes I am expecting more problems

plClient sorted on Windows10

I should add this was cured by installing a fresh MOUL on the Client PC this obviously added something in the way of a .dll or the like to the system that made it possible for plClient to work.

[J'Kla]

Advise Requested.

OK I am confident this method works I have tested it on my LAN and from remote locations using No-IP.com to give me a web address.

I would just stuff this into the Wiki but not only as previously demonstrated I am the duty idiot, I am also not exactly rolling in confidence having just been torn off a strip by the Tsar Hoikas for not reading his Wiki entry on Journals within Korman 0.08. The strip is still bleeding.

I have attached the two files here as word documents

Short Version of dirtsand build.docx

(13.56 KiB) Downloaded 22 times

Long version of dirtsand build.docx

(28.18 KiB) Downloaded 18 times

I am unsure as to the best method i.e. Do we/I edit the current entry or add a new page highlighting that this is Noob territory?

There is also the mater of the correction that is inserted as a temp fix in AuthDaemon.cpp where I was told that a proper fix would be forth coming.

This leaves me in some doubt, does this get posted with the temp fix pending the official correction or do I continue to hold off because a fix is imminent.

[J'Kla]

Reviewing the new Ubuntu Server Release