Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


Dibya

Creating a Full-Blown Compatibility Layer.

Recommended Posts

On the topic of "Creating a complete compatibility level". Except construction sites I see no progress. For 2 months Extended XP would have to be updated due to the published security updates of MS. Maybe a user who has the appropriate competence has a sensible project on his feet and not just big promises. Here a part as a part, only concept-less tinkering, where ultimately only can fail.

See the project Extended XP as failed!

:(

Share this post


Link to post
Share on other sites

@98SE

With all due respect :) why limiting the patch to 192 GB or 2 TB?

Why not promoting the idea that every single device should have no less than 128 Petabyte of RAM? :dubbio:

I mean, if you dream, dream big. ;)

In the real world, most machines have tops 4 Gb RAM, a few have 8 or 16 Gb, a handful have 32 or 64 GB, I have never seen in my life (and I have seen quite a few machines, rest assured) an actual machine with 128 Gb of RAM, most probably the people I know are not rich (or gullible) enough to spend the kind of money needed for 128 Gb of RAM (and for the accompanying top level hardware), maybe I should try to elevate the circle of my acquaintances. :unsure:

@Heionoganda

Why this new statement? I thought you saw it coming early enough. :(

jaclaz
 

Share this post


Link to post
Share on other sites
13 hours ago, heinoganda said:

On the topic of "Creating a complete compatibility level". Except construction sites I see no progress. For 2 months Extended XP would have to be updated due to the published security updates of MS. Maybe a user who has the appropriate competence has a sensible project on his feet and not just big promises. Here a part as a part, only concept-less tinkering, where ultimately only can fail.

See the project Extended XP as failed!

:(

Come on fixing A Vast issue almost done . what about running Chrome 56 ?

Share this post


Link to post
Share on other sites

@jaclaz

Everyone should get his chance, you need not be sad with me and I stand by it even though the signs have been there already.

:)
 

@Dibya

Do not be angry with me, but be honestly it is missing now 2 months where updates were not implemented and thus Extended XP became useless! What should the user think of, for example, Palemoon from version 27 onwards, updated updates from MS installed and nothing goes more! I explained before you the situation, only you seem not want to understand and not enough lets the users in the "rain" stand.

:no:

Edited by heinoganda

Share this post


Link to post
Share on other sites

@Heinoganda

I am not sad with you, only sad for you as it seems like the thingy isn't going as you expected, but was perplexed about your statement (in the sense that it seems to me nothing changed, if not maybe some time that passed without progress). :)

jaclaz
 

Share this post


Link to post
Share on other sites

@jaclaz

Ok, then I did not understand that correctly. Well, as far as my time is concerned, I have invested in this project is still the smaller problem, but the users of the original projects (mfc42 extension as an example) that were linked together in this project. The point that here is also the necessary respect before his projects is missing and I find it too bad to find then parts in Extended XP were inserted where then standstill! This frustrates me the most!

:)

Share this post


Link to post
Share on other sites

Guys, I don't like to be the one to disrupt your conversation, but please create a separate topic for it or use PMs. :ph34r: This topic is about compatibility layer for Windows XP. Thank you. :)

Share this post


Link to post
Share on other sites

Hi any one can analyze this why firefox 53 is crashing when i want to type some thing


Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.

