Leaderboard

To steer this back to kernel discussion, I saw the ReactOS code. However, as I am not under the same restrictions for code usage that ReactOS has, I will try with the Windows 7 version of the function first, in both ntdll and ntoskrnl. January 2021. Before that, there is a possible solution to the kernel32 x86 problems I have discovered. I now have a hunch that putting any code after rsrc and reloc (in addition to the export table) is a recipe for disaster so I will have to rework the file with the export tables and code all before rsrc/reloc.

The English requirement on the forum is for text posts, not for screenshots. Our users are from all over the world and we have no expectation that the language on their computers is in English. If you see something in a screenshot in another language and you do not know what it says, you can use an OCR translator, or transcribe it yourself into a translator program, or worse case, just ask the poster to translate for you. Otherwise, ignore it if you do not want to go through the effort to try to help someone.

I didn't want to argue, I just presumed that this generic message is known to everyone. Oh well, sorry if you felt offended by that.

Hello MSFN users. I decided to create an account here because when I'm searching for error messages and information about Windows I'm constantly running into this website. I do software development and and I test my programs on a variety of versions of Windows to ensure it works good on Windows.

There is indeed a difference between VLC versions due to what kind of icons developers chose to put on the buttons. But this topic was started as a discussion for the solution about the technical problem that happens under specific circumstances and causes the application to render GUI in the old fashion, like how it was always done before Microsoft added visual style functionality in Windows XP. The topic was also initially placed in Vista sub-forum, which I think was appropriate, considering it is related to Vista specific issue. The workaround ensures theming works for the application so the buttons and other GUI elements get background texture from Microsoft's Aero theme. That's all there is to it. It doesn't seem like this discussion is going anywhere, so I believe that unless there is an interest in fixing the issue at the OS level, we can just call it a day. BTW, I have tested the following code snippet: SetDefaultDllDirectories(LOAD_LIBRARY_SEARCH_SYSTEM32); HMODULE hUxThemeLib = LoadLibraryExW(L"C:\Windows\System32\UxTheme.dll", NULL, LOAD_WITH_ALTERED_SEARCH_PATH); It works as expected on Vista. So if the code that loads UxTheme.dll used the absolute path, there wouldn't be a problem. It's also done like that on Win7.

The windows experience index no longer works https://imgur.com/JIYX3B0 I don't care about it but just to let you know

VLC 2.2.x UN-patched with beautiful Vista buttons , now with these high quality pictures , which I spent some time to deliver , I assume one can see that patching is only a 50/50 solution at best , and I really hope this will help TCHEGEEK to finally notice the difference on his display . By the way , @TECHGEEK , have you ever considered writing to the developers of VLC directly ? I mean with your advanced skills of communicating with other people , I guess they will finally shed some light on what's really going on .

VLC 3.0.12 patched

Well, @Jaguarek62 was right when presuming people here would be familiar with any of the standard messages from any module of an NT-Family OS, simply because it actually is a reusable template commonly seen, as @asdf2345 nicely explained. Bear with me, please, your going like ... ... with all due respect and wishing to cause no offense but just state a known fact, just shows how people from the younger generations are more sensitive than us old timers. While you're right about the rules and all, you're failing to factor in the different generational sensibilities (we have members ranging from tweeners to 80+ years old, here at MSFN) : *nobody* here wanted to disrespect you nor offend you, and your participation is quite welcome, but older people like me tend to be seen as rude by younger people, nowadays, when, in fact, we just mean to be straightforward.

An unknown ancient wiseman once told "First they will insult you and/or your language , then they will kill your dog , then {one could guess}" Most of you were so busy beating this poor new guy up {what is it , some sort of a tradition?} , but no one bothered to comment on the link he sent, regarding the error with that function. Search that page for "RtlUTF8ToUnicodeN" , without quotes.

Thank you! I finally managed to dualboot them. Man you saved me.. Thank you from the bottom of my heart. Could you also please lock the thread? since it may help someone too, but I don't need any more help.

It's not like they killed your dog or something, this is too much for a basic everyone knows the error message argument.

Its fine man , i dont believe anyone was in the wrong here.

I could confirm that PCSX2 v1.6.0 was working on my "vanilla" Windows Vista SP2 Business 6.0.6003 (mostly up-to-date to Dec 2020 patches except for IE updates cannot be installed for some weird reason and neither latest .net 4.6 patches which requires a "payment") x64 virtual machine. I just need some time to get that installed back to my virtual machine and try running some .iso games - I currently don't have time for it now.

