Still some quirks, but this is how I got it to work in my case

I posted the following thread:

showthread.php?t=19786

This is not completely resolved but I got it to work, and the following is how I did it. I'm posting a separate thread to share this with others so those having the same issue might be able to try:

1) Uninstall PowerCMS Builder extension via Adobe Extension Manager. Took it half an hour or more to complete the job. It does act as if it's locked up but I left it running because Activity Monitor showed it was doing something. It eventually finished the job.

2) Reinstall PowerCMS Builder beta build. I used Build 38 which is the latest beta at the time this is posted.

3) Delete .dat file under Configuration folder. The instruction is under "Common Installation Issue" link somewhere in this site.

4) Launch Dreamweaver. Mine is CS4. Set up a DW site and make sure both test server and remote server are set up correctly. In my case, I created a dummy site, set Access to local on both and made sure that the URL Prefix matched the one enabled in MAMP Pro. (That's what I use as a test server.)

5) Try the Quick Start Guide instructions. It worked for me this time, I activated the software with my serial code, and I was in.

6) I ran a setup screen in PowerCMS via browser and it gave me an error saying "PowerCMS" directory and "PowerCMS/Connections" didn't have proper write permission. These directories didn't even exist when I looked inside, so I created both, set both to 777, and just in case I set the site root folder to 777 as well. There was no error after that.

7) After the first time you add PowerCMS contents, the connection name in the PowerCMS Builder dialog would say "PowerCMSConnection". I ignored that, went ahead and added more CMS contents, and they all worked fine.

I still don't know why there was no PowerCMS directory when PowerCMS Builder tried to set up PowerCMS. But the trick I performed seemed to work here. Not sure if it will for other people though.

Come to think of it, I suspect the URL Prefix wasn't correct or not filled out when I first tried. Maybe that was why it didn't do anything...?

I would also check database user name and password and make sure not only it's correct but also make sure the user has proper write/access privileges as well.

It's likely that the test server setting and the remote server setting has to match for some reason. In my case, I didn't have the actual remote server (hosting account) so I simply used "local" option and matched them that way. Because of URL Parameter troubles I ran into, I suspect it might cause some issues if you have to use something like "http://localhost/~site" for testing server while having a real domain name for remote server. PowerCMS seems to be very picky about these settings. In my case I run my local test sites on MAMP Pro with "real" domain names. MAMP Pro lets me set up domain names locally very easily, so I can fake a real hosting including domain names. Or, I would just wait to run the installer until I upload the whole package to a remote hosting and run the installer script there.

WA, for your sake I really hope you guys will be able to address all these things at the extension level so we won't have to figure things out like we have been having to. This should've been caught in QA process. So many people are having trouble here....