CRACK Windows XP Live USB USB Tools (Portable)
Cora Auch
For a firmware update that is only provided as Windows executable by the vendor (Asus motherboard USB-C PD firmware here), I need to have a temporary Windows installation. All the tutorials on how to create a USB flash drive to get a temporary/portable Windows installation that I find (1, 2, 3) are using Windows tools. None seem cross-platform. However, I don't have any current Windows PC at home, it's all Linux. ? So there you have it; a chicken-and-egg problem. ?
N.B. I'm not looking for a bootable Windows installer, I need to get a running Windows install instead to perform some Administrator-enabled commands running a .exe to flash a device. Ie. the equivalent of a Linux live desktop image.
If your computer does not support a regular Windows 11 installation,it will likely boot with the Windows 11 PE version, as Windows PEversions have significantly lower hardware requirements. For instance,if your computer boots with the Windows 10 PE version, it is highlyprobable that it will also boot with the Windows 11 PE version.
Upon booting, the PE version attempts to install drivers for essentialcomponents such as graphics, sound, wireless and Ethernet cards foryour hardware, facilitating connection to a WIFI or Ethernet network.If your WIFI or Ethernet card is not recognized by the PE version,kindly Contact Us with your hardware model. We will strive toincorporate the necessary drivers in upcoming releases.
I've recently been trying to 'install' stuff a lot less on my Windows machine (I hate installers - I need to know where programs put stuff...), choosing to use portable or standalone versions of applications instead.
I put them all in a 'Programs' dir on a drive separate from my Windows partition, so whenever I reinstall, I have all my applications available with minimal effort and on the plus side, I get a nice clean setup.
Why do Windows apps still need installing? Why can't we just drag Photoshop to a folder la OSX and just have it work? Does anyone else focus on portable apps, or am I just being OCD about the whole thing?
.NET introduced the concept of app.config (almost ini files mark 2, this time with a little more structure saving developers wasting time writing manual parsers). The GAC was introduced to version shared assemblies in an attempt to prevent DLL Hell.
In Windows XP and moreso in Vista, Microsoft attempted to define the userspace as a place to store user data and configuration files in a single standard location to allow for roamning profiles and easy migration (just copy your profile) with the applications installed in Program Files.
So I guess, the reason is that "applications in windows are designed to live in one place, their shared dependencies in another, and the user specific data in another", which pretty much works against the concept of xcopying a single location.
Simple and blunt answer: it's simply a question of who has control. Most software nowadays is designed by corporate giants for the corporate or institutional environment where users are told what to do instead of telling their computers what to do for them.
Your question is extremely important because it raises a fundamental question about individual rights and freedoms that are being eroded more and more, not by tyrants like in societies of old, but by corporate greed and the need of the few to control the many.
As a matter of fact, we seem to have forgotten that the exact same people who used to decry the tyranny of giants such as IBM have become the IBMs of this day and age... Just look closely at the business practices of Microsoft, Apple and Adobe to name a few and tell me with a straight face that with their restrictive licenses are more benign than IBM's business practices were, the same IBM who, by their openness, actually led the path to the personal computing revolution...
I have been using many self contained, portable apps over the years and without exception they have proven to be the most effective, the fastest and the smallest in terms of footprint and resources and last but not least, not only are they superior to their bloatware counterparts, but most of the time, they are free as well.
It's high time for a second personal computer revolution. Enhancing portability by reducing bloat and clarifying where settings are stored, in one distinct folder on a distinct physical location on a tangible, physical medium, is one step in the right direction.
A few others have said the main reason is due to the registry. If you are talking about a device driver or some other COM component etc, then yes this may be necessary, but not for GUI applications such as Word processors or spreadsheets.
It's quite possible to write an application that either checks on start-up for required registry settings, and prompts the user for them / uses defaults. Or, as many protable apps currently do, jst let the user know that OS integration is currently limited because you are running in portable mode.
Installers often also have a lot of "knowledge" about how the application works. Then when the application changes, you often have to update the installer too. This is a classic cause of bugs/problems I've seen in my time programming.
A combination of the registry and per user storage. The registry is a critical piece, especially if your application is COM based (which requires registering, which happens in the registry). Per user storage (of configuration etc) is also an important component. The only good way to do this is to store it in some specially designed directories (see Isolated Storage).
The .Net Framework is the platform to enable this type of functionality, and mostly installers are just used because this is what normal users are used to. The same way Mac users are used to copying files into the Applications folder.
Majority of installers simply expand files into the Program Files folder and creates a shortcut. It's more a case of what users know, and often it is just to simpler to keep the process the same even if the application is portable.
An app that uses the Windows Installer system properly will have all sorts of info about it saved in the Windows Installer database on your machine, as well as quite often a cache of important parts of the setup files.
If the app breaks for some reason (something else deletes/replaces a file, registry gets corrupted, disk problems, user deletes shortcut etc) then if its an "advertised shortcut" the Installer actually checks key files and keys every time it starts up and replaces if they're not present, or you can go into Add/Remove Programs and click Repair on the app.
Many Windows applications must make use of system environments or services, such as SQL Server, IIS, WMI, security domains, Active Directory, and many others. A typical user may have no idea how to configure these, or may not even have access to them.
Applications like Microsoft Office are not single files; they contains dozens of files, executables, utilities, services, templates, plug-ins, drivers, and so on. When you install an application you can't just overwrite everything the new app uses, it has to fit in with what's already there. Windows installers do more than just copy files, they can query the system environment, run scripts and install services, and set up the machine as if they were an administrator.
At the very least, a decent installer with decompress the installation file and set up the appropriate shortcuts and make it easy to remove the program when no longer wanted. I thnk the decompression and copy is probably what takes the longest.
Most importantly, some programs need to be configured for the machine and some (I presume at least) attempt to optimize based on the machine or at least thats what adobe's dialog leads me to believe.
There are multiple desktops available for use with Fedora. Each has a slightly different look and feel and offers varying levels of customization. You can use the Fedora Workstation image, which comes with the GNOME desktop by default, and then change your environment afterwards by installing additional packages, or you can download a spin image which will give you a different environment out of the box. Visit Fedora Spins for more information.
You can also take advantage of Fedora Labs. Fedora Labs is a selection of curated bundles of purpose-driven software and content as curated and maintained by members of the Fedora Community. These may be installed as standalone full versions of Fedora or as add-ons to existing Fedora installations. Visit Fedora Labs for details.@
The official and supported tool to create a Fedora USB stick is the Fedora Media Writer utility, which was formerly known as LiveUSB Creator. See Fedora Media Writer guide in Fedora User Documentation overview.
Fedora Media Writer destroys all data on the USB stick. If you need a non-destructive write method (to preserve existing data on your USB stick) or support for 'data persistence', you can use the livecd-iso-to-disk utility on Fedora.
This method is for people running Linux, or another unix with GNOME, Nautilus, and GNOME Disks installed. Particularly, if you are using a distribution other than Fedora which does not support Flatpak, this may be the easiest available method. A standard installation of Fedora, or a standard GNOME installation of many other distributions, should be able to use this method. On Fedora, ensure the packages nautilus and gnome-disk-utility are installed. Similar graphical direct-write tools may be available for other desktops, or you may use the command-line direct write method.
The livecd-iso-to-disk method is slightly less reliable than Fedora Media Writer and can be used reliably only from within Fedora: it does not work in Windows or macOS, and is not supported (and will usually fail) in non-Fedora distributions. However, it supports three advanced features which FMW does not include:
You may use a non-destructive method to create the stick, meaning existing files on the stick will not be destroyed. This is less reliable than the destructive write methods, and should be used only if you have no stick you can afford to wipe.
b37509886e