ea3aqr wrote:To restart Thetis I must delete my current database and import a saved one.
Does it run well if you do not import your old database, just run with the rest database (and do a setup manually)?
ea3aqr wrote:To restart Thetis I must delete my current database and import a saved one.
ea3aqr wrote:Impossible to set up new thetis 2.6.8 on my Anan 7000 DLE running P2 2.0 Pre1.
Always ending with a crash. I've deleted all directories (in "program files" and "users") and started building it 100% from scratch (except for my transmiting profile that I always import).
Today, with the latest build from GitHub, (I've tested every single build) while I was setting it up I've clicked on the screen to tune one station on 20m and both VFOs changed to 61.440 and decimals changed from .xxx to .xxxx
I can switch to any band again clicking on it, but the VFOs are still showing 4 decimals
Crash1.jpg
After this crash (I got the same crash every time with every build) Thetis never starts again and always shows the same error.
crash2.jpg
To restart Thetis I must delete my current database and import a saved one.
I don't know what's going on!
Help please
Excuse me for my bad english...
ea3aqr wrote:Later, this afternoon, I will try another clean installation without importing my transmission profile.
Thanks!
vk1hx wrote:There is now an even newer version uploaded to the Github site: Thetis_v2.6.8.0_Setup_17Sept19.msi
vk1hx wrote:NC3Z wrote:I see on the repository that a new 2.6.8 installer (with a 16 Sept date and file name) was uploaded last night. There are no notes like Richie makes so not sure where this repository version lines up with Richie's code.
Hi Gary,
There is now an even newer version uploaded to the Github site: Thetis_v2.6.8.0_Setup_17Sept19.msi
ramdor wrote:All my changes up to and including last night are in there. Its in a big state of flux at the mo as many changes being integrated by Doug from multiple sources. I'm sure when it settles there will be a big change log. Hang in there
vk1hx wrote:Jordi,
As the others have said, try just installing the new version: Thetis_v2.6.8.0_Setup_17Sept19.msi from https://github.com/w5wc/Thetis/releases/tag/v2.6.8 and setting up as a new install. Run Thetis and see if it is stable. If all ok running normal then introduce your TX profiles one at a time and test.
Part of that fatal error message you are getting looks to be a corruption of the main installation application. I've seen similar errors when others have tried to run the Beta Thetis.exe updates on a older version of Thetis or when something did not go right with the installation.
Another thing to look for is when running the Thetis installation setup if you get a windows message that audio applications need to be shut down, cancel the installation of Thetis and shut down those services manually. Then relaunch the Thetis installation.
I see you run a modified Thetis skin? maybe stick to the standard for the moment while testing stability.
You could also reinstall the Microsoft .Net 4.8 installer again just in case its corrupted? You can download the "Offline" installer from this link: .NET Framework 4.8 Offline installer: https://go.microsoft.com/fwlink/?linkid=2088631
I am happy to send you my DB to try. It will be configured for a 7000 DLE (MK1) with audio profiles as a test. you'll need to change VAC settings and CAT settings accordingly. I can email the DB to your QRZ email address if you like?
73 - Phil VK1HX
ea3aqr wrote:Update 1
No Microsoft .Net 4.8 installation possible, setup stops because I have a newer version already installed...
SA3ATF wrote:Hi!
It was this that I tried to explain a bit above here. It was the same phenomenon in the last big release of Thetis and then it worked if you changed the language of the computer to English which I have not been able to test this time.
It is different how comma and dot are used what I can see in the XML files.
ramdor wrote:ea3aqr wrote:Update 1
No Microsoft .Net 4.8 installation possible, setup stops because I have a newer version already installed...
Please you use regedit to check key...
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full
look for Release Dword on the right hand side. You should see decimal value in brackets (528040) or (528049)
All info here...
https://docs.microsoft.com/en-us/dotnet ... -installed
ea3aqr wrote:FOUND!
Looks like the problem is the DX spotting option.
Setup was fine until I've activated this option, on the next click on the screen to tune a station I had a crash.
I was recording all my setup process. I will upload it to Youtube and link the video when done!
Thanks for you help!
ea3aqr wrote:BAD NEWS...
Same crash again without enabling DX Spotter.
ramdor wrote:ea3aqr wrote:BAD NEWS...
Same crash again without enabling DX Spotter.
Yeah thought so as it seemed ok on my installed (and others), but I did fix the click on yellow area bug in the spot window
Is this after a fresh install, after an uninstall, with removal of C:\Users\<user>\AppData\Roaming\OpenHPSDR ?
Also, if you get it up and running again, keep eye on bottom left frequency reading, just before you click to change frequency. Does this number look ok?
Next test will be setting up a vm, with a spanish language install. Or perhaps it is related to really wide display causing issue with freq calculation.
Also, I am investigating the save/apply settings code, I dont like the way it gives up if there is already a save in progress, but this should not cause what you are seeing.
Everyone should be seeing this issue.... very odd.
ramdor wrote:ok, it is language issue, when I change windows over to Spanish (and probably) others the ,. issue happens when reading from db. 24.odd becomes 24 thousand with a ,
Will look into. Cheers to SA3ATF who mentioned it a couple of times
ramdor wrote:Hi,
For those having issues related to region/language (ea3aqr SA3ATF etc) please try : https://www.dropbox.com/s/s2376eb4xf99y ... 9.zip?dl=0
You will need to delete/remove/reset your database, and possibly your memory.xml file if those have become corrupt.
Richie.
changes (b6)
change: forced whole app to en-US, to overcome issue with settings files containing , instead of . Spot and Memory forms were already forced to en-US and caused issues with rest of Thetis
fix: clicking on the spot window (yellow) background does not cause an error