Tripredacus

Welcome to the MSFN!

When Microsoft uses the term "install" they are referring to Setup.exe and an unaltered installation. They also use terms in relation to what is supported, not what is technically possible. MSFT has also told me you can't install DOS with WDS which is not true. Is it a lie or is it just that it is something that they do not support? What about the fact that it is commonly accepted you can't boot both 32bit and 64bit (dual/hybrid) on the same hardware in EFI mode, despite the fact that there are boards where this is possible? The capabilities of being able to boot (or use) Windows in unsupported configurations is solely dependent on the hardware and what the firmware allows. I see in your examples you only did this on a virtual machine. Repeating this test on different models of actual hardware may yield different results.

As a bare minimum, I usually run a setup like so: - Chromium based browser, typically Iron but sometimes Chrome. - Mozilla based browser that supports NoScript. - Malwarebytes free version for impromtu scanning - CrystalDiskInfo for checking hard disk health. - 7zip for opening archives. I do not use an actual anti-virus software on any machine. Defender (built-into Windows) does well enough and other anti-virus are not worth the overhead on the system. Hardening the system via browser settings/add-ons and using the firewall (in Windows or as hardware) properly (using alllow-list standpoint) is much better than running with reckless abandon and hoping your anti-virus program will save you. I also never use actual email clients, only webmail.

Its as if you need to get a dedicated phone just for the bank website. Like one that isn't even on a plan and you connect only using wifi or something.

Is that for all updates or just the ESU Licensing Preparation Package?

If you know the kb numbers, you can get updates for the Embedded SKUs from the Update Catalog: https://www.catalog.update.microsoft.com/Home.aspx IDK if they will install to the retail OS, I haven't had the need to install an update in awhile.

On a well used system, trying to dig through the dir structure manually is a real pain. The visualisation programs are so much easier for that task.

There is a Treesize for Win9x as well, all the way at the bottom of this page: https://www.jam-software.com/treesize_free The UI is reminiscent of some Norton program that did/does the same thing, but I can never remember the name of it.

Which HAL is installed? This shows up in Device Manager in the Computer section. I have seen a wrong HAL in XP cause a MP appear as a UP in both Device Manager and Task Manager Performance tab. https://www.betaarchive.com/wiki/index.php/Microsoft_KB_Archive/309283

It is invalid parameter. Also not aware of this IE9-vista.msu. Usually you install IE9 by way of installing the 3 .msu pre-requisite updates and then running the .EXE. In this scenario, IE9 is not integrated into the image, rather is installed during first boot. There are also compatibility issues regarding Vista where you may need to use the WAIK for the OS version. WAIK 1.1 for Vista SP1 servicing. Also that you may need to use peimg to service images instead of DISM. Verify /english exists. /image is for a file not a mount point. Make sure you are using the Deployment Tools Command Prompt.

Want to know the actual error text shown in the Deployment Tools CMD. You'll also want to find the relevant log entries that line up with the cmd you run in the DISM.log file. To make things easier, do not do a batch run, just use 1 file.

I don't hate it, I just prefer not to use it if I don't have to.

DISM can integrate .msu and .cab files. What is the error you get with DISM?

Ah just looking now, it seems XP doesn't natively support the manifest, and will ignore it. Apparently, Vista also. So perhaps this is a dead end. That, however, doesn't invalidate that Common-Controls v6 is required. I would run depends on the setup.exe (formerly setup.tmp) and see if anything else is missing. Otherwise, it is possible you can run into an issue with the certs that are in there as well. Since the issue isn't really to do with the original setup, the one that uses the .iss. But perhaps, you can still rebuild the whole thing since you have both the files and the .iss. You'd need to change all those minVersion values. When doing this, do not include the setup.tmp/exe from before, perhaps the rebuild will create a new one. And see about using an older version that v6, if you use v6 you probably don't have to change the .iss. I haven't used inno setup in a long time.

This setup requires the Common Controls for Vista, this is specified in the manifest. It may require .net Framework 1.1, 2.0 or 4.0. Also the setup does not contain the installation files. There must be a different file that can be opened, or an archive that is included. It is safe to remove those attachments now.

Microsoft hasn't had an official WinPE distribution program since 2011, and as such any links to a WinPE posted on MSFN cannot be posted. If anyone has information regarding the resumption of a redistribution policy, you can send it to me for review.

That wouldn't be a good idea.

Is the split files complete? The forum only shows 6-9. Perhaps do not put this .tmp file onto the forum at all and put it somewhere else like a Google/OneDrive. See if you can get the insides using Innounp: http://innounp.sourceforge.net/ Note: can't force https on that link. With the .iss file you have, you can see exactly what the setup is going to do, and so you can modify it. For example, you may want to remove everything except the last line in [Run] section and everything except "createdesktopicon" in [Tasks]. For the MinVersion, XP should be set to 5.0. My reference .iss file is for a setup that is for XP and that is what it has. Example from that file: Source: "{app}\setup.exe"; DestDir: "{app}"; MinVersion: 0.0,5.0; Flags: ignoreversion Since you have the .iss file, and can extract the files from the archive, you can repackage it using a modified .iss file if you wanted to create an XP installer.

It has nothing to do with what we think, rather the governments for the countries our users and the website is in. I was not around when rule 1 came into being, so I cannot say whether is was just decided on or if it came into being due to a reaction for something. The redistribution portion certainly did come in as a reaction to something. Xper decided it is better to just not allow unauthorized redistribution rather than having to constantly deal with other companies' legal departments.

Is the setup within the setup also an Inno package, or something else? The original package built with Inno, should have an .iss file, which is the script file that inno uses to install the package. An OS version can be specified in there. Also, either program's manifest can be blocking the install.

Ok the board has 3 mechanical x16 slots but two of them are 4x electrical. The video card should be installed in the slot closest to the CPU. I do not think that the card being a PCIX 4.0 in the 3.0 electrical 16x slot would cause the issues you describe. You wouldn't be able to get everything out of the card while it is in that board, but it shouldn't be unusable. As for the TDP, it may be that with Win 10/Linux Turbo Boost isn't being used at idle, while in Win7 it is. May be due to settings, drivers or lack of drivers.

Things change, new ideas come about, people like to relive old times, etc. Not closing topic.

Gigabyte makes at least 3 video cards with that chip and you didn't post your motherboard make/model.

Since you still haven't posted specs, I can only ask: is there any mechanical vs electrical considerations with the motherboard?

I'd take the route of calling the bank to complain about it. I would hate it if my bank went that route. I do not have anything on my phone connected to financials in any way and prefer to keep it that way.