On 11/16/2022 1:19 PM, Mayayana wrote:
"AK" <[email protected]> wrote
|I have not found anything for Ubuntu that suits my needs.
|
| I need a simple timer that can show a user defined message.
|
| I have wine installed, so many Windows programs will work.
|
If it were me I'd use a VBScript. I don't know
if that's orth your trouble. You might have to install
Windows Script Host. (scrrun.dll, etc) Last time I
tried Wine it was a mess, divided into 32 and 64 bit
and difficult to use actual Windows libraries. So I
don't have easy instructions.
It's a very simple script:
For i = 1 to 5
WScript.Sleep 1000
Next
Msgbox "This is the message."
Sleep pauses for a given number of ms. This script
waits 5 seconds.
WinXP had "at". The temporal aspect can be handled by the scheduler.
at 23:41 some.bat
Linux happens to have a look-alike "at"
at 11:41 PM "/usr/bin/some"
But when I tried the Linux version, a check
with "atq" showed it was in the job queue, but
it didn't fire as near as I could tell. Probably
needs some systemctl command to get the equivalent
of the atd daemon running.
In Windows, "at" was discontinued past WinXP, because
it was considered a security risk. It's possible it
was running jobs as SYSTEM, and if you put cmd.exe
as the executable, that would provide a way of elevating
for a limited user. Something like that.
You could even incorporate some WINE in there if you wanted.
I expect the Linux version just runs as the user who registered
the job in their personal queue.
The purpose of using a ready-made calendar style application,
is not because it delivers sparkle ponies, it's because
packages like that are more likely to have been inspected
when put in the tree. Whereas crappy little "at" likely got
half-hearted attention. I'm sure it would work with
enough pampering.
https://web.archive.org/web/20210815082014/https://opensource.com/article/21/8/linux-at-command
One reason I'm not a huge fan of WINE, is the out-of-the-box
configuration in the popular distros isn't very good. And it's
possible the materials involved in a proper installation of
WINE, have "licensing issues". The lawyers likely prevent
a curated set of "winetricks" from being executed.
In Linux, it used to be the same issue with the NVidia driver
versus the Nouveau driver. They likely wanted to make
the NVidia driver install for NVidia cards, but their
"license esthetic" prevented that. You do occasionally find
a distro where the NVidia is installed for you. The only
reason I don't "clamor for Nouveau", is it loses communications
with my 1080 and has no VPU recover coded up. Which yields a
black screen and is no fun at all.
Paul
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)