Jump to content

modnar

Member
 View Profile  See their activity

  • Posts

    176

  • Joined

  • Last visited

  • Donations

    0.00 USD 

  • Country

    Slovenia

 Content Type 

Everything posted by modnar

  1. modnar
    Interesting. Could this be malware or fragmentation problem? Long ago when I had Diskeeper 10 (not 2010) on and every option turned off (it was inactive) when I opened firefox and browsed around the Windows just crashed/restarted from heavy fragmentation. Then I finally installed DK2011 (in 2013) and never again any problems.
  2. modnar
    It's not crap at all with h264ify. Windows is usually crap (but with potential). Now I'm interested what was written in that blue screen (you probably have auto-restart @bluescreen ON)?
  3. modnar
    Not here - in Serpent 52.9 22-9-2024 it's not working (buffering but not garbled picture anymore), but that's alright, h264ify makes 1080p videos work flawlessly.
  4. modnar
    @roytam1 please, would you fix Mail clients links.
  5. modnar
    Instead of using plain XP_SP3 you could install XP_SP3 and then Harkaz' fine Unofficial Service pack 4 - it contains .NET things, but there is a procedure to follow. VisualC redist you can use from Abbodi from mydigitallife. Maybe such a system would be more workable...
  6. modnar
    Just a heads up - to watch videos on Youtube normally @1080P (with RT's Serpent 52.9) you may need to download the h264-ify firefox extension. Latest (v1.1) works well in Serpent.
  7. modnar
    It is instantaneous here either way (Serpent 52.9 on good ol' XPSP3 (USP4_Harkaz)).
  8. modnar
    @Multibooter you should know that these fixes only get applied when you write/import them into registry and then restart Windows (these are really low level/near hardware system settings). There is strong possibility the settings weren't even applied (applying them in a Sandbox - you can't restart such a system...). NtfsDisableLastAccessUpdate_1 is not really appropriate for Windows XP - it causes more fragmentation of normal files (and I've used this tweak the longest time). To remove it from your system delete it from (Registry) HKeyLocalMachine/System/CurrentControlSet/Control/Filesystem so there are only 3 factory entries: NtfsDisable8dot3NameCreation (0), Win31FileSystem (0), Win95TruncatedExtensions (1) and reboot. If you have Diskeeper, lack of NtfsDisableLastAccessUpdate is not felt (speedwise) and Diskeeper protects the disk from unnecessary work. Edited GroupOrderList values have to be as long as the factory ones, that means 03 entries for SCSI_Class and 0b entries for Filter otherwise internet browser crashes sometimes (observed). They are posted in my previous post on page 2 of this topic. Nothing more to add - with factory XP filesystem settings, sbiedrv happily works without Load Order Group.
  9. modnar
    Primary disk is better left factory (05, as in newer Windows) - nothing problematic, just overall behaviour. GroupOrderList_Primary_Disk_05_XP_USP4.reg
  10. modnar
    The most important update for FltMgr (minifilter manager) that got updated with XP SP3 (from SP2 when it was introduced to Windows XP), this is the driver that all minifilters talk to in order to reach the system/kernel. Thing is that when introduced FltMgr (service) had a "Tag" of 4, however when XPSP3 was introduced they changed its "Tag" value to 1. The fine folks at M$ of course did not delete 04 00 00 00 from FSFilter_Infrastructure GroupOrderList entry so it would look as 03 00 00 00 01 00 00 00 02 00 00 00 03 00 00 00 (as all other unused minifilter entries or for use with Tag of 1). Turns out this "small" mistake was the reason for funky behaviour/disk traffic slowdowns that are especially felt when Diskeeper 12 (the best and the last version for XP) is used with WinXP (SP3). Not because DK12 is the problem but being that precise it pointed out that GroupOrderList was flawed. So here I am attaching the most important fix/.reg file for the whole minifilter mechanism that especially shows when you use 4k (modern) HDD's and SSD's with WindowsXP SP3. Consistent good results at long last. GroupOrderList_FSFilter_Infrastructure_03_XP_USP4.reg
  11. modnar
    An update regarding SCSI Class from GroupOrderList - turns out that the shorter version for this group can be added, works just fine (programs with minifilters, e.g. Diskeeper may need to be reinstalled after this change - I have observed Serpent 52.9 browser throwing errors of "mozjs.dll" on videocardz.com which is typical of filter traffic conflicts - after DK12 reinstall - not anymore). Update: Removed the file - shortened version is not good over all - in some situations it may cause slight $Secure:$SDS metadata fragmentation. It's either factory (03 01 02 03) or the long version all 45 entries (2d 01 02...2c 2d) but the long ver. is not necessary. While SbieDrv Group setting "File system" is mentioned in Sandboxie source it is not needed for normal XP filesystem (without edits of CCS/Control/FileSystem). File also deleted.
  12. modnar
    Just a quick comment on Kaspersky - never run 2 instances (same or different) of antivirus or firewall on one machine. Kaspersky AV is already bogging down the PC with so many mini-filter drivers it's running.
  13. modnar
    Yes, dmboot and i2omgmt services stay unchanged (as they come with WindowsXP installation). Interesting... I'm glad they observed the problem before me. It took me by myself some time to really discover what kept my system back so to speak and David enthusiastically replied to me: Thank you, I'm glad the whole thing is solved - by Tag's no less. In the beginning of this process I would had never admitted it's the Tag's. I was quite focused on service altitudes of minifilters, but they weren't it...
  14. modnar
    Great! That should do it. I always leave those low level system drivers with their factory tags as they are, hence the added entries in the GroupOrderList. The key issue has been remedied. Now driver/service tags match those in the Group(load)OrderList and the system should already be/feel more responsive. Another thing is to keep your disk defragmented/in order so there are no slowdowns with loading/saving files.
  15. modnar
    You're welcome! Now first the procedure how to check whether you need to correct any of the known-to-have-issues-groups: In registry editor you click on HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services and then press CTRL+F (Edit/Find...) and write into that window the name of wanted group, e.g. Filter; also tick "Match whole string only" so you don't get false results. Updated: Filter 0b is not necessary with factory filesystem (not disabling LastAccessUpdate or other similar useless stuff). Filter 06 is good and also a factory setting when installing XPSP3 anew with Unofficial SP4 from Harkaz. Besides - the system is faster this way. The other 2 files are Primary Disk and SCSI Class groups of which the last is either 03 (factory) or full up to 2d (with all 45 members /that don't exist/). Please, do check Tags before editing. GroupOrderList_Primary_Disk_05_XP_USP4.txt GroupOrderList_SCSI_Class_03_XP_USP4.txt GroupOrderList_Filter_06_XP_USP4.txt
  16. modnar
    My findings to add: By default Sandboxie driver (HKLM/Sys/CurrCtrlSet/Services/sbiedrv) registry entry is flawed from way back when v4.20 was released - instead of "DependsOnService" it should have "DependOnService" (FltMgr) - I have contacted David Xanatos about it and he acknowlegded my observation. The second thing was observed in installing XP with harkaz's USP4 - again in registry - Control/GroupOrderList: for "Filter" group tags should go up to "0b" and not only "06", so 07 00 00 00, 08..., 09..., 0a..., 0b... should be added to that group or Sandboxie (at least 5.22) complains it cannot hook in its driver at system boot (with other minifilters installed, such as diskeeper's or perfectdisk's). Tags (component load order monikers) are very important especially in older Windows systems - even if services containing them are not loaded. The other group lacking mention in GroupOrderList is SCSI Class - should go up to 2d 00 00 00 because there is one driver containing such a Tag. While it may seem superficial, when Tag-problems are corrected, the whole system is much more responsive and also faster to boot. This way Sandboxie functions very well in my install of XP_USP4 with Avast, Privatefirewall, SBie and Diskeeper12 (all programs that use low-level drivers with XP_SP3's limited fltmgr).
  17. modnar
    For some reason Avast wants to send the latest Mailnews (2024-07-13) .exe to the mothership for the examination over and over again. The report always comes back it's a good file - I could have told them that. The same was going on with the version from two weeks ago (2024-06-29) but never before. Is there any particular reason for such happening?
  18. modnar
    I have uBlock turned off on videocardz.com site. And now it's fine. That "SCSI Class: 03 01 02 2d" entry though correct was too much speed of ol' XP.
  19. modnar
    Thank you for the new releases, roytam1. By the way I have to add - that mozjs.dll rare crash with videocardz.com - some days ago I have noticed just how important in Windows the Service "Tag" values are and that they are properly registered in "GroupOrderList". One really needs to go through all "Group"'s mentioned in CurrentControlSet/Control/GroupOrderList and search in "Services" if their "Tag" value is mentioned in "GroupOrderList". This goes for any service, even with the "Start" value of 4 (stopped), if it has a "Tag", it has to be registered in CurrentControlSet/Control/GroupOrderList. So I was fixing M$ half a$$ed work and for service "i2omgmt" of "SCSI Class" with "Tag"="2d" I couldn't be bothered to type in all the values from 01 to 2d, so I just punched in 03 01 02 2d (with the usual 3 pairs of zeroes for each), but that while making the whole driver stack more fluen, also wasn't optimal and mozjs crashes are an indicator - I know that now. So yesterday I added in all values from 01 to 2d and all is well with 06-22 and 06-29 versions of Serpent. Unbelievable that even in Windows 7 there are some left out (to mind comes some HP service and its tag of 103 while in SCSI Miniport only 100 and 101 are metioned). Haven't checked Windoze 10 yet. Here are my registry files for such problems 3 groups appear to have them and it really helps to have these in order - even Diskeeper12 (has very low level drivers) works much better (renamed to .txt - for perusal - the second, FSFilterInfrastructure is shortened to 03 because there aren't any filters with Tag=4 anymore). GroupOrderList_Filter_0B_not_06.txt GroupOrderList_Infrastructure_03.txt GroupOrderList_SCSI_Class_01_to_2d.txt
  20. modnar
    @roytam1 BOC/UXP (Mailnews) link also doesn't work (404). Please fix it.
  21. modnar
    This last version (2024-06-21) of Serpent 52.9 is a bit unstable at times on "heavy sites" such as videocardz.com (haven't observed it elsewhere).
  22. modnar
    Just a heads-up if this in any way touches any of roytam1's browsers: I have just seen this video about G**gle quite possibly deliberately hampering Fireferret VP9 performance, but Mozilla found a way around it, but it's not in the new v127 release yet... Mozilla Has Finally Found a Fix for YouTube Playback Issues in Firefox - Says Google is to Blame
  23. modnar
    Just keep using x86 version (Serpent 52.9 preferably), it builds character.
  24. modnar
    I wholly allow quality websites such as msfn.
  25. modnar
    Showing their ignorance which apparently is bliss, they wallow in their muck.
×
×
  • Create New...