All Activity

According to the documentation the "Length"-field and the "MaximumLength"-field are values in bytes. This explains why the maximum path length with the "\\?\"-trick is a little bit over 32,000 characters (which is about 64 KB). That should be good enough or at least it's much better than 260 characters.

They can also be extracted without third party tools: open a command prompt (cmd.exe) drag and drop the kb...exe into the command prompt window add " -x" or " -c" (c with old updates, x with new updates) to add the command line parameter hit [enter]

I want to use Windows XP in 486 as WinPE bootable rescue shell. Here is command line from WinPE constructor ( xpsp3_opk_en original, cannot post it here, paths can be different ): Z:\OPK\mkimg.cmd Z:\DIST Z:\OUT winpe486.iso /NOWF Created image cycled reboots. Even on Pentium and later CPU. Please help.

That's one thing I never liked about XP's default setup. Something like "C:\Documents and Settings\YourName\My Documents" might not seem like much at first, but those 47 characters is using up 18% of your allotted 256. The thing that always annoyed me is that Windows would run everything just fine, even if you exceed 256, *UNTIL* you go to copy/archive the files and only then does Windows throws up a name-too-long error. Even though it's been using those names as-is without any issues.

Microsoft Visual C++ v14 Redistributable removed support for Visual Studio 2015. Besides, it seems that v14 Redistributable also dropped support for Windows 7.

programming-wise normal strings get translated to the unicode string (windows do so internal with its deeper function) https://learn.microsoft.com/en-us/windows/win32/api/ntdef/ns-ntdef-_unicode_string theoretical these can have a bigger value of 260 - max_path has not 256 for a reason of terminating 0´s an example would be CreateFileA/W this one gets translated to ZwCreateFile(NtCreateFile) to create this unicode string there is : RtlInitUnicodeString( &fileNameUnicodeString, L"\\Device\\Harddisk0"); and then: InitializeObjectAttributes( &objectAttributes, &fileNameUnicodeString, OBJ_CASE_INSENSITIVE, NULL, NULL ); then it looks something like: ZwCreateFile( &hFileHandle, SYNCHRONIZE|FILE_ANY_ACCESS, &objectAttributes, &IoStatus, NULL, 0, FILE_SHARE_READ|FILE_SHARE_WRITE, FILE_OPEN, FILE_NON_DIRECTORY_FILE, NULL, 0); explaining that unicode-string: typedef struct _UNICODE_STRING { USHORT Length; USHORT MaximumLength; PWSTR Buffer; } UNICODE_STRING, *PUNICODE_STRING; this one got a buffer and a Length and MaximumLength - ushort is 65535 in size but that are theorecial numbers it raise questions to make so many folders so they extend the length of 256 signs

The restriction you addressed in the FAT32 file system and the NTFS file system is probably the most difficult part to solve. Since these 2 file systems allow no object names (folder names or file names) longer than 256 characters, it will be a problem storing longer names if the file system driver prevents it. Your suggested solution to shorten long object names leads to truncated names and looses the uniqueness of the names. Once a name is shortened the truncated part is lost and we might have 2 folders or 2 files with the same name. --- There is an easier part where at least some progress can be achieved: Some of the functions restrict the caller to max_path for the total path name (not the object name), even though there doesn't seem to be a good reason. So it might be the case, that these restrictions can be lifted. However, some functions return a path and the caller might provide a buffer, that can take no more than max_path characters. These functions are more problematic, because we don't want to create buffer overruns. Here is the list of functions, which don't return paths: CopyFile2 CopyFileExW CopyFileW CreateDirectoryExW CreateDirectoryW CreateFile2 CreateFileExW CreateFileW CreateHardLinkW CreateSymbolicLinkW DeleteFileW GetCompressedFileSizeW GetFileAttributesExW GetFileAttributesW GetFullPathNameW GetLongPathNameW MoveFileExW MoveFileW MoveFileWithProgressW RemoveDirectoryW ReplaceFileW SetCurrentDirectoryW SetFileAttributesW Here is the list of functions, which return paths: FindFirstFileExW FindFirstFileNameW FindFirstFileW FindFirstStreamW FindNextFileNameW FindNextFileW FindNextStreamW GetCurrentDirectoryW GetFinalPathNameByHandleW SearchPathW --- Well, if you are talking about KernelEx for Windows 98 and Windows Millenium, we might also consider looking into the slim-character versions of the functions (for example RemoveDirectoryA) and not just the wide-character versions (for example RemoveDirectoryW). I don't know a good reason, why long paths should be limited to a specific character set used.

