Tripredacus

OK that part number matches what you put in the first post. If your computer has an N license/OS on it now, the key from the SBK probably isn't going to work. You can attempt to change the product key in the OS and/or even trying to activate it but knowing a couple things: - The OS installed may or may not access the new key but beyond that, it may not have the additional stuff inside of the OS to change to Pro. - If it happens to take the key and does actually activate but doesn't change the edition (or worse, changes winver but not the actual features) then you might need to use the telephone activation when you reinstall using the SBK. I have not had to deal with N, at least in this type of scenario, there is no production or support scenario where changing a product key to change editions is viable. So I do not know whether or not N would accept the key or not. My gut tells me that the OS would just say the key is wrong. No such thing as overkill for backup drives, sometimes it is just what happens to be available. For my main computer which has maybe 400 GB total space among 4 HDDs, I have a 4 TB backup drive. Why so big? Well it is simple, I went to the store to buy a USB HDD for backup and that was the size for the cheapest one.

People just repeat what they are told and this is especially true if they do not fully understand how something works. The root of this comes from sales pitches from companies from years ago. Even old versions of Windows have had advertisements like "most secure ever" which implies the predecessor is not secure once the new version comes out. Also people conflate installing updates or the ability to get new updates with security. They know some bad thing happened to someone online and there is an update, and if you have the update you will be protected from that thing. But people do not actually look at what the update is, or the CVE or anything like that. They have no idea whether or not the update even has anything to do with their operating environment or how they use their system. This is why I never understand people who just go an install all of the updates, or worse, brag about installing all of the updates. No one needs all those updates, but people will just put them all in there anyways because it is easier than learning how their computer or OS actually works and being able to determine which updates they actually need.

N editions and typical System Builder (OEI DSP, which is in the retail channel) are not in the same channel and the keys are not compatible with each other. There is no shared upgrade path between the two editions. You will need to buy the media kit and will need to reinstall the OS entirely. But, what is the kit number on your existing media pack? Because the name you put in bold does not look to be for an N edition, but we can know for sure with the part number. This is the "End Item PN" above the first barcode on the pack.

Played Just Cause 2 for the first time since 2017, according to the save game.

The drivers at that link appear for me, showing XP to Win 10.

No.

You can buy COAs on the secondary market, either used or NOS FPP. It is a license violation to transfer a license to different hardware but it isn't illegal. If you are a individual who purchases and uses a license, there is no problem but caveat emptor if a used key doesn't activate. There is no recourse with the seller or Microsoft in that case. If you are a business, you can fail auditing if you are found to be in violation of the license (or contract should you have one) so it is not recommended at all for a business to buy used licenses. A sealed System Builder or Retail FPP is perfectly safe from any of that. As for the forum, you can ask for a product key but no one is allowed to post one that isn't an install key.

If you hate Windows 7, stay out of Windows 7 threads. When a person asks "how can i fix this" we should never answer with "change the OS" unless it is specifically a software related question. For OP, my recommendation is to get the OS to 4 GB RAM, or if the system supports more than 4 GB RAM physical, get it to above that and use a 64-bit OS. Would like to know what type of operations are being done on the system that make it slow. If you are talking about using websites, then this is a totally different situation. As a daily user of a 32 bit Win 7 (specs are higher than yours but) I can tell you that some websites are just too heavy. For example, Youtube works fine but sites with heavy scripting can lock up or crash the browser. Examples of this are sites that continuously load into RAM such as Facebook, Twitter or say... Yandex image search. In my experience, once a browser's memory usage hits around 800 MB on a system with 3.2 GB RAM (4 GB installed on 32bit OS), things can get very slow or things will stop working. It is this experience that I am even considering of replacing my own Win 7 system.

Not using ClearType for Font Smoothing?

Merged threads

This version of IPB doesn't show who leads what anymore. The "leaders" are typically the moderators or globals who used to be the moderators of a specific section. I knew it was some "old OS" section, I just couldn't confirm. Back to the topic at hand, doing a quick look and it seems to me that there should only be 2 topics pinned: puntoMX's AHCI thread and mixit's H.264 thread. Everything "above" the H.264 thread are active enough that they do not need to be pinned. Everything below is the dead weight. If that seems to be correct, we can just unpin all of them besides the two I mentioned. And an FAQ/link thread can be made later. But the reason why a forum "leader" needs to do this is because they would be the ones to know what is and what isn't important enough to put into there. I haven't used XP in 10 years now except for doing disk work.

