Tripredacus

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).

Status doesn't matter. Read the forum rules.

Removed from where?

I don't have that specific disk to try, but in general I haven't heard of any particular issues with any OS working on SATA SSDs.

Just on socket, since no board is being considered... It would be Pentium Extreme 965 3.73 GHz at 1066 MHz https://ark.intel.com/content/www/us/en/ark/products/27615/intel-pentium-processor-extreme-edition-965-4m-cache-3-73-ghz-1066-mhz-fsb.html vs your example of the Pentium 4 570J, 670 or 672 3.8 GHz at 800 MHz Now the other thing to consider is how you would even be able to tell in any real world application as to which is faster in DOS.

Seems this notebook is extremely old for modern computing, so it would seem to indicate that it has an older version of Windows. Since you don't say what version, this may not be applicable but... Use F8 at boot time to get the boot menu, and choose disable automatic restart on system failure. That should stop the reboot from occuring. However if this is not working, then you have some other options such as booting off removable media. If this is the same 8922 that searching shows has 1 GB RAM, you can boot a WinPE 3.0 on it, or a Linux live CD. Also if you think that the system is restarting before getting to Windows, you can remove the HDD and turn it on and see if it resets that way. You should go into the BIOS and enable LAN booting just so it can get to that point (you aren't meaning to boot that way). Also going into the BIOS and resetting to defaults is not something I would recommend. Primarily because the OS may not boot if the SATA type was previously IDE and the default is AHCI. Or on a modern system where CSM was enabled and default is disabled, etc.

I remember something like this happening without going through those steps. I don't remember the timeline exactly but I had reported the issue with MS. I don't think it was the entire OS that looked like this.

It can be done with DISM also but you'll need a third disk or network share to store the image temporarily. In this method you do not need to transfer the hidden partitions at all. I can put a workflow here but will need to know what the current partition layout is now and if the disk is mbr or gpt type.

The forum doesn't keep email address history. It can't show me who had a live.ca email in the past and had since changed it.

No user has registered/used with a live.ca email since 2015 but that email domain is not being blocked by the forum. The issue lies elsewhere.

Not sure about 2000 but for XP you can use WSUS

If the issue is that the image is too big, they can use imagex /export to see if it reduces the filesize. Maybe DISM export does the same thing.