Noob_Is_Relative (OP)
Jr. Member
 Offline
Activity: 45
Merit: 62
|
First, let me state my bias: I hate, oh, wrong word, I LOATHE Windows OS. I have been running Linux as my primary OS since 2001. Like a lot of Linux users, I run Windows because I must, in my case, mandatory imaging software for my Zeiss microscope. I also run the Core on Windows because my linux box doesn’t meet the hardware specs I need for a complete blockchain without pruning.
Cutting to the Chase
When you download the Core from bitcoin.org you can see that the team, the devs, recommend checking the box in settings for running at logon to Windows. I did that.
Windows being Windows, in spite of the fact that I have a newly purchased Dell machine and a virgin Windows 11 OS and 16 GB of RAM, that all programs, in general, are very slow to load—think minutes rather than seconds. On my Linux machine, loading is in seconds. And the Core in Windows is so slow that many a time I did not know if there was an error and it had failed to load.
In fairness to Windows, I do have a hardware bottleneck. Although I have the storage capacity I need for personal use and running the Core, 1 TB, on Windows, on Linux I have a Samsung ssd on a fast M.2. bus whereas on Windows I have a hdd on SATA. This explains some of the problem but not, I think, all.
When it seemed that the Core was having a problem and not loading, I then went to the app directly and initiated it. Then I got a message that said it was already running. Hmm. It’s already running but it’s nowhere to be found. It’s running but it hasn’t yet loaded on the level of the GUI yet. Of course, running a daemon from CLI would bypass all that nonsense but also be more difficult to interact with.
Then, for some weeks, I was playing cat and mouse between "start when login" and going directly to the app. After playing for a while, the app ran until I needed to reboot a few days later, and play another cat and mouse game.
I run the Core 24/7 and if I had my druthers I’d never reboot but, as you know, sometimes it’s necessary.
Suffice it to say that eventually my under the hood start files became corrupted as indicated by an error message. After googling, it became pretty obvious that there was no solution except uninstall and reinstall the Core, a major hassle, second only to doing a fresh install of the OS.
So, as I now count the hours, for the second iteration of the blockchain to download—it’s been about 48 hours—so that progress shows 1.0, I decided to NOT check start at login. With Windows’ wonkiness and one more thing to break, I decided to go without.
When I had network issues during the downloading, I checked out my new protocol. Shutdown via stop command in the Console. The GUI window appears and disappears. I also keep Task Manage open and can confirm that that process is killed.
Then when I reboot, the Core is doing nothing, ah good, just what I want. Then I wait for Windows GUI to stabilize. Generally, when Dropbox gives me a check that it’s up to date, I know that the system is stable. Dropbox takes some time because it must connect, index, etc.
Then I go to the Core app click on it and wait for it to load. It still takes some time and I can see that it loads different things at different times but fine, I can eyeball what is happening whereas in the start on log I can’t see anything, it’s taking forever, and I don’t know if it’s broken.
So, for now, never start at logon!
What’s your experience with start at logon, particularly for Windows, but also for Linux and Mac OS?
|
