Ai4rei

@Keju Nothing strange in there, have you tried the nightly (2.15.0)?

@Keju Please provide opensetup.log (SHIFT+ESC) when in Engine:LUA.

Notice about the 2GiB soft-limit is removed as of 2.4.23. The hard-limit of 4GiB remains due to limitations of the file format.

@pongpong Have not confirmed in the client yet, but the official setup recently limits height to 664 (latest nightly offers a setting to override this limit for older clients), which means, that the lowest resolution is typically 1280x720 or 1024x768.

As of last week, only patches from 2017 on-wards are provided. Edit: Updated to 2.4.23, removes notices and behavior related to archives over 2GiB.

@Emistry, the user that you have configured for the task, might not have R/W access to all the items in the patcher directory (i.e. one file with messed up permissions is sufficient for that message). As far I'm aware, the "Run as Administrator" option has no effect on scheduled tasks. Otherwise the patcher is designed to work with task scheduler. Reference task: <?xml version="1.0" encoding="UTF-16"?> <Task version="1.3" xmlns="http://schemas.microsoft.com/windows/2004/02/mit/task"> <RegistrationInfo> <Date>2016-03-08T22:25:39.51075</Date> <Author>User</Author> </RegistrationInfo> <Triggers> <CalendarTrigger> <StartBoundary>2016-03-10T23:22:22Z</StartBoundary> <Enabled>true</Enabled> <ScheduleByWeek> <DaysOfWeek> <Friday /> </DaysOfWeek> <WeeksInterval>1</WeeksInterval> </ScheduleByWeek> </CalendarTrigger> </Triggers> <Principals> <Principal id="Author"> <UserId>User</UserId> <LogonType>InteractiveToken</LogonType> <RunLevel>LeastPrivilege</RunLevel> </Principal> </Principals> <Settings> <MultipleInstancesPolicy>IgnoreNew</MultipleInstancesPolicy> <DisallowStartIfOnBatteries>false</DisallowStartIfOnBatteries> <StopIfGoingOnBatteries>true</StopIfGoingOnBatteries> <AllowHardTerminate>true</AllowHardTerminate> <StartWhenAvailable>false</StartWhenAvailable> <RunOnlyIfNetworkAvailable>false</RunOnlyIfNetworkAvailable> <IdleSettings> <StopOnIdleEnd>true</StopOnIdleEnd> <RestartOnIdle>false</RestartOnIdle> </IdleSettings> <AllowStartOnDemand>true</AllowStartOnDemand> <Enabled>true</Enabled> <Hidden>false</Hidden> <RunOnlyIfIdle>false</RunOnlyIfIdle> <DisallowStartOnRemoteAppSession>false</DisallowStartOnRemoteAppSession> <UseUnifiedSchedulingEngine>false</UseUnifiedSchedulingEngine> <WakeToRun>false</WakeToRun> <ExecutionTimeLimit>P3D</ExecutionTimeLimit> <Priority>7</Priority> </Settings> <Actions Context="Author"> <Exec> <Command>D:\RO\rsu-kro-rag-lite.exe</Command> <Arguments>/downloadonly /nocleanup</Arguments> <WorkingDirectory>D:\RO\kro\Patch</WorkingDirectory> </Exec> </Actions> </Task>

Updated to 2.14.1, updates Russian translation and fixes an UI glitch. A test build for 2.15.0 is available. If someone wants to help or is just plain bored, following tests (in addition to general function) are wanted: Behavior on AMD and nVidia graphics cards, please include opensetup.log Behavior on CJK systems, especially readability and clipping (Mis-)Behavior on Windows 10, especially clipping, please include opensetup.log (Mis-)Behavior on Windows 8(.1) Behavior on Windows 7 Functionality (whether or not selected settings work) with more recent clients (July 2018 and newer) Functionality with not so recent clients (2016 and older) opensetup.log can be created by pressing SHIFT+ESC (= write log and discard changes). Of course you can also suggest new functionality. Thanks in advance.

@Rizky Ramadhan Unless you have problems, don't do anything.

@Rizky Ramadhan : The kRO GRF has grown beyond 2GiB. Due to technical reasons older clients may not be able to use an archive that large.

The primary mirror server is broken. No ETA.

My mirror server silently died, and the only contributed mirror is outdated. Should work now.

Thanks!

Thank you very much for this microsoft-support-staff-esque answer. Actually I consider it quite rude if services dictate what kind of OS or browser its users have to use, just because they have incompetent devs. It is possible by patching the client to use a proxy DLL that forwards the calls to the real DLL when that call is supported, and emulates it when it is not. This is also the way I use to analyze new clients on Windows 98 SE.

