Jump to content

Informática

Conéctate para seguir esto  

Sub Category  

161 archivos

  1. Ghidra

    A software reverse engineering (SRE) suite of tools developed by NSA's Research Directorate in support of the Cybersecurity mission.
    Platforms Supported
    Microsoft Windows 7 or 10 (64-bit) Linux (64-bit, CentOS 7 is preferred) macOS (OS X) 10.8.3+ (Mountain Lion or later) NOTE: All 32-bit OS installations are now deprecated. Please contact the Ghidra team if you have a specific need. Minimum Requirements
    Hardware
    4 GB RAM 1 GB storage (for installed Ghidra binaries) Dual monitors strongly suggested Software
    Java 11 64-bit Runtime and Development Kit (JDK) (see Java Notes) Free long term support (LTS) versions of JDK 11 are provided by: AdoptOpenJDK Amazon Corretto
    Installing Ghidra
    To install Ghidra, simply extract the Ghidra distribution file to the desired filesystem destination using any unzip program (built-in OS utilities, 7-Zip, WinZip, WinRAR, etc)
    Installation Notes
    Ghidra does not use a traditional installer program. Instead, the Ghidra distribution file is simply extracted in-place on the filesystem. This approach has advantages and disadvantages. On the up side, administrative privilege is not required to install Ghidra for personal use. Also, because installing Ghidra does not update any OS configurations such as the registry on Windows, removing Ghidra is as simple as deleting the Ghidra installation directory. On the down side, Ghidra will not automatically create a shortcut on the desktop or appear in application start menus. Administrative privilege may be required to extract Ghidra to certain filesystem destinations (such as C:\), as well as install the Ghidra Server as a service. Ghidra relies on using directories outside of its installation directory to manage both temporary and longer-living cache files. Ghidra attempts to use standard OS directories that are designed for these purposes in order to avoid several issues, such as storing large amounts of data to a roaming profile. If it is suspected that the default location of these directories is causing a problem, they can be changed by modifying the relevant properties in the support/launch.properties file. Java Notes
    Ghidra requires a supported version of a Java Runtime and Development Kit on the PATH to run. However, if there is a version of Java on the PATH that Ghidra does not support, it will use that version of Java (if 1.7 or later) to assist in locating a supported version on your system. If one cannot be automatically located, the user will be prompted to enter a path to the Java home directory to use (the Java home directory is the parent directory of Java's bin directory). This minimizes the impact Ghidra has on pre-existing configurations of Java that other software may rely on. If Ghidra failed to run because no versions of Java were on the PATH, a supported JDK should be manually installed and added to the PATH. The following steps outline how to add a JDK distribution to the operating system's PATH. Windows: Extract the JDK distribution (.zip file) to your desired location and add the JDK's bin directory to your PATH: Extract the JDK: Right-click on the zip file and click Extract All... Click Extract Open Environment Variables window: Windows 10: Right-click on Windows start button, and click System Windows 7: Click Windows start button, right-click on Computer, and click Properties Click Advanced system settings Click Environment variables... Add the JDK bin directory to the PATH variable: Under System variables, highlight Path and click Edit... At the end of the the Variable value field, add a semicolon followed by <path of extracted JDK dir>\bin Click OK Click OK Click OK Restart any open Command Prompt windows for changes to take effect Linux and macOS (OS X): Extract the JDK distribution (.tar.gz file) to your desired location, and add the JDK's bin directory to your PATH: Extract the JDK: tar xvf <JDK distribution .tar.gz> Open ~/.bashrc with an editor of your choice. For example: vi ~/.bashrc At the very end of the file, add the JDK bin directory to the PATH variable: export PATH=<path of extracted JDK dir>/bin:$PATH Save file Restart any open terminal windows for changes to take effect In some cases, you may want Ghidra to launch with a specific version of Java instead of the version that Ghidra automatically locates. To force Ghidra to launch with a specific version of Java, set the JAVA_HOME_OVERRIDE property in the support/launch.properties file. If this property is set to an incompatible version of Java, Ghidra will revert to automatically locating a compatible version. Note that some Java must still be on the PATH in order for Ghidra to use the JAVA_HOME_OVERRIDE property. This limitation will be addressed in a future version of Ghidra.
  2. Romulus Rom Manager

    ROM Manager developed by F0XHOUND.
    Features
    Romulus is able to import all kind of know DAT files like Clrmame pro OLD and XML format, Romcenter, Offlinelist, MESS softlists or import using a MAME based EXE.  DAT files can be imported as Zip, Rar, 7z or uncompressed. Offlinelist DAT information loaded to able to automatic download images or update complete DAT if update is available, can be change the filename description params like Offlinelist original application.  Multiple loaded profiles at same time displayied in tabs. Can Scan and Rebuild files from a selected directories and fix them, this process can be in Zip, Rar, 7z or uncompressed. If DAT information is available in scan or rebuild process can be in Split/Merged, Split/Non merged or Not Split filemode. Scan and Rebuild can be done in a batch automatic mode. Configure and run emulators added the correct params for the selected file. Reports of profiles or files information with a different options and formats to export ( HTML, DOC, TXT ). Statistics can be displayied to know the status of your files. Log information for important processes and save log option. Updater option to know changes and download  Different languages to select ( Work in progress ),  Many others.
    < REQUIREMENTS >
      Really Romulus can be runned in every computers with Windows XP, Vista, 7, 8, 8.1, 10 and probably in    future Windows versions including 64bits releases.    Some users tested Romulus using WINE (Windows interpreter for different OS), and reports works fine.   Overall speed is different in computers with quick CPUs, more RAM memory or quick Hard Drives.   Romulus was tested under different computers speed, and the result is...   Minimum Requirements
      INTEL or AMD Single Core Processor of 1Ghz   RAM 2Gb   HDD with some Mb free, but enought for Database that will be increasing when you add new DAT files.   HDD formated in NTFS/ExFAT is required for more than 4Gb databases.   Recommended Requirements
      INTEL Core I5 or Ryzen5 2Ghz processor or higher   RAM 8Gb   SSD with some Mb free, but enought for Database that will be increasing when you add new DAT files.   HDD formated in NTFS/ExFAT is required for more than 4Gb databases. Thx to
    Translators : F0XHOUND, Kludge, SpaceAgeHero, Thallyrion, Kaito-Kito, Xiao, Caboteta, Squalo, Jangminsoo, Agus, xlmldh, Michip, Elijah067 Betatesters : SpaceAgeHero, Kaito Kito, Mr Ravik, Thallyrion, Grinderedge, Elfish, EmuLOAD, Maero, Xiao, xTMODx, Agus, ToniBC, RowlaxX
  3. Karabiner Elements

    Karabiner-Elements is a powerful utility for keyboard customization on macOS Sierra or later.

    Easy to use
    You can configure simple key mappings from GUI. Powerful
    There are many powerful, predefined rules. Diamond cursor Emacs key bindings anywhere Vi key bindings Prevent unintended command-q Mouse keys You can import them from the Internet. Flexible
    You can write your own rules if you want to modify existence rules or create new rules from scratch.
  4. GPEdit - Editor de directivas de grupo local para Windows 10

    La versión Home de Windows 10 no viene por defecto con el Editor de directivas de grupo local, pero se le puede instalar por separado y así gestionar algunos aspectos relacionados con licencias, certificados y demás.
    Tan sencillo como descargar este archivo, descomprimirlo y ejecutar el GPEDIT.bat como administrador. Se nos abrirá una línea de comandos e iniciará la descarga e instalación de los paquetes necesarios.

    Una vez hecho esto ya podemos ejecutar el Editor de directivas de grupo local tecleando "gpedit.msc" en Inicio -> Buscar.
  5. ViDL

    ViDL is a free Mac app that allows you to easily download videos from YouTube and hundreds of other websites for offline viewing.
    It is based on the popular youtube-dl command line tool, but much easier to use, especially with videos/playlists that require a login (like your personal "Watch Later" list).

    Browser Integration
    ViDL includes a browser extension for Safari, and a bookmarklet for other browsers, so you can download a video directly from a page you're viewing.
    In-App Browser for Logins
    Some videos or playlists require a login before you can view or download them. ViDL can use login sessions (cookies) from an integrated web browser, so you can log in to e.g. YouTube to download your personal Watch Later list, private videos, etc.
    Playlist Download
    You can easily download entire playlists from YouTube (just enter the playlist URL), or pick and choose from the list of thumbnails.
    Download Audio
    ViDL can optionally extract the audio track from any video you download (or, depending on the website, only download audio, e.g. from SoundCloud).
    by OMZ Software.
  6. Big Sur Micropatcher

    A primitive USB patcher for installing macOS Big Sur on unsupported Macs.
    By the way, if you have a Mac Pro, Big Mac by StarPlayrX is another patcher worth considering. For 2008 Mac Pros (MacPro3,1) in particular, Big Mac is clearly a better option than this patcher (at least for now).
    Thanks to the following people for their hard work to get Big Sur running on unsupported Macs:
    ASentientBot for developing the Hax series of installer patches which are so incredibly helpful for installing Big Sur on unsupported Macs, as well as for his patch to NVDAResmanTesla.kext which allows the GeForce Tesla (9400M/320M) framebuffer to work in Big Sur. jackluke for figuring out how to patch the Recovery USB to bypass compatibility checks and AMFI enforcement in the absence of NVRAM boot-args settings. highvoltage12v for developing the first 802.11n Wi-Fi patches for Big Sur (no longer used by default, but still available through the --wifi=hv12v-old and --wifi=hv12v-new options for patch-kexts.sh), as well as patches used for Metal GPU support on 2011 iMacs. ParrotGeek for developing the LegacyUSBInjector kernel extension that allows USB to work on various pre-2011 Mac models, and for creating the "trampoline" that allows the installer to be patched at runtime without first running Terminal commands. testheit for describing how to use a kmutil feature that I was previously unaware of. This turned out to be a good way to make LegacyUSBInjector function under Big Sur, and more generally and more importantly, it was absolutely essential for improving overall patcher reliability. Ausdauersportler for integrating patches for iMac Metal GPU support. In addition, thanks to Ben Sova, MachInit, johncaling40, and Travis Parker for their contributions to this patcher.
    This documentation is more thorough than for previous versions of this patcher, but it may still be incomplete. Remember that you do this at your own risk, you could lose all your data (it's your responsibility to do a Time Machine backup first!), expect bugs and crashes, and Big Sur is still under development (as is this patcher).
    I repeat, do a Time Machine backup before upgrading!! Big Sur changes how Time Machine backups are done, and I have heard that it is not possible to use previous versions of macOS to recover data from Big Sur's Time Machine backups. (I have created Time Machine backups with Big Sur, and I have restored them using Big Sur, but I have not yet tried to access Big Sur Time Machine backups using previous macOS releases.)
    Compatibility of various Mac models
    Note that this information is incomplete and may not be 100% correct yet, but I'll add more information over time and fix any errors as I learn about them.
    Also, note that Macs without Metal GPUs (basically 2011 and earlier Macs, except for Mac Pros and iMacs with upgraded GPUs), "no graphics acceleration" is a tremendous, almost exponential, slowdown. For instance, consider a simple benchmark, simply minimizing a Safari window:
    Late 2012 13" MacBook Pro: <1 second Early 2011 13" MacBook Pro: 13 seconds Late 2009 13" MacBook: 23 seconds Keep in mind, Mojave and Catalina will probably receive security updates until roughly September 2021 and September 2022 respectively (give or take a month), so most users do not need to urgently upgrade to Big Sur.
    Mostly compatible Mac models:
    If you have a 2013 or later Mac, please check Apple's official list of supported Mac models (search the page for "See if") first, to make sure that you actually need this patcher. By the way, with the exception of Mac Pros, all of the Macs in this section officially support Catalina. This section is basically "Macs without official Big Sur support but with Metal support", with the exception of pre-2012 iMacs that have upgraded GPUs. (In fact, a 2011 iMac with upgraded GPU is almost equivalent to this category. Earlier iMacs may have compatibility problems caused by other components; see below.) Late 2013 iMac: Everything should work (and, after step 14, you're finished -- no need for step 15 and later). Note that there have been some reports of very poor performance with Fusion Drives on this model when running Big Sur, which may be why Apple does not support Big Sur on this model. 2010/2012 Mac Pro: I have received positive feedback about this patcher, but I do not know which features work perfectly and which don't. If I had to guess which features might be problematic, I would guess sleep and Wi-Fi. patch-kexts.sh (step 15) should fix Wi-Fi, but I don't know what effect it might have on sleep. (You should upgrade the graphics card, as you would for official compatibility with macOS Mojave.) 2009 Mac Pro: Once it's flashed to MacPro5,1 firmware, it should be equivalent to a 2010/2012 Mac Pro. (As with those, you will want to upgrade to a Mojave-compatible graphics card.) However, note that some people have had their flashed MacPro4,1s enter boot loops during installation. We don't yet know what causes this or why it only happens sometimes. Other 2012/2013 Macs: Most things should work after the initial installation, except for Wi-Fi (unless you have upgraded to an 802.11ac Wi-Fi card) or possibly GPU switching (on 15" MacBook Pros). Step 15 of the installation process fixes Wi-Fi support, but GPU switching may not yet be a solved problem. Partially compatible Mac models:
    Most models that officially support High Sierra, but not Mojave, fall into this category. The exceptions are the Mid 2010 15" and 17" MacBook Pros (see the Incompatible category below), and possibly the Late 2009/Mid 2010 iMacs (see the "Unknown status" category below). Note that 2009-2010 iMacs that have been upgraded with Metal GPUs also need certain kext patches which are not (yet?) provided by this patcher. 2011 Macs: Several features may not work after initial installation (after step 14 finishes), including sleep, screen brightness control, Wi-Fi (unless you have upgraded to an 802.11ac Wi-Fi card), and graphics acceleration (unless you have upgraded the GPU in a 2011 iMac). With the exception of a 2011 iMac with upgraded GPU, no 2011 Mac models have graphics acceleration under Big Sur. Make sure to use the --2011 command line option in step 15. This fixes sound and Wi-Fi on all 2011 Macs. On 13" MacBook Pros it also fixes sleep and brightness control, and installs the correct Intel framebuffer driver (this is still unaccelerated, but it still increases speed somewhat -- enough to make full-screen YouTube in Safari work with very few frame drops, although this pegs both CPU cores). For 15" and 17" MacBook Pros, disabling the discrete GPU will probably increase performance, and sleep and brightness control probably won't work without disabling it. (That isn't to say that sleep and brightness control will necessarily work even with the discrete GPU disabled -- but it might possibly work if you have a way of disabling the GPU that also keeps sleep and display brightness functional in a dosdude-patched Mojave or Catalina.) MacBook Airs should be equivalent to the 13" MacBook Pro in terms of compatibility with Big Sur and this patcher. Mid 2010 white MacBook, 2010 13" MacBook Pro, 2010 MacBook Air: In addition to the features which don't work after initial installation on the 2011 13" MacBook Pros (Wi-Fi, sound, graphics acceleration, sleep, display brightness control), Ethernet doesn't work. The --2010 option for patch-kexts.sh (step 15) installs fixes for Wi-Fi, sound, and Ethernet, as well as drivers that enable the GeForce Tesla (9400M/320M) framebuffer (thereby fixing sleep and display brightness control). The framebuffer driver does not provide acceleration; the lack of graphics acceleration plus the relatively slow Penryn CPU means performance is sluggish. On at least some of these models, step 6 may fail with errors. Late 2009 white MacBook, Late 2009 21.5" iMac, 2010 Mac Mini, (if equipped with Core 2 Duo) Late 2009 27" iMac: In addition to the features which don't work after initial installation on the 2011 13" MacBook Pros (Wi-Fi, sound, graphics acceleration, sleep, display brightness control), Ethernet and USB 1.1 also don't work. The --2010 option for patch-kexts.sh (step 15) installs fixes for Wi-Fi, sound, Ethernet, and USB, as well as drivers that enable the GeForce Tesla (9400M/320M) framebuffer (thereby fixing sleep and display brightness control). The framebuffer driver does not provide acceleration; the lack of graphics acceleration plus the relatively slow Penryn CPU means performance is sluggish. Also, the installation has to be performed on a newer Mac first (basically a 2010 or newer Mac, or a 2009 or later Mac Pro), with patch-kexts.sh --2010 run on that same newer Mac, then moved over to the old Mac (via either a hard drive/SSD transplant or by using a USB enclosure or USB hard drive/SSD). Otherwise, the installer will boot because USB 2.0 works, but the keyboard and trackpad won't work because USB 1.1 doesn't work. USB support in the installer for these Macs is planned for a future patcher release. Potentially incompatible Mac models:
    Late 2009 27" iMac: Compatibility will vary based on the CPU. If your Late 2009 27" iMac has a Core 2 Duo CPU, then it is equivalent to a Late 2009 21.5" iMac (see above). If it has a Core i5 or i7, CPU, then it is equivalent to a 2010 iMac (see below). Incompatible Mac models:
    Any Macs with a pre-Penryn CPU. Basically, this means the original MacBook Air as well as all 2006/2007 Macs (except for iMacs with upgraded CPUs). Currently not supported by this patcher, but future support may be possible:
    2010 15"/17" MacBook Pro, 2010 iMac, (if equipped with a Core i5/i7) Late 2009 27" iMac: A fix has been created, but it requires OpenCore. Even if OpenCore eventually turns out to be absolutely required for these Macs, a future release of this patcher may still be helpful in providing support for these Macs' hardware. Macs which have a Penryn CPU but which do not officially support High Sierra: These include pre-2008 iMacs with upgraded CPUs, as well as all 2008 and most 2009 Mac models (any 2009 models not listed above). All of these require "legacy USB" support, just like (for instance) 2010 white MacBooks. Once support for those MacBooks is improved in a future patcher release, perhaps support for some of these Macs will be worth revisiting. Without a Metal GPU upgrade (certainly possible on 2008 Mac Pros and possibly iMacs, but not possible on the MacBooks and Mac Minis), these are expected to be unusably slow. As mentioned at the top of this README, 2008 Mac Pro owners should use StarPlayrX's Big Mac patcher instead of this patcher. Other important information to know before upgrading or installing
    I strongly recommend that you create, and hold onto, an installer USB for an older version of macOS, perhaps one that is supported on your Mac (so that it can run without the use of a patcher). Or, at the absolute minimum, practice booting into Internet Recovery (boot while holding down Command-Option-R) so that you know it actually works. Once it boots, try starting Safari and (as a test) see if it can visit GitHub.com. If not, then it may have booted into OS X Lion, which is also old enough that attempting to install it through Internet Recovery will fail. (Internet Recovery tends to be especially likely to boot into Lion if you have only 4GB of RAM. Also, if you have upgraded to an 802.11ac WiFi card, Internet Recovery will fail completely unless you plug into Ethernet. In addition, with the possible exception of flashed 2009 Mac Pros, Internet Recovery is not available on any Mac models prior to 2010.)
    In any case, if you are unable to start Internet Recovery, or it has a version of Safari too old to visit GitHub.com, then it is vital that you create an installer USB for an older macOS version and hold onto it in case of emergency.
    Once you create the patched installer USB for Big Sur, hold onto it as well. If you ever reset your Mac's NVRAM, then you will need to use the patched installer USB to repeat step 9 of the installation instructions.
    On a Mac without a Metal GPU, several programs, including Maps and Photos, will not work. Perhaps there may be patches in the future to provide partial fixes, but upgrading to a Metal GPU is the only actual solution.
    FileVault has been buggy throughout the entire Big Sur development cycle. For maximum stability, disable FileVault before upgrading to Big Sur. Once you upgrade to Big Sur, bugs may make it impossible to disable FileVault and may make it impossible to unlock your FileVault volumes when applying updates or booting from the installer USB. (Not to mention, FileVault bugs may also make it impossible to open Terminal on the installer USB.) The best way out of this conundrum is probably to back up the entire Big Sur installation using Time Machine (Time Machine encryption, unlike FileVault, appears to be stable), erase and reinstall Big Sur, and use the Setup Assistant to restore the Time Machine backup.
    Upgrading from a Catalina installation which has been patched using dosdude's macOS Catalina Patcher results in an unstable system. The instability is not fixed by running the Big Sur installer again. So far, the only fix seems to be similar to the method for disabling FileVault: Back up the entire Big Sur installation using Time Machine, erase and reinstall Big Sur, and use the Setup Assistant to restore the Time Machine backup. In my testing, this appears to correct the instability.
    Time Machine backups must be restored by first performing a fresh Big Sur installation and then doing the Time Machine restore from the Setup Assistant. Attempting to do the restore from the installer USB fails. I do not yet know if this is inherent to Big Sur, inherent to the patching process, or a bug in this patcher.
    If you encounter "com.apple.DiskManagement.disenter error 49168" during installation, try rebooting and see if the installation process continues, or try erasing the volume and starting installation over. This appears to be an error that also happens sometimes on supported Macs. If all else fails, a possible workaround is to try formatting the volume as Mac OS Extended instead of APFS in step 8 or 11; it will still be converted to APFS during the installation process, but this may perturb the installation process enough to avoid the error.
    Instructions for use
    Make sure you have a 16GB or larger USB stick to use for creating the installer. Obtain a copy of the macOS Big Sur Public Beta (or, if you are member of the Apple Developer Program, the Big Sur developer beta). Download a copy of this patcher. If you are viewing this on GitHub, and you probably are, then click the green "Code" button then "Download ZIP". Use Disk Utility to erase the USB stick using "Mac OS Extended (Journaled)" format and "GUID Partition Map" scheme. (You may need to choose "Show All Devices" before Disk Utility will allow you to do this.) In order for this patcher to run optimally, the USB stick must use GUID Partition Map and not Master Boot Record. (This is a new requirement as of micropatcher v0.2.0.) Note that the volume name does not particularly matter, since it will be renamed by createinstallmedia in the next step. (If this USB stick already contains a patched Big Sur installer created using micropatcher v0.2.0 or later, and you are re-creating it with a newer version of the micropatcher or a newer version of Big Sur, you may skip this step.) Use createinstallmedia as usual to create a bootable USB stick with the installer and recovery environment, as you would on a supported Mac. (This patcher is easier to use if the installer USB stick is not renamed after createinstallmedia is used, but it can still work if the USB stick has been renamed.) Run micropatcher.sh to patch the USB stick. If micropatcher.sh is unable to find the USB stick, then try specifying the pathname of the USB stick to micropatcher.sh. The easiest way to do that is to open a Terminal window, drag and drop micropatcher.sh into the Terminal window, go back to Finder, choose Computer from the Go menu, drag and drop the USB stick into the Terminal window, then press Return. Another program also needs to be patched onto the USB stick, so run install-setvars.sh. If necessary, the same Finder/Terminal drag-and-drop instructions that work in step 6 for micropatcher.sh will also work in this step for install-setvars.sh. Unlike micropatcher.sh, install-setvars.sh needs root permissions (since it accesses the normally hidden EFI partition on the USB stick), so it uses sudo to obtain root permissions. Typically this means it will ask for your user account password when it starts. If you want the patched USB stick to configure your Mac to boot in Verbose Mode, run install-setvars.sh -v instead of just install-setvars.sh. However, the "Verbose" in "Verbose Mode" is not a joke, and most users will want to avoid this. As of Big Sur Micropatcher v0.4, install-setvars.sh will now install a version of setvars which enables Apple's System Integrity Protection (SIP) and Authenticated Root Volume (ARV) security features if it is run on a Late 2013 iMac, or a version of setvars which disables both of these features if it is run on any other model of Mac. You may add a -d option to force the installation of the setvars version which disables these features (for instance, if you are creating the USB on a Late 2013 iMac but you will be using it on another Mac). You may also add a -e option to for the installation of the setvars version which enables these features (for instance, if you are installing Big Sur on a 2012 or 2013 Mac that has been upgraded with an 802.11ac WiFi card and therefore does not need a WiFi patch). Since Disk Utility in Big Sur may have new bugs, this may be a good time to use Disk Utility in High Sierra/Mojave/Catalina to do any partitioning or formatting you may need. (Try repeating this step if you see a prohibited/no-entry sign during boot) Restart the Mac while holding down the Option key to use the Startup Selector. The installer USB will actually show up as two different drives with the same icon, "Install macOS Big Sur Beta" (or similar) and "EFI Boot". (If you have multiple "EFI Boot" drives, it's the one with the yellow icon. If more than one has a yellow icon and you cannot tell which one is the one on the installer USB, try unplugging the installer USB, observing the set of icons on the screen, then plugging the installer USB back in and watching how the icons change.) Start up from "EFI Boot". Within a few seconds, although most likely in under a second, the Mac will suddenly power down. This indicates that the setvars EFI utility has finished making the necessary changes to the Mac's NVRAM settings. (These changes include disabling SIP, disabling authenticated root, and enabling TRIM on non-Apple SSDs.) Turn the Mac back on (or reboot it if you skipped step 9), with the Option key down again, to use the Startup Selector again. This time, boot from "Install macOS Big Sur Beta" (or similar). (If the Startup Selector is not showing your USB stick this time, try unplugging and replugging the USB stick.) If you see a prohibited/no-entry sign, then try repeating step 9. If you need to do any partitioning or formatting with Disk Utility, and you didn't do it in step 8, now is the time to do it. (Optional, for very advanced users only, 99.9% of users should just pretend this step doesn't even exist) This patcher normally disables APFS system volume sealing, except when both SIP and ARV are enabled (see step 7 for more information about that). If you wish to unconditionally enable APFS system volume sealing, then open Terminal, run the command /Volumes/Image\ Volume/insert-hax.sh --seal and quit Terminal. If you have no idea what any of this means, just skip this step. (Also, note that even though volume sealing is disabled by default with this patcher, snapshot root is still enabled. Just mentioning this because people sometimes confuse the two issues. If you have some need to disable snapshot root, that is beyond the scope of this README. Personally, I would suggest learning to live in harmony with snapshot root rather than declaring war on it; the section "Modifying the System volume yourself" at the end of this README may help in that regard.) Start the Installer as you would on a supported Mac. Once installation is underway, come back in an hour or so, and you should be at the macOS Setup Assistant! It may take less time if you're installing on a 2012/2013 Mac, or more time (possibly 2-3 hours) if you're installing on a hard drive/SSD connected via USB 2.0, or if you're upgrading instead of a fresh install. (If you actually watch the installation process, don't be surprised if it seems to get stuck at "Less than a minute remaining..." for a long time. Allow it well over half an hour. It should eventually reboot on its own and keep going. Likewise, don't worry if it reboots with 10-12 minutes remaining; that is also often normal.) On many pre-2011 Macs, such as 2010 MacBooks, it will start crashing repeatedly with kernel panics shortly before the Setup Assistant would normally show up. Once this happens, boot from the installer USB and perform step 15 (the next step), with the --2010 option. That will fix the kernel panic. If you're on a Late 2013 iMac, or you've replaced the 802.11n card in your 2012/2013 Mac with an 802.11ac card, you're done. Otherwise, press Command-Q and wait a few seconds, then the Setup Assistant should let you shut down. After you shut down, boot from the patched installer USB again (as in step 10), then open Terminal. Next, run the patch-kexts.sh command to add working Wi-Fi. There are several ways of formatting this command. For example, for a system volume named Macintosh HD, try one of the following: /Volumes/Image\ Volume/patch-kexts.sh /Volumes/Macintosh\ HD '/Volumes/Image Volume/patch-kexts.sh' '/Volumes/Macintosh HD' "/Volumes/Image Volume/patch-kexts.sh" "/Volumes/Macintosh HD" You can also mix-and-match quotation/escaping formats, such as /Volumes/Image\ Volume/patch-kexts.sh "/Volumes/Macintosh HD" Backslashes may work better with tab completion (see below), but many users will find quotation marks to be easier. Don't forget that tab completion is your friend! For instance, you can type /V<tab>/Im<tab>/p<tab> /V<tab>/Mac<tab> at the command prompt -- that's much less typing than /Volumes/Image\ Volume/patch-kexts.sh /Volumes/Macintosh\ HD! On 2011 MacBook Pro 13" and 2011 MacBook Air, add a "--2011" option after the ".sh" and before the volume name, for example /Volumes/Image\ Volume/patch-kexts.sh --2011 /Volumes/Macintosh\ HD, to fix sound, brightness control, and sleep as well as Wi-Fi. (Use this "--2011" option on 2011 iMacs and Mac Minis as well.) If you have a 2011 Mac that has been upgraded with an 802.11ac Wi-Fi card, add a "--no-wifi" option as well, for example /Volumes/Image\ Volume/patch-kexts.sh --2011 --no-wifi /Volumes/Macintosh\ HD or /Volumes/Image\ Volume/patch-kexts.sh --no-wifi --2011 /Volumes/Macintosh\ HD. (As of micropatcher v0.5.0, WiFi hardware is autodetected and this option is used automatically if necessary.) Normally patch-kexts.sh installs the mojave-hybrid WiFi patch (used since micropatcher v0.2.1), but if you need to try a different WiFi patch for any reason, try adding the --wifi=hv12v-old (same as v0.0.6-v0.0.20) or --wifi=hv12v-new (same as v0.1.0 or v0.2.0) option. If you're going to use the installation on a 2010 or older Mac, add a "--2010" option likewise (except for 2009-2012 Mac Pros, which should use neither "--2010" nor "--2011"). patch-kexts.sh tries to automatically detect whether it should create a new APFS snapshot if it is running in a live system, and it defaults to creating a new snapshot if it is running from the patched installer USB. If you need to override this, there are now --create-snapshot and --no-create-snapshot command line options, as of micropatcher v0.3.0. It is also possible to do this step without booting from the patched installer USB -- just open Terminal and run /Volumes/Install\ macOS\ Big\ Sur\ Beta/patch-kexts.sh with any command line options if needed (such as /Volumes/Install\ macOS\ Big\ Sur\ Beta/patch-kexts.sh --2011), but do not specify a volume name, and patch-kexts.sh will automatically default to the boot drive. If you have a 2011 iMac that has been upgraded with a Metal GPU (especially NVidia), then try adding --2011 --iMac as options for patch-kexts.sh to install the necessary patches for Big Sur to use your Metal GPU. At this time, the --iMac option only works if you boot from your Big Sur installation before running patch-kexts.sh (as described in the previous bullet point), and not if you boot from the installer USB. (This step is unnecessary for most users.) If you will be using the Big Sur installation on a different Mac (for instance, installing on a 2011 or later Mac and using it on a 2009 or 2010 Mac), it is possible that the other Mac (the one not used for installation) may try to boot off the wrong APFS snapshot. To prevent this, run zap-snapshots.sh on your System volume, to remove all but the most recent snapshot. For instance, /Volumes/Image\ Volume/zap-snapshots.sh /Volumes/Macintosh\ HD. (Or you can also do this if you are running low on disk space on an older beta of Big Sur.) This is basically the same as step 15, but with zap-snapshots instead of patch-kexts, and without any command line options like --2010 or --2011. After step 15 (and 16 if necessary), reboot into your Big Sur installation and complete the Setup Assistant if you have not already done so. Pay particular attention to the screen that asks if you want to transfer information from another Mac or PC; if you want to restore a Time Machine backup, you must do it from this screen. The previous method of restoring it from the macOS Installer USB is still visible in the Installer USB's menu, but it no longer works. On Macs which do not support Metal (many 2011 and older models), make sure to enable Reduce Transparency to eliminate many seemingly random crashes, and if icons on the right-hand side of the menu bar are invisible afterward, try Dark mode. Enabling Reduce Motion will increase performance a little more, and so might Increase Contrast. (If you will be using the installation on a 2009/2010 Mac, it would be a good idea to finish the Setup Assistant on a 2011 or later Mac and enable Reduce Transparency before moving the installation over.) Optional (but can greatly improve performance for Macs that do not support Metal): Once booted in your Big Sur installation, run disable-animations.sh from the patched installer USB to disable most animations. If you want to reenable them, run reenable-animations.sh. (Thanks to johncaling40 for these contributed scripts.) If you reset your Mac's NVRAM, attempts to boot Big Sur afterward will fail with a prohibited/no-entry sign on the screen. To fix this, repeat step 9 (booting the "EFI Boot" partition of the patched installer USB). Likewise, if you transplant the hard drive with the Big Sur installation from one Mac to another, or you move an external hard drive/SSD with Big Sur from one Mac to another, you will need to repeat step 9 on the destination Mac before it can boot Big Sur.
    To update from one beta to the next, you may create a bootable USB for the new beta (using createinstallmedia), patch it with this patcher, then follow the directions above (except skip Disk Utility, i.e. skip steps 8 and 11) to boot from the patched USB and install it on top of the previous beta. (Allow something like 1-3 hours for the update, even if it looks like it froze up at some point, especially on a 2011 or older Mac.) This will uninstall the Wi-Fi, etc. kexts that were installed in step 15 on the previous beta, so you will need to redo that step as well. There are other methods of updating using delta updaters, but they are more difficult (and you will need to run patch-kexts.sh -u, described below, to remove all kext patches before attepting that type of update).
    For what it's worth, patch-kexts.sh has a -u command line option for undoing the kext patches (such as 802.11n Wi-Fi). It can only undo kext changes applied through patch-kexts.sh and not any kext changes applied through other means. (A more time-consuming but potentially more thorough alternative is to reinstall Big Sur on top of your existing installation, as if you were using the method described in the previous paragraph to update to a new Big Sur beta.)
    If you want to undo the setvars EFI utility's changes to boot-args and csrutil settings, then boot from the USB stick, open Terminal, and run /Volumes/Image\ Volume/reset-vars.sh. (Or you can just start your Mac while holding down Command-Option-P-R to reset NVRAM. That is probably a better way of doing it.)
    The best way to remove the patch from the USB stick is to redo createinstallmedia, but if you are working on patcher development or otherwise need a faster way to do it, you can run unpatch.sh.
    Modifying the System volume yourself
    After you finish installation, you may want to modify the System volume yourself. For various reasons you may want to install kext patches other than those which are part of this patcher. Or there may be other changes you want to make to the System volume. However, Big Sur normally boots from a read-only snapshot of the System volume, so making changes is typically not as simple as remounting the volume as read-write. Two shell scripts to assist with this, remount-sysvol.sh and rebuild-kc.sh are provided. For now, remount-sysvol.sh should be run from the patched installer USB (but after booting from your Big Sur installation).
    Run /Volumes/Install\ macOS\ Big\ Sur\ Beta/remount-sysvol.sh. Due to a bug which will be fixed in a future patcher release, it must be run like that, with the full pathname. The script will either remount / as read-write (if your system somehow started directly off the System volume), or it will create a temporary mount point and mount the underlying System volume at that temporary mount point. Then it will change the current directory to /System/Library/Extensions wherever the System volume is mounted read-write (probably on the temporary mount point), and it will start a subshell. At this point, you can make whatever changes you want to the kexts in /System/Library/Extensions, or whatever other changes you want to make on the System volume for that matter. These changes can be made using whatever means you prefer -- they do not need to be done through the subshell (although they can be). You may also run /Volumes/Install\ macOS\ Big\ Sur\ Beta/zap-snapshots.sh to delete all APFS system snapshots except for the most recent (this script must be run inside the subshell). Once you are done modifying the System volume, run "$REBUILD_KC" (including the quotation marks). This must be run inside the subshell. This will rebuild the kernel/kext collections that Big Sur uses as its kernel cache. Note that if you try to install a kext which is incompatible with Big Sur, this may fail; in that case, you will need to undo the incompatible kext change and try "$REBUILD_KC" again. (If you ran zap-snapshots.sh in step 3 without making any other changes to your System volume, then this step is not required. For most Big Sur systems, this step will be required if any other changes are made to the System volume, to create and "bless" a new snapshot. If your Big Sur system boots directly from the System volume rather than using snapshot booting -- this is rare -- then this step is only needed if you make kext changes, and it will not create any snapshots.) Once "$REBUILD_KC" finishes successfully, run the exit command in the subshell. The remount-sysvol.sh script will then attempt to unmount the temporary mount point. The unmount attempt may fail, but if so, it's no big deal because macOS will unmount it when restarting anyway. by barrykn.
  7. Logitech Options

    Logitech Options es una aplicación para Windows y macOS eficaz y fácil de usar que mejora los ratones, teclados y touchpads de Logitech. Personaliza tu dispositivo con Options y haz lo imposible.

    Características principales:
    PERSONALIZACIÓN DE TECLAS Y BOTONES Puedes configurar asignaciones de teclas y botones, la velocidad del cursor y el botón rueda, y mucho más. BOTÓN DE GESTOS Incrementa tu productividad con el botón de gestos, para reproducir los usados en el trackpad. CONFIGURACIÓN ESPECÍFICA DE APLICACIÓN Asigna botones a tareas concretas NOTIFICACIONES Y ESTADO Con notificaciones e indicadores de estado específicos es fácil saber qué está pasando en un dispositivo concreto. LOGITECH DUOLINK Usa el teclado para agregar funciones al ratón. LOGITECH FLOW Coloca el cursor en el borde de la pantalla para cambiar de ordenador automáticamente y transferir texto, imágenes y archivos.  COPIA DE SEGURIDAD DE CONFIGURACIÓN DE DISPOSITIVO Crea una cuenta y haz una copia de seguridad de la configuración de tu dispositivo en la nube.
  8. Youtube-dl

    youtube-dl is a command-line program to download videos from YouTube.com and a few more sites. It requires the Python interpreter, version 2.6, 2.7, or 3.2+, and it is not platform specific. It should work in your Unix box, in Windows or in Mac OS X.
  9. USB Defender

    MOST POWERFUL application to protect you from autorun viruses!
    Did you ever wonder, why is anyone talking about so dangerous USB drives? Why can't you protect yourself from thousands (!) of viruses that are spreading only by your flash drive? Today there are many programs that can be in your memory, waiting for any new flash drive connected, finding viruses on it and removing them. But isn't it better just to VACCINATE your drive once and forever? No more viruses. No more danger.

    About this program. Short FAQ.

    USB Defender was developed to be extremely easy in use. You can see just two buttons on it: "Protect" and "Unprotect". First button you are using to vaccinate your drive, second - to remove protection. After selecting any drive, program automatically detects, if there is any protection active and only one button will be available for you. Also you have a checkbox there, which is to choose, what level of protection use. If you put a tick on it - you 'll need administrative rights on your PC to protect (and then, if needed, unprotect) USB drive. BUT using Pro way of protection is MUCH more secure and protect you with 99.999999999(9)%.


    Also, you can see a mark of your USB protection. If you don't use Pro method, you can't achive 5/5 protection but you'll be able to REPROTECT flash whenever you'll have admin account.

    If there is any autorun.inf file on your drive, corresponding sentence will start blinking. This was done to warn you, when you are going to protect drive with AUTORUN function, that may be useful (like running menu program at moment stick is inserted).

    USB Defender is fully portable - so you can take it with you wherever you want.

    NOTE!: Previous versions of USB Defender does't support current (1.1). With current version you CAN easily unprotect previous kind of protection.

    Possibilities and advantages:
    Fully portable Much more powerful and easy then Panda USB Security, USB Threat Defender and else Supports ANY Windows file system Absolutely free Impossibly easy GUI interface Protection auto-detect function Very fast in work Only one exe-file Most powerful protection of all similar programs TOTALLY clean And, totally free by Mbentefor.
  10. SpeedOut

    Do you have a Flash Stick? Yes, of course. Do you know, how fast it is? Will you be able to run program from within it, play a portable Call Of Duty or just quickly copy a film from/to it? You don't know.
    When you are going to buy a USB Drive or Stick, you can see big amount of different vendors, and everywhere is label "The BEST". Who is the best? Kingston or Kingmax, PQi or SanDisk, Transcend or Canyon?
    NOW YOU WILL HAVE AN ANSWER. No. Better. YOU WILL HAVE A WAY TO FIND THE BEST PRICE/QUALITY PRODUCT YOURSELF.
    Presenting new utility SpeedOut.

    About this program. Short FAQ.

    It's really easy to use this application.  Just one button 2 go. Anyway, lets get into deep and decide, why is my program better then many other. Well, SpeedOut is an application, created for calculating USB drive (stick or external HDD) read/write speed. It is using low-level technology, which allows you to know REAL drive speed, without slowdowns, caused by File System. After program start you can see simple interface:

    By pressing Start, program will make four read and four write tests. After that you'll get result for reading and writing. DON'T TOUCH MOUSE AND KEYBOARD DURING THIS OPERATION! Also, you will get a mark for your drive, showing how fast is it.
       
    As you can see, first graph is showing mark on Read Speed, second - on Write Speed. Here it is. The main thing, why program is better then another (like Everest HDD Bench or HDD Tune): no data will be destroyed while writing test is performed! No need to reformat your drive! Nothing more, just one click. Also, at system menu (Alt+Space) you will have two important functions - Save to file (just click enter - program will save file on drive that was checked) and Copy to clipboard (easy way to bounce in chat with your friends).

    SpeedOut is fully portable - so you can take it with you wherever you want.

    Question: I have a problem, many exe-files on my PC can not run. I double-click and nothing happens!!!
    Answer: Probably, you have IndieVolume installed on your Windows. It is using invalid hook data - so, remove IndieVolume - and problem is decided.

    Question: Your program is showing different resultsfor one stick. Why?
    Answer: It depends on port and time, you were using USB. Just put off your flash, wait five mins and set on. I'll try to make results less different in next version.

    Question: Is program working under User-mode.
    Answer: Nope. Low-level is only allowed under administrator.
    Possibilities and advantages:
    Fully portable No need to reformat your drive Low-level technology Beautiful interface Easy to use - click2go No bugs as soon as you are not disasming it Short tests - realistic results. TOTALLY clean And, of course, free by Mbentefor.
  11. Aegisub (Advanced Subtitle Editor)

    Aegisub is a free, cross-platform open source tool for creating and modifying subtitles. Aegisub makes it quick and easy to time subtitles to audio, and features many powerful tools for styling them, including a built-in real-time video preview.



    Aegisub is available in Windows & Mac versions.
  12. eMule

    eMule es un cliente P2P para Windows que parte de la base del eDonkey2000, pero añadiéndole multitud de nuevas funcionalidades y una interfaz gráfica más atractiva.

    Algunas funciones disponibles
    Los clientes usan varias redes para crear una red fiable (eD2K, Intercambio de fuentes, Kad) Desde las versiones 0.42 eMule es capaz de utilizar Kad. El sistema de colas y créditos de eMule contribuye a garantizar que todos consigan el archivo que buscan dando preferencia a aquellos que aportan archivos a la red. eMule es totalmente gratis y no contiene absolutamente nada de adware, spyware o similares. Nos mueven la diversión y las ganas de aprender, no el dinero. Todos los archivos son comprobados a lo largo del proceso de descarga para evitar la aparición de archivos corruptos. El Control Inteligente de Corrupción (ICH) de eMule acelera la corrección de las partes corruptas y el Control Inteligente de Corrupción Avanzado(AICH) ayuda a obtener una completa integridad de los datos con un gasto mínimo de redescarga o de sobrecarga al gestionar elementos mucho más pequeños. El sistema de prioridades automático y el control de fuentes te permiten iniciar múltiples descargas sin que tengas que monitorizarlas. La función "Previsualizar" te permite ver tus vídeos y archivos antes de que se haya completado su descarga. Para previsualizar archivos de vídeo recomendamos el cliente de VLC VideoLan. eMule incluye servicios de web y un servidor de web que te permitirán un rápido y cómodo acceso desde y hacia Internet. Puedes crear categorías para organizar tus descargas. Para encontrar el archivo que buscas, eMule te ofrece una amplia gama de posibilidades de búsqueda: "Servidores" (tanto en búsqueda local como global), a través de la "Red Kad" " y Basados en web" (Filedonkey). eMule también te permite usar búsquedas booleanas muy complejas para que tus búsquedas sean mucho más flexibles. El sistema de mensajería y el de amigos te permiten enviar mensajes a otros clientes y añadirles como amigos. Una de las ventajas de tu lista de amigos es que en ella siempre puedes ver si tus amigos están conectados. eMule incorpora un cliente IRC con el que podrás chatear con otros usuarios de todo el mundo. Autores
    Unknown (John) Ornis Merkur (Retirado) Tecxx (Retirado) Juanjo (Retirado) Dirus (Retirado) Barry (Retirado)
  13. Astro Command Center

    La aplicación Astro Command Center permite la configuración completa de todos los ajustes de los siguientes dispositivos Astro: MixAmp Pro TR, A50 Wireless + Base Station y A20.
    El software no detectará ningún otro producto Astro Gaming diferente a estos, y tampoco es compatible con el mando C40 TR.
    Astro Command Center es compatible con:
    - MIXAMP PRO TR GEN 3 (lanzamiento de finales de 2015)
    - MIXAMP PRO TR GEN 4 (versión 2019)
    - A50 WIRELESS + BASE STATION GEN 3 (versión de finales de 2016)
    - A50 WIRELESS + BASE STATION GEN 4 (versión 2019)
    - A20 WIRELESS (versión de finales de 2017)





    Instrucciones de uso:
    Descargue el archivo haciendo clic en el botón de descarga correspondiente a su sistema operativo. Ejecute el archivo una vez que se complete la descarga. Siga las instrucciones paso a paso en el software ASTRO Command Center. Conecte su dispositivo a su computadora a través de USB. Asegúrese de que su dispositivo esté en modo PC.
  14. Mos

    A lightweight tool used to smooth scrolling and set scroll direction independently for your mouse on MacOS.
    Take Full Control of Your Mouse

    Mos separates touchpad and mouse scrolls independently, then, you can set the direction of the touchpad and mouse wheel separately. Also, Mos providing smooth scrolling for your mouse, whether you are a Windows user or a MacOS, you can move freely.
    Scrolling, Smoother Than Ever

    Mos's special interpolation algorithm can make every mouse roll as smooth and silky as possible.
    Manage Programs Independently

    Mos can independently manage the scrolling behavior of each application. For some annoying programs, we help you.
    Design & Create by Caldis.
  15. Amlogic USB Burning Tool

    Amlogic SUB Burning Tool es una pequeña aplicación para Windows que nos permite flashear el firmware de stock en los dispositivos con chipset Amlogic.
    Features

    Flash Firmware
    It helps you to flash the stock firmware on the Mobile device running on the Amlogic Chipset. After launching the Amlogic Burning Tool, you need to load the firmware by clicking on the File > Import Image (img). Then after connecting your Mobile device to the computer and click on the start button to begin the flashing process.
    Configuration
    It comes with multiple configuration options, i.e. Erase Flash, Erase Bootloader, Reset After Success, Overwrite Key. The Erase Flash supports four types of methods, i.e. Normal Erase, Force Erase, Erase All, Force Erase All.
    Other Options
    It also comes in Multiple Languages, i.e. English and Chinese. The Main Grid can be adjusted from the View > Select  Menu. The Grid can show Device ID, Progress, Time, Statistic, MAC, SN/USID, MAC_BT, MAC_WIFI.
  16. DiscUtils

    DiscUtils is a .NET library to read and write ISO files and Virtual Machine disk files (VHD, VDI, XVA, VMDK, etc). DiscUtils is developed in C# with no native code (or P/Invoke).
    Implementation of the ISO, UDF, FAT and NTFS file systems is now fairly stable. VHD, XVA, VMDK and VDI disk formats are implemented, as well as read/write Registry support. The library also includes a simple iSCSI initiator, for accessing disks via iSCSI and an NFS client implementation.
    How to use the Library
    Here's a few really simple examples.
    How to create a new ISO:
    CDBuilder builder = new CDBuilder(); builder.UseJoliet = true; builder.VolumeIdentifier = "A_SAMPLE_DISK"; builder.AddFile(@"Folder\Hello.txt", Encoding.ASCII.GetBytes("Hello World!")); builder.Build(@"C:\temp\sample.iso"); You can add files as byte arrays (shown above), as files from the Windows filesystem, or as a Stream. By using a different form of Build, you can get a Stream to the ISO file, rather than writing it to the Windows filesystem.
    How to extract a file from an ISO:
    using (FileStream isoStream = File.Open(@"C:\temp\sample.iso")) { CDReader cd = new CDReader(isoStream, true); Stream fileStream = cd.OpenFile(@"Folder\Hello.txt", FileMode.Open); // Use fileStream... } You can also browse through the directory hierarchy, starting at cd.Root.
    How to create a virtual hard disk:
    long diskSize = 30 * 1024 * 1024; //30MB using (Stream vhdStream = File.Create(@"C:\TEMP\mydisk.vhd")) { Disk disk = Disk.InitializeDynamic(vhdStream, diskSize); BiosPartitionTable.Initialize(disk, WellKnownPartitionType.WindowsFat); using (FatFileSystem fs = FatFileSystem.FormatPartition(disk, 0, null)) { fs.CreateDirectory(@"TestDir\CHILD"); // do other things with the file system... } } As with ISOs, you can browse the file system, starting at fs.Root.
    How to create a virtual floppy disk:
    using (FileStream fs = File.Create(@"myfloppy.vfd")) { using (FatFileSystem floppy = FatFileSystem.FormatFloppy(fs, FloppyDiskType.HighDensity, "MY FLOPPY ")) { using (Stream s = floppy.OpenFile("foo.txt", FileMode.Create)) { // Use stream... } } } Again, start browsing the file system at floppy.Root.
  17. DVD Decrypter

    Completa aplicación para ripear DVD's de forma rápida y sencilla, con multitud de opciones para elegir qué y como queremos conservar del disco original.

    Las imágenes de disco generadas pueden luego ser:
    Vistas en la computadora usando programas como PowerDVD y WinDVD (WinDVD, solo puede ver estructuras completas de DVD-Video). Codificadas a un tamaño más pequeño y eliminando extras indeseados como los avances de la película con herramientas de reautoría como DVD Shrink y Nero Recode. Grabadas sobre medios ópticos (DVD-R, DVD-RW, DVD+R, DVD+RW, DVD+R DL y DVD-RAM) para producir discos que puedan ser vistos en equipos reproductores de DVD. Exportadas a los formatos VCD, SVCD o DivX y posiblemente grabadas sobre medios CD-R o CD-RW.

  18. Razer THX Spatial Audio

    Advanced 7.1 Surround sound with superior positional accuracy, for all your games.
    What separates good sound from phenomenal audio is the ability to transport you right into the action. Whether it’s knowing the precise location of enemy gunfire or embracing the moment as you stand in the center of an arena, the THX Spatial Audio App delivers advanced 7.1 surround sound with pinpoint positional accuracy to make your game come alive.
    THX Spatial Audio technology is an advanced positional audio solution that delivers a heightened, immersive experience as you game. Designed for pinpoint positional accuracy, here's how it benefits your gaming:
    SUPERIOR POSITIONAL ACCURACY THX Spatial Audio lets you locate sneaking enemies, hear approaching footsteps and detect nearby threats before anyone else does. SURROUND SOUND CALIBRATION THX Spatial Audio allows you to adjust the distance, volume and position of speakers for a personalized positional audio experience. WORKS WITH MORE GAMES THX Spatial Audio immerses you in surround sound even from stereo sources, ensuring immersive audio with a wider selection of games. EQ CUSTOMIZATION Personalize your EQ settings for just the right balance of Highs, Mids and Lows, or up the ante by applying Bass Boost levels, Sound Normalization and Vocal Clarity. STAY FOCUSED LONGER THX Spatial Audio delivers such a natural listening experience, it can help to reduce ear and brain fatigue because you’re able to figure out where every sound is coming from instinctively. COMPATIBLITY WITH BLUETOOTH AND USB Works with a wide range of headsets, including 3.5mm, Bluetooth and USB.
  19. Transmission

    Transmission is a fast, easy, and free BitTorrent client. It comes in several flavors:
    A native Mac OS X GUI application GTK+ and Qt GUI applications for Linux, BSD, etc. A headless daemon for servers and routers A web UI for remote controlling any of the above
    Open Source
    Transmission is an open source, volunteer-based project. Unlike some BitTorrent clients, Transmission doesn't play games with its users to make money:
    Transmission doesn't bundle toolbars, pop-up ads, flash ads, twitter tools, or anything else. It doesn't hold some features back for a payware version. Its source code is available for anyone to review. We don't track our users, and our website and forums have no third-party ads or analytics. Easy
    Transmission is designed for easy, powerful use. We've set the defaults to Just Work and it only takes a few clicks to configure advanced features like watch directories, bad peer blocklists, and the web interface. When Ubuntu chose Transmission as its default BitTorrent client, one of the most-cited reasons was its easy learning curve.
    Lean
    In separate benchmarks, Linux Format and Lacrocivious both found Transmission to use less CPU than any other GUI client. It even used less CPU than some non-GUI clients.
    Transmission also has the lowest memory footprint of any major BitTorrent client.
    Imageshack chose Transmission for its BitTorrent farms because the competition requires amounts of memory several times greater than Transmission.
    Transmission's small footprint is one reason why many home device manufacturers, such as FON, Belkin, and Networked Media Tank ship with Transmission. When Belkin and Vuze Inc. partnered to write a Torrent Genie to let people who ran Vuze and owned a Belkin router keep sharing files even when Vuze wasn't running, they decided to use Transmission -- not Vuze's own BitTorrent client -- on the router.
    Native
    Unlike many cross-platform applications, Transmission integrates seamlessly with your operating system.
    The Mac OS X interface is written in Objective-C and uses Growl notifications and dock badging to keep you informed.

    The GTK+ interface has been carefully written to follow the GNOME Human Interface Guidelines. If your desktop supports popup notifications, desktop sounds, and a system tray, the GTK+ interface will make use of them.
    Powerful
    Transmission has the features you want from a BitTorrent client: encryption, a web interface, peer exchange, magnet links, DHT, µTP, UPnP and NAT-PMP port forwarding, webseed support, watch directories, tracker editing, global and per-torrent speed limits, and more.
  20. ViewSonic Elite Display Controller

    The ViewSonic ELITE RGB Controller allows users to easily make adjustments to their monitor’s settings all on one app. Select from preset game modes, customize display settings, and control your RGB lighting for a more personalized gaming experience.

    Take control over your monitors various settings from display options to RGB lighting. Then save each customized setting for easy and immediate access that turns your monitor into weapon for victory.
    Too busy playing to adjust display options? Quick Access allows you to easily switch to your preferred mode anytime with a single click.
  21. Microsoft Image Mastering API (IMAPI)

    Image Mastering API v2.0 (IMAPIv2.0) enables IMAPIv2 dependent applications to stage and burn images to CD and DVD optical storage media.
  22. Windows USB/DVD Download Tool

    When you download Windows from Microsoft Store, you have two options: You can download a collection of compressed files, or you can download an ISO file. An ISO file combines all the Windows installation files into a single uncompressed file.
    If you choose to download an ISO file so you can create a bootable file from a DVD or USB drive, copy the Windows ISO file onto your drive and then run the Windows USB/DVD Download Tool. Then simply install Windows onto your computer directly from your USB or DVD drive.
    When you download the ISO file, you must copy it onto a USB or DVD. When you're ready to install Windows, insert the USB drive or DVD with the ISO file on it and then run Setup.exe from the root folder on the drive.
    This allows you to install Windows onto your machine without having to first run an existing operating system. If you change the boot order of drives in your computer's BIOS, you can run the Windows installation directly from your USB drive or DVD when you first turn on your computer. Please see the documentation for your computer for information about how to change the BIOS boot order of drives.
    Making copies
    To install the software, you can make one copy of the ISO file on a disc, USB flash drive, or other media.
    After you’ve installed the software and accepted the license terms that accompany the software, those license terms apply to your use of the software. The license terms for Windows permit you to make one copy of the software as a back-up copy for re-installation on the licensed computer. If you do not delete your copy of the ISO file after installing the Windows software, the copy of the ISO file counts as your one back-up copy.
    If you need to download the software again, you can go to your Download Purchase History in your Microsoft Store account and access the download there.
    Installation
    To install the Windows USB/DVD Download Tool:
    1. Click to open the Windows USB/DVD Download Tool page.
    2. Click Download then Run.
    3. Follow the steps in the setup dialogs. You'll have the option to specify where to install the Windows USB/DVD Download Tool.
    You must be an administrator on the computer on which you are installing the Windows USB/DVD Download tool. It requires the Microsoft .NET Framework version 2.0 or higher.

    System requirements
    Windows XP SP2, Windows Vista, or Windows 7 (32-bit or 64-bit) Pentium 233-megahertz (MHz) processor or faster (300MHz is recommended) 50MB of free space on your hard drive DVD-R drive or 4GB removable USB drive For Windows XP users
    The following applications must be installed prior to installing the tool: Microsoft .NET Framework 2.0. Microsoft Image Mastering API v2. Using the Windows USB/DVD Download Tool
    Before you run the Download Tool, make sure you have purchased the Windows ISO download from Microsoft Store and downloaded the Windows ISO file to your drive. If you have purchased Windows but have not yet downloaded the ISO file, you can download the ISO file from your Microsoft Store Account.
    To make a copy of your Windows ISO file:
    Click the Windows START button, and click WINDOWS USB/DVD DOWNLOAD TOOL in the ALL PROGRAMS list to open the Windows USB/DVD Download Tool. In the SOURCE FILE box, type the name and path of your Windows ISO file, or click BROWSE and select the file from the OPEN dialog box. Click NEXT. Select USB DEVICE to create a copy on a USB flash drive or select DVD disk to create a copy on a DVD disk. If you are copying the file to a USB flash drive, select your USB device in the drop-down list and click BEGIN COPYING. If you are copying the file up to a DVD, click BEGIN BURNING. When your Windows ISO file is copied to your drive, install Windows by moving to the root folder of your DVD or USB drive, and then double-click Setup.exe.
  23. UNetbootin

    UNetbootin le permite crear unidades USB Live de Ubuntu y otras distribuciones de Linux sin necesidad de grabar un CD, desde Windows, macOS y Linux.
    Puedes dejar que UNetbootin descargue una de las tantas distribuciones soportadas en el menú desplegable o puede suministrar su propio archivo .iso de Linux.
    Características
    UNetbootin puede crear un USB Live que arranque desde su PC.
    Es capaz de utilizar las distribuciones, ya sea descargando archivos ISO (imagen de CD) para usted, o mediante el uso de una imagen ISO que usted haya descargado con anterioridad.
    Using Unetbootin
    Seleccione el archivo ISO o una distribución para descargar, seleccione el disco destino (Memoria USB o Disco duro) y reinicie una vez finalizado el proceso. Si su dispositivo USB no es mostrado, vuelva a formatearlo en FAT32.

    Si utilizó el modo de instalación "USB Drive": Después de reiniciar, arranque desde el disco USB. En los PC, esto suele implicar presionar un botón como Esc o F12 inmediatamente después de encender el equipo, mientras que en Mac, debe mantener pulsada la tecla Opción antes de que OSX arranque.
    Si utilizó el modo de instalación "Hard Disk": Después de reiniciar, seleccione la entrada de UNetbootin desde el menú de arranque de Windows.
    Instalar otras distribuciones usando UNetbootin
    Descarga y ejecuta UNetbootin, una vez hecho selecciona la opción "disk image" para utilizarlo con un fichero ISO (Imagen de CD).
    UNetbooting no utiliza reglas específicas para cada distribución a la hora de grabar la imagen en el disco USB por lo tanto, muchos ficheros ISO de Linux deberían funcionar correctamente utilizando esta opción. Hay que tener en cuenta que no todas las distribuciones soportan el arranque desde el USB y algunas otras requieren opciones extra de arranque u otras modificaciones antes de que estas puedan arrancar desde el disco USB. Por lo tanto, esos ficheros ISO no funcionaran directamente. Por otro lado, los ficheros ISO de sistemas operativos distintos a Linux tienen diferentes mecanismos de arranque, por lo tanto es posible que no funcionen correctamente.
  24. Overcast for macOS

    Use Overcast as a native macOS application (unofficial).

    Features:
    Use your keyboard's media keys (play/pause/skip/prev) Alt-tab your way to Overcast, instead of using a browser tab Remembers your state, so you can pick up where you left off by nathanbirrell.
  25. qBittorrent

    qBittorrent is a bittorrent client programmed in C++ / Qt that uses libtorrent (sometimes called libtorrent-rasterbar) by Arvid Norberg.
    It aims to be a good alternative to all other bittorrent clients out there. qBittorrent is fast, stable and provides unicode support as well as many features.

    The main features are:
    similar user interfaces with µTorrent (for a smooth transition). integrated and customizable search: on most famous BitTorrent search sites. support for all BitTorrent extensions: Magnet/BitComet, Peer Exchange, DHT, etc. advanced control for trackers, peers, and torrents (torrent queueing and prioritizing). support for UPnP / NAT-PMP port forwarding. bandwidth scheduler and sequential download. IP Filtering (compatible with eMule and PeerGuardian) and IPv6 compliant. detailed torrent info: size, status, seeds, peers, download and upload speed, ratio, etc. by sledgehammer999.
Conéctate para seguir esto  
×
×
  • Crear nuevo...