Jump to content

modnar

Member
  • Posts

    90
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Slovenia

Everything posted by modnar

  1. Thank you - on the reactOS forum they agree with your explanation. I might try the mattermost client for windows...
  2. Thank you for the new releases. I wonder why https://chat.reactos.org/select_team upon logging into https://chat.reactos.org still does not work. I have notified the folks there.
  3. Currently ReactOS chat page displays nothing, when I log in (same login as for the Forum). There should be selection of teams to chat with (developers etc.). Is there any way to access it with Serpent 52.9? https://chat.reactos.org/login
  4. You have to tell which version of NewMoon you're using - it's 27, right? You should use v28 - it's better - more feature-rich. Here in Serpent 52.9 x86 "Rabota v Moskve" (hh.ru) site works fine.
  5. Didn't know about that geo.enabled setting, I usually just choose "Never share location"...
  6. Interesting; since your card is nvKepler arch. (more compiler dependent shader processor), it looks like this version of the driver really occupies the shaders in some way. Just strap a fan over its heatsink, connect it to 5 V to make it silent and monitor temperature. As long as it's stable.
  7. I'm glad the 6.14.13.6881 worked better - I reiterate - the only thing changed in all inf-files was the version - to make driver compatible with fireferret foolish blocklist.xml so we can have browser graphics acceleration. If your GT710 isn't stable, it might be overheating peradventure? I mean it's not necessarily software fault. It's a nvKepler card, so it should work as any other, I had GTX 680, 770 and 780Ti with this driver and all worked well, no instabilities. Any yeah GT730 is better than 710, theoretically 2x, it has 2x the amount of shaders (384) in 2 texture processing clusters.
  8. @MinimumAttic410: The first (most important file) is nv4_dispi.inf, but there are 45 of them (to cover all use cases). Here is the .7z package of all of 368.81 inf's (just copy them into your upacked driver directory: Display.Driver) with version changed from 10.18.13.6881 to 6.14.13.6881 (only version has been changed, nothing else). 368-81_xp-last_v6-14.7z
  9. Avast v18.8.4084.0 (XP-last) works well - just choose minimal install + Mail shield (that is these four: File Shield, Behaviour Shield, Web Shield, Mail Shield) and it's fine.
  10. Just try the 368.81 and edit the .inf just becuase nv decided that they would bump up the version in the last few XP drivers to 10.18.13.6881. Now that causes problems (no hw page acceleration) with Firefox and other browsers derived from it, like RT's Serpent 52.9. Correct the version to 6.14.13.6881 that is standard for XP (the 6.14 part - it's found in ATi drivers too) and all works as it should. DVI support in control panel seems bugged up though (less resolutions than VGA and the screen is identified as TV) but driver is stable (better than AdiosMyDineros' 14.4 driver I used with my HD7850).
  11. Wow! Msfn was down for at least 3 days here. Glad it's back up.
  12. Same on Serpent 52.9.0 x86 2024-2-23, just says "Ładowanie aplikacji..." / "Loading application...". You can use speedtest.net though.
  13. Hi! mega.nz works here too, Serpent x86 2024-02-23 (latest). Perhaps there's something wrong with your ST profile?
  14. Quite an update: XP fltmgr (5.1.2600.5512) replaced (on real computer) with 2003 version from SP2 (R2) (5.2.3790.3959), no updates (simple is good). AttachWhenLoaded has to be 0 (XP default). DK12's DKTLFSMF I set at 137100, so it has a broader view and can then better guide DKRtWrt at 137102 to rightly write things down. While the above works, it is not really balanced; sometimes Serpent crashes due to write request conflicts. I guess we'll have to wait for ReactOS's fltMgr or the whole OS to really be able to have a decent solution for our elderly and neglected system while at Microsoft their collective heads are further up their arse-s.
  15. 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.
  16. 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.
  17. 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...
  18. 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}
  19. 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!
  20. 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.
  21. 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.
  22. 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... :-(
  23. By the way - today (sunday) I just saw this piece of news....don't people have anything to do these days?
  24. 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.
×
×
  • Create New...