Tclock-Win10 startup error / Tclock-Win10 起動エラー

[Ander3232]

When I log in to Windows 10 (22H2), this error message appears:

["smiley" icon] "Failed to modify clock: 1"

Screenshot: https://i.postimg.cc/JnxZRc6R/Tclock-Win10-startup-error.png

I close the message, then run Tclock manually, and it works. I gave Tclock's .exe permission to access my protected folders, so that's not the problem.

(BTW, why isn't there a way to attach screenshots here? Isn't it important to show GUI events?)

Thanks, Andy

Windows 10 (22H2) にログインすると、次のエラー メッセージが表示されます:

【「スマイリー」アイコン付き】 "Failed to modify clock: 1"

Screenshot: https://i.postimg.cc/JnxZRc6R/Tclock-Win10-startup-error.png

メッセージを閉じてから、Tclock を手動で実行すると、動作します。

Tclock の .exe に保護されたフォルダーへのアクセス許可を与えたので、それは問題ではありません。

ここにスクリーンショットを添付したいのですが、そのためのボタンが表示されません。

(ところで、ここにスクリーンショットを添付する方法がないのはなぜですか? GUI イベントを表示することは重要ではありませんか?)

ありがとう、Andy

[Ander3232]

Anybody?

[MantisMountainMobile]

Sorry my delayed reply.
I did not know this kind of problem so far.
First of all, as mentioned in readme file, the application is tested only for the case in user folder.
Protected folder + permission, is not tested.

I am away from this project for a while and I cannot answer clearly now.

Error code means that TClock-Win10 was failed find the taskbar when it was launched.

It may caused by any change of Windows OS operation.

If the TClock-Win10 app works correctly when you launch again manually, the solution is that please try to launch TClock-Win10 after the taskbar process was launced by Windows.

It is beyond TClock-Win10's operation and thank you for your understanding in advanec.

[Ander3232]

こんにちは MMM, MMM> Sorry my delayed reply... I did not know this kind of problem so far. First of all, as mentioned in readme file, the application is tested only for the case in user folder. Protected folder + permission, is not tested. I'm not sure what you mean. I installed TClock Win10 the normal way (in C:\Program Files), so it's not in a protected folder (for example, Documents). MMM> Error code means that TClock-Win10 was failed find the taskbar when it was launched... It may caused by any change of Windows OS operation... If the TClock-Win10 app works correctly when you launch again manually, the solution is that please try to launch TClock-Win10 after the taskbar process was launced by Windows. I put TC-W10 in Windows 11's Task Scheduler, with a 1-minute delay—that should be long enough, right? But it still doesn't run. 🤷 It's not a big problem... TC-W10 is so good, I'm glad to run it manually. But I thought you might like to know. BTW, I love Japan. I played music for the Grand Opening of Tokyo Disneyland in 1984. I got to live in Tokyo for several months, and made many friends there. I hope I can visit your beautiful country again... But meanwhile, there are some great Japanese TV shows to enjoy here. My wife and I are now watching the police show "MIU404 – Mobile Investigative Unit". 😊 Tclock を使用した優れたプログラミングに感謝します。 幸運をお祈りしています、Andy  - - Andy Fielding Vancouver, Canada  •  (778) 379-2424 _______________________________________________________________________________ On Sunday, January 29, 2023 at 04:10:54 a.m. PST, Mantis Mountain Mobile ***@***.***> wrote: Sorry my delayed reply. I did not know this kind of problem so far. First of all, as mentioned in readme file, the application is tested only for the case in user folder. Protected folder + permission, is not tested. I am away from this project for a while and I cannot answer clearly now. Error code means that TClock-Win10 was failed find the taskbar when it was launched. It may caused by any change of Windows OS operation. If the TClock-Win10 app works correctly when you launch again manually, the solution is that please try to launch TClock-Win10 after the taskbar process was launced by Windows. It is beyond TClock-Win10's operation and thank you for your understanding in advanec. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>

[MantisMountainMobile]

Dear Andy,

I'm not sure what you mean. I installed TClock Win10 the normal way (in

C:\Program Files), so it's not in a protected folder (for example, Documents). It may be the reason. TClock-Win10 is not designed and confirmed to work in Program Files and other OS folders. It will not work correctly in Program Files. *The "Protected Folder" for me means "Program Files" in my previous e-mail.. It is recommended to have it within your use folder (C:\Users\***your user folder***\). As far as I checked, if you have and launch the APP in your user folder, you can simply make a shortcut in startup, using TClock preferences -> About TClock-Win10 -> Create a Shortcut in Startup. (No need to make any trick in task scheduler) I hope this can be a solution for you. Best, Thank you very much for your sympathy to Japan. 2023年2月6日(月) 17:46 Ander3232 ***@***.***>:

…

