Tripredacus last won the day on October 8 2025
Tripredacus had the most liked content!
About Tripredacus

- Birthday September 29
Contact Methods
-
AIM
atrbludgeon
-
Website URL
http://tripredacus.net/
Profile Information
-
OS
Windows 7 x64
Recent Profile Visitors
64,188 profile views
Tripredacus's Achievements
1.4k
Reputation
1
Community Answers
-
Win10 LTSC IoT lag issues. How to resolve?
Tripredacus replied to DeathAdderSF's topic in Windows 10
Microsoft has "public" or generally public versions, or Enterprise versions of Embedded SKUs that can be legally obtained. Upgrade paths are technically blocked on any of those, but it is not impossible to do. -
Win10 LTSC IoT lag issues. How to resolve?
Tripredacus replied to DeathAdderSF's topic in Windows 10
IoT is a branded Embedded SKU. It is bit-different than regular Enterprise but I do not know what is functionally different. It doesn't have the Store for example. Notification Mode means that the OS will Notify that it isn't activated. This happens if you don't put in an activation key, or the OS can't get to the internet after install, or something broke activation like a driver or system file damage, etc. -
Win10 LTSC IoT lag issues. How to resolve?
Tripredacus replied to DeathAdderSF's topic in Windows 10
I am curious about this "upgrade" mentioned, as I don't believe that IoT Enterprise LTSC has any upgrade path. It *is* true that it is possible, as I had taken about 3 months to figure out how to upgrade from Win7 to it but it is NOT designed to do that. 1809 version is the oldest I would use. I have that on my gaming computer and my old work notebook. I use 21H2 on my dev notebook. I previously had lag issues similar to what was mentioned on my gaming computer at various times but only when write operations were occuring, such as when a background process was running an update, Windows Update or Steam, etc. The culprit ended up being the SSD I was using having a write speed bottleneck. When I did my upgrade, I was using a Crucial SSD and upgraded on that, but then cloned it to a Sandisk SSD. The issue occured on the SanDisk SSD only. May not be relevant but it took me a lot of tooling around in the OS only to discover the OS wasn't the issue. -
You have no idea how large of a project it is to migrate a 20 year old forum full of custom code to a different forum software.
-
If you had any experience with enterprise level infosec, my statement would make perfect sense. To note that I (personally) have an understanding of the execution chain in theory but this is not confirmed. It would be foolish for me to provide that information as if it were valid, and an exploit exists, it could allow malign actors to take action against the site. If you had any experience in running a website, you would know that you never make public anything that could potentially allow someone to exploit the site. The site is sometimes redirecting to a new url now, a 98m4. User Agent may play a role, but changing the user agent in Palemoon (where I am typing from) to the one that Iron uses (where the redirect happens) doesn't cause the redirect to occur in Palemoon. I suspect that I know the reason for that, however since that information could be linked to an exploit, that won't be shared.
-
Understanding Windows - Low On Registry Space
Tripredacus replied to freakedenough's topic in Windows XP
First find whether or not the errors being reported are actually the correct errors. A lot of times, Windows will show an error when a condition is blocked, but that doesn't necessarily mean the error text shown is accurate. For example, you can get a disk space error if a process that is attempting to write to disk gets interrupted or blocked because Windows doesn't actually run a secondary check on whether or not there is free space. All it knows is that it tried to write and could not, so it presumes there is no space. You could run into the same issue here. But since you are looking at Paged Pool Memory, you do have the ability to check to see whether or not this is actually exhausted and if so, what is using it. BUT for this you need to use Kernel Debugging with WinDbg. I can't find a download for the version that would work on XP using google! but the Windows Software Development Kit for Windows 7 would at least work. Then this would be a start: https://gemini.google.com/share/adaf5e6e2c36 But windbg is not an easy program to use, you'll end up having to do a lot of research before you can actually know what you are looking at. An LLM would be able to help, but of course they make mistakes in interpretation just like people do. yes/no. Some parts of the registry are compressed on disk, and on OS load, they are expanded into RAM. Then they only exist in RAM at that point. You can probably research which portions are like this, but you can get some hints when using regedit when you run across either parts that are read-only or parts that if you change them, do not survive a reboot. -
There is more information about this issue that is not being shared for confidentiality reasons. There's no shade being directed with a statement like that. This isn't a client issue but if people do happen to find ways (like @NojusK did) or other specific software + versions, it is good to post that here. According to Xper, the issue doesn't seem to be with the server itself, rather likely with some other piece of infrastructure somewhere between the client and server. The issue remains, I've had to change browsers to visit the site.
-
Stop fighting against people who are trying to provide information! The issue has been seen in Discord Preview, some search engine results, Some versions of Supremium and one version of Iron so far. Posting user agents that are affected are OK but I have a thought that it isn't user agent based. On my Iron install where the redirect happens, I have this user agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Iron Safari/537.36 If I change my user agent in Chrome to that using the Network Conditions option in DevTools, the redirect doesn't occur. I verify that Chrome is using the Iron UA via whatsmyuseragent.com The thing in common is that all browsers are using an older Chromium engine. I do not think that it is a client issue per se.