modnar

This site, while it is "heavy", works fine in latest Serpent 52.9 here (asked me about cookies and all).

vkvideo.ru sure is a heavy site, eats 1.3GB of RAM and videos (or rather pictures of them) are really stretched (magnified)... (Serpent 52.9, latest)

After trying out different configurations, I've seen that it's better to add (LoadOrder)Group of File System and Tag=14 to the SBieDrv instead of trying to delay loading of SBieSvc. On multicore systems with many partitions and many services there can occur that the system is too busy to properly load SBieDrv because of it not having "Group" or "Tag" and XP is known to need more strictly defined services. This is of course with FSFilter Infrastructure group at 03 (as is in Server 2003), which unlocks first three places to any FSFilter and doesn't make the system hitch and stutter anymore. I hope this is the final update. GOL_FSFilter_Infrastructure_03_XP_USP4.reg SBieDrv_Group_File_System_Tag_14.reg

It used to be (intentionally) broken to burden (very high CPU usage) the csrss.exe service (as seen in Task Mgr). I've installed Avast (from v18 online installer) in my testing XP_VM and will tell you tomorrow. Today everything was calm. Avast and AVG in their new, broken, state begin to burden the system through csrss.exe the next day... EDIT: The results are in and nothing changed: AvastSvc.exe constantly eats up ~25% of (dual-core configured) CPU in VM and csrss.exe eats up the other 20% of (dual-core configured) CPU. So both take up almost 1 whole core! That is outrageous, but Avast got our data, they don't care.

Thank you! Mighty fine! When it worked, this Serpent really ate less RAM than any version to date.

Quite. See here - a newly opened Serpent 52.9 2026.01.16 (latest): only went to majorgeeks.com and then to msfn.org Forum and basilisk.exe in TaskManager is wildly going up and down 1 full CPU core usage and memory from 700MB to 1.5GB and back down to ~700 then CPU usage stops. First I noticed that also in my XP VM which I use to get me fresh prefs.js to compare with my normal one outside VM (all of 1.3GB of dedicated VM RAM went missing while on sapphiretech.com). Edit: in the before session imgur.com, there weren't any swings, just normal behaviour; RAM usage going up till ~1.2GB (even somewhat lower than with the previous version of 1.3GB). Edit2: Could it have something to do with: - htmlparser: break when infinite loop happens (8201dadf41) ? Edit3: On videocardz.com and again on msfn.org (new session after videocardz crash) Serpent crashed with stated mozjs.dll as the point of breaking. Faulting application basilisk.exe, version 4.8.7.8956, faulting module mozjs.dll, version 0.0.0.0, fault address 0x00293c73. Both times. Edit4: Again on videocardz.com, now with different reason - xul.dll and then again on msfn Forum the upper mentioned mozjs.dll. Faulting application basilisk.exe, version 4.8.7.8956, faulting module xul.dll, version 4.8.7.8956, fault address 0x00063a79.

I use Panda 22.03.01 and on a dual or quad core systems PSANHost upon boot up doesn't really waste any cycles, only swells to ~100MB and then goes down to ~15MB from what I observed in TaskManager. It's been a wonderful replacement for Avast and/or AVG and their treachery of the XP systems after all this data we've shared with them throughout the years.

I have written it thusly with intent of being a carefully deliberated workaround instead of just a quick fix. And who will find it, will do the effort of going through the four points of implementing it. Besides, points 1.) and 2.) are pre-conditions for even going through with the change. If it has a "Tag" of "4" (unsafe remnant from XPSP2, thanks so much M$, not) abort or change manually even that. Filesystem part should be as mentioned if nothing was added by user.

The WorkAround for WinXP SP3 fltMgr (build 5512) with Tag=1 for now is (obeying "Tag" rules and similar to other Windows' configurations): 1.) Go into regedit (Run: regedit), HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/FltMgr, make sure that it has "Tag" [DWORD] value of "1" (0x00000001). 2.) Go into HKEY_LOCAL_MACHINE/System/CurrentControlSet/Control/Filesystem and make sure only these three settings are in there (factory XP_SP3 settings): NtfsDisable8dot3NameCreation [DWORD] 0x00000000 (0) Win31FileSystem [DWORD] 0x00000000 (0) Win95TruncatedExtensions [DWORD] 0x00000001 (1) 2. B) Go into HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/disk and make sure it has TimeOutValue [DWORD] 0x0000003c (60) . 3.) If fltMgr service has Tag=1, you can then go to HKEY_LOCAL_MACHINE/System/CurrentControlSet/Control/GroupOrderList/FSFilter Infrastructure and edit it so it reads: 03 00 00 00 01 00 00 00 02 00 00 00 03 00 00 00 . 4.) Restart and enjoy extra responsiveness without any ill-effects. Oh, by the way, @MilkChan you packed the wrong fltMgr in the KB44xxxxxx package, the beta build instead of 6912.

What if you tried updating it with the Simplix Update pack for "Windows 7" (up-to-date with telemetry disabled)? Regarding RAM: X86 version of Windows cannot use the additional RAM.

I have msvcr100.dll v. 10.0.40219.473 in XP. I use abbodi1406's CPPredist AIO x86 v35 (XP_last).

I'm sorry, somehow I thought I'd just normally decompress them instead of installing them. :-) Since MilkChan has built those fine update packages, I'd say SSE (b5107) for slower computers and SSE2 (b6912) for faster. Could you please test both and see which is faster. I think b5107 might be faster (it is also the last build in non-ESU fully updated Server 2003 x86).

Thank you, @MilkChan for these two builds. 7-zip and WinZip here says the second, SSE2 update is corrupt - would you mind updating the archive, please? Thank you, @Multibooter for testing. The funniest thing now is upon re-configuration of my mini-filters, my system works better than ever before with the 5512 XPSP3 fltmgr and filter cascade. I also put TimeOutValue = 3c (60) (s) DWORD before minifilter re-config in my "disk" service (CurrControlSet) that for some reason did not exist in my harkaz-updated SP2 (to uSP4) XP. That might have had the most to do with it...

Exactly! I'm glad you noticed the difference! That is how much filter manager is important for the system (it's a tree that all mini-filters are branches of) and bloody Microsoft scum put such pile of horse manure into WindowsXP_SP3!!! Outrageous! I'm superglad it works out for you. I'm glad it works well for you too! It's such an important part of the system and really can make a difference. I just don't know how on my multi core and multi partition and multi disk system it can't work right... Sigh.