ATI 2013 - Try & Decide cannot handle Extended Memory - Update of posting

I just tested Try & Decide with the software RamDisk Plus v10 under Win 7 32 Bit Ultimate. Just for the understanding: I have 8 GB memory installed and only 4 GB can be used under Win 7 32 Bit (in reality it is less than 4 GB of the installed memory because HW components have memory too like the graphik card. And the 4 GB is the memory a 32 bit system can address and has little to do with what is installed).

So I use this extended memory from about 4 to 8 GB for a ram disk. I start Try & Decide and so far no problems - the disk is there as before and can be used. But when I reboot the ram disk is gone (did not switch off Try & Decide). I have a different ram disk running without using this extended memory. Here is no problem. Sadly some other installed software would need this disappeared ram disk...and does not work anymore.

Now I switch off Try & Decide and reboot to discard the changes and the ram disk is back again.

What I cannot tell for sure is if the problem is caused by the software RamDisk Plus version 10 or by using the extended memory above 4 GB. To find this out would be a lot of effort since I had to change many things at my current system setup. But Primo Ramdisk Ultimate version 5.5.0 where I do not use this extended memory has no problems.

Update:
=====

I did some further research and found out:

Try & Decide has no problems to manage the extended memory as long as it is not rebooted. If the system is rebooted with Try & Decide it does not allow anymore the usage of the extended memory. What RamDisk Plus does then is that it moves the ram disks to the conventional memory (not to the extended because this is not possible anymore). Since my ram disk was 4 GB there was no space for it in the conventional memory and so it did not get created at reboot (explanation again -> Conventional memory = the memory that a 32 Bit OS can address. Extended memory = all the memory above this. You can address and therefore use this with special software).

What this all means is that Try & Decide cannot handle extended memory after a reboot anymore (with Try & Decide still active). So you do not get the same system that you had before the reboot. I would call this a bug ;-)