MiniTioune V1.0.1p Beta released 25ks
- G1LPS Terry
- Posts: 198
- Joined: Mon Mar 10, 2008 10:33 pm
MiniTioune V1.0.1p Beta released 25ks
Hi All a beta release of MiniTiouner V1.0.1p has just been release over on the Viva Datv forum.
This version allows down to SR25 reception.
The new look is snazzy with a payload diagram generated.
Ive tested it on QO-100 and across the shack It locks quickly and works well.
Check it out.
Many thanks to JP for the early release.
Terry G1LPS
This version allows down to SR25 reception.
The new look is snazzy with a payload diagram generated.
Ive tested it on QO-100 and across the shack It locks quickly and works well.
Check it out.
Many thanks to JP for the early release.
Terry G1LPS
Re: MiniTioune V1.0.1p Beta released 25ks
Is anyone else having problems running this latest version?
The previous version works fine for me but this new one just gives me an error message in French saying “it is impossible to Set Visible in onShow or onHide” (which I think is a Delphi error message) if I click through that the program starts but displays a massive cascading list of error dialogues about memory access violations.
This is on a fairly recent fresh install of Windows 10 Pro.
Colin G4EML
The previous version works fine for me but this new one just gives me an error message in French saying “it is impossible to Set Visible in onShow or onHide” (which I think is a Delphi error message) if I click through that the program starts but displays a massive cascading list of error dialogues about memory access violations.
This is on a fairly recent fresh install of Windows 10 Pro.
Colin G4EML
Re: MiniTioune V1.0.1p Beta released 25ks
Make sure you have 32 bit VLC installed. Also found it didn't work in non-VLC mode on my latest PC.
Mike
Mike
Re: MiniTioune V1.0.1p Beta released 25ks
Yes, 32bit VLC is installed and working on its own.
Re: MiniTioune V1.0.1p Beta released 25ks
Hi Colin,
I had similar problem.
First warning regarding VLC library then the cascading warning.
I changed "Choose Components" in VLC install from Custom to Recommended
That worked for me.
regards Roger G8HKN
I had similar problem.
First warning regarding VLC library then the cascading warning.
I changed "Choose Components" in VLC install from Custom to Recommended
That worked for me.
regards Roger G8HKN
Re: MiniTioune V1.0.1p Beta released 25ks
Thanks Roger, that points to it possibly being a VLC problem. I will try a fresh install of VLC. I know that it needs the 32 bit version, and that is what I am using, but I wonder if the exact version number is also critical. I will see if there is another available.
73 Colin.
73 Colin.
Re: MiniTioune V1.0.1p Beta released 25ks
hi Colin,
I use Ver 3.0.11 Vetinari and it works for me on my win7 PC.
best 73
de
i2NDT Claudio
I use Ver 3.0.11 Vetinari and it works for me on my win7 PC.
best 73
de
i2NDT Claudio
i2NDT Claudio
Dalmine, Italia
Dalmine, Italia
Re: MiniTioune V1.0.1p Beta released 25ks
Where you put it is critical. Minitioune expects the default location - the readme explains where. I am not sure the default is where JP expects for all installations.
Mike
Mike
Re: MiniTioune V1.0.1p Beta released 25ks
There was a discussion on QO100 chat this morning where it looks like JP's instruction are not quite correct:
Noel0:58PA2JSA_JaapJean-Pierre, I think your message by starting the new Minitiouner version about VLC is a littlebit misleading. 32 bits VLC will be stored in Program Files (x86) en 64 bits will stored in Program Files. In the message by starting up it is the other way.
11:04F6DZP Jean-Pierre32 bits VLC will be stored in Program Files (x86) en 64 bits will stored in Program Files. YES
11:05F6DZP Jean-PierreI will check and change
11:10PA2JSA_JaapThe new version is running now on my Minitiouner Express. The problem was the name in the FTprog MinitiounerExpress version Minitiouner-Express. I have changed it. Thanks for the new version.
11:11F6DZP Jean-PierreOK
Re: MiniTioune V1.0.1p Beta released 25ks
Looks like my problem was down to using an older version of VLC.
After removing it and installing V3.0.11-win32 with the recommended settings it now appears to be working OK.
After removing it and installing V3.0.11-win32 with the recommended settings it now appears to be working OK.