$HKLM missing from Win32::Daemon::Simple

renodino has asked for the wisdom of the Perl Monks concerning the following question:

(WinXP Pro, AS 5.8.6) I'm trying to install/use Win32::Daemon::Simple, but the sample app that comes w/ it fails with the following error:

Global symbol "$HKLM" requires explicit package name at C:/Perl/site/l
+ib/Win32/Daemon/Simple.pm line 66.
[download]

There are numerous other such errors in it. Google surfaced a single thread on perl-win32-admin mailist that described the issue, but never specifies the solution, aside from mentioning a replacement version of Win32::Registry, which the Win32::D::S's author's site indicates is for old Perl versions.

Anyone have an idea what magic I'm missing ?

Update:
Found it. I installed the aforementioned Win32::Registry patch and it seems to behave better. It appears the author's website is a bit stale wrt version info - which is a bit disconcerting when installing a module which can completely trash your entire OS installation w/ even the slightest bug. <sigh/>

Comment on $HKLM missing from Win32::Daemon::Simple Download Code

Replies are listed 'Best First'.
Re: $HKLM missing from Win32::Daemon::Simple by spiritway (Vicar) on Nov 28, 2005 at 01:12 UTC
It appears the author's website is a bit stale wrt version info - which is a bit disconcerting when installing a module which can completely trash your entire OS installation w/ even the slightest bug. So true... that's why they all have that big disclaimer about "if it trashes your hard drive, don't blame us". The best thing is to back up your registry (and your data) before getting too creative with the registry.	[reply]

Replies are listed 'Best First'.

Re: $HKLM missing from Win32::Daemon::Simple
by spiritway (Vicar) on Nov 28, 2005 at 01:12 UTC

It appears the author's website is a bit stale wrt version info - which is a bit disconcerting when installing a module which can completely trash your entire OS installation w/ even the slightest bug.

So true... that's why they all have that big disclaimer about "if it trashes your hard drive, don't blame us". The best thing is to back up your registry (and your data) before getting too creative with the registry.

[reply]