top of page

Freedom 515 - Illinois

Public·139 members
Axel Cox
Axel Cox

How AMD Radeon RAMDisk Can Speed Up Your Gaming, Multimedia, and Browsing Experience

This software is for personal use only. If you would like to use this software for business/commercial use (or any purpose other than personal use), a commercial license fee and appropriate commercial license is required. The registration and payment of the commercial license fee is supported and made available through our website at -and-services/software/ramdisk by selecting the option for "Commercial Licenses" or by emailing

amd radeon ramdisk key


Firmware Keys are keys which decrypt bootloaders, ramdisks, and root filesystem of iOS firmware, if those components are encrypted. Apple uses encryption to make it harder to analyze and modify them. Over time Apple changed the way they encrypt firmware files, hence the way to decrypt them and get decryption keys changed as well.

Following IMG2 came the IMG3 file format. They were introduced with iPhone OS 2.0 beta 4, and have been in use ever since. In order to maintain their integrity, they use multiple layers of encryption. Apple took encryption seriously with IMG3 by utilizing AES (based on the Rinjndael key schedule). In terms of the pre-iPhone OS 3 VFDecrypt key, it is stored as plain-text in the "__restore" segment of the ASR image within the ramdisks.

The ramdisk keys can only be retrieved with the processor specific GID Key. The GID key is currently unretrievable and can only be utilized through the built-in AES engine. To complicate things even more, the engine is only accessible through a special bootrom or iBoot exploit (jailbreaks typically expose it with /dev/aes_0). This makes usage of the key nearly impossible.

However, once you have access to the AES engine, the entire system falls apart. You are able to upload an encrypted ramdisk and grab the decryption keys for it. Once you manage to decrypt the ramdisk, you can run it through GenPass to decrypt the firmware key.

After installing RAMDisk, I get a BOD (blue screen of death). What do I do?Remove/Uninstall RAMDisk from your system. Reboot the system making sure the BSOD does not reoccur. Download the latest version of RAMDisk -and-services/software/ramdisk. Install RAMDisk on your system.

Many Unix and Unix-like systems provide some form of RAM drive functionality, such as /dev/ram on Linux, or md(4)[8] on FreeBSD. RAM drives are particularly useful in high-performance, low-resource applications for which Unix-like operating systems are sometimes configured. There are also a few specialized "ultra-lightweight" Linux distributions which are designed to boot from removable media and stored in a ramdisk for the entire session.

Thank you, this was very helpful to me.Could some one clarify when using a ramfs ramdisk and I delete a file from it (using Gnome) is the file file still kept on the ramdisk?Say I have a sensitive document that I decrypted to the ramdisk and then I want to delete the file without removing the ramdisk is it safe to delete it using Gnome?

This tool will let you mount image files of hard drive, cd-rom or floppy, and create one or several ramdisks with various parameters. This all-in-one package includes the ImDisk Virtual Disk Driver (2.0.9), the DiscUtils library that extends the number of supported image file formats, and adds several GUIs and features.

The ramdisk feature improves overall system performance and speed. The RAM disk can improve overall system performance. The temporary files frequently accessed by system or other application, and the read and write the RAM memory speeds far greater than the real hard disk, so the RAM disk can improve overall system performance; additional hard disk, and SSD storage medium has its read and write times limit, the RAM disk improve the life of a real hard disk too.

The problem is that the maximum size of a ramdisk, more specifically of size of memory that can be accessed via the ramdisk driver is configured at compiletime, can be overwritten at boottime, but remains fixed once the kernel is loaded into memory. The default value is probably measured in Megabytes. If I recall correctly the memory for a ramdisk is reserved right when the driver is loaded, all ramdisks are the same size and there is are some 16 ramdisks by default. So not even you want a ramdisk size of 16G :-)

As stated in the other answer, tmpfs is what you want to use. Further, you won't win a lot by having your entire OS in a ramdisk/tmpfs. Just copy your builddir to a tmpfs and do your compiling then. You may have to ensure that all temporary results are written to a location thats in the tmpfs as well.

I'm not sure that the OP asked for a debate on why or why not to use a ramdisk in the first place. The Lazy Mans' Tech-Support Groups' stock answer: " don't need to be doing that in the first place".

I found that to be very direct & to the point, with some actual benchmark data. But it's always nice to check with SE as it is like watching the View after the morning news broadcast. I'm sure to get a broad perspective on the issues of the day. The efficiency of the memory management of Linux is not the issue. The issue is to avoid having "valuable" data flushed to drive by the sheer fact that the system touches a high percentage of disk data. When you want to lock that data in RAM for maximum performance a ramdisk is the way to go. When you need faster random disk i/o, the answer is to increase disk bandwidth or disk parallelization, where a larger cache and faster disk hardware make more sense than a ramdisk. The question is at what size of a ramdisk, and what rate of accessing what files, does it make more sense to just let the OS allocate the memory to a disk cache. Assuming of course that the OS doesn't let efficiency take precedence over performance. Always, sometimes, never, these all depend on how much and how often? Can the thoughtful user or administrator beat a generic auto-tuning disk cache? Food for thought!

Thanks for your search westf !As I see, it's not easy and maybe even not worth the hassle... Arduino does not like to work with RAMdisks...As reply to your question how to get a ramdisk : there's several ways to do it. Just google "ramdisk" and many programs will show up.

The result of Ramdisk determines whether your device has ramdisk in the boot partition. If your device does not have boot ramdisk, read the Magisk in Recovery section before continuing.

If your device has boot ramdisk, get a copy of the boot.img (or init_boot.img if exists).If your device does NOT have boot ramdisk, get a copy of the recovery.img.You should be able to extract the file you need from official firmware packages or your custom ROM zip.

In the case when your device does not have ramdisk in boot images, Magisk has no choice but to hijack the recovery partition. For these devices, you will have to reboot to recovery every time you want Magisk enabled.

Installing using custom recoveries is only possible if your device has boot ramdisk. Installing Magisk through custom recoveries on modern devices is no longer recommended. If you face any issues, please use the proper Patch Image method.

To adjust the size of the RAMDISK, edit /etc/fstab and verify by remounting the ramdisk (you will lose your current RAMDISK content as you will on reboot). The following will change the size of the ramdisk to 512M

Then all left to do is to specify the file system type, RAM disk size, device name and mount it to the above directory. You can see from the screenshot above that I have plenty of free RAM, so I can easily allocate 1GB for my RAM disk. This can be done with the following one-liner. It will be using tmpfs file system and its size is set to 1024MB. myramdisk is the device name I gave to it.

If you have an existing VM, then select the VM in the main VirtualBox Manager window and go to the menu bar and select Machine -> Move, or right-click the VM and select Move from the context menu. You will be prompted to choose a new folder for the virtual machine. Select /tmp/ramdisk/ as the new folder.


Welcome to the group! You can connect with other members, ge...
Group Page: Groups_SingleGroup
bottom of page