Jump to content

modnar

Member
  • Posts

    77
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Slovenia

1 Follower

About modnar

Profile Information

  • OS
    XP Pro x86

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

modnar's Achievements

45

Reputation

  1. Hi! mega.nz works here too, Serpent x86 2024-02-23 (latest). Perhaps there's something wrong with your ST profile?
  2. Quite an update: XP fltmgr (5.1.2600) replaced (on real computer) with 2003 version from SP2 (R2) (5.2.3790.3959) and then updated (only fltmgr file) to version 5.2.3790.5107 (from KB2839229) - all works well, no service is "unstoppable" anymore, diskeeper is at 137100 (native) only aswSnx is in "Open File" group becuase "Virtualization" doesn't exist for XP/2k3 fltmgr and it has to be in its own group (not together with aswSP). Smooth sailing.
  3. Mighty fine! Thank you @ED_Sln, @MilkChan. I'll test the updated versions, I hope they do not require some additional kernel functions that WinXP_SP3 (SP4_Harkaz) doesn't have. I use Harkaz's USP4 for all my XP installs now. What I can say thus far is that the 5.2.3790.3959 works very well with XPSP3 (for now tested in VM) system boots quite a bit faster (with AttachWhenLoaded = 1, it is so in Win7 too). This shows how much this driver is important for good operation of the OS: hard drive/file system is the slowest component and to have a driver as important as fltmgr to perform badly - it slows down the whole system considerably and can cause stutters at high disk loads. If we look at the .inf, XP uses 2001-made fltmgr with its 2008_SP3 5.1.2600.5512 release, 2003 uses 2002-made driver in the form of 5.2.3790.3959 so it signifies a considerable upgrade to XP. Update: I have downloaded the XP and 2003 x86 version of the KB2839229 (you don't have to unpack it, just open it with 7zip and "View" _sfx_manifest_ file - will tell you the contents), @ED_Sln, and wouldn't you know it, the M$ b*stards included kernel updates to both systems, but fltmgr update to only Win2003. More and more are my suspicions confirmed: they wanted to kill XP because of its great popularity and they did so by making it hobble at the slowest computer subsystem - file storage. Quite telling. They shan't prevail, that's for sure! Update II: All the way - version 5.2.3790.5107 works just fine so far. Thank you again, @ED_Sln.
  4. Thank you! I will test it but I have checked that KB packet and looks like kernel files are also in there; might not work... Some people even had problems with KB3045999... I think I'll just stick with the one I got from my SP2 install. I believe it works properly, need to test it thoroughly.
  5. Does anyone here have a fully updated Win2k3 SP2 - I'm interested in fltmgr.dll version: is it different/higher than 5.2.3790.3959? Also - would anyone know: what does HKLM,"SYSTEM\CurrentControlSet\Services\FltMgr\","AttachWhenLoaded",0x10001,1 mean? Because WinXP SP3 has 0 at the end, so fltmgr doesn't attach when loaded - have to test it at 1. Thank you. Edit: I searched a bit and found a M$ article on the AttachWhenLoaded for fltmgr - it means that it attaches to all drives whether any filters are registered or not; if 0 - fltmgr only attaches when a mini-filter gets loaded... I'll do some testing with "1" and with server 2k3 SP2 files...
  6. Wow! That's quite something. The SP2 version does have superior fltmgr.dll (filter manager), but with less functions; are you using any updates (a pack?) for SP2 install? {OFFTOPIC just a wee bit}
  7. I tried it a while ago, but it was from vista, not 2k3 - I actually tested it today and it works on XP without a problem. As with 2k3 I also enabled AttachWhenLoaded for fltmgr service (in registry) as it is on Win2k3 and now I have to do extensive testing to see if it's safe for data and stable in all circumstances. Should be... It looks mighty promising. E.g.: DKService ("12") can easily be stopped with its DKRtWrt filter at its native altitude of 137100. Wow wow wow, just wow. That means no more artificial hitching on XP just because a program uses low altitude filters like antiviruses with virtualization like to do. I'm just 10+ years too late... Oh well better now than never. Long live XP, yet!
  8. Thank you. I should look around the Forum more. I have usually downloaded pdfs before opening, so I use in-browser viewer if that is not an option.
  9. Thank you - might just be my dirty profile, that I carried over from my fireferret 52.9 installation (I cleand up some settings from it comparing with the clean ST profile). Savefrom usually worked... Just a heads-up: I use SumatraPDF (v3.1.2 XP-last) on my systems sometimes with built in ST viewer.
  10. Interesting - looks like saving videos from with savefrom.net site crashes Serpent 52.9 (latest: 24-02-23) right after clicking a prepared link of the video. xul.dll is mentioned... :-(
  11. By the way - today (sunday) I just saw this piece of news....don't people have anything to do these days?
  12. Update: Yesterday I reinstalled Avast and today I have removed both FSFilter Virtualization and Imaging from the above mentioned places in Current Control Set. Filter manager in XP is so old it simply doesn't recognize these two groups and filter communication suffers (as seen in DK12's time to prevent fragmentation using Intelliwrite and Instant defrag and general web browsing). AswSP service is left as factory FSFilter Security Enhancer and I set aswSnx (virtualization service) to FSFilter Security Enhancer (XP's native group). First impressions are good, web browsing is smoother than before, we'll see. DKService can be stopped normally (and restarted) but DK12 uninstall requires aswSP (self-defense) to be disabled due to group-altitude "stretching" of the above services, so DKTLFSMF filter can be stopped normally. Update: It's better to just set aswSP and aswSnx as FSFilter Activity Monitor, with also changing aswSnx altitude to 366996 for smoother system operation and no lying to the touchy-feely fltmgr.
  13. If I may chime in - basilisk-dev: while that may be true, we never experienced major problems with roytam1's releases and even if we did have some crashes, they were resolved rather quickly and painlessly. All I can say is that we can be thankful for your and roy's efforts and we should work together to push development of better classic browser forward, even for us that are cemented in the "old" system which may be unpopular, but it sure is fun to have it as daily driver even now, when all the world is crazy for excessive data sharing and automatic idiots.
  14. Thank you for the new builds, Roy. They are really swell.
  15. I started with this research rather late - in 2023, original problem has been introduced with XP_SP3 release, so in 2008 - quite nasty really: I have experimented with Diskeeper (2010, 2011, 12) and Avast filters in XP_SP3, because the way at least Avast (its filter drivers) is set up does slow down the system (its aswSP is at altitude 388401 but group is set as FSFilter Security enhancer, which is at much lower altitude range). With any program that "lies" thusly to XP_SP3 the computer gets bogged down for a nit-picking reason (IMO). I have found out that just for the XP_SP3 M$ really messed up fltMgr driver to require a mini-filter to really obey it's "Group"'s altitude range, which is quite a bit different than in XP_SP2 or Vista and newer Windows. Therefore I would like to know if there is a newer fltMgr.sys driver (or a modification) that allows "normal" (not so restrictive) mini-filter behaviour (basically altitude freedom) for XP_SP3? Example: DKRtWrt mini-filter is usually at 137100 (its native altitude as per M$'s own list) in XP_SP2 even though it's "Group" is "Activity Monitor", but can't be in XP_SP3 and its restrictive fltmgr - it's unstoppable (manually) then. Current version is 5.1.2600.5512. I tried transplanting it with Vista's (doesn't work) and XP_SP2 (works but lacks certain functionality for Avast to work properly). A working, perhaps temporary, solution by me was to re-classify aswSP as FSFilter Activity monitor (as was in old Avast 11 AV), add missing filter groups of virtualization and imaging to xp's GroupOrderList and ServiceOrderGroup/List (registry CurrCtrlSet) now all works well, however the nagging question remains - why should XP_SP3 be an exception - is it to further disable it in light of higher versions of the OS? I sure think so.
×
×
  • Create New...