Leaderboard
Popular Content
Showing content with the highest reputation on 03/30/2022 in Posts
-
This project make possible to compile ACPI 2.0 driver from leaked XP SP1 & W2003 RTM sources, has same functionality as existing acpi.sys v6666 (still missed integer/fields/memory 64 bit support/) Grab leaked XP SP1/W2003 RTM sources (google it) Use "XPSP1/NT" directory as basedir if you want to compile acpi.sys for Windows XP x32 Use "Win2K3/NT" directory as basedir for Windows 2003 x32 / Windows 2003 x64 / Windows XP x64 Download any GNU patch package for windows (gnuwin32.sourceforge.net, cygwin, mingw, msys2, ...) Open command console, change current dir to base\busdrv\acpi\ (Windows XP x32) Save text diff patch https://pastebin.com/C5NXwHbS (v7 update) to file base\busdrv\acpi\sp1_to_sp3(ACP2).patch (Windows 2003 x32 / Windows 2003 x64 / Windows XP x64) Save text diff patch https://pastebin.com/8QURrM49 (v7 update) to file base\busdrv\acpi\rtm_to_sp2(ACP2).patch (Windows 2003 x32 / Windows 2003 x64 / Windows XP x64) Rename Win2K3/NT/public to Win2K3/NT/public2 (Windows 2003 x32 / Windows 2003 x64 / Windows XP x64) Update compiler and headers to mix of W2003 DDK+WRK, unpack https://anonfiles.com/J1W9H1a8y1/W2003_tools_update_7z to basedir with overriding existing files Remove "read only" flag from base\busdrv\acpi directory including sub-dirs and files Apply patch to convert original SP1/RTM sources to SP3/SP2 with extended ACPi 2.0 syntax: patching file driver/amlinew/amlipriv.h patching file driver/amlinew/amlitest.c patching file driver/amlinew/data.c patching file driver/amlinew/misc.c patching file driver/amlinew/object.c patching file driver/amlinew/parser.c patching file driver/amlinew/proto.h patching file driver/amlinew/type1op.c patching file driver/amlinew/type2op.c patching file driver/inc/aml.h patching file driver/nt/debug.c patching file driver/nt/debug.h patching file driver/nt/devpower.c patching file driver/nt/internal.c patching file driver/nt/interupt.c patching file driver/nt/irqarb.c patching file driver/nt/osnotify.c patching file driver/nt/pciopregion.c patching file driver/nt/rangesup.c patching file driver/nt/root.c patching file driver/nt/wake.c Change current dir to basedir (Windows XP x32 / Windows 2003 x32) Run razzle environment setup: (Windows 2003 x64 / Windows XP x64) Run razzle environment setup Change current dir to base\busdrv\acpi\driver\ Complie ACPI driver: build /Dcegbw Compiled acpi.sys.sys will be in (x32) base\busdrv\acpi\driver\nt\obj\i386\ or (x64) base\busdrv\acpi\driver\nt\obj\amd64\ Project contains implementation of new ACPi 2.0 syntax: ToInteger ToString ToHexString Continue ConcatenateResTemplate ToDecimalString Mod ToBuffer CopyObject MidString QwordConst (inside ParseIntObj) Timer CreateQWordField(fake it as CreateDWordField) Know issues workarounds: BSOD 0xA5 (0x10006, ...) missing _DIS method for "PNP0C0F" (PCI Interrupt Link Devices) BSOD 0xA5 (0x02,xxx, 0x0, ...) ACPI vs E820 mem ranges conflict IOTRAPS I/O range 0xFF00-0xFFFF vs VGA (10-bit decode!) conflict BSOD 0xA5(0x03, ..., C0140008, ...) error in ValidateArgTypes() when reading 64-bit fields BSOD 0x7E(c0000005, ...) error in AcpiArbCrackPRT() when referencing null pointer BSOD 0xA5 (0x11, 0x08, ..., ...) error in _AMLILoadDDB() (zero lenght buffer) BSOD 0xA5 (0x11, 0x08, ..., ...) error in _AMLILoadDDB() (doubled device definition) BSOD 0xA5 (0x0000000D, ..., 0x4449555F, 0) absence _UID method BSOD 0xA5 (0x11, 0x08, ..., ...) error in _AMLILoadDDB() (Connection() opcode) CPU definition as Device with _HID=ACPI0007 BSOD 0xA5(0x03, ..., C0000034, ...) postponed SSDT loading on x64 platform (v8 update) Assertion Fail on loaddsdt.c, line 488 for x64 builds (v8 update) Unresolved issues: BSOD 0xA5 (0x0000000D, ..., ..., ...) duplicated/absence _HID/_UID method (AMD boards) BSOD 0xA5 (0x2001, 0x01, 0xC0000034, ...) failure to evaluate the _PIC method in NotifyHalWithMachineStates() Conflicted device names in Windows device manager (Code 42)1 point
-
1 point
-
I think I'll never let go of XP as its great for other things besides internet access. Other than that, I think we can always keep it for so long as it stop working totally. I quite enjoy my music recording programs and they are very old and obsolete.1 point
-
I collected videos for about 10 years, so I still have years worth of VHS and DVD to watch before getting rid of it. That includes many DVD box sets for TV shows that I binge watch. No real difference really, except that I've missed out on anything recent.1 point
-
That's kind of the "mistake" that I have made. I have Netflix and Hulu but tend to binge-watch something on one for a full month and not touch the other, so I paid that month for it just to sit there! Then there's folks like my sister that has Netflix, Hulu, Peacock, Disney, and Epix and those are just the one's that I know of. They probably have a few that they've forgotten about but yet still pay the monthly subscription.1 point
-
1 point
-
I can't make use of an edited output. If you are wary about sharing the full output of the two tools, you can PM me the full information. EDIT: since you used rearm (should not have been done) now you are in grace period. You can run the slmgr /ato as suggested above, and if you get an error, relay that error here.1 point
-
Thanks, I'll delete it and report back if it makes any difference or not.1 point
-
1 point
-
You don't have to lose your current profile. Just start the profile manager (use the -P command line option) and create a new one. You can switch back to your old profile after you are done testing.1 point
-
It's the swiss-army knife of web filtering. It's "too much" for most people. Most people are happy with NoScript versus actually being able to EDIT the scripts. Most people are happy with Stylus for editing css. Most people are happy with Greasmonkey to inject js/css. Most people are content with blocking cookies versus filtering the contents inside that cookie. Et cetera. And only a very tiny handful of folks want one app to do "all of the above". The cipher bit is over my head. The original Proxomitron was created by Scott Lemon in 1999. Proxomitron Reborn was created by "amy" a few years ago and it's still in its infancy. Cloudfare "capchas" cannot be handled by XP + Proxomitron. Not sure if that can be fixed by "amy" or not.1 point
-
That has been said so many times... In any case, maybe access to some websites is lost. But for almost all other day to day business still works, and better, than subsequent versions (excluding perhaps a well modded w7). In my imagination, I can see a near future where I connect into a raspberry-pi 4 for both internet connection and x-windowing of a few apps that require something better than xp and are worth the effort (i.e., apps with no suitable replacement in the "They"-wanna-see-deprecated xp).1 point
-
... He already said that he did and the previous 64-bit St52 build works OK: Have you tried clearing up both browser cache and cookies and then restart the browser (in normal, non-private, window) ? If clearing cookies, you'll have to log-in again to the sites you were previously logged-in... Also, and this is essential, have you tried to replicate your issue with a new/fresh St52 profile? Are those FxESR 52.9.x and Chrome 49/50 (yes, Chrome 50, if you can still find it, works fine on Vista SP2) ? For the sites not supported in UXP browsers (like Serpent 52/New Moon 28), you can check versions 12 and/or 13 of the Chinese-made 360 Extreme Explorer (Chromium 78/86 forks); you can search for them in other MSFN threads, where you'll hopefully find that two competent fellow MSFN members have created and shared modded versions, with practically most of the Chinese "spyware" removed (however, these mods are primarily targeting WinXP usage...). Welcome to the forums, fellow Vista user !1 point
-
Corollary (old Italian/Tuscany saying): "Le bestie non conoscono feste comandate" which translates roughly to "Animals don't know about Sundays or holidays". jaclaz1 point
-
I suspect that this type of reasoning is made up by people who aren't or haven't any farming experience. I did work (and live) on a farm for some time and I can say that it makes no different if there is DST or not. You work from sunrise to sunset (or beyond but indoors) and you determine what time to wake up based on what time the sunrise is the next day.1 point
-
1 point
-
I did all your step then I've got it work in W2k1 point
-
1 point
-
Yes; IIRC, there was no iPhone 9 either! In Apple's case, they were in a hurry to get to 10, because the Roman numeral for 10 is X, and they wanted to advertise the "iPhone X" (as in Xtreme, I suppose) But I don't recall M$ ever advertising Windows 10 as "Windows X" or some such nonsense. Anyway, I hope you're right that the 360EE version is now the year (on the Gregorian calendar) - I just wish M$, Mozilla, and Google would follow suit! <off topic>My sincere apologies for trying to dissuade @InterLinked from buying an automobile from the era when gasoline in the US still had lead in it (not to mention wishing I could buy an unGoogled EV) - that one comment once again derailed the entire thread with a raft of political propaganda. You'd think I would've learned by now!1 point
-
I just found out that there is another about:config item related to e10s: user_pref("extensions.interposition.enabled, false); // set (true for no e10s) and there is also another related extensions.interposition.prefetching EDIT: using these tweaks, it seems to me that I can see less v-synch (or whatever is the horizontal-line artifact that every now and then shows up while watching videos. Some old extensions (for example, TB profile switcher 1.77) become less responsive due to lack of shims, but no other significant drawback. Cheers!1 point
-
The mirror of latest BNavigator, Firefox 45ESR, IceApe, IceDove, K-Meleon 1.5.x/74/76, MailNews 52, New Moon 26.5/27/28 and Serpent 52/55 builds by @roytam1 has been updated -> soggi.org - tools. changelog: - added latest New Moon 28 Win64 20220326 bugfix build --------------------------------------------------------- OK...I can't imagine anything more unresponsive than WinXP on a Pentium Pro... xD Unfortunately I don't have the time to test it myself on several HW configs. Just tested latest builds on a C2D laptop some months ago. Did you use one of the latest builds? I agree it's still in alpha status and therefor it's not optimal. kind regards soggi1 point
-
Download this WU patch: https://download.ru/files/DMFZOv3t First stop the Automatic Update service. Copy the wuaueng.dll from the x86 folder to c:\winnt\system32\dllcache and to c:\winnt\system32. Then run the .reg file. Restart the PC and launch WU. You need this version of ProxhttpsProxy: https://download.ru/files/d4uaSsgD Cr. to @whenever on Tuopf Start ProxhttpsProxy on your 2nd PC. Install the generated certificate in "local computer". You must install the same certificate in W2k. To do this, simply copy the certificate to W2k using a USB stick and also install the certificate in "local computer". Run ipconfig in cmd on your 2nd PC and enter the IPv4 address in W2k in the proxy settings under secure and the port (usually 8079). Enable "Use http 1.1 through proxy" and Tls 1.0. Disable SSL 2.0. Start ProxhttpsProxy on your 2nd PC and open WU in W2k. To access WU in W2k you need to go to this page: http://fe2.update.microsoft.com/windowsupdate/v6/default.aspx?g_sconsumersite Or check out this post: W2k WU registry entries.reg1 point