I've been reading this thread and haven't put in my two-cents yet so, for what it's worth, here's my two cents . . .

I use both a Dell laptop with Windows 10 Pro and a Dell desktop with Windows 10 Pro.? I learned a long time ago to make backup image files of my C: drive for various computer configurations so I can reload the image if something gets corrupted installing new software or experimenting with system settings or a virus infects my computer.

One of my backup images is set up for my custom software I use for my part-time work supporting a custom product for a customer.? It also happens to work with zero problems with updating my TinySA Ultra using DfuSe Demo (v3.0.6).? Then I have another backup image configured for things not work related and is used for my video editing and other "fun" things.? And that configuration will not work with DfuSe Demo no matter how hard I try.? I have no idea why the difference and I really don't worry about it since I have a backup image that works with the DfuSe Demo utility program.

I also have a backup image of just a fresh install of Windows 10 Pro in case I want to try installing new software and not have to deal with the possibilities of other software drivers or configurations causing issues with a new software install.

I use Acronis for my backup images but there are other programs out there that will allow you to make an exact backup image too and boot off a thumb drive or CD instead of your hard drive to make images or recover images.

Don't rely on the Windows recovery utility built into the OS!? You'll not get reliable results like you will with an actual recovery image of a known working system.

I have tried about everything proposed in this topic and others at the NanoVNA forum and have given up trying to use my WIN-11 tablet to update the Ultra. Lucky, I still have a WIN7 computer that I use to run some older test equipment and that one, combined with the tinySA-app works like a charm. New OS software is not always better.

John

On Tue, Mar 28, 2023 at 10:54 AM, DiSlord wrote:

right click on any of the files to save them to the PC.

I add only button, real save not work yet :(

DiSlord,
? Thanks for clarifying.? At least image files on the Sandisk card can be saved by double clicking on their name and saving them from the pop-up screen shot window.

Herb

right click on any of the files to save them to the PC.

I add only button, real save not work yet :(

开云体育

Hi Jim,

On Tue, Mar 28, 2023 at 09:19 AM, DiSlord wrote:

You can use NanoVNA-App


TinySA support read file commands as NanoVNA, so possible read screenshots:
Enable SD card panel (use button SD Card)


Select *.bmp
and you can see list of screenshots on card:

Now double click on any file, and image load as screenshot
PS for nanoVNA also possible load snp files

Erik,
? ?I just tried DisLord's latest NanoVNA-APP and the app worked great with the TinySA Ultra for transferring files from the Sandisk card to my PC without removing the card.? This is the functionality I was looking for when I inquired about a CARD READER mode on the TinySA Ultra.?

? How hard would it be to add this feature to TinySA-App?



You can double-click on an image file to view it in a child window, as DisLord posted, or right click on any of the files to save them to the PC.

Herb

Hi Terry
Thank you very much indeed.
Correction made,
I am awaiting the corrected update from Erik before releasing
Kind regards
Kurt

-----Oprindelig meddelelse-----
Fra: tinysa@groups.io <tinysa@groups.io> P? vegne af Terry Perdue
Sendt: 28. marts 2023 17:35
Til: tinysa@groups.io
Emne: Re: [tinysa] Ultra Menu Tree document

Hi Kurt,

A few things I missed. I'll keep looking!

Terry

You can use NanoVNA-App


TinySA support read file commands as NanoVNA, so possible read screenshots:
Enable SD card panel (use button SD Card)


Select *.bmp
and you can see list of screenshots on card:

Now double click on any file, and image load as screenshot
PS for nanoVNA also possible load snp files

The camera icon captures the live screen only.? It does not capture a saved image that is currently displayed on the tinySA Ultra screen

Use the camera icon in the top row ....



If you hoover over each icon a tool tip appears.

Herb

Yes.? 10.6MB

Hi Kurt,

A few things I missed. I'll keep looking!

Terry

@psehome
Did you start the right APP ?
I just wasted an hour, fumbling with the "small" app ... You want the "large" APP (10+MB in size)

See my picts here
/g/tinysa/message/10842

Kurt,
I tried the app, and it would display live screen, but did not display an saved image that was on the diplay.
Paul

Ohh ....

I just installed Wine8 (stable), following this , edited the registry to add COMxx mapping - Noting else.


Btw: My tinysa came w. an SD card inserted ..Thnx :-)

Well - I'm glad i did? try the tinysa Ultra :-)

I upgraded the fw to the latest 1.4-82 (named 1.4-77) , and cleared config , set the clock , calibrated the touch sreen , and gave selftest a spin (PASSED)

I tried the "APP" under Wine in linux , and it's actually working fine (I think)
I did have to install "Wine 8" on my inux-mint 21.1 (a bit reluctantly) , but the app seems to be running fine..




I did waste most of 1h, as i started the : tinySA.exe
And that didn't behave very well .....
I had the idea that the "small .exe" was the launcher for the lager .exe ....
But after i tried the tinySA-APP.exe , i was met with the above screen.

The tinysa is "dancing" a little around /dev/ttyACM0 & /dev/ttyACM1 , but i can see the mapping in the syslog , or else i can prob lock to /dev/tinysa01 via an udev script & the serial.


I have a set of? - 3 x 2 SMA attenuators on the way - 10,20,30 dB weinschel 18GHZ.
Now to calibrate the frequency offset against my counter & gpsdo

Thank you to Erik & all who helped out ...

Carsten

Ps: I attached a "Wine registry extract" of my COMxx to /dev/ttyxxx mapping.

Hi Kurt, yes, makes sense to change the default. Will be in next release
--

开云体育

On Mon, Mar 27, 2023 at 06:38 AM, Bill Cromwell wrote:

Anything beyond a nonjudgmental suggestion should be left out

OK, here's my nonjudgmental suggestion: if vitaliy is worried - and, apparently rightly so, based on his report - that something as simple as installing a driver might trash his Windows system, maybe he should try running Linux from a USB stick, which makes no changes to any operating systems or files installed on the drives in the computer, and update his tinySA from there.? It's easy to do, and would only take a few minutes.? End of nonjudgmental suggestion.

@hwalker - I had *not* seen your post #10798 - following it easily allowed me to upgrade my firmware - thanks! At step #13 I selected the file that I'd downloaded previously (and had renamed "tinySA.bin" per the instructions at tinysa.org) and it worked like a charm. I will have to make a copy of that post and keep it with my TinySA documentation for future reference :)