We do not need more than one thread created for this.

Closed poll. Forum moderation/administration is not up to community vote. Typically we would like to limit the amount of pinned topics to at most 1/4 of default view of forum index. Our typical way to manage this is to create FAQ/Important Threads topics such as in win9x: https://msfn.org/board/topic/95815-important-stickified-pinned-959898-seme-topics/ and in winPE: https://msfn.org/board/topic/131897-new-win-pe-faq/ However, this is managed by the "forum leader" and is not usually handled by globals or supers. I believe the XP forum leader is @LoneCrusader

The primary reason for archiving is to save space on the server. We are well past the point of that being useful.

Your guide has been removed because it violated the forum rules. Windows install.wim has multiple editions and either the answer file or ei.cfg will determine which edition is installed. This is handy because you can use just one install source for multiple editions.

You should post how you fixed it. Even if it was a simple thing that was missed, others may find it useful in the future.

I am going to presume this is a translation error, since baseband refers to signal frequency and typically you only see baseband referenced in the installation of OS onto mobile phones.

Welcome to the MSFN!

Presumably, you will still be able to play up to v1.12 using Magic Launcher. Not that I ever had a need for running offline, but I just realized I've never played a version newer than 1.12.2 myself. So I would not even consider it to be a deal breaker to have to stick to old versions.

They only have "Windows 7 and up" but specify bitness for Linux and MacOS. They really should put the bitness on the Windows requirement, since if the game requires 4 GB RAM, a 32-bit OS isn't going to meet that requirement. Now the thing I am wondering about is whether you can still use an old launcher on an old OS, or if they are going to block that from working.

8.0 and newer EDIT: I am also only referring to having the appropriate product key installed. 8 and 8.1 are technically different SKUs and so is Windows 10. So a 8.0 from any OEM can work on an 8.0 system of any OEM, 8.1 to 8.1 and 10 to 10. There is no garauntee that you can cross up the SKUs, for that depends on how the recovery media was made. An 8.1 to 8 may work better than an 8 to 8.1 or 10 to 8/8.1, but I would have no expectation that an 8/8.1 would activate on a 10 system.

I wasn't even going to attempt that type of fix. The owner of the computer is not savvy enough to understand how it works, it would just result in more phone calls tbh. Besides, they were not using any of the advanced functions. They just print and scan, and that can be done without having the HP software installed.

The HP Solutions Center software for HP Printers was built using Flash. I have run into a situation where that software will generate an error in Event Viewer saying that you need to reinstall the software after upgrading the OS! This gets written when that software is set to load at boot. If you try to open the software, it will just show the Flash killswitch image. HP has not released any other version that doesn't have Flash in it, so it basically has ended support for this. In the situation I had to deal with yesterday, it was on Windows 8.1 and it was actually not possible to print until the software was uninstalled. https://h30434.www3.hp.com/t5/Printers-Knowledge-Base/HP-Solution-Center-not-working-Adobe-Flash-Player-Error-and/ta-p/7946145

An installation using the OEM's recovery media of Windows 8-10 will always try to read the product key in the BIOS. An installation that is not provided by the/an OEM will not try to read the key from there. For example, System Builder will not make use of that. It does not matter if you are using UEFI boot or legacy. However, in contrast to previous versions of Windows, it is now possible to use recovery media from any OEM on any OEM's hardware. Such as using an HP recovery disc on a Dell, which in Win7 and older would not result in a successful activation.

You'll want to look in the registry under HKEY_CLASSES_ROOT\.png which should show the default association for that type of file. I can't do a good comparison for you because I don't have Irfanview but I can tell you what mine has: Windows Registry Editor Version 5.00 [HKEY_CLASSES_ROOT\.png] "Content Type"="image/png" @="Fireworks.Doc" "PerceivedType"="image" [HKEY_CLASSES_ROOT\.png\OpenWithList] [HKEY_CLASSES_ROOT\.png\OpenWithList\ehshell.exe] [HKEY_CLASSES_ROOT\.png\OpenWithProgids] "pngfile"="" [HKEY_CLASSES_ROOT\.png\PersistentHandler] @="{098f2470-bae0-11cd-b579-08002b30bfeb}"