1. Is it possible for Primo Ramdisk installation to configure automatically without needing the user to go into details of specifying where to start and where to stop the ram blocks, reserve how much of unmanaged ram at the beginning/ending blocks etc? If Primo Ramdisk can determine the environment by itself automatically, less crash will be expected.
2. some devices/drivers will use the ending blocks of unmanaged ram. Primo suggest limiting the size of the ramdisk to not extending into those reserved blocks. This means, the size of the ramdisk will be severely limited. Is it possible that Primo Ramdisk "known" where the memory blocks should be avoided and to continue after those blocks so that the size of the ramdisk is not affected?
3. different versions of Primo Ramdisk have different allowable ramdisk size. The issue is, technology is advancing so fast that today a 4GB ramdisk seems to be quite acceptable may be in 2 years be really unacceptably small. The licence of Primo Ramdisk is however a free lifetime version upgradable licence. How can this lifetime warranty claim be meaningful to the user if the size of the ramdisk is stuck? And, the licence say "Primo" is lifetime upgradable. What if in one year "Primo" is named to say "Supremo", just like "Vsuite" changed into "Primo"? Is there any defined policy to make clear the warranty?
automatic ram configuration
Re: automatic ram configuration
I think the question 1 and 2 are related to the Invisible Memory, correct? Because Invisible Memory is also affected by motherborads and there are quite a lot of motherboard models, it is really not easy to get it automatically configured. Also we need a lot of testing platforms to verify this function.
Regarding the question 3, as you said, different editions of Primo Ramdisk supports different maximum disk size. I don't think this conflicts with the policy of lifetime free updates, does it? When uses buy a license, it means that the current specifications of Primo Ramdisk are accepted, right? A new version may add some functions, fix some bugs, or improves the features/performance, but it does not mean that it must update the specifications to apply for new scenarios. Of course, with the development of the technology, we may increase the maximum disk size supported by different editions of Primo Ramdisk. Users can also upgrade their licenses to an advanced edition with the price difference.
PS. I think Primo Ramdisk will be our final ramdisk product. It is quite impossible to be changed to another product.
Hope this helps.
Thanks.
Regarding the question 3, as you said, different editions of Primo Ramdisk supports different maximum disk size. I don't think this conflicts with the policy of lifetime free updates, does it? When uses buy a license, it means that the current specifications of Primo Ramdisk are accepted, right? A new version may add some functions, fix some bugs, or improves the features/performance, but it does not mean that it must update the specifications to apply for new scenarios. Of course, with the development of the technology, we may increase the maximum disk size supported by different editions of Primo Ramdisk. Users can also upgrade their licenses to an advanced edition with the price difference.
I'm really sorry that the changes of "VSuite" caused such confusions. Actually we always try to smoothly transfer VSuite Ramdisk to Primo Ramdisk. The existing users of VSuite Ramdisk can freely upgrade to Primo Ramdisk, besides, they still own the licenses of VSuite Ramdisk. Anyway, I can assure you that even Primo Ramisk may be upgraded to another product, all its specifications and licenses will be kept and existing users can freely upgrade to the new product.wmiswm wrote:What if in one year "Primo" is named to say "Supremo", just like "Vsuite" changed into "Primo"? Is there any defined policy to make clear the warranty?
PS. I think Primo Ramdisk will be our final ramdisk product. It is quite impossible to be changed to another product.
Hope this helps.
Thanks.
Re: automatic ram configuration
This is not the way to do it. The easiest means is upon initial installation, Primo will install as "safe mode". This means, most of the frequently affected memory blocks are avoided in this safe mode installation. If the user choose "optimize", then Primo will launch a small memory resident optimizer. This optimizer will take a snap shot of invisible memory blocks and create a checksum table for each of the blocks. The optimizer will take snap shot of the memory blocks again periodically, say when the computer is idle, and compare the new checksum table with that of the original table. Another table is then created recording the addresses of the memory blocks that have changed values. This process is kept ongoing until a certain accumulated period of computer operation. The optimizer will then configure Primo to avoid those memory blocks that will change value with computer operation. Upon finishing the optimization process, the optimizer will terminate by itself.Because Invisible Memory is also affected by motherborads and there are quite a lot of motherboard models, it is really not easy to get it automatically configured. Also we need a lot of testing platforms to verify this function.
Re: automatic ram configuration
This method seems workable. However there are still some issues needed to be overcome. For eg, the "optimization" process may take lots of time, and still, the results are not reliable. Besides, for Invisible Memory, it is not safe on some motherboards to monitor data before you have already detected the range.
Anyway, the idea is quite great! Thank you, wmiswm!
Anyway, the idea is quite great! Thank you, wmiswm!
Re: automatic ram configuration
Your concern is valid but is solvable by simple approach.
If the system becomes unstable for whatever reason, the user is instructed to go back to the control panel of Primo and re-activate the optimizer. By re-activating the optimizer, Primo reverts temporary back to safe mode.
It may even be better that Primo only uses system managed memory in safe mode, then extending to the invisible memory upon optimization. The user can specify a minimal ramdisk size for safe mode, and state the intended size of optimized mode if invisible memory is detected safe by the optimizer. Or alternatively, the user can have a choice to run the optimizer first, without setting up for a ramdisk at the moment. After the optimizer detect the safe zone of the invisible memory, the user can then set up the ramdisk as desire.
The optimizer is re-activated to detect for invisible memory block changes. The user is instructed to run whatever application that cause the instability. The optimizer then detect the causative memory block addresses and add in the cumulative avoid table for re-configuration of the Primo ramdisk. This approach though may not be bullet proof, will be much more reliable than user (layman) configuration.
If the system becomes unstable for whatever reason, the user is instructed to go back to the control panel of Primo and re-activate the optimizer. By re-activating the optimizer, Primo reverts temporary back to safe mode.
It may even be better that Primo only uses system managed memory in safe mode, then extending to the invisible memory upon optimization. The user can specify a minimal ramdisk size for safe mode, and state the intended size of optimized mode if invisible memory is detected safe by the optimizer. Or alternatively, the user can have a choice to run the optimizer first, without setting up for a ramdisk at the moment. After the optimizer detect the safe zone of the invisible memory, the user can then set up the ramdisk as desire.
The optimizer is re-activated to detect for invisible memory block changes. The user is instructed to run whatever application that cause the instability. The optimizer then detect the causative memory block addresses and add in the cumulative avoid table for re-configuration of the Primo ramdisk. This approach though may not be bullet proof, will be much more reliable than user (layman) configuration.
Re: automatic ram configuration
Personally I think there still be some issues with this method. Anyway I have already delivered your suggestions to our R&D team.
Many thanks.
Many thanks.