To: Scott Hurring
You probably could have just changed the security restriction on the
dll in question.. the problem was likely that winamp was running in a
separate desktop space from the user apache was running as.. so either
you would have to create a wrapper service, or pretty much do what
You're entirely correct -- IF it was an internet
accessable webserver.
It's installed locally on my workstation solely for
local development. It's got a pretty nice corporate
firewall and "httpd.conf" restrictions setup to deny
access to everyone 'cept me. Of course, firewalls
and corporate LAN
At 09:15 09/07/2002 +, you wrote:
>Message-ID: <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>From: "Scott Hurring" <[EMAIL PROTECTED]>
>Date: Mon, 8 Jul 2002 17:36:52 -0400
>Subject: Re: WinampCOM problem
>
>What user is your Server running as?
Whoa ! This is a really, really *bad* idea - you h
