then 5 pounds of chips on the way back is worth millions of dollars so it can be flown on a passenger jet or fedex jet that is already going here. or a boat and take up 3% of a container
AntView is an ActiveX wrapper for the Microsoft WebView2 component. AntView enables programming languages that cannot use the WebView2 component directly to have a modern browser component in their applications.
I had to blink twice last time when I installed Sonoma on a new partition that I did not have to provide a wifi password.
This appears to confirm that. While I can understand that some people would appreciate this, I'm not exactly chuffed by a fresh install silently grabbing passwords from an old install.
It has the SSID in plaintext in current-network and preferred-network, not the passphrase. I’m not sure how it’s obfuscated or encrypted but it is not plaintext
The other commenter is correct - the last (few?) Wi-Fi passwords are stored in NVRAM so that the recovery environment can connect to the network more conveniently.
The tinySA can also be used for that, it's not only a spectrum analyzer, it can also generate signals and optionally modulate those for you.
edit: https://tinysa.org/wiki/pmwiki.php?n=Main.Specification here says it works from 100kHz for the low output. When I just tried it did let me select 60kHz and turn it into output mode. Haven't hooked it up to a scope to see what it does. Sorry no time to set it all up now.
60kHz is very low though, if you browse AliExpress then I'm sure plenty of signal generators will offer that for a really low price (cheaper than the tinySA)
edit 2: Sorry my European brain kicked in and missed you are looking for a 60Hz one that is very precise and not a 60kHz one. I'd better get some sleep.
> It did not seem to affect home computers like the Apple ][, Commodore 64, and such.
Your software most likely did not ran off a hard disk. So it was slow to load anyways.. and after that it ran within the memory it had. One program at a time, no memory swapping.
> I don't think it affected PC compatible computers running DOS.
Umm.. I remember being mesmerized by disk defrag programs.
There was also TSR programs and other ways to run more as one program at a time.
Circa 1987 I switched from a TRS-80 Color Computer 3 which had two floppy drives to a 286-based IBM AT clone with an HDD that almost exclusively ran MS-DOS or DR-DOS.
In general though if you have more state there is more possibility that the state goes bad (e.g. malware counts as "bad state", as does a configuration database growing without bound, or something like the XP-era updating mechanism in Windows that was O(N^2) in terms of the number of previous updates)
I could swear I didn't notice this rot with that 286 machine, the 486 machine I replaced it on that ran Linux, the Sun 3 and Sun SPARC workstations at my undergrad school, AIX workstations at grad school, etc. (There was the SGI machine that always struggled to get out of its own way at anything that a professor bought, never bothered to set a route password, never got anything done with it, but left it plugged into the Ethernet and power)
Once we got into modern Linux distributions like Fedora that had Gnome or KDE I definitely had this problem though.