CommandLine: "E:\Test XP\core\firefox.exe"
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path.           *
* Use .symfix to have the debugger choose a symbol path.                   *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
ModLoad: 00400000 00481000   firefox.exe
ModLoad: 7c900000 7c9b4000   ntdll.dll
ModLoad: 7c800000 7c8ff000   C:\WINDOWS\system32\kernel32.dll
ModLoad: 10000000 10022000   E:\Test XP\core\mozglue.dll
ModLoad: 77dd0000 77e6b000   C:\WINDOWS\system32\ADVAPI32.dll
ModLoad: 77e70000 77f03000   C:\WINDOWS\system32\RPCRT4.dll
ModLoad: 77fe0000 77ff1000   C:\WINDOWS\system32\Secur32.dll
ModLoad: 03000000 0312c000   C:\WINDOWS\system32\dbghelp.dll
ModLoad: 70860000 7090a000   C:\WINDOWS\system32\msvcrt.dll
ModLoad: 6b430000 6b439000   C:\WINDOWS\system32\VERSION.dll
ModLoad: 00280000 002ec000   C:\WINDOWS\system32\MSVCP140.dll
ModLoad: 002f0000 00305000   E:\Test XP\core\VCRUNTIME140.dll
ModLoad: 00310000 00314000   C:\WINDOWS\system32\api-ms-win-crt-runtime-l1-1-0.dll
ModLoad: 00320000 00400000   E:\Test XP\core\ucrtbase.dll
ModLoad: 00490000 00493000   C:\WINDOWS\system32\api-ms-win-core-string-l1-1-0.dll
ModLoad: 004a0000 004a3000   C:\WINDOWS\system32\api-ms-win-core-errorhandling-l1-1-0.dll
ModLoad: 004b0000 004b4000   C:\WINDOWS\system32\api-ms-win-core-file-l1-1-0.dll
ModLoad: 004c0000 004c3000   C:\WINDOWS\system32\api-ms-win-core-timezone-l1-1-0.dll
ModLoad: 004d0000 004d3000   C:\WINDOWS\system32\api-ms-win-core-namedpipe-l1-1-0.dll
ModLoad: 004e0000 004e3000   C:\WINDOWS\system32\api-ms-win-core-handle-l1-1-0.dll
ModLoad: 004f0000 004f3000   C:\WINDOWS\system32\api-ms-win-core-file-l2-1-0.dll
ModLoad: 00500000 00503000   C:\WINDOWS\system32\api-ms-win-core-heap-l1-1-0.dll
ModLoad: 00510000 00513000   C:\WINDOWS\system32\api-ms-win-core-libraryloader-l1-1-0.dll
ModLoad: 00520000 00523000   C:\WINDOWS\system32\api-ms-win-core-synch-l1-1-0.dll
ModLoad: 00530000 00533000   C:\WINDOWS\system32\api-ms-win-core-processthreads-l1-1-0.dll
ModLoad: 00540000 00543000   C:\WINDOWS\system32\api-ms-win-core-processenvironment-l1-1-0.dll
ModLoad: 00550000 00553000   C:\WINDOWS\system32\api-ms-win-core-localization-l1-2-0.dll
ModLoad: 00560000 00563000   C:\WINDOWS\system32\api-ms-win-core-datetime-l1-1-0.dll
ModLoad: 00570000 00573000   C:\WINDOWS\system32\api-ms-win-core-sysinfo-l1-1-0.dll
ModLoad: 00580000 00583000   C:\WINDOWS\system32\api-ms-win-core-synch-l1-2-0.dll
ModLoad: 00590000 00593000   C:\WINDOWS\system32\api-ms-win-core-console-l1-1-0.dll
ModLoad: 005a0000 005a3000   C:\WINDOWS\system32\api-ms-win-core-debug-l1-1-0.dll
ModLoad: 005b0000 005b3000   C:\WINDOWS\system32\api-ms-win-core-processthreads-l1-1-1.dll
ModLoad: 005c0000 005c3000   C:\WINDOWS\system32\api-ms-win-core-file-l1-2-0.dll
ModLoad: 005d0000 005d3000   C:\WINDOWS\system32\api-ms-win-core-profile-l1-1-0.dll
ModLoad: 005e0000 005e3000   C:\WINDOWS\system32\api-ms-win-core-memory-l1-1-0.dll
ModLoad: 005f0000 005f3000   C:\WINDOWS\system32\api-ms-win-core-util-l1-1-0.dll
ModLoad: 00600000 00603000   C:\WINDOWS\system32\api-ms-win-core-rtlsupport-l1-1-0.dll
ModLoad: 00610000 00613000   C:\WINDOWS\system32\api-ms-win-core-interlocked-l1-1-0.dll
ModLoad: 00620000 00624000   C:\WINDOWS\system32\api-ms-win-crt-string-l1-1-0.dll
ModLoad: 00630000 00633000   C:\WINDOWS\system32\api-ms-win-crt-heap-l1-1-0.dll
ModLoad: 00640000 00644000   C:\WINDOWS\system32\api-ms-win-crt-stdio-l1-1-0.dll
ModLoad: 00650000 00654000   C:\WINDOWS\system32\api-ms-win-crt-convert-l1-1-0.dll
ModLoad: 00660000 00663000   C:\WINDOWS\system32\api-ms-win-crt-locale-l1-1-0.dll
ModLoad: 00670000 00675000   C:\WINDOWS\system32\api-ms-win-crt-math-l1-1-0.dll
ModLoad: 00680000 00685000   C:\WINDOWS\system32\api-ms-win-crt-multibyte-l1-1-0.dll
ModLoad: 00690000 00693000   C:\WINDOWS\system32\api-ms-win-crt-time-l1-1-0.dll
ModLoad: 006a0000 006a3000   C:\WINDOWS\system32\api-ms-win-crt-filesystem-l1-1-0.dll
ModLoad: 006b0000 006b3000   C:\WINDOWS\system32\api-ms-win-crt-environment-l1-1-0.dll
ModLoad: 006c0000 006c3000   C:\WINDOWS\system32\api-ms-win-crt-utility-l1-1-0.dll
(35c.370): Break instruction exception - code 80000003 (first chance)
eax=00191eb4 ebx=7ffd4000 ecx=00000006 edx=00000040 esi=00191f48 edi=00191eb4
eip=7c90120e esp=0012fb20 ebp=0012fc94 iopl=0         nv up ei pl nz na po nc
cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000202
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntdll.dll -
ntdll!DbgBreakPoint:
7c90120e cc              int     3

