Tripredacus

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}"

I think it is just naming. Defender is just MSSE and the the Defender Firewall is just the Firewall with Advanced Security. If it were me, I would change the ACLs on HOSTS to deny write permissions to the Trusted Installer security context and then look in Event Viewer for errors. I did a quick look at my "Windows Security" app (apparently not called Defender anymore ) and I didn't really see anything besides "allowed threats" option.

32bit vs 64bit is really a matter of preference. And specifically about what kind of programs you are going to want to be running. With Windows 10, there probably isn't going to be any need for running a 16bit program, but there may be a need for a 64bit program. If there is any chance to add more RAM to the system, 64bit would be the way to go.

Done.

What, tabbed browsing? IIRC Maxthon was the first IE shell (or maybe even the first "browser") to have tabbed browsing, but I don't know if the 9x versions have it. Unless you are talking about memory pages...

Wireshark can be overwhelming for beginners, you can also look into something else like TCPView. https://docs.microsoft.com/en-us/sysinternals/downloads/tcpview

Moved to GD. I tried to figure it out, but without a complete inventory I can't say for sure. Perhaps I will do that and confirm. For this post I will say 5 that are current, plus an additional 6 that are known to work, and perhaps another 15 20 that are complete systems but in an unknown level of operation. EDIT: oh god I forgot about the servers.

WHY YUO SHOULD NEVAR INSTALL DIRECT X 8.0 OR AND MICROSOFT IS SUCKS!!! ANYWAYS!!!

I have no clue how a multi-boot with Win7 on UEFI would work. I was never able to get a deployment with a recovery partition to boot, and while Microsoft supposedly did support that configuration, no one could tell me how to do it. They never did release documentation for that type of configuration, and only later did they (incorrectly) state that the Windows 8 deployment docs would work with Windows 7. In order to maintain license requirements, any Windows 7 on UEFI that was done had to ship with a recovery DVD, and of course DVD install had no problem installing to UEFI. So for my Win7 on UEFI deployments, I used these parts: 260 MB EFI 128 MB MSR "remainder" partition where the OS was deployed. A recovery partition is the same basic concept of a dual boot, since you just have an additional partition with a WinPE in it instead of an OS install. BCDEdit had no issues and BCD was always correct, but with the other partition present, the OS would never boot. I had given up on it myself, since there is a difference between what is technically possible and what is allowed by license. The only guidance I can give is that you likely would want to remove Setup from doing anything, and to manually be building the BCD for any multiboot setup. Using a partition scheme like so: Part 1: EFI Part 2: MSR Part 3: Windows 7 Part 4: Windows 8.1 or 10 Part 5: Windows 8.1 or 10 Perhaps look into using something else such as Grub4DOS for UEFI: https://msfn.org/board/topic/182107-grub4dos-for-uefi/

Windows 7 64bit works on UEFI with GPT spindle disks just fine. It is only some NAND or NVMe that can cause a problem. IMO: unless you want to use Bitlocker, a boot disk larger than 2.2 TB or a UEFI-only video card, there is no reason to enable UEFI for Windows 7.

Sure it is an A6 CPU and not an A9? Obviously, see if your installation works on another computer.

The EFI partition is the "system reserved" partition it is referring to.

For what I use of them, I find no real functional differences between 2008 R2 to 2019. As for which to use on a specific hardware platform, I would pick the OS that is certified or qualified for it, so that drivers are available and that support is available if needed.

What country am I really from?

Welcome to the MSFN!