if you want to give a installer to us you can make it by using this project file installer.zip you know about the kb-upgrades ? they are compressed like a zip file (Intrapackage Delta compression or IPD) - the most common unzip files like winzip, winrar, 7z can unpack this format inside is useally a .inf file and that .inf file contains both the registry and the file entrys typically they are easy to find because they useally come over this 2 entrys: CopyFiles = filesnumber1 AddReg = regnumber1 then somewhere is a string called filesnumber1 and there are the entrys the same goes for regnumber1 so the common idea is to read out that information (what is stored in that .inf file) and combine more kb-upgrades in 1 upgrade - a problem with that is that this .inf engine is like a script its not very fast - so its not very good for many entry´s so i came up with a own installer that can do the same thing (but many times faster, having full control of the code, dont need other things to be installed first) so if you want to make us a file that install that fltmgr.sys you can make it with this project file - might be something for you

New build of post-deprecated Serpent/moebius for XP! * Notice: This repo will not be built on regular schedule, and changes are experimental as usual. ** Current moebius patch level should be on par with 52.9, but some security patches can not be applied/ported due to source milestone differences between versions. Test binary: Win32 https://o.rthost.win/basilisk/basilisk55-win32-git-20251220-81840e9b0-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk55-win64-git-20251220-81840e9b0-xpmod.7z repo: https://github.com/roytam1/basilisk55 Repo changes: - import from UXP: Issue #2873 - Don't let toolkit override colors of autofilled form elements. (17d95132) (41862e21c) - ported from UXP: Issue #2861 - Part 1: Allow nsNPAPIPlugin::RunPluginOOP to be made false. (d2ab9697) (f4c8acc40) - import from UXP: Issue #2861 - Part 2: Restore nsIPluginHost.isPluginOOP. (69ebe832) (b1ed368ee) - import from UXP: Issue #2861 - Remove checks that forcibly enable or disable OOP. (e6d9cc01) (9e977be49) - import from UXP: Issue #2875 - Cleanup: Remove leading whitespace in nsPluginHost.cpp. (372df4eb) (0dd28cf96) - import from UXP: Issue #2861 - Remove Mac-specific ifdefs. (108523f5) (be5c04d98) - import from UXP: Issue #2875 - Ensure OOP for plugins by default even if pref couldn't be found. (cdab710e) (f5d6b5e44) - import from UXP: Issue #2861 - Bring back forced OOPP for GTK3. (dd61d079) (5e872b560) - import from UXP: Issue #2861 - Part 2 Follow-up: nsIPluginHost.isPluginOOP should not always return true. (668296cf) (06ce41698) - import from UXP: [devtools] Further improve "Copy as cURL" (b3c406bb) (7059944d3) - import from UXP: [js] Append InstSize factor for secondary range veneers. (81bcafc3) (1f1743630) - import from UXP: [DOM] Add stride check for canvas tex conversion from blob. (95e0feec) (f3ff4fb05) - import from UXP: [devtools] Further improve "Copy as cURL" (68fa0f0d) (54292a252) - import from UXP: [image] Use the TriggeringPrincipal if we have one, not the SystemPrincipal (4667b7f4) (2eae097a1) - import from UXP: [NSS] Destroy certificate on error paths (01d89493) (b39f71e0f) - ported from UXP: Issue Pale-Moon#2002 - Remove FreeBSD compat13x dependency on 15.x. Remove the 2 libutil OS_LIBS and dynamically load libutil.so instead. (2a2a85f8) (46bae686f) - import from UXP: Issue #2865 - Implement `URL.canParse()` (12e5c5c3) (81840e9b0)

