[freenet-support] installation into a decrypted container

[James]

Victor Denisov <vdenisov at ...> writes:

> 
> 
> I guess that this happens because DriveCrypt hadn't finished mounting
> its volumes before the OS decided to start Freenet service. When I was
> running Freenet on an encrypted volume (using TrueCrypt) I had to set
> its start mode to manual, so that it won't be started before I had the
> chance to enter the volume password.
> 
> Regards,
> Victor Denisov.
> 

No, that's not the reason.
I have set the service to start manual, so i start it after mountung the DC 
volume.

The path S:\Freenet\bin\wrapper-windows-x86-32.exe -s S:\Freenet\wrapper.conf' 
in the service is also correct. I just don't know what could be wrong.