Tripredacus

Either one of Hiren's boot CD still contains warez and cannot be discussed here. Make a new topic on how to fix your booting issue.

I haven't been able to try Windows 11 22H2. I went to make a base image but it stops during setup saying the computer doesn't meet system requirements. MS has changed their online support and now it is a gauntlet for me to get answers as to why it is giving this error. In regards to multi-boot, I only use it on specific devices. Regular computers I want to have maximum uptime, makes no sense for me to multi-boot or VMs in. The only systems I use multi-boot on are my notebooks which are for specific purposes, and are supposed to be turned on as needed and off most of the time.

You can run MGADiag. Click Copy button and paste the results here. It may reveal the issue.

One reason why I always use Pro editions (at least) so that if my profile were to get corrupted, I can boot into Safe Mode and have access to the Users and Groups cpl in MMC without having to enable Administrator. Profile corruption was common in NT4, 2000 and XP inside of domains specifically because users would always be saving things in local profile folders even if considerations where made to have a User share. The corruption happens due to there being a large file size in the domain profile, and copy errors occur during synchronisation. However, having very large "for the time" user profiles (2 GB+ is where it becomes a problem) in local only (no domain) profiles can still cause issues with corruption. Those OSes also occasionally had issues with path length and also there was that mysterious "number of files in folder*" issue which did not match to Windows or file system limits which did not help. The local profile corruption still occurs these days but not because of size or file counts in modern OS. Now it is usually caused by some program or virus behaving badly. The network desync in AD can still occur for those types of profiles however. * This is some bug where some dirs became unresponsible/unusable when number of files in a single dir/subdir would number 1000+. The actual limits by the OS or filesystem (even FAT32) were well above where the problem occurred so it must have been something else. I never did figure it out. Sometimes would happen over 1000 files, sometimes over 3000 files.

Done

It probably doesn't like the pipe.

Ubisoft had an update to Uplay/Connect and now some games launched from them (even via Steam) will not run. I say some because Far Cry 4 works for me but Far Cry New Dawn shows this message:

No and no.

Ref: https://www.bleepingcomputer.com/news/security/intel-confirms-leaked-alder-lake-bios-source-code-is-authentic/ As Intel's position is not against is being released and is actively asking for people to look at it (for security purposes) we shall allow this content... for now.

Windows is a lot more resilient these days. Back in NT4 times seeing corrupt user profiles was commonplace.

I am well aware of what a dummy driver is. For me it depends on the application. If this is for a product, and the client signs off on it, then using a dummy driver is fine. If it is for a personal system, I'd rather just not even bother and just leave things not installed for devices I'm not going to be using.

Yeah but does HDMI audio work?

Updated

Another thing to check, ECC vs non-ECC.

Yeah, the problem with (XP and) older MS downloads is that they were paywalled and/or only available via CD. In fact, a lot of the time back then you couldn't actually download from MS but instead ordered a CD and it came in the mail. So the result is that a lot of their stuff was never on a public website that could have been archived and makes things hard to find these days.

Since my recent phone adventures have involved situations where I couldn't move everything over, even between the 2x S4, I had gone a little while running two phones. Of course one only worked normally and the other was in airplane mode or on wifi only because I took the sim out. Both of the S4 (the original + the replacement and the replacement + the S7) had no problem in keeping a battery charge for at least a month when in standby or off. It was only when the phone was on did it drain battery like no tomorrow. Especially those S4 batteries finally were really giving up the ghost, they would last maybe 8 hours of just being on with no apps "running" before the battery would die or get down to powersave mode. I think even though it would seem that the batteries were wearing out, that in fact it is the phone software that had been causing their fast draining. It is just too bad that there doesn't seem to be any real good way to strip all of the junk out of OS in the phone to actually make it usable.

You should test on RDRAM if you can since it is also not only faster than DDR2, but it was also around during the service life of 9x.

On that second link there is another link to older, which has the 7 and 8.1 WDK but not older than that. https://learn.microsoft.com/en-us/windows-hardware/drivers/other-wdk-downloads

I had used a Galaxy S4 for the past... idk 5 years or something. The first one had melted a chip inside and resulted in sound not working for anything besides a phone call. I had bought another S4 on Ebay and it was OK but the call quality was terrible. I was really really concerned with the fact that "modern" phones have a non-removable battery and didn't like the idea of getting one of those. About a month ago I got a letter ( ! ) from my carrier saying my phone will stop working because it uses 3G for talk/text and I had to get a new one. It seems they are going to turn off those radios and I think it may be a nationwide change because the prices on used phones have gone up a decent amount in the past couple of months. So unfortunately this not only limits the selection, but ended up pushing the removable battery phones that support my carrier's network out of my price range. I use this site to compare phone specs https://www.gsmarena.com/ It doesn't have everything under the sun but does have a lot more brands than I've ever heard of. So it doesn't have unihertz for example. I ended up getting a Galaxy S7, which has a battery I can't take out but the price is still low enough (comparatively) that if it can last a few years that will be good enough.

This topic has a misleading title, and if you don't read the first post you will miss that it is involving virtual desktops and not physical computers. I have 2 PCs that have VirtualBox and I'm going to presume running DOS does not count. Also not certain if RDP counts as 1 PC can RDP into 2 (physical), while another one can RDP into 2 VMs that are running on Hyper-V off another system. I don't use these as actual "Desktops" tho, it is only if needed as all of these are Servers and anything I need to do can be done via network shares.

UEFI 2.3.1 is the current standard and many boards come from factory with no CSM. So many people do not have a choice these days. Also, UEFI does not have a bitness involved. The architecture capabilities of booting a UEFI application is based on the processor. The manufacturer of the board decides whether or not to allow a user switch or lock UEFI applications to a particular architecture. To my knowledge, there is no fully limited firmware out there, all are modified to meet the design requirements of the ODM. There is also the video card consideration where many video cards from the past few years are UEFI only.

Sorry, I haven't used anything from nVidia since the 210 series.

I don't end up using those programs as a first attempt in most cases. Since I have an imaging server, I tend to attempt to copy the partition image to the server and deploy it to the new disk as if it were a new installation. Sometimes that doesn't work and I have to hunt for some program to do it, but rarely has that happened that I don't even remember what programs I had used to resolve those issues.

It is in the kernel32.dll from Windows 10, so try copy that to the working dir on the game and see what happens.

That is for 2 servers, but single server is actually quite simple (meaning you don't have to do most of the stuff in the first post), especially in the newer Server versions. 1. DC Promo 2. add the DHCP role 3. add the DNS role 4. add the WDS role 5. add the boot image to WDS Obviously you still need to pre-plan the network environment, which scope you will be using, the domain name, which users to assign to the shares, etc. But there is a caveat involved when dealing with PXE. You want to determine whether you are going to be doing MBR or UEFI clients and stick to that one only. The issue is that the WinPE still has a bug involving diskpart where it cannot make MBR disks if booted in UEFI and WDS still does not properly detect some LAN card capabilities (meaning it can provide boot loader for "wrong" boot type, and thus diskpart runs the wrong scripts. I personally only use the WDS portions now do to MBR or legacy installation and just boot my WinPE boot image on USB and bypass WDS entirely for UEFI (which is like 99.999% of installations at this point).