--- /kRO/PatchClient/Lua Files/ServerInfoz/ServerInfo_KR.bak Thu May 25 18:21:24 2017 +++ /kRO/PatchClient/Lua Files/ServerInfoz/ServerInfo_KR.lua Thu May 31 19:23:26 2018 @@ -6,80 +6,18 @@ g_strPatchInf = "patch.inf" g_strPatchData = "data.grf" g_strExcute = "Ragexe.exe" +g_strExcute2 = "Setup.exe" g_strExcuteArg = "1rag1" g_strExcute2Arg = "2rag2" g_nProtocol = 1 -g_strWeb = "webpatch.ragnarok.co.kr" -g_strWebDir = "/patch" +g_strWeb = "ropatch.xcache.kinxcdn.com" +g_strWebDir = "/PatchInfo" g_strHttp = "ropatch.xcache.kinxcdn.com" g_strHttpDir = "/Patch" -g_webLoginPage = "http://ro.game.gnjoy.com" +g_webLoginPage = "http://ro.gnjoy.com" g_regPath = "RagPath" InitServerInfo = function() if g_nServerType == SERVER_TYPE.PRIMARY then - g_strPatch = "patch2.txt" - g_strNoticeClose = "ServerCheck.html" - else - if g_nServerType == SERVER_TYPE.RENEWAL_SAKRAY then - g_strPatchAllow = "patch_allow_RE.txt" - g_strPatch = "patchRE.txt" - g_strNoticePatch = "Sakray.html" - g_strNoticeClose = "ServerClose.html" - g_strPatchInf = "patchRE.inf" - g_strPatchData = "rdata.grf" - g_strExcute = "ragexeRE.exe" - g_regPath = "SakrayPath" - else - if g_nServerType == SERVER_TYPE.INDOOR then - g_regPath = "" - g_strPatch = "patch_i.txt" - g_strNoticePatch = "notice_Test.html" - g_strPatchInf = "in_dr.inf" - g_strExcute = "Indoor.exe" - g_strWeb = "192.168.5.52" - g_strFtp = "192.168.5.52" - g_ftpPort = 2000 - g_strNoticeWeb = string.format("http://%s/%s", g_strWeb, g_strWebDir) - else - if g_nServerType == SERVER_TYPE.INDOOR_IDC then - g_regPath = "" - g_strPatch = "patch_i.txt" - g_strNoticePatch = "notice_Test.html" - g_strPatchInf = "in_dr.inf" - g_strExcute = "Indoor.exe" - g_strWeb = "192.168.5.52" - g_strFtp = "192.168.5.52" - g_ftpPort = 2000 - g_strNoticeWeb = string.format("http://%s/%s", g_strWeb, g_strWebDir) - else - if g_nServerType == SERVER_TYPE.QM_PRIMARY then - g_strPatch = "patch_QM.txt" - g_strWeb = "192.168.5.52" - g_strWebDir = "/QMPatch" - g_strFtp = "192.168.5.52" - g_strFtpDir = "/QMPatch" - g_ftpPort = 2000 - g_regPath = "QMPath" - g_webLoginPage = "http://ro.game.gravity.co.kr/devGame/index.asp" - else - if g_nServerType == SERVER_TYPE.QM_SAKRAY then - g_strPatch = "spatch_QM.txt" - g_strWeb = "192.168.5.52" - g_strWebDir = "/Sak_QMPatch" - g_strFtp = "192.168.5.52" - g_strFtpDir = "/Sak_QMPatch" - g_ftpPort = 2000 - g_strPatchInf = "patchRE.inf" - g_strPatchData = "rdata.grf" - g_strExcute = "ragexeRE.exe" - g_regPath = "QMSakPath" - g_webLoginPage = "http://ro.game.gravity.co.kr/devGame/index.asp" - end - end - end - end - end - end end InitServerInfo() Hmm, they have changed the meta data server to match with the file server. K, thanks for the notice. Edit: Updated to 2.4.21, updates kRO patch information. Updated to 2.4.22, fixes potential patch process issues introduced in previous release.

As far as I know, they have only shutdown the FTP server that has been sitting around unused since they switched to HTTP last year in May.

@nikita54421: Back up. Updated to 2.14.0, adds support for high DPI screens and kRO:Zero, and fixes various UI glitches.

Updated to 2.4.19, updates twRO patch information and makes the UI less confusing. @iAmGnome: Back up. Updated to 2.4.20, the real thing.

Too old client. Too old patcher. Missing/corrupt/unreadable patch.inf / patchRE.inf

If it does not work with the official setup (assuming it is up-to-date), wouldn't that mean that there is something wrong with the RO-folder or client itself? Edit: Looking at kRO 2018-03-15a, nothing significant seems to have changed.

If this happens when the client has loaded display interface, then the above crash log indicates, that the stack most likely got corrupted (otherwise it would have to be longer with an entry to kernel32 or ntdll). Also the 2010-07-30 ragexe is known to have defects, so I would advice against using it.

Thank you very much.

@ZelosAvalon The luac5.1.4 that the batch file is supposed to run, looks odd, since it does not have an icon and is rather small, which indicates that the file is either corrupt or not built correctly (ex. depending on a DLL that is not there), or both. Try to replace the luac5.1.4 with this zero-dependency build and try again with your batch file.

Updated to 2.4.18, fixes a potential crash due to wrong memory usage.

Updated to 2.4.17, adds iRO:Restart, kRO Zero and phRO, and updates jRO patch information (for details see docs). Fixes a super-random crash on super-modern systems. The way the patcher currently processes parameters allows only predetermined combinations. /updateonly implies the normal patch process, so whichever comes first, will set the resulting mode. This changed in the nightly already, but although the nightly records /updateonly along with /repak, the repacking process does not take the auto-close into account either. Will take a look at it in the future.

What a coincidence, that's exactly how I update all my official RO data. The required magic for it is in command line switches: rsu.exe /updateonly