Just reburbished 3 CRT televisions that may reflect the power requirements, load and capacitor quality of 1980-1990s vs 2000 era hardware. The older sets work like new and the capacitors appear immaculate. The newest set requires more warm-up time, sometimes has a fluctuating image and one of the primary capacitors was bulged and leaking. The oldest sets have the most runtime by far. 1987 92-Watt 21" Zenith (perfect) 2000 110-Watt 27" Sharp (perfect) 2007 180-Watt 27" Sony (capacitor issue) Aside from the above, a <10 year old LCD television was received as a giveaway a couple years ago. The set would sporadically turn itself off. After spending way too much time replacing capacitors, there was minimal improvement in runtime and the problem persisted. Finally gave up and sent it for recycling. Does this mean today's engineers can't design a decent capacitor? Of course not, it's probably the easiest component to manufacture that works well for about 12 months then starts to fail. https://en.wikipedia.org/wiki/Engineered_failure

Application should follow OS setting for displaying date and time, especially if it doesn't provide the ability to specify custom format.

The template is literally: "The procedure entry point (Function) could not be located in the dynamic link library (dll)." For that one screenshot, it'd be: "The procedure entry point RtlUTF8ToUnicodeN could be not be located in the dynamic link library ntdll.dll."

Found this with dell Inspiron but may work to find the wifi. If you go to your computers wifi driver on dells official site, then figure out it is say "Intel Centrino 1050-n" or something. Then search intel centrino 1050-n but with softpedia at the end, then on softpedia there sometimes is an various drop-downs for all the OS the driver equivalent is made for. See if XP x64 is on the list. Used to have a latitude good luck! -TheSaga

? I'm typing in english. And my guess anyone dealing with extended kernel is familiar with this error message. If it was important, I would translate that.

New build of BOC/UXP for XP! Test binary: MailNews Win32 https://o.rthost.win/boc-uxp/mailnews.win32-20201212-355db4de-uxp-4281fcc16-xpmod.7z BNavigator Win32 https://o.rthost.win/boc-uxp/bnavigator.win32-20201212-355db4de-uxp-4281fcc16-xpmod.7z source repo (excluding UXP): https://github.com/roytam1/boc-uxp/tree/custom-older * Notice: the profile prefix (i.e. parent folder names) are also changed since 2020-08-15 build, you may rename their names before using new binaries when updating from builds before 2020-08-15. -- New build of HBL-UXP for XP! Test binary: IceDove-UXP(mail) https://o.rthost.win/hbl-uxp/icedove.win32-20201212-id-eed0566-uxp-4281fcc16-xpmod.7z IceApe-UXP(suite) https://o.rthost.win/hbl-uxp/iceape.win32-20201212-id-eed0566-ia-41157bf-uxp-4281fcc16-xpmod.7z source repo (excluding UXP): https://github.com/roytam1/icedove-uxp/tree/winbuild https://github.com/roytam1/iceape-uxp/tree/winbuild for UXP changes please see above.

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.7.win32-git-20201212-6d0527a-uxp-4281fcc16-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.7.win64-git-20201212-6d0527a-uxp-4281fcc16-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom IA32 Win32 https://o.rthost.win/basilisk/basilisk52-g4.7.win32-git-20201212-6d0527a-uxp-4281fcc16-xpmod-ia32.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/ia32 NM28XP build: Win32 https://o.rthost.win/palemoon/palemoon-28.10.2a1.win32-git-20201212-31167a236-uxp-4281fcc16-xpmod.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.2a1.win64-git-20201212-31167a236-uxp-4281fcc16-xpmod.7z Official UXP changes since my last build: - Issue #1694 - Part 1: Use scriptabledateformat for the Cookie Accept dialog. (16a1ff22a) - Issue #1694 - Part 2: Use scriptabledateformat for Update History display. (6cb00e2cf) - Issue #1695 - Fix socket timeout logic. (6b45065f1) - Revert "Issue #1391 - Disable DOM Filesystem/dirpicker APIs by default." (4281fcc16) Official Basilisk changes since my last build: - Issue #31 - Part 1: Use nsIScriptableDateFormat in Page Info. (c7a029f) - Issue #31 - Part 2: Use nsIScriptableDateFormat in feeds. (8a74eeb) - Issue #31 - Part 3: Use nsIScriptableDateFormat in places library window. (5f97253) - Issue #31 - Part 4: Use nsIScriptableDateFormat in cookie preferences. (01c2847) - Issue #31 - Part 5: Update back-end branch pointer for toolkit changes. (6d0527a) Official Pale-Moon changes since my last build: - Back-end branch pointer update (unstable 2020-12-06) (31167a236) My changes since my last build: - Reverted Issue UXP#1694 and Basilisk#31 related changes

Good day, I have good news - I was able to get the broadcast on Twitch and the video on Twitter to work on latest versions of Firefox or Pale Moon! Before running the latest browsers, you need to install the extended kernel from @win32 As we know, initially on newer versions of Firefox and Pale Moon, some built-in codecs in Windows Vista do not work, since the Firefox development team simply removed some of the Windows Vista codecs part of the code from the browser. As a result, some sites (including Twitch, Twitter) stopped displaying videos. To fix this, download this archive and extract it to your Firefox or Pale Moon root folder. It simply replaces two files, thanks to which videos or broadcasts will work on those sites on which it did not work.