Qsoft Ramdisk X64 Crack
2017, September 22 th: Limited amount of packages for sale. Starting from 2017, October 1st, users will be provided with a pre-built version 5.3.2.15. There are currently about 1000 x64 pre-built packages available, and about 150 x86 pre-built packages available. When this stock is exhausted, selling of this ramdisk product will end and the site will go off line.
2017, Februar 21 th: The WinRamtech ramdisk configured to its 128 GB limit on Server 2012 R2. 2016, October 18 th: The WinRamtech ramdisk installs and runs smoothly on Windows Server 2016 Essentials Evaluation. Tests as per date above have proven that the current version 5.3.2.15 runs without any issues on the 'Windows Server 2016' OS version. This was expected since the kernel software of Windows Server 2016 is practically the same as the Windows 10 kernel.
As per consequence and announced on 2016, August 17th below, version 5.3.2.15 will be the last and final release of this ramdisk product. 2016, September 29 th: The WinRamtech ramdisk installs and runs smoothly on Windows Server 2016 Essentials Technical Preview 5. 2016, August 17th: WinRamtech ramdisk 'full support with updates' not available anymore.
Because of the increasing costs and decreasing demand, the effort to provide the 'full support with updates' option becomes to high compared to the benefit. For the same reason, updates to existing 'full support with updates' users will only be provided upon corrections to reported bugs ( as far as a correction or amelioration is possible ) till 2017, August 1st. What does this mean in practice? 1) Development of the ramdisk software will end on 2017, August 1st. 2) If the current version 5.3.2.15 works flawlessly and without any issues on the upcoming 'Windows Server 2016' OS version, it will be the last version of the life time of this ramdisk product. If corrections are necessary, a new version 5.3.2.16 will be distributed to all existing 'full support with updates' users before 2017, August 1st and this update version 5.3.2.16 will then become the final version of the ramdisk product. Will this software be still available after 2017, August 1st?
Yes, the 'no support without updates' option will remain available for a restricted amount of new users. 2016, Mars 12th: WinRamtech ramdisk price changes.
The price of the 'full support' 64-bit version is slightly increased from $25 USD to $26 USD. The price of the 'no-support' 64-bit version is reduced from $12 USD to $11 USD. 2015, July 26th: The WinRamtech ramdisk may not install on Windows 10 after 2016, August 8th. ( Updated: August 4th ) Microsoft has decided to introduce a new Code Signing strategy for kernel mode Device Drivers in Windows 10. Since the ramdisk is a PNP kernel mode device driver, it is affected by this new regulation. This implies that: a) the Device Driver software must be signed with a new EV ( Extended Validation ) Code Signing certificate. B) each package with the signed driver must be submitted to and additionally signed by the 'Windows Hardware Developer Center Dashboard portal' ( ) More details about this new strategy can be found here: Consequences: Custom builts, as they were used in the past by providing each individual user with an own time stamped or branded version will not be possible anymore after 2016, August 8th.
This was especially practiced for OEM users and for 'full support' users that automatically obtained updates with their 'branded' e-mail address in the RAMDriv.sys driver file. The CERTUM CA ( Certification Authority ) does currently not provide EV certificates. They will not become available before 2016 to individual developers.
By this, the ramdisk software can currently not be signed and submitted to the Microsoft Dashboard which makes it unavailable for Windows 10. What is about to change: New users after 2016, August 8th will still be able to purchase 'full support' versions and existing users will still receive updates with a Ramdisk version that installs and works on Windows OS versions prior to Windows 10 ( starting from Win2000 to up to Windows 8.1 ) and on Windows 10 with 'Secure Boot' disabled ( Secure Boot Overview: ). Support for Windows 10 with 'Secure Boot' may become available again in 2016.
The price for this specific version will however drastically increase, and it will be sold as 'non support' i.e. Without providing automatic updates.
Each update will have to be purchased again. The time needed to manually submit the package to the Dashboard prevents providing individualized updates to every existing full support user.
The increased price is regrettably caused by the increased amount of costs to support this ramdisk: - yearly and expensive payment to Microsoft for receiving tools and operating systems - the price for the currently used Code Signing certicate to support OS verions from XP to up to Windows 8.1 - the high price for the EV certificate to be used to sign and to submit the software after 2016, August 8th. The sum of these costs EXCEEDS currently the yearly revenue of providing the software to customers and OEM users.
As described in the OSR blog from the link above, the current ramdisk version will install and run on Windows 10 when disabling 'Secure Boot', which is not recommended and meant for test purposes only. Also, users that do pay for 'non-support' will receive a package that will install and run on Windows 10, even with 'Secure Boot' enabled. This applies to OEM users and for 'full-support' users as well under the condition that they purchase the ramdisk before 2016, August 8th. After that date, OEM users will have to code sign and submit the package themselves with their own code signing certificate. 2015, June 2nd: The WinRamtech ramdisk installs and runs smoothly on Windows 10 Enterprise Insider Preview. 2015, Januar 21th: Concurrent benchmark of two different ramdisk programs installed on the same computer The speed of ramdisks strongly depends on the used PC hardware ( CPU, RAM speed, etc. A benchmark of a ramdisk is by this to interprete with caution.
The most accurate tests are comparative tests between one or more ramdisks on the same PC, with the same ramdisk size an using the same file system. To be accurate, the tests must even be carried out simultaneously ( concurrent run of the ramdisks ), thus by starting the benchmarks at the same time. Next picture shows a concurrent run of the Dataram ramdisk ( drive E: ) and the Winramtech ramdisk ( drive B: ).
Next picture shows a concurrent run of the SoftPerfect ramdisk ( drive H: ) and the Winramtech ramdisk ( drive B: ). 2014, November 19th: 'Fast Startup' on Windows 8 Starting with Windows 8, the OS uses per default a hybrid combination of a cold startup and a wake-from-hibernation. In practice, services and applications stop running and are closed at shutdown, but the status of kernel memory, including the status of device drivers and the memory it uses, is saved into the hybernation file.
This method increases the start up time during boot. As per consequence however, the content of the ramdisk is saved as well. This behaveour differs from the behaveour on older Windows versions and this is sometimes not whished at all. To clean the ramdisk content on Windows 8 at shutdown, a small utitity 'RAMDrivCleanContent.exe' was created. It can be download here: How it works and how to use it?
On startup of that utility, it writes an entry in the registry that tells the OS to start it up again during the next boot. Once started, it sleeps ( does not perform any action ) and waits for the OS shutdown. When shutdown occurs, it first deletes all ramdisk content and then ends. While the utility runs, a icon is displayed on the taskbar. See picture hereafter.
The user has to customize this icon to 'always show' it. When the user clicks on the icon with the right mouse button, a popup window is displayed. When pushing 'Uninstall RAMDrivCleanContent', the utility ends after deleting the registry entry that tells the OS to start it up at boot time. When pushing 'Exit RAMDrivCleanContent', the utility simply ends. In both cases, no actions will be taken at shutdown since the utility is not running anymore. To use this utility, copy it on the hard disk into an existing directory or a new directory of your choice and start it up.
When moving the utility to another location, one has to start up it once again to refresh the registry entry. Since the ramdisk is not restarted when the OS boots from its hybernation state, and thus can not reload an image file, the utility will NOT clean the content when the ramdisk did load its image file. In this case, the ramdisk acts as if 'Save content at shutdown' was set. 2014, October 27th: Version 5.3.2.15 compatible with Windows 10! Version 5.3.2.15 installs and works without a problem on the upcoming Windows 10 64-bit version ( available from Tech review as Evaluation Version ).
Qsoft Ramdisk X64 Cracker
2014, Januari 12th: Version 5.3.2.15 released. Version 5.3.2.15 is now available for download and purchase. Changes to this version are described below. The distribution of updates to the full support users has completed. 2013, November 24th: Urgently testers wanted! The upcoming version will be capable to be configured as a 128 GB disk.
To achieve this goal, I kindly ask the owners or users of systems with more than 128 GB on board to cooperate with the development of this version whose release date depends on those test results. Users should run the 64-bit version of Windows 8 or Server 2012 per preference. The upcoming version will correct following issues: - Due to a changed behavior while setting security on registry keys, the content within 'RAMDisk Properties' panel and within the Image Configuration Utility was broken on Windows 8 within a non-administrative account. The ramdisk is extended to allocate 128 GB and the possibility to configure these bigger sizes is enabled in 'RAMDriv Properties'. Potential Driver software crash when using the exFAT filesystem on the ramdisk with a disk size bigger than 24 GB. Automated memory allocation when loading image files.
Version 5.3.2.15 allocates the necessary ramdisk space calculated out of the bootsector from an image file that has to be loaded. Within previous versions, the ramdisk disksize had to be manually configured to a value that matches the bootsector Image File coordinates. BSOD may occur after the trial version has expired ( trial version only problem ). This problem has been solved. Reordered selectable disk sizes within 'RAMDriv Properties'. Prevent of driver crash when the image file could not be read due to a hard disk hardware error. Optimized Image Load.
When using the non-compatible Image File format, the map of occupied blocks of 32 MB are stored into a 512 byte bitmap at the beginning of the Image File. This bitmap now reflects more accurate the occupied blocks without a manually saving of the ramdisk content.
2013, May 21th: Testers wanted! The upcoming version will be capable to be configured as a 128 GB disk. To achieve this goal, I kindly ask the owners or users of systems with more than 128 GB on board to cooperate with the development of this version. Users should run the 64-bit version of Windows 8 or Server 2012. 2013, Januar 18th: Update Versions 5.3.2.14 not available anymore at Full support users whose updates to version 5.3.2.14 are stored at may not be able anymore to download their version via the link at the bottom of the update notification e-mail. These users may still request to receive their update version via e-mail.
2012, December 07th: Versions 5.3.2.14 released. Version 5.3.2.14 is now available to be purchased. All update notification e-mails have been sent to the 'full support' users. From now on, the purchase of the 'full support' 32-bit version is abandoned due to the lack of interest.
This 'full support' 32-bit version will still be made available when it is purchased together with the 'full support' 64-bit version for the price of $35.00 USD or more. Existing 'full support' 32-bit version users will still receive updates as before. 2012, October 28th: Development progress. The release of the new version 5.3.2.14 is planned before the end of 2012, but new 'full support' users may get a final 'RTM' ( Ready To Manufacture ) version upon their payment. They have to request for this RTM before they make their payment.