Re: [GENERAL] initdb problem on Windows XP Home

2006-12-01 Thread adurrant
Hi Shane, Thanks for the tip. I think be default XP Home has simple file sharing enabled, and there is no way to turn it off. The only way to access the security tab is to log in under Safe Mode. Thanks again. Alex. > > [EMAIL PROTECTED] wrote: > > > (I've discovered this morning that I can b

Re: [GENERAL] initdb problem on Windows XP Home

2006-12-01 Thread adurrant
Hi Richard, Some more information tonight. I logged in under safe mode and checked the security settings for "C:\Program Files\PostgreSQL" and the user postgres had full control. However, I could not issue a cd "C:\Program Files\PostgreSQL". I looked at the security for Program Files, and pos

Re: [GENERAL] initdb problem on Windows XP Home

2006-12-01 Thread adurrant
Hi, I gave restricted permissions to the postgres user on the C: drive. After doing this, I could run initdb without issue. Something doesn't sit right with me with giving access to C: drive, but it works. If anyone has any insights on what this problem is/was and how I can get around it with

[GENERAL] 8.1.5 installation problem with initdb on WinXP Home

2006-12-01 Thread adurrant
Hi, I apologize for being yet another noob posting about this problem. I have spent 2 days searching the archives and the net for a solution to no avail. Hence my post here. The problem I am having is on install of 8.1.5 it fails at the initdb call. In checking the log, it seems to fail when

Re: [GENERAL] initdb problem on Windows XP Home

2006-12-01 Thread adurrant
Hi Richard, Thanks for getting back to me. Yes, I have a "postgres" limited account that will own the files. (This was the one created by the installer.) In order to ensure the this user has access/full control to "C:\Program Files\Postgresql\8.1", I used the "cacls" command to edit the acces

[GENERAL] initdb problem on Windows XP Home

2006-11-30 Thread adurrant
Hi Again, I posted earlier about a problem installing 8.1.5 on Windows XP Home. THat message was delayed, so it likely will not show up. THe problem is occuring on execution of initdb. I skipped the cluster creation in the installation so that I could run it manually, but it made no difference