Tripredacus

Another gripe I'm not sure I mentioned: the borderless windows. Since by default the explorer windows are white, now with no borders, there is no way to know where one stops and another begins. I am getting confused when having multiple windows open and having to resort to Alt+Tab to navigate them and not being able to use the mouse.

Well the camera in the MS-163K isn't great but for a video conference rarely is it required to have good picture quality. Now you talking about streaming, meaning you are broadcasting/recording instead of watching, then that is an entirely different situation. I'd say you need a quad core + HT and 16 GB RAM minimum. Not sure about what video card would be needed. Also many people use a separate PC to handle the streaming aspects in order to reduce overhead on the system actually playing the game. Just looking now, you can find an older 4 GB Radeon for under $300 on Newegg.

Is it a discrete graphics controller or add-on?

I found the answer myself https://wiki.osdev.org/UEFI#UEFI_class_0-3_and_CSM Calling it UEFI class 3 is incorrect, as it clearly indicates a class 0 is BIOS and thus cannot be UEFI. I don't see why it would matter. Vista SP1 x64 should support a Class 3 system. Just use boot menu and see if the DVD has the UEFI prefix.

Can you explain what you mean by class 3? UEFI spec is still on version 2.

Presuming the working dir for the program isn't System32, you can be safe but you put the "newer" file into the program's working dir. Typically the working dir is where the .exe is, unless launched from a shortcut that indicates the working dir is somewhere else. Windows depends search order is in your favor as the working dir is often the first place Windows will look for a file with System32 being last, which is a compatibility shim that dates back to the 9x days. BUT the caveat is that this only works if the binary uses relative paths to find files and may not work if the binary uses absolute paths or paths with env vars. At least it doesn't hurt to try using the working dir method as you aren't changing anything with the OS.

Done

If you expect nothing, you can't be disappointed.

I must not have saved the original PCB or had taken a picture of it. IIRC there was a burn mark on it and one of the components was missing.

I think you are OK with Zoom with just about anything. There is more to needing a modern OS for that than anything. I used zoom just once in 2020 and it was on an MSI MS-163K, a notebook from 2009, and it worked just fine.

Not allowing someone who disagrees with you to have the last word or let something slide is what caused this thread to get out of control. MSFN does not have a War Room but we do have a Hurt Locker. Edit: We can try again now

The chip shortage is only really effecting new products and only certain ones at that. It shouldn't have any effect on buying parts for an old computer or a mid-range new build. You're only going to run into problems if you need highly specific parts. IMO we are at a plateau when it comes to components being any better than the past few years. In my gaming PC, my CPU came out in 2017 and my video card is from 2018. Are CPU and video cards that are recent better than that? Maybe technically, but not to a point where I could tell the difference and I can run all of the games and programs I want with no performance issues. My work computers often have issues with detecting USB drives. The notification about needing to be scanned can be ignored for the most part. That happens because the dirty bit is written by the OS, which is normally cleared when you use Safe Remove Hardware option on the drive. In my experience, that is the only thing wrong with drives that make that show up. But for USB detection for rear ports, it can indeed be an issue with the ports themselves or with the board. Front ports are usually remedied by replacing the USB header but those tend to be proprietary to the chassis so getting a replacement may not be ideal. For my one PC where the fronts do not work anymore, and I have no replacement USB header, I just don't use those ports anymore.

I just used Google Maps on Directions mode and changed it from driving to walking. I live close to a supermarket and I used to live close to work. But my company got purchased a long time ago and the office moved farther away. I could walk to the old building in 45 minutes each way if I wanted to.

If this page is to be believed https://www.userbenchmark.com/System/Asus-X55A/88 You can use a 2020M CPU which has VT-x https://ark.intel.com/content/www/us/en/ark/products/71142/intel-pentium-processor-2020m-2m-cache-2-40-ghz.html The board in the X55A has a socket so the CPU can be replaced.

It seems like it may be a trend going forward. That company is not relying on Microsoft doing the drivers, MS doesn't do that. Instead the ODM is pushing the correct drivers to Windows Update only. I am working with a product from Intel that has been frustrating me for some time. Where with both Windows 10 and Windows 11, there are drivers for it you can get from Intel or the update catalog, but they do not work in the OS manually. Only the drivers installed from Windows Update work. So for products that are not specifically aimed at Enterprise channel, appliances or Server OS, drivers may more and more only appear on Windows Update.

1. https://remysharp.com/2010/10/08/what-is-a-polyfill 2. All (or most) but it seems that this is just a modern term for an old thing. One could consider the classic MM_reloadPage javascript function from Dreamweaver 2 to be a polyfill. But if that is not an example of one, then perhaps I need clarification as well.

Just for fun I decided to calculate how long my commute would be if I walked instead of drove 12 miles. It would take 4 hours to walk that, but I suspect it could be shorter. And that's one way, so an 8 hour commute of just walking. Not really so much of an easy solution in my case.