New build of BOC/UXP for XP! Test binary: MailNews Win32 https://o.rthost.win/boc-uxp/mailnews.win32-20251220-40a79c75-uxp-b9f12b43c6-xpmod.7z BNavigator Win32 https://o.rthost.win/boc-uxp/bnavigator.win32-20251220-40a79c75-uxp-b9f12b43c6-xpmod.7z source repo (excluding UXP): https://github.com/roytam1/boc-uxp/tree/custom * 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-20251220-id-656ea98-uxp-b9f12b43c6-xpmod.7z IceApe-UXP(suite) https://o.rthost.win/hbl-uxp/iceape.win32-20251220-id-656ea98-ia-c642e3c-uxp-b9f12b43c6-xpmod.7z source repo (excluding UXP): https://github.com/roytam1/icedove-uxp/tree/winbuild https://github.com/roytam1/iceape-uxp/tree/winbuild

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20251220-3219d2d-uxp-b9f12b43c6-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20251220-3219d2d-uxp-b9f12b43c6-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.8.win32-git-20251220-3219d2d-uxp-b9f12b43c6-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.7a1.win32-git-20251220-d849524bd-uxp-b9f12b43c6-xpmod.7z Win32 IA32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20251220-d849524bd-uxp-b9f12b43c6-xpmod-ia32.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20251220-d849524bd-uxp-b9f12b43c6-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20251220-d849524bd-uxp-b9f12b43c6-xpmod.7z Win7+ x64 AVX2 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20251220-d849524bd-uxp-b9f12b43c6-w7plus-avx2.7z Official UXP changes picked since my last build: - Issue #2873 - Don't let toolkit override colors of autofilled form elements. (17d951328f) - Issue #2861 - Part 1: Allow nsNPAPIPlugin::RunPluginOOP to be made false. (d2ab969724) - Issue #2861 - Part 2: Restore nsIPluginHost.isPluginOOP. (69ebe8322d) - Issue #2861 - Remove checks that forcibly enable or disable OOP. (e6d9cc0146) - Issue #2875 - Cleanup: Remove leading whitespace in nsPluginHost.cpp. (372df4ebe7) - Issue #2861 - Remove Mac-specific ifdefs. (108523f5fd) - Issue #2875 - Ensure OOP for plugins by default even if pref couldn't be found. (cdab710ed0) - Issue #2861 - Bring back forced OOPP for GTK3. (dd61d079b0) - Issue #2861 - Part 2 Follow-up: nsIPluginHost.isPluginOOP should not always return true. (668296cf5d) - [devtools] Further improve "Copy as cURL" (b3c406bb25) - [js] Append InstSize factor for secondary range veneers. (81bcafc331) - [DOM] Add stride check for canvas tex conversion from blob. (95e0feec7c) - [devtools] Further improve "Copy as cURL" (68fa0f0d54) - [image] Use the TriggeringPrincipal if we have one, not the SystemPrincipal (4667b7f4b0) - [NSS] Destroy certificate on error paths (01d894938b) - Issue Pale-Moon#2002 - Remove FreeBSD compat13x dependency on 15.x. Remove the 2 libutil OS_LIBS and dynamically load libutil.so instead. (2a2a85f888) - Issue #2865 - Implement `URL.canParse()` (12e5c5c303) Official Pale-Moon changes picked since my last build: - [Pale-Moon] Issue #1979 - Use async callback to update cache UI (7e23650580) - [Pale-Moon] Issue #1914 - Update several SSUAOs (da35b48afd) - [Pale-Moon] Un-prefix -moz-user-select (06890bcb06) - [Pale-Moon] Remove Instagram SSUAO (4265868605) - [Pale-Moon] Issue #1987 - Use `overflow: clip` (88f220896b) - [Pale-Moon] Issue #1954 - Reset `userTypedValue` if fragment navigating within a doc. (c167bc756f) - [Pale-Moon] Issue #1991 - Add UI preference for reduced visual motion. (58648a77ad) - [Pale-Moon] Update Windows version check caller after WindowsVersion.h updates. (f0d40ae44b) - [Pale-Moon] Issue #1992 - Part 1: Update AppMenu icons (6933910ed5) - [Pale-Moon] Issue #1992 - Part 2: Tweak Windows 10+ styling. (02fac4d52e) - [Pale-Moon] Issue #1992 - Part 3: Remove italic style from AppMenu edit label. (f61835829a) - [Pale-Moon] Issue #1992 - Part 4: Fix issues with the main toolbar. (5f2bc6123b) - [Pale-Moon] Issue #1992 - Part 5: Slightly more breathing room for the window title. (1843e173cf) - [Pale-Moon] Issue #1992 - Part 6: Overhaul caption buttons and add win 11 specifics. (ca7e904b27) - [Pale-Moon] Issue #1992 - Part 7: Remove glass override for Win 10/11. (4af2abb312) - [Pale-Moon] Issue #1992 - Part 8: Minor tweaks and update downloads button styling. (4e3531ed96) - [Pale-Moon] No Issue - http -> https for start.palemoon.org default. (cdd4d99499) - [Pale-Moon] Issue #1992 - Correct default non-compositing color on Win 11 to RGB 243. (549e05be0c) - [Pale-Moon] Add Win11 styling in browser-title.css (442965e997) - [Pale-Moon] Add id to viewToolbarsMenu's menupopup (c955ee0ac4) No official Basilisk changes picked since my last build. My changes picked since my last build: - [Pale-Moon] partly revert rev f0d40ae4 to fix build (b9f12b43c6) Update Notice: - You may delete file named icudt*.dat inside program folder when updating from old releases. * Notice: From now on, UXP rev will point to `custom` branch of my UXP repo instead of MCP UXP repo, while "official UXP changes" shows only `tracking` branch changes.

