little foxes at the keyboards little foxes making clicky-clacky little foxes on the servers little foxes all untame there's a black hat and a white hat and a grey one and fun for everyone! and they're all making clicky-clacky and they're all in your mainframe
When I was younger I was privileged to attend special classes because my doctor found out I am "severely artistic." Still, I have never allowed my learning ability to make me feel superior to the common plebs.
https://support.hp.com/ca-en/document/c01553159
https://support.hp.com/ca-en/drivers/selfservice/hp-elitebook-2530p-notebook-pc/3782222
https://smallbusiness.chron.com/disable-intel-active-management-29020.html
https://www.bhphotovideo.com/lit_files/158136.pdf EXTENSIVE HP BIOS GUIDE
https://support.hp.com/ca-en/product/hp-elitebook-2540p-notebook-pc/4138624/manuals Docs Index
http://h10032.www1.hp.com/ctg/Manual/c01824416.pdf RAID
http://h10032.www1.hp.com/ctg/Manual/c03453264.pdf BIOS (actually FOR this model...)
https://support.hp.com/ca-en/product/hp-elitebook-2540p-notebook-pc/4138624/manuals talkinga lot ab
Before Windows got its WSL swagger installing grep was cumbersome (but at least it was possible, thanks for the memories, Cygwin!)
That being said, you could count on Rando McClient's winb0x to ship with with its own take, the command line tools find:
c:\>find /?
Searches for a text string in a file or files.
FIND [/V] [/C] [/N] [/I] [/OFF[LINE]] "string" drive:][path]filename[ ...
/V Displays all lines NOT containing the specified string.
/C Displays only the count of lines containing the string.
/N Displays line numbers with the displayed lines.
/I Ignores the case of characters when searching for the string.
/OFF[LINE] Do not skip files with offline attribute set.
"string" Specifies the text string to find.
[drive:][path]filename
Specifies a file or files to search.
If a path is not specified, FIND searches the text typed at the prompt
or piped from another command.
c:\>findstr /?
Searches for strings in files.
FINDSTR [/B] [/E] [/L] [/R] [/S] [/I] [/X] [/V] [/N] [/M] [/O] [/P] [/F:file]
[/C:string] [/G:file] [/D:dir list] [/A:color attributes] [/OFF[LINE]]
strings drive:][path]filename[ ...
/B Matches pattern if at the beginning of a line.
/E Matches pattern if at the end of a line.
/L Uses search strings literally.
/R Uses search strings as regular expressions.
/S Searches for matching files in the current directory and all
subdirectories.
/I Specifies that the search is not to be case-sensitive.
/X Prints lines that match exactly.
/V Prints only lines that do not contain a match.
/N Prints the line number before each line that matches.
/M Prints only the filename if a file contains a match.
/O Prints character offset before each matching line.
/P Skip files with non-printable characters.
/OFF[LINE] Do not skip files with offline attribute set.
/A:attr Specifies color attribute with two hex digits. See "color /?"
/F:file Reads file list from the specified file(/ stands for console).
/C:string Uses specified string as a literal search string.
/G:file Gets search strings from the specified file(/ stands for console).
/D:dir Search a semicolon delimited list of directories
strings Text to be searched for.
[drive:][path]filename
Specifies a file or files to search.
Use spaces to separate multiple search strings unless the argument is prefixed
with /C. For example, 'FINDSTR "hello there" x.y' searches for "hello" or
"there" in file x.y. 'FINDSTR /C:"hello there" x.y' searches for
"hello there" in file x.y.
Regular expression quick reference:
. Wildcard: any character
* Repeat: zero or more occurrences of previous character or class
^ Line position: beginning of line
$ Line position: end of line
[class] Character class: any one character in set
[^class] Inverse class: any one character not in set
[x-y] Range: any characters within the specified range
\x Escape: literal use of metacharacter x
\ Word position: end of word
For full information on FINDSTR regular expressions refer to the online Command
Reference.
It is also possible to leverage the Windows Explorer shell by navigating to a folder containing the file or files you wish to search and entering your query into the search box integrated into the top-right corner of the window. You can improve the results and reduce query time/resource load by filtering the file type or file name with the file: modifier and conventional Windows filename wildcards like ?, _ and *. For example, to limit the query to plaintext files one would append file: *.txt after the search term(s), separated by a space.
Explorer's Search functionality is virtually identical from v.7 through 11.
I compiled a small testing sample of various formats and some ZIP archives out of the first two acts of Shakespeare's Antony and Cleopatra, with gratitude to MIT.
Explorer didn't adopt Ribbon graphical widgets until v. 2008 but Folder Options has managed searching inside ZIP files since XP.
The ability to search inside of ZIP files appeared with the introduction of Windows XP and its broad, built-in support abstract "Compressed Folders" based on the format.
Cabinet (.CAB) Files support multiple compression algorithms but are usually encoded similarly to .ZIPs
...Searching inside archive files can also be enabled through Folder Options which can be accessed via Explorer's View Tab > View Ribbon > Options Button or...
A side-by-side comparison of Windows 10's apparently stand-alone File Folder Options and File Explorer's Folder Options
...you can modify the exact same settings in what appears to be the exact same interface, other than the title: File Folder Options which is easily dredged up by way of the the taskbar's integrated Search Bar or the reduced-width Search Button or, if you have wisely deleted it altogether: Meta (Windows) Key & Start Typing...
I personally tend to disable Indexing, especially on SSD/Flash backed storage.
For improved performance going forward you may wish to take this opportunity to (same as above) Search for Indexing Options then click the Advanced Button > File Types Tab and find the 'zip' Entry and change the How should this file be indexed? radio button to Index Properties and File Contents; rinse and repeat for any of the other file formats Windows thinks it can handle...
WIndows has an impressive ability to search the contents of many formats./figcaption>
Unfortunately Windows does not support Search and Replace natively. Therefore if you need that ability in conjunction with multi-file search you must adopt a third party solution.
If one is to use a GUI-first operating system I think it's only appropriate to exercise its strengths; running operations against groups of files should be any GUI's cakewalk, especially with some arbitrary file and recursive directory selection/exclusion. I can't tell you how much I wish I could slap a mouse and control/shift keys on the Linux find command some days (fortunately KATE has me covered where interfacing through NFS/FUSE sshfs is feasible). If you often find yourself having to search multiple files at once, as one certainly does in analytical, systems/network administration and software development roles, I have recently had cause to evaluate these two free, GPLv3 solutions for Windows environments:
Side-by-Side Comparison of grepWin and AstroGrep
grepWin (Downloads | Source @ GitHub) will only run on Windows 7 SP1 and above. You have the option of 64 and 32 bit conventional installers or a 1.1MB (uncompressed) portable executable which makes it perfectly suited to bootable USB and DVD environments, PXE or staging on a remote server or site (like this one! :o) for rapid access in the field. Supports PERL-inspired (PCRE) Regular Expressions (RegEx) and recommends a third party a tutorial here, while the software has a powerful on the CLI.
grepWin substantially outperforms AstroGrep
The first thing I noticed running grepWin against my sample set was an at-least 2x possibly three-fold reduction in processing time compared to AstroGrep, having run the same search pattern with it a dozen times prior. An identically matching set across text and RTF files was acquired, only among the plain text (*.TXT) and rich text (*.RTF) files. String replace functionality was fast and I was admonished both to enable backups and disable UTF-8 mode (which I had changed from the default off value; while that shouldn't have caused any issues it is nice to know that an appropriate level of hand-holding is implemented before executing a potentially destructive and ultimately embarrassing act.
AstroGrep: Does what it claims to. And not a penny more.
AstroGrep (Downloads | Source @ SourceForge) has a long history and an established userbase. AstroGrep adds a context menu to Explorer when you right-click on directories while grepWin adds a context menu for individual files. Even if your main use-case substantially differentiates between their featuresets or if the lack of replace functionality is a deal-killer (as it sadly is for me) that could be enough utility to warrant installing both.
Out of the box AstroGrep was able to parse the plain text (*.TXT) and rich text format (*.RTF) files from my sample set. Enabling the "File Handler" plugin added the two OpenDocument Format (*.ODF) files but got nothing out of the HTML, PDFs or the files in archives (as expected). Unfortunately, while it could see the matches I could not: despite the plugin apparently parsing the ODF format enough to find text strings, the reproduction inside of AstroGrep's interface was binary and largely unintelligible.
According to this thread from 2017 that appears to document a discussion between to developers a Replace functionality may have been planned but in the intervening five years apparently that has gone nowhere. A test version of the app (in "portable" form) is provided in the thread; after completing your search the greyed out "fast-forward" button at the bottom of the search form in the left panel of the UI becomes slightly less grey; clicking on it reveals the Replace field. While the replace procedure did work, it only worked for my plain text (*.TXT) files; the rich texts and ODF remained unchanged.
I was hoping I would be able to recommend both applications but the lack of a replace function in AstroGrep - at least for now - cements my personal endorsement with winGrep.
The following are some bootable Windows (WinPE) environments & builders/utilities, Linux-based recovery/utility LiveCD/LiveUSB images and some general purpose multiple image boot stick tools I have come across and want to come back to when I have the time but (for the most part) have not tested yet - so before using any of them be sure to perform due diligence. I have not and have no idea how trustworthy or effective any of the following projects, sites and executables are; do not consider this list to be an endorsement. As such this list doesn't belong on my Favourite Windows Software page so I'm putting it here for our (my) benefit. I will come back to update this page once I have something educated to say. Feel free to let us know your experience - once I finish programming the comments thing. Some day. Never. Maybe. Gesundheit.
According to the Wikipedia article on WinBuilder this package used to be available at https://winbuilder.net but at the time of this writing the domain redirects to https://reboot.pro probably the result of expired domain sniping. Which may be for the best: it appears to be a relatively active mutual support community that hosts downloads for numerous delicious looking utils and some member-rolled bootable images. No idea as to the safety of this site or its downloads, you may prefer to find the official home pages for those utilities before downloading - but as far as WinBuilder is concerned this seems (at present) to be the best place to get it at a glance. The wiki handily links to a bunch of bootable images that were created with WinBuilder.
A WIM file is saved in a file-based imaging format that was introduced with Windows Vista. It allows a single disk image to be deployed to multiple computer platforms. WIM files are used to manage files such as drivers, updates, and components without booting the operating system image.
Ahhh. So that's how the wind0ze buggers do "slipstreaming". https://theoven.org/ seems strongly correlated with support for this utility.
Ventoy is an open source tool to create bootable USB drive for ISO/WIM/IMG/VHD(x)/EFI files.
With ventoy, you don't need to format the disk over and over, you just need to copy the ISO/WIM/IMG/VHD(x)/EFI files to the USB drive and boot them directly.
You can copy many files at a time and ventoy will give you a boot menu to select them (screenshot).
x86 Legacy BIOS, IA32 UEFI, x86_64 UEFI, ARM64 UEFI and MIPS64EL UEFI are supported in the same way.
Most type of OS supported (Windows/WinPE/Linux/ChromeOS/Unix/VMware/Xen...)
Dang. I need the hell out of this...
I would make the observation that you will want to include version numbers for your isos in the boot menu.
...a Linux system rescue toolkit available as a bootable medium for administrating or repairing your system and data after a crash. It aims to provide an easy way to carry out admin tasks on your computer, such as creating and editing the hard disk partitions. It comes with a lot of Linux system utilities such as GParted, fsarchiver, filesystem tools and basic tools...
What I think they should mention up front is that it includes PhotoRec which makes this the ISO I'll be reaching for next time a grampa drive dies.
UNetbootin allows you to create bootable Live USB drives for Ubuntu and other Linux distributions without burning a CD.
You can either let UNetbootin download one of the many distributions supported out-of-the-box for you, or supply your own Linux .iso file.
Clonezilla is a modern, open-source and more fully featured disk imaging/cloning suite than the long-defunct Norton Ghost which I used to see running in the shop at all hours in my youth. It is included as part of Diskless Remote Boot in Linux (DRBL) https://drbl.org/ for turn-key network booting
ophcrack has a livecd!!! Get it from https://ophcrack.sourceforge.io/download.php and be sure to select the correct image for your target version of Windows to ensure it comes with the correct rainbow tables or download the table-less image and choose a specific table from https://ophcrack.sourceforge.io/tables.php for better coverage (many will not fit on smaller media/drives). NOTE If you already have NT or LM hashes extracted and ready to crack you can quickly just plug them into the rainbow tables live via their site at https://www.objectif-securite.ch/en/ophcrack!
If you don't care to crack Windows account passwords you can simply disable them; this feature is widely available on distributions like Hiren's but since that hasn't been officially maintained in years and it doesn't look like a supported feature of SystemRescue (above) I feel I should include https://www.supergrubdisk.org/rescatux/ and https://pogostick.net/~pnh/ntpasswd/.
The Microsoft Desktop Optimization Pack (MDOP) "is available as an additional subscription for Software Assurance customers" which means you have to pay for it. Apparently. Anyway it comes with the Diagnostic and Recovery Toolkit (DaRT) which is a bootable image full of recovery tools. However, I am way more interested in the virtualization features...
Another official Microsoft offering was the Windows to Go Live USB functionality available from Windows 8 Enterprise through Windows 10 Enterprise until the May 2020 update
As we have known for some time Windows 11 will install from bootable DVD or USB stick (but not Windows Update) on virtually any x86-64 (aka amd64 - I have noticed in some documents Microsoft is calling this architecture "IA 64-bit" which is trop droll considering it was Microsoft's pressure on AMD to innovate the 64 bit 80x86 platform at Intel's expense at a time when IA64 clearly referred to the ill-fated Itanium architecture) CPU, including for a short and embarrassing moment where it would "officially" be happy to install on Pentium 4 661s. The catch is that new Windows Updates will not be delivered to so-called unsupported systems which sounds rather pointless to me; as I recall Windows Updates are made available to the public freely as individual executable installers from their Knowledge Base and if a dozen people haven't already written an automatic scraper for Windows 11 updates I would be utterly shocked and disappointed.
Unfortunately there are a few more minimum requirements that the installer checks for that may get in our way, particularly if we are trying to simply preview what is to come in this new version from the safe confines of a Virtual Machine instead of risking an otherwise perfectly good and still supported Windows 10 installation at this early stage in its release:
System must present a Unified Extensible Firmware Interface (UEFI) instead of a Basic Input/Output System (BIOS) and further:
A Trusted Platform Module meeting the version 2.0 specification must be provided by a discreet chip/module, as a component of the integrated chipset or as a firmware implementation. Newer machines should be able to enable their TPM if it appears to be missing.
At least 4GB RAM must be available to the system. This could be a problem on bare-metal hosts with 4GB of RAM but a portion allocated to shared graphics memory.
I think it's interesting that Microsoft would impose such a strict requirement on RAM while in many areas it has embraced virtualization technology and employed it in impressive, creative ways to make the Windows operating system vastly more secure, relevant and capable than it ever has been before. It seems in these early days at least Microsoft is aiming for a very smooth, very optimal first impression among early adopters at the expense of bringing more budget-constrained users and virtualization-backed service providers along to this new paradigm of sophisticated security measures, Android application compatibility and more.
IMPORTANT UPDATE!17-03-2025: It has come to my attention after digging for Rufus' apparently (at present) missing Fido ISO downloading PowerShell script that a new method of installing Windows 11 has emerged which is superior to this initial kludge. Flyby11 is a PowerShell-based patcher that utilizes Windows Server edition facilities to install Windows 11 while bypassing all but the POPCNT requirement (affecting only those CPUs Nehalem/Phenom II and older (i.e. Core 2). Download the latest versions of Fido and Flyby11 directly from their GitHub release pages (then don't forget to swing back to README.md to rtfm :3):
That said, they couldn't stop us if they put their backs into it, and we're going to leverage some handy functionality they left in the installer for us that will shimmie right past the most egregious of its hardware requirement checks. Upon running the installer you have likely encountered the error:
This PC Can't Run Windows 11
This PC doesn't meet the minimum system requirements to install this version of Windows. For more information visit https://aka.ms/WindowsSysReq
Anything you can do I can do better.
Use the Back button embedded (practically camouflaged) in the top left corner of the window's title bar to return to the edition selection menu.
The one that doesn't get in my way, please.
From here you can press Control + F10 on your keyboard to launch a command prompt.
We're taking command of this operation!
Type regedit and hit Enter to launch the registry editor.
The registry is the key.
Navigate to HKEY_LOCAL_MACHINE\SYSTEM\Setup. Right-click on the Setup key and select New > Key. Name the new key LabConfig.
Bypass is DE-WORD!
Right click on the LabConfig key or anywhere in the right-hand pane while it is selected. Under New click on DWORD (32-bit) value and create the following values:
BypassRAMCheck
BypassSecureBootCheck
BypassTPMCheck
I value control over my own system.
Now double click on each value or Right Click/press the Context Menu key and Modify each item to contain the value 1 (integer one).
I put a hex on you! Now you're mine~
Exit the registry editor and carry on with your installation as usual.
How do you like me now? :/
Hopefully at this point your installation continues without a hitch. It's not certain whether Microsoft will stick to these draconian requirements in the future or ease them up to make Windows 11 a more realistic virtualization candidate (among many other great reasons) but one thing is certain: there will always be a way around them - whether provided as a somewhat convenient override by Microsoft themselves or through unofficial channels as part of yet another arms race.