DISM supports offline installation. So you can boot a PE and attempt to inject a driver to another vol using the -IMAGE option. IIRC DISM will be able to install any driver you'd normally be able to install that way. For example, you wouldn't be able to add a stock .inf for a video driver. You may also need to use -FORCEUNSIGNED depending on the situation. I use this method to add some drivers after deployment, mostly storage drivers. Drivers of other types may install but you can't know if Windows will actually use them or not until you boot the target.

A test of Windows 11 Search has failed spectatularly, but of course I have come to accept that Search will never be as good as it used to be. The test being have a folder with a text file and a string, then do a file contents search for that string and ideally that file should appear in the results. Well, no it shows no results even after choosing the option for file contents. This has been a big issue for me for years even going back to Vista. Even Windows 7 has this issue where file content search doesn't work except for when it does. I have 3 PC here (2x Win7 and 1x Win10) and if I need to find a string in a file, I have to copy everything to the other Win7 PC to do the content search because it doesn't work on the other Win7 or the Win10 PC. And even so, actual file search in Explorer (when not looking for contents) is usually so slow that I may often find myself using CMD to find file locations instead.

You can be certain any systems running some version of XP are running on hardware purchased over a decade ago. And the fact that the computers are old and running old OS gives you a clue about how much they invest on something new. No instead they hold onto what they have and resist upgrading until there is no other option. I'm aware of one company that has an active "bounty" on specific types of motherboards with VESA slots on them because they are stuck in that type of rut of continuing the use of the old tech because making things work with modern hardware is either prohibitively expensive or time consuming.

It is perhaps not a situation where ATSC 1 has been turned off (I read it hasn't) rather that the broadcasters like to move things around to different transmitters and share channels with others, and it is perhaps these particular channels that I can't get had their ATSC 1 source moved to a transmitter I don't get good reception from.

It sounds like your company needs to re-evaluate their internals. At any manufacturing company, computers that run critical machines should either be segregated or firewalled. Or the company should be using a WSUS and only push updates to it that have been vetted beforehand. Alternatively, they may be using the wrong (but cost effective) SKUs. I see that a lot where a company will save costs by using a retail OS instead of an Embedded/IoT OS. Last year I got to visit a company and do a site inventory for them. Their critical machines controlled lasers for micro-manufacturing, and none of the computers attached to those systems were connected to the internet. For the same reason you outlined, because if one goes down, manufacturing stops and the company looses big dollars. So they had made it so those systems did not get updates. That company also were using the "wrong" OS for the job as a reason to cut costs (I don't want to think about how much those laser machines cost) and that was their mitigation strategy.

Your first post was moved to the Startisback forum. Your second duplicate post was deleted. Do not make duplicate posts in the forum, it will just annoy the users and give everyone a bad impression.

Finding exact info is kind of tricky but I know this. Almost a year ago is when the big stations switched to ATSC 3 in my area. When that happened, the CBS and NBC affiliated stations can only be picked up by the ATSC 3 tuner I bought for my upstairs TV. My downstairs TV can't get those channels anymore and they are not found when doing a rescan. Maybe I have my numbers off, maybe that TV only has ATSC 1 and those stations changed to 2 and not 3.

The issue seen here is that since the rearm was used, it put the licensing system into grace period. So this means that the initial cause for Windows to be in notification is not know because Windows does not log previous states as far as I'm aware. There may be something in Event Viewer indicating when the licensing change occurred. These are kept in a combination of Winlogon and Security-SPP sources at a logon. Security-SPP will initialise the status check and will log the status, afterwards Winlogon will write an even which normally would say "Windows license validated." As far as the status log by Security-SPP, this log is also written when MGADiag is run and potentially there would be a way to compare a log where the OS is in notification, in grace period and in activated state. However, since the system is in grace period, we can't know for sure why now it is in Notification. By looking at the log files I can confirm a legitimate OS is installed but obviously I can't confirm the partial. The OS does appear to be System Builder. There is not present any file corruption that interferes with licensing. Now what to do. First make sure the time is set properly in the BIOS and then verify the time is correct in Windows. Verify that the partial product key in the logs matches the one on the COA. Attempt slmgr -ato again. If it says the product key is blocked still, then there is only one thing left. You run slui 4 and call the number. But one thing to keep in mind when dealing with a person at the Activation Center, you don't need to explain anything and the less you say the better. You can say that your Windows is telling you to activate but it doesn't. You can say you have the COA and the product key and ask for help to activate. There is no need to say anything else, nothing about the computer itself, no small talk, nothing about what you have tried to solve the issue already. The Activation Center has the keys to the kingdom and what you say will determine whether they run the code generator for you. If, when you call into the phone number, it gives you the option to text you a link instead of talking to someone, do that. Because that link will have the activation code generator (you put in your product key and it spits out some numbers that you type into Windows to activate). In my experience, this code generator will work 99% of the time presuming that your key isn't flagged as "stolen" on the Activation Server. If the rep still can't help and/or the code generator rejects your key then the option to buy another key is an option... BUT it should be a key for the same SKU aka Windows 7 Pro SP1 OEM System Builder. With a new key, you can try to use slmgr /ipk to change to the new key and slmgr /ato to activate online, but you still may need to use slui 4 to call the activation number with a new key.