Share this post


Link to post
Share on other sites

Stack dump is missing, so impossible to determine who called ntdll!DbgBreakPoint. MS Debugger might need to be reconfigured to provide more details. An automated stack trace would be easier. Try debugging with VisualStudio, Ollydbg, GoBug, FineSSE, etc. You may also need to download and test with a debug build of FF53.

Share this post


Link to post
Share on other sites

@Dibya I tried FontCreator 11 on vanilla XP SP3 and it doesn't show any window, can you test it in your ExtendedXP?

Share this post


Link to post
Share on other sites
8 hours ago, roytam1 said:

@Dibya I tried FontCreator 11 on vanilla XP SP3 and it doesn't show any window, can you test it in your ExtendedXP?

okay

EDIT::
following API are missing on my system may be more on vanilla XP

KERNEL32.DLL
GetTimeZoneInformationForYear
USER32.DLL
CloseGestureInfoHandle
GetGestureInfo
GetTouchInputInfo
IsTouchWindow
PhysicalToLogicalPoint
RegisterTouchWindow
SetGestureConfig

I will try let see what happen

Edited by Dibya

Share this post


Link to post
Share on other sites

FontCreator 11 , ultra edit , ultra compare , Adobe reader DC , Filezzila , Firefox 53 , palemoon , some games working with out hick so its time to release extendedXP soon . i want to optimize code and ensure better stability . I will create a new thread . 

Those who want to test before public release let me know .

any one has any idea how to get vista mui compatibility in xp ? @blackwingcat seems to know . I wish he say something in this context .

I wish creator of Xompie to create a new thread and update his project with some new screenshots .

  • Upvote 1

Share this post


Link to post
Share on other sites

@TuMaGoNx man are you here ?

Share this post


Link to post
Share on other sites
42 minutes ago, Dibya said:

@TuMaGoNx man are you here ?

No, he isn't.

You should use PM's if you want to contact another member directly, the function is there for some reasons (among them avoiding using the board for this kind of activity), a board is not (and should not become IMNSHO) Twitter or Yo.

jaclaz

Edited by jaclaz
  • Upvote 1

Share this post


Link to post
Share on other sites
7 hours ago, TuMaGoNx said:

I might polish XomPie, (installer, makefiles...) but no further feature plus removing half-baked functions.
Other note: UI related library is hardest one (shell32.dll) it unlikely reliable to bridge from older OS unless the shell (explorer.exe) itself get upgraded...
Regarding Wine: the more you take from there the more it become incompatible with original XP system files --> the more you will replace everything with wine... silly
the less you take from wine.. ummm the more works to be done doh.. sometime approach like func_new(a,b) -> func_old(a) is enough but often unreliable

donot leave your hope 

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...