Not unless its somehow hardcoded. I just unpacked the tgz and copied over my templates and settings (so the same extensions as in 3.8 should be enabled, nothing extra).
Accessible website starting from eZ publish 3.0 (currently: 4.1.0): http://pluspunkt.at
I don't know if the problem is the same but I have the same problem.
I installed xampp 1.6 (last release) and when I try to start the instllation setup of 3.9.1rc1 it doesn't work. Explorer and Firefox reply a "page not found".
Other php scripts and html pages works good. Some ideas?
Strangely enough, the siteaccess selection box in the admin interface INI editor is disabled. But yeah, I even put things in the override settings (manually of course, I am a command line junkie), so the settings were definitely applied.
I "solved" the problem by reworking my templates to work with the root folder, which is semantically cleaner anyway, but still, a strange bug.
Accessible website starting from eZ publish 3.0 (currently: 4.1.0): http://pluspunkt.at
I set IndexPage to a different node than the standard node 2, which worked fine until we upgraded from 3.8.7 to 3.8.8 recently. Now {$module_result|attribute(show,1)} in pagelayout.tpl shows me node_id '2' on the start page despite my ini setting.
I worked around it with a system URL forward from / to /content/view/full/xx (via URL translator in the admin).
Update: I just added a bug report: http://issues.ez.no/IssueView.php?Id=10436