Page 1 of 1

Telegram Desktop ends support of Windows XP

Posted: Fri Jul 19, 2019 6:29 am
by Quim
Telegram Desktop ends support of Windows XP and of course ReactOS. The applications warns about it:
https://jira.reactos.org/secure/attachm ... legram.png
Image

Re: Telegram Desktop ends support of Windows XP

Posted: Fri Jul 19, 2019 7:01 am
by Quim

Re: Telegram Desktop ends support of Windows XP

Posted: Tue Sep 03, 2019 6:11 am
by Quim
Image

I hope that compatibility layer will be enough to run newer versions... Telegram is a golden app.
I will see when new version will be available to test...

For the moment last version (1.8.8) works natively under ROS. :D

Re: Telegram Desktop ends support of Windows XP

Posted: Mon Jan 06, 2020 10:52 pm
by Quim
Finally it happens, version 1.9.3 (what I tested) does not work under ROS.
See here https://jira.reactos.org/browse/CORE-16617
Image

Last working version under ROS is 1.8.15 . https://github.com/telegramdesktop/tdes ... ag/v1.8.15

From the bug report:

Code: Select all

(dll/win32/kernel32/client/proc.c:138) Accepting image version 6.0, although ReactOS is an NT 5.2 OS!
Does it mean NT 6.x kernel compatibility or something like it? :?

Re: Telegram Desktop ends support of Windows XP

Posted: Mon Jan 06, 2020 11:59 pm
by EmuandCo
This does mean that the exe was built for NT6.X user mode aka > Windows XP/2003 and likely does not run on ROS yet.

Re: Telegram Desktop ends support of Windows XP

Posted: Tue Jan 07, 2020 2:40 pm
by shunesburg
Do you have try with the compatibility mode?
You can force NT6 compatibility, sometimes it works for some software.

Re: Telegram Desktop ends support of Windows XP

Posted: Wed Jan 08, 2020 12:18 am
by Quim
shunesburg wrote:
Tue Jan 07, 2020 2:40 pm
Do you have try with the compatibility mode?
You can force NT6 compatibility, sometimes it works for some software.
Does not work too... exactly the same message about missing procedure entry point CompareStringEx not located in the dynamic link library KERNEL32.dll.

So , are there enough NT 6.x documentation (maybe WINE, Windows Internals,...) in order to implement enough NT 6.x APIs in ROS?

From https://source.winehq.org/WineAPI/kernel32.html says "CompareStringEx (not documented)" , so even WINE does not have implemented it? I didn´t tested running in WINE yet...

Re: Telegram Desktop ends support of Windows XP

Posted: Thu Jan 09, 2020 11:29 pm
by Quim
EmuandCo wrote:
Mon Jan 06, 2020 11:59 pm
This does mean that the exe was built for NT6.X user mode
So just implementing the necesary NT 6.x API , with actual ROS NT 5.2 it could work finally or must be NT 6.x kernel too?

Re: Telegram Desktop ends support of Windows XP

Posted: Fri Jan 10, 2020 1:09 am
by irony
quim, why you search info on a WinAPI function on a whine site, instead of where it really belongs? where it is perfectly documented. that "not documeted" on the whine site means, that they (whiners) all are c00l h4ck3rz and writing documentation is not for them and totally not, that MS hid the specification of a string comparison function. so no need to dig into Windows Internals or sink in the reverse engineering for days if your goal is getting to know what that function does or implementing it for ReactOS.

Re: Telegram Desktop ends support of Windows XP

Posted: Fri Jan 10, 2020 2:30 am
by justincase
Looks like we have a partial implementation of CompareStringEx in the code. I can understand if it's hidden by ReactOS not exposing NT6+ exports, but the NT6+ shims should make it so it at least be findable, even if it may need more work to make it function correctly, right? or is the NT6+ compatibility shim still not able to do that yet?

@irony: Dude, no need to blow up over something so trivial, quim obviously didn't know that they should first look to Microsoft's documentation, then other places.

Re: Telegram Desktop ends support of Windows XP

Posted: Fri Jan 10, 2020 3:37 am
by irony
@irony: Dude, no need to blow up over something so trivial, quim obviously didn't know that they should first look to Microsoft's documentation, then other places.
right. :D it's too hard to comprehend. I just helped giving him the link anyway, no "blowing up", it looked very suspicious, that a string comparison function is "not documented", so when ensured it is, I expressed my wondering why one ever would search on garbage half assed resources, that only add to confusion instead of clarifying.