こんにちは MMM, MMM> Sorry my delayed reply... I did not know this kind of problem so far. First of all, as mentioned in readme file, the application is tested only for the case in user folder. Protected folder + permission, is not tested. I'm not sure what you mean. I installed TClock Win10 the normal way (in C:\Program Files), so it's not in a protected folder (for example, Documents). MMM> Error code means that TClock-Win10 was failed find the taskbar when it was launched... It may caused by any change of Windows OS operation... If the TClock-Win10 app works correctly when you launch again manually, the solution is that please try to launch TClock-Win10 after the taskbar process was launced by Windows. I put TC-W10 in Windows 11's Task Scheduler, with a 1-minute delay—that should be long enough, right? But it still doesn't run. 🤷 It's not a big problem... TC-W10 is so good, I'm glad to run it manually. But I thought you might like to know. BTW, I love Japan. I played music for the Grand Opening of Tokyo Disneyland in 1984. I got to live in Tokyo for several months, and made many friends there. I hope I can visit your beautiful country again... But meanwhile, there are some great Japanese TV shows to enjoy here. My wife and I are now watching the police show "MIU404 – Mobile Investigative Unit". 😊 Tclock を使用した優れたプログラミングに感謝します。 幸運をお祈りしています、Andy - - Andy Fielding Vancouver, Canada • (778) 379-2424 _______________________________________________________________________________ On Sunday, January 29, 2023 at 04:10:54 a.m. PST, Mantis Mountain Mobile ***@***.***> wrote: Sorry my delayed reply. I did not know this kind of problem so far. First of all, as mentioned in readme file, the application is tested only for the case in user folder. Protected folder + permission, is not tested. I am away from this project for a while and I cannot answer clearly now. Error code means that TClock-Win10 was failed find the taskbar when it was launched. It may caused by any change of Windows OS operation. If the TClock-Win10 app works correctly when you launch again manually, the solution is that please try to launch TClock-Win10 after the taskbar process was launced by Windows. It is beyond TClock-Win10's operation and thank you for your understanding in advanec. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***> — Reply to this email directly, view it on GitHub <#10 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXXWNI3H6YK7VKOAEPSUVJDWWC25HANCNFSM6AAAAAAUG7Z22I> . You are receiving this because you commented.Message ID: ***@***.***>

[Ander3232]

Hi MMM-san 😉 MMM> TClock-Win10 is not designed and confirmed to work in Program Files and other OS folders... It will not work correctly in Program Files. *The "Protected Folder" for me means "Program Files" in my previous e-mail.. I'm running it from my Documents folder, and it's working fine. (I gave the .exe permission, of course.) I don't understand why Microsoft has made Program Files and Program Files (x86) so hard to use—do you? Everything there is Read-Only now, even if you make yourself the "owner". I guess MS doesn't know a better way to protect users from viruses, so they've locked everything. 🤷‍♂️ Maybe it's time to consider Linux (LOL). We also can't completely hide the system clock now... The best we can do is to show a two-digit date (see screenshot). But I'm still glad to have TClock—it looks so much better. Thanks, Andy  - - Andy Fielding Technical Writer, Editor Vancouver, BC, Canada

____________________________________________________________________________________ On Monday, February 6, 2023 at 12:57:46 a.m. PST, Mantis Mountain Mobile ***@***.***> wrote: Dear Andy,

I'm not sure what you mean. I installed TClock Win10 the normal way (in

C:\Program Files), so it's not in a protected folder (for example, Documents). It may be the reason. TClock-Win10 is not designed and confirmed to work in Program Files and other OS folders. It will not work correctly in Program Files. *The "Protected Folder" for me means "Program Files" in my previous e-mail.. It is recommended to have it within your use folder (C:\Users\***your user folder***\). As far as I checked, if you have and launch the APP in your user folder, you can simply make a shortcut in startup, using TClock preferences -> About TClock-Win10 -> Create a Shortcut in Startup. (No need to make any trick in task scheduler) I hope this can be a solution for you. Best, Thank you very much for your sympathy to Japan. 2023年2月6日(月) 17:46 Ander3232 ***@***.***>:

こんにちは MMM, MMM> Sorry my delayed reply... I did not know this kind of problem so far. First of all, as mentioned in readme file, the application is tested only for the case in user folder. Protected folder + permission, is not tested. I'm not sure what you mean. I installed TClock Win10 the normal way (in C:\Program Files), so it's not in a protected folder (for example, Documents). MMM> Error code means that TClock-Win10 was failed find the taskbar when it was launched... It may caused by any change of Windows OS operation... If the TClock-Win10 app works correctly when you launch again manually, the solution is that please try to launch TClock-Win10 after the taskbar process was launced by Windows. I put TC-W10 in Windows 11's Task Scheduler, with a 1-minute delay—that should be long enough, right? But it still doesn't run. 🤷 It's not a big problem... TC-W10 is so good, I'm glad to run it manually. But I thought you might like to know. BTW, I love Japan. I played music for the Grand Opening of Tokyo Disneyland in 1984. I got to live in Tokyo for several months, and made many friends there. I hope I can visit your beautiful country again... But meanwhile, there are some great Japanese TV shows to enjoy here. My wife and I are now watching the police show "MIU404 – Mobile Investigative Unit". 😊 Tclock を使用した優れたプログラミングに感謝します。 幸運をお祈りしています、Andy - - Andy Fielding Vancouver, Canada • (778) 379-2424 _______________________________________________________________________________ On Sunday, January 29, 2023 at 04:10:54 a.m. PST, Mantis Mountain Mobile ***@***.***> wrote: Sorry my delayed reply. I did not know this kind of problem so far. First of all, as mentioned in readme file, the application is tested only for the case in user folder. Protected folder + permission, is not tested. I am away from this project for a while and I cannot answer clearly now. Error code means that TClock-Win10 was failed find the taskbar when it was launched. It may caused by any change of Windows OS operation. If the TClock-Win10 app works correctly when you launch again manually, the solution is that please try to launch TClock-Win10 after the taskbar process was launced by Windows. It is beyond TClock-Win10's operation and thank you for your understanding in advanec. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***> — Reply to this email directly, view it on GitHub <#10 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXXWNI3H6YK7VKOAEPSUVJDWWC25HANCNFSM6AAAAAAUG7Z22I> . You are receiving this because you commented.Message ID: ***@***.***>

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>