Tripredacus

Duplicate post deleted.

Seen the same with other online emails besides gmail. You just have to regularly check your spam/junk folder on those webmails and make sure to mark things as "not spam" that are actually not spam. It happens with a lot of websites (especially forums) that I belong to that may send emails.

The message as it appears (in Polish) Niedługo przestaniemy obsługiwać tę przeglądarkę. Aby zapewnić sobie jak najlepsze wrażenia, zaktualizuj ja. translates to (in English) We will soon stop supporting this browser. To get the best experience, update it. But there is a link in there, where does it go?

It showed up for me yesterday, I just clicked the X and it didn't come back today.

Being close to the border, we always had the ability to pick up some Canadian channels in the analog days. On average it would be (presumably Toronto stations) 9 and 11. I have heard that analog Canadian stations still exist, yet when the digital switchover happened in the US, I stopped being able to receive any Canadian channels on any analog tuners. Because of this, I had just figured that Canada had made the change as well.

Perhaps that is the reason why Microsoft has made the Windows 7 ESU process different, seemingly more complicated than just changing a registry value.

Do you really think they (the broadcasters) are going to be putting DRM on everything? You think it will be at the transmitter itself and the DRM isn't tied to the actual programming, similar to Macrovision for VCRs? Let's say they do decide to do it for PPV or On-Demand (as the article says) and let's say they put it on all the 4K transmissions. If a broadcaster's ATSC 3.0 devices are DRM or nothing, I can't see them bothering to keep those extra channels that just show Bonanza or Green Acres all day, or bothering to put DRM on the shopping networks or the religion commercial channels.

I guess we'll see how it is handled. This website indicates it is in ESU: https://support.microsoft.com/en-us/lifecycle/search?alpha=Windows Embedded Standard 7

Well there is always a way. We'll see what the ATSC 3 tuners end up supporting. My guess would be that they would want to couple the DRM into the HDMI spec. Will we get set top tuners that will still have composite on them? Even my modern 1080p tuner still has a coax out on it. If the DRM ends up only on 4k content (and even so) it may not be an issue if you pass it through an AVR first. Only time will tell.

WES7 has entered ESU period, just as the retail OS did, so that is out of the question. However, I read that POSReady 7 is to get updates until Q3 2021.

Well I am getting emails from the forum (for reports) just not for PMs.

I think it just has a bit too much extra plastic. Also they are rounded, so not real easy to stack them.

Those Dell chassis are terrible, but not as bad as the ones Sony used during the Pentium years.

As put in the FAQ, the process of using ESU is laid out. There is an update to install and then the user will be able to put in a product key (MAK) that specifically licenses the system to receive ESU. It even says that Windows Update should still work as usual. As far as we are concerned, if any new updates appear on the Update Catalog site, we can talk about them. It is just the mechanism to modify the OS to fool the updates or update mechanism to install updates that is what we are talking about being against the rules. Time will tell if something changes, if we are still around in 2023 when this program expires, we can think then how we should handle such topics.

Yes, the posts have been hidden. Not really concerned with people using it or knowing it exists. As a wise man once said "we do not police the internet" ... the notice is in regards to discussion on MSFN only.

I'm not getting email notifications for PMs.

Dropping support is one thing, and that is not what happens with software these days. Instead these developers are actively blocking OSes that are not in their support list. That is entirely different situation.

Notice: anything relating to the ESU Bypass will fall under rule 1.a until further notice.

Not every system has an on-board RAID controller. I don't see it in the specs or guide for the 7010MT. To use RAID on that board you'll need an add-on card.

Aren't we all (US OTA users) going to run up against a hard switch when ATSC 3.0 goes live anyways?

It is possible that you may never be able to get the disks to enumerate in the order you want in Windows. You could always try it, since unless you are using a RAID controller or these devices are in any vdisks, it shouldn't make any difference to Windows. BUT: what you can do instead is use the volume label to identify what port is being used. And also you could write on the disk itself which port it is connected to.

I am going to go out onto a limb and say that there is nothing built-in Windows 7 to produce those kinds of messages. So for those who use the "as needed" update method instead of the "all critical/all" updates method may not ever see anything.

Edge is not Chrome, they are both Chromium. Those using Win7 will just have to disable the update services before the end date, although I'm sure some Win7 specific Chromium builds will be available for years to come.

Split this post into new topic as it was posted into the "Lite for Longhorn" topic.

Not weird at all. It is one problem with using Embedded OSes, you don't know what you are missing until you run into a problem. The issue being is that most software developers (or ISVs) write their software for, and test it on, retail Windows XP. When the time come to move to an Embedded product, presuming they are not opting for an Enterprise SKU, the OS is built from the ground up. The client sends a list of requirements, and a demo installation is created and sent to the client.* The client tests their software with their hardware and makes reports back any problems. The Embedded Partner then adjusts the OS and the ISV will retest until they are satisfied. Then the unit gets approved and is put on site somewhere. The problem lies with situations where the client doesn't test for all situations that their product would be involved in, or they may not communicate a need properly. Then on the other side, the documentation of what package does what is not detailed enough when building an OS. So these things do end up happening. There are also situations where an expected OS component you would think is enabled by default ends up not. One example I can think is that even if you install the USB package for Windows 8.1 Industry Pro, USB (bi-directional) 2.0 or 3.0 doesn't actually work. One client I build this OS for got all the way past testing phase and had units on site when it was determined their machines did not have fully functional USB. The issue was discovered when they tried to do firmware updates using USB keys. There have been other situations where expected low-level functions are missing, and since they are not documented properly, can take a while to figure out. Another I recall is an OS (I forget which Embedded SKU it was) didn't support the function of RS232 (Serial Port) but did install the drivers for the device. *This example follows the ISV/Embedded Partner model and not the in-house model.