Ran into a small problem after downloading your 'offline installer' download. I got offline to run the download and found out that I need to have .NET Framework also installed. I did have .NET Framework 2.0 installed years ago but removed it. Didn't seem to have much use for it on Win XP at the time. If there were any programs that might require it I was always able to find another program that didn't need .NET Framework to run. I have all the .NET Framework versions that worked on XP stored on a DVD backup with other old Win XP programs ... in case needed one day. I think at the time .NET Framework 3.5 was the last version to work on XP but after getting back online to search around I now see that there is a .NET Framework 4.0 that will install on Win XP SP3. I have now downloaded that version but I may just try .NET Framework 2.0 first out of curiosity and see if that works. If not then I can jump to version 4.0. That version from MS is dated from last year: 07/15/2024 ... I will put the MS link here in case someone else has need for it. Microsoft .NET Framework 4 (Standalone Installer) https://www.microsoft.com/en-us/download/details.aspx?id=17718 Date Published: 07/15/2024 Supported Operating Systems: Windows 7, Windows 7 SP 1, Windows Vista SP 1, Windows XP SP 3 Windows XP SP3 Windows Vista SP1 or later Windows 7 Windows 7 SP1 Supported Architectures: x86 x64 Thanks ...

Thanks for this tip! Finally, a working login form appears. Unfortunately, a login into a personal Outlook email account is not possible. Only for school or work accounts. Thank you, Microsoft!

I can't find much information on KB2839299. Do you have a little bit extra on what was changed in fltmgr.sys?

You can try it if you are frustrated with XP fltmgr that bogs down internet browsing with many mini-filters installed. In KB2839229 for WinXP there are just kernel files, in KB2839229 for Win2003 there is also a fltmgr.sys, which is updated version build5107, from before build3959. You can replace WinXP_SP3 build 5512 with this one, but ONLY fltmgr.sys (overwrite) and you preserve fltmgr service settings XP-factory. Works well so far, without hitches. I used Hiren's Boot CD to perform replacement in my XP_uSP4 (in my installation locations are: Windows/system32/drivers, Windows/ServicePackFiles/i386 and Windows/system32/dllcache).

