I have xoop srunning without trouble in mydomain.com/xoops.
Installing it into a seperate directory was a breeze.
No errors during install, it all went so well. Had to use this tweak, but after that it all went well.

then i tried to redo it, this time into my publi_html folder, or root folder. This way people can view sites by intering mydomain.com rather then mydomain.com/xoops.
It should be simple really. But for some reasson I can not complete the install process in my root folder.
I get this error:

check path & URL
Physical path is correct.
Physical path must be a directory.
Virtual path is a valid URL.

The server path to your XOOPS root directory: D:/Clients/my_ID/mydomain.com/public_html
URL to your XOOPS root directory: http://mydomain.com.85.seekdotnet.com



Correct me if I am wrong, but the pulic_html folder is a directory, right?

Below are the server info:

General Server Information
Operating System Windows 2003
.NET Version 1.1.4322 & 2.0 and 2.0
PHP Version 5.12
IIS Version 6
Perl Version Active Perl 5.8
MySQL 5.12
Xoops 2.0.13.2
host: seekdotnet.com

So , basically I can install and run it if I install it into a subfolder of the public_html folder. How can I install it into the root folder?

Hmm. Strange. I tried to muscle past the error during the install, and guess what, it is working.
The databse connection worked, and the tables was created.
When I clicked the link to my site, I was rather impressed that it would run, becaause of the error.

I guess one have the option to override the installer, by muscle past it

I had the same problem and thanks to your post, I followed what you did and "muscled" past the error for direct path. I have Yahoo hosting and the root directory is a /. XOOPS has a problem with the trailing backslash and since my root directory is only a backslash, it shows and error with direct physical path.

I had installed Mambo previously and it installed fine in the / directory so I knew it was correct.

When I continued with the XOOPS installer past this error, it worked fine!

Thanks!