← VBar NEO for external transmitters

Installing Vbar Setup Software on Mac OS11 translated

VBar › VBar NEO for external transmitters · Started by horigan on 14 October 2021 02:4314.10.2021 02:43
horigan 14 October 2021 02:4314.10.2021 02:43
I'm having trouble running Vbar Setup software V5.3 or V6.3 on my Macbook Air running OS11, but with a Volume running OS10 (Mojave). I know V5.3 or V6.3 won't run directly on OS11. I've created a Volume on the Mac and installed OS10.

I've successfully installed V6.3 on the OS10 Volume and it sees the NEO (USB green), but is now asking for a key file update to communicate with the NEO. I can see the NEO on my list of devices on Vstabi and have downloaded the updated keys.STO file multiple times and placed it in the Vbar applications folder. Unfortunately, the V6.3 application is still not recognizing the NEO. Interestingly, on my older Mac with OS10 installed as basic, V6.3 can see the NEO. This is when using the same keys.STO file.

For my Blueline Vbar I'm able to run it with V5.2, but it when I try to run V5.3 it asks for a firmware update on the Vbar. When I try to update the Vbar it shows the current version as 5.2.4. When I try to Online Upload the 5.3.4 I get an error, "Error at uploading firmware. Option not available." When I click the Info button it takes me to the Vstabi site where it tells me "This device has already a V5 pro license!
Don't but it twice ;-)". I recall doing this update years ago.

Does anybody have any thoughts in how I can get V6.3 to recognize my device key file or how to get V5.3 to run with the right firmware? If no other options are presented I may trying installing OS10 on a new partition of the Mac and re-installing the V5.3 and V6.3 software.

Many thanks in advance.

Rich
Synergy E5S - Vbar
Synergy 516 - Vbar NEO
Eddi E. aus G. 14 October 2021 10:5014.10.2021 10:50
Hi Rich,

keys.sto must be named exactly so, no numbers (like keys (1).sto from multiple downloads), and I'm not sure if the capital .STO could make a difference.
Please send a screenshot of the folder contents, it should look like this (attachment).

I had 'em all, from 10.4 on, I'm now on Catalina (so no more 4.x/5.x for me), so I know it should work.

About the update, you have to register your legacy VBar if it's not yet registered, and you have to request a license key (free of charge) from vstabi.info/devices, confirm the link in the e-mail you get, then you should be able to update.

Kind regards

Eddi

Born to fly ...
forced to work.



1 mal bearbeitet. Zuletzt am 14.10.2021 10:51 von Eddi E. aus G..

horigan 14 October 2021 19:5214.10.2021 19:52
Thank you Eddi!

The license key request worked great for my V5 Vbar. Thank you.

Attached are two screen shots from my V6.3 NEO. The first one is from my OS11 Mac with a Volume created that's running OS10 Mojave showing the Finder window for the Vbar application. It shows the keys.sto file just downloaded again from my list of devices and the error message I'm getting.

The second file is a screen shot from an older Mac running OS10 Mojave as baseline where the V6.3 app is able to connect to the NEO using the same keys.sto file.

(My earlier post used keys.STO as this was what I recalled when I was trying to run the Vbar setup files on a Windows partition with Bootcamp, but I gave up on that approach.)

I appreciate any insight or suggestions you can provide.

Rich

Eddi E. aus G. 15 October 2021 08:5715.10.2021 08:57
Hi Rich,

the keys.sto file goes _into_ the VBar NEO App, right-click, show package contents, follow the white rabbit.

I suppose you did that on the old installation, and miss it on the new installation.

On Windows, you copy it into the program folder, which equals the App on a Mac.
An App on a Mac is basically a folder with special properties and a special subfolder structure inside, so it doesn't show as a folder but as an App with Icon and everything.
On Windows, there's the folder, and then there's an App Icon in your Start Menu or on your desktop, containing the cue with runtime parameters (pointing to the actual program) as well as icon information etc.

Best,

Eddi

Born to fly ...
forced to work.
horigan 15 October 2021 18:2315.10.2021 18:23
Thanks Eddi! That worked! I didn't know that about the Mac Application file structure. If I had read the Vstabi instructions more carefully, I would have caught that nuance.

Rich
Eddi E. aus G. 18 October 2021 13:0518.10.2021 13:05
;-) it's in the read me.txt file I wrote :-) so yes, no argument here :-)

Cheers

Eddi

Born to fly ...
forced to work.
VStabi VStabi Pioneer of Flybarless