RAIDar "update" destroyed my functioning RAIDar installation

---

mdgm-ntgr wrote:

I have Java 8 installed and RAIDar 6.4.0 works fine for me.

 

I've seen issues with RAIDar being downloaded in the past and it's been at the end user end.

 

I just downloaded RAIDar 4.3.8 using Safari from the ReadyNAS Downloads page and that worked fine.

---

RAIDar was also working fine for me UNTIL I tried to install the latest update, mistook an "app" file for an app rather than an installation file, and in the process clobbered the working version. Since then neither 6.x or 4.x has worked. But I will address your points individually.

1. I have 6.4.0 installed on a MacBook laptop, which in turn has Java 8 version 181 installed. The laptop was able to download & install 6.4 using Safari. RAIDar works on the laptop.

2. I also tried downloading and installing 4.3.8 onto the laptop. The file downloads, and the .dmg file opens. But clicking on the installation app brings up an error window saying, "To open "RAIDar Installer.app" you need to install the legacy Java SE 6 runtime."

From these two observations I conclude that if indeed the problem is on the end user end, it's probably Java-related. But if a piece of software is designed to be downloaded but does not download cleanly due to configuration issues on the client computer's end, and if the instructions for downloading the software do not describe the necessary configuration for successfully downloading the software, and if there is no obvious help page explaining how to deal with such issues, I cannot leave the software's providers off the hook.

To make an analogy, if someone puts regular fuel into a car known to be diesel, and the manufacturer warns against this, then any problems are the end-user's fault; OTOH, if the manufacturer sells the car as one having a conventional engine and does not tell the buyer it's really a diesel that can use only diesel fuel, the manufacturer's at fault.

In any case, my iMac still can't run RAIDar. Knowing that 6.4 installs and runs successfully on systems running Java 8 does not help solve the problem of 6.4 not working on a system running Java 10. While the fact that 6.4 seems to work with Java 8 and the error message calling for a legacy version of Java seem to suggest the problem is Java-related, at this point this is still conjecture. But even if it isn't, I still don't know how to fix the problem.