I was able to login in with OAth2 using MailNews with an outlook account. I had to go in the config editor and set *general.useragent.compatMode.firefox* to true. Then the Microsoft login page displayed properly and worked. Hope it helps some folks, I am using windows server 2003

I was having many problems with Mypal68 74.1.2 shutting down on many websites ... after updating to Mypal68 74.1.3 in early December, all those problems have gone away. Mypal68 74.1.3 is very stable for my WinXP system with only a 'very rare' shutdown. I also use New Moon but it has problems with some websites. Mypal68 74.1.3 has now become my main WinXP daily browser. Thanks for your work and this newer update. ...

AstroSkipper ... Just came across you're updated information dealing with Windows XP and Panda Free Antivirus. Around two weeks ago I was actually looking for any antivirus programs still working with WinXP in 2025. Didn't find any after doing a quick search on some programs that worked many years ago and reading your earlier post on the subject. Thanks again for the update on this valuable information for Windows XP users. ...

For FAT and NTFS drives, API wrappers could walk the path string and shorten each long folder or file name as needed. Network shares to other file systems could be a problem. Temporary environment variables and drive mappings might also be possible. I've considered these possibilities for KernelEx should the need arise, but haven't done any tests. For years I have been successfully using a function I wrote to walk a path string and lengthen each short folder or file name. Doing the opposite should be easy.

Just visited the RetroZilla GitHub repository and was pleasantly surprised to find that rn10950 published a new official 2.3 release in June incorporating roytam1's TLS 1.3 updates and other pull requests and improvements. https://github.com/rn10950/RetroZilla/releases

There are now (at the end of 2025) very, very few anti-malware programmes for Windows XP with real-time protection free of charge. Panda Free Antivirus is an absolute exception. It is still maintained and runs under Windows XP. Here are two screenshots of the current version 22.03.05, which has just been released: An anti-malware programme with a most recent scan engine and up-to-date virus definitions even under very old OSes like Windows XP or Windows Vista. What more could be wanted? Here is the link to my updated article: Cheers, AstroSkipper

This thread is about anti-malware programmes under Windows XP. BTW, there is definitely no need to use an "ancient version of whatever" under Windows 10. And talking about your "ancient version" is like "beating a dead horse". A version of this programme running under Windows XP has not been available for a long time. And it gets even worse: the programme is not secure, and its country of origin is beyond good and evil. In my next article, I will post something current for Windows XP.

I'm also using Windows 7 on both my ThinkCentre m58p and ThinkPad T60. I also run Windows 2000 and Windows XP Pro x64, but it's mostly Windows 7 that does the work. I do not and have never had anything newer in my network and the only "upgrade" is going to be Q4OS, but that won't be happening until these OSes are going to be completely unusable and even then I still will be looking for solution to getting the much needed programs running,..

Personally, I don't expect modern websites that are full of multimedia or completely overloaded to still run in UXP browsers under old OSes like Windows XP, but I am happy about those that still do. All others are called up by me under Android 10 and above. That's why I'm extremely relaxed about the whole thing. The more websites running in New Moon or Serpent, the better, but if not, then that's just the way it is.

Agreed! I shouldn't have tied to CPU but rather tied to GPU. My bottom-line remains the same, same EXACT browser profile, both Serpent 52 and Chrome 140) *DOES* work on my "i7+gpu hardware" but does *NOT* work on my "core2+gpu" hardware. I won't really be digging in deeper here either. My *LIMITED* tests *reveal* (at least between two of my computers) that this is clearly HARDWARE-RELATED (and perhaps even with about:config "flags" as a WORKAROUND for said hardware). And we would need details on the Original Poster's HARDWARE to go any further.