At 06:15 PM 3/3/2006 -0800, Lyle Kopnicky wrote:
Just a S.W.A.G. but not knowing what exactly they mean by NULL have u
tried an ascii null? Maybe if u feed it a 0x00 it'll work.
Isn't 0x00 the same as 0? Or is 0 really a C 0 where 0x00 is a C 0?
Sorry I didn't specify. Getting an ascii
Chris Wagner wrote:
At 07:39 PM 3/1/2006 -0800, Lyle Kopnicky wrote:
According to MSDN, you're supposed to feed SetTargetComputer() a NULL to
get it to target the local host. But I don't have any way of passing a
NULL to the Perl version. I tried undef, and that generates an
Allegakoen, Justin Devanandan wrote:
Can you not just feed it $ENV{'COMPUTERNAME'} ?
Or Win32::NodeName
The other thing I remember doing a while back when we were migrating
machines was copying everything in $ENV{'windir'}\Tasks and putting it
all in the new machine's Tasks folder. In your
At 07:39 PM 3/1/2006 -0800, Lyle Kopnicky wrote:
According to MSDN, you're supposed to feed SetTargetComputer() a NULL to
get it to target the local host. But I don't have any way of passing a
NULL to the Perl version. I tried undef, and that generates an error.
I tried 0, and that fails.
Thanks to those who provided suggestions. They were:
1. Use ENV{'COMPUTERNAME'} - worked
2. SetTargetComputer(\0) - gave an error when calling NewWorkItem()
3. Use Win32::NodeName - worked
I think it would be an improvement to the Win32::TaskScheduler module if
there was a way to get
- Original Message -
From: Lyle Kopnicky
.
.
According to MSDN, you're supposed to feed SetTargetComputer() a NULL to
get it to target the local host. But I don't have any way of passing a
NULL to the Perl version. I tried undef, and that generates an error.
I tried 0, and that
--8
I've found that if I create a new TaskScheduler, then by default it
operates on the local host. But if I change it to point at another
host, then want to point it back at the local host, I don't know how,
without knowing the name of the local host. It isn't convenient, the
