What is difference in disc based webs vs web based in localhost mode


G

Guest

I'm having a little trouble determining the difference between the following with XP Pro IIS 5.1 j2002 extensions in localhost mode (not publishing). Default directory C:inetpub\wwwroot
1. Opening FP 2002 file/new/web discussion web & create at D:FP webs\discweb. I open IIS and create new/virtual directory named discweb & browse to D:FP Webs\disc web. Then in IE 6.0 , I can open web/localhost:79/discwe
& test my post (which fails either due to FPError See Webmaster or else FP Componen
2. Other approach FP2002 open web localhost:79. File/new folder test. Right click test & convert to web.
Double click and in FP2002 file/new/discussion web at http://localhost/test/discweb. Test post here has worked at times, but also same errors at 1, & I can't reconstruct

a. Is the first one a disk based web and the second a web/server based web
b. Approach 2 puts 2 more folders & some different files into test then approach 1. Is this important
c. Is approach 2 preferred for creating webs
d. If so, how do I get FP2002 to create the web on my D drive where I want to keep all my data instead of in C:inetpub/wwwroot. I tried cutting and pasting inetpub folder to D & renaming it early on but IIS didn't seem to like that
e. The extensions seems to be in inetpub/wwwroot. If I change the default directory to D:FP Webs/root, can I configure extensions for that, and IIS will then act the same ways as with inetpub/wwwroot? Some folders like admin in inetpub don't seems to appear in FP Webs, if I recall my attempt to try to do something like that

Regards, Ro

PS: log error last two lines
22:06:59 192.168.0.140 POST /_vti_bin/_vti_adm/fpadmdll.dll 20
22:06:59 192.168.0.140 GET /_vti_bin/_vti_adm/Images/navlink.gif 20
 
Ad

Advertisements

C

clueless but learning

Anyone should feel free to correct me and anything that I
post, since I am flying blind myself. But a clip I
collected while trying to solve my own issues appears to
answer part of what you asked, about how to change the
default directory for webs in FP. In short, it appears you
can either change an entry in the system registry, or
download a tool that purports to do it for you from the
source named at the bottom below (all of this tip was
obtained from a third party FP support site).

I have not done any of this, can't vouch for it, and merely
pass on the info in case it's of use to somebody else.


-------- snip -----------

FP 2002: How to change the FrontPage Open Page default
directory

When you open the Open Page dialog box, it does default to
My Webs, unlike the Open Web dialog box that defaults to
the last open web directory you opened. To change that, you
have to change a registry key:

To have the FILE > OPEN launch a directory in the Open File
dialog box of my choice - as opposed to the default
location: My Webs - but I don't necessarily recommend
making changes to your registry - unless you know what you
are doing...

HKEY_CURRENT_USER\Software\Microsoft\FrontPage\Explorer\FrontPage Explorer\Settings

change the DefaultWebName from

C:\Documents and Settings\Name of user\My Documents\My Webs
to any old folder path you want it to default to instead...

If you are using FP 2002 you can, instead of changing the
registry, add a new button to the left of the Open Page
dialog box that would give you a one click link to a
directory of your choice... do that:

Open the FrontPage New Page dialog box (FILE > OPEN )
Navigate to the folder you want to add the shortcut to In
the upper right corner of the dialog box select ADD TO MY
PLACES from the TOOLS menu. This will add a button on the
left of the dialog box to the directory you selected.

* OR

For those of you that may be uncomfortable editing the
system registry, Steve Easton of http://www.95isalive.com/
(and long time contributor to the FrontPage newsgroup) has
provided FP users with a free tweak installer to do the
registry work for you! For more information and to
download the installer see: http://www.95isalive.com/fixes/

-----Original Message-----
I'm having a little trouble determining the difference
between the following with XP Pro IIS 5.1 j2002 extensions
in localhost mode (not publishing). Default directory
C:inetpub\wwwroot.
 
T

Thomas A. Rowe

Doesn't really apply when working with a server-based web, as you are
connecting via http. To change the physical location of the web accessed via
http, requires changes to the setting within the web server application,
which then determines where http://localhost actually points to when FP
connects or via a browser.

--

==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, Forums, WebCircle,
MS KB Quick Links, etc.
==============================================


message Anyone should feel free to correct me and anything that I
post, since I am flying blind myself. But a clip I
collected while trying to solve my own issues appears to
answer part of what you asked, about how to change the
default directory for webs in FP. In short, it appears you
can either change an entry in the system registry, or
download a tool that purports to do it for you from the
source named at the bottom below (all of this tip was
obtained from a third party FP support site).

I have not done any of this, can't vouch for it, and merely
pass on the info in case it's of use to somebody else.


-------- snip -----------

FP 2002: How to change the FrontPage Open Page default
directory

When you open the Open Page dialog box, it does default to
My Webs, unlike the Open Web dialog box that defaults to
the last open web directory you opened. To change that, you
have to change a registry key:

To have the FILE > OPEN launch a directory in the Open File
dialog box of my choice - as opposed to the default
location: My Webs - but I don't necessarily recommend
making changes to your registry - unless you know what you
are doing...

HKEY_CURRENT_USER\Software\Microsoft\FrontPage\Explorer\FrontPage
Explorer\Settings

change the DefaultWebName from

C:\Documents and Settings\Name of user\My Documents\My Webs
to any old folder path you want it to default to instead...

If you are using FP 2002 you can, instead of changing the
registry, add a new button to the left of the Open Page
dialog box that would give you a one click link to a
directory of your choice... do that:

Open the FrontPage New Page dialog box (FILE > OPEN )
Navigate to the folder you want to add the shortcut to In
the upper right corner of the dialog box select ADD TO MY
PLACES from the TOOLS menu. This will add a button on the
left of the dialog box to the directory you selected.

* OR

For those of you that may be uncomfortable editing the
system registry, Steve Easton of http://www.95isalive.com/
(and long time contributor to the FrontPage newsgroup) has
provided FP users with a free tweak installer to do the
registry work for you! For more information and to
download the installer see: http://www.95isalive.com/fixes/

-----Original Message-----
I'm having a little trouble determining the difference
between the following with XP Pro IIS 5.1 j2002 extensions
in localhost mode (not publishing). Default directory
C:inetpub\wwwroot.
 
C

Carla B.

To change the physical location of the web accessed via
http, requires changes to the setting within the web server
application, which then determines where http://localhost
actually points <<

This sounds quite relevant to my (still pending) dilemma,
thanks! (The hub is only slightly less clueless than I).

I did realize that the tip I passed on for the benefit of
"cove" might help her but was probably not going to help
me. Nonetheless it's useful to have that confirmed and stop
wondering ;->
 
K

Kevin Spencer

a. Is the first one a disk based web and the second a web/server based
web?

It would be better to understand the principle here than to simply answer
your question. An HTML page is a text document that is read and interpreted
by a browser. A web is a collection of pages and other entities that are in
the same general location (directory) and are linked together via
hyperlinks, etc. A web can be either a disk-based web or a server-based web.
A disk-based web is simply a web that cannot be reached via HTTP, over the
Internet, but only as files on a local machine or network. You can recognize
a URL to a disk-based web, as it always begins with "http://". Browsers
often allow you to drop the protocol section of the URL, which may be a bit
confusing, but the browser uses it internally when navigating to a
server-based web on the Internet. A server-based web has files that exist on
the file system of the machine on which they reside, but they are accessed
via their HTTP URL. So, even though you may have a server-based web locally,
you might stil be able to open the pages in it using their local file system
location, but FrontPage would not be able to properly track changes.

To open a server-based web, always use "http://" in the URL to it in
FrontPage.

--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
Big things are made up
of lots of little things.


cove3 said:
I'm having a little trouble determining the difference between the
following with XP Pro IIS 5.1 j2002 extensions in localhost mode (not
publishing). Default directory C:inetpub\wwwroot.
1. Opening FP 2002 file/new/web discussion web & create at D:FP
webs\discweb. I open IIS and create new/virtual directory named discweb &
browse to D:FP Webs\disc web. Then in IE 6.0 , I can open
web/localhost:79/discweb
& test my post (which fails either due to FPError See Webmaster or else FP Component
2. Other approach FP2002 open web localhost:79. File/new folder test.
Right click test & convert to web.
Double click and in FP2002 file/new/discussion web at
http://localhost/test/discweb. Test post here has worked at times, but also
same errors at 1, & I can't reconstruct:
a. Is the first one a disk based web and the second a web/server based web?
b. Approach 2 puts 2 more folders & some different files into test then approach 1. Is this important?
c. Is approach 2 preferred for creating webs?
d. If so, how do I get FP2002 to create the web on my D drive where I
want to keep all my data instead of in C:inetpub/wwwroot. I tried cutting
and pasting inetpub folder to D & renaming it early on but IIS didn't seem
to like that
e. The extensions seems to be in inetpub/wwwroot. If I change the
default directory to D:FP Webs/root, can I configure extensions for that,
and IIS will then act the same ways as with inetpub/wwwroot? Some folders
like admin in inetpub don't seems to appear in FP Webs, if I recall my
attempt to try to do something like that.
 
G

Guest

Ok, I think I'm getting close. I uninstalled IIS & reinstalled with default extensions. Default directory inetpub/wwwroo
Here's what I've foun

1. Create non-fp extension disc based web at D: FP 2002 file/new/1 page web at D:My Documents/My Webs/nofp. Put sample text in index.htm page
2. In IIS, right click Default Web Site/New/Virtual Directory named "nofp" at above D location
3. Right click nofp/properties/documents & moved index.htm to top. Seems 4 below needs this to fin
4. Open IE 6.0 to http://localhost/nofp. Web opens & all is well. All my non-fp webs can be created & saved on D driv

5. Create fp extension server? based web. FP 2002/open web/http://localhost. View/folder
6. File/new/folder "test". Right click on test/convert folder to web
7. Dble click test & file/new/discussion web at http://localhost/test/discweb. Finish without going through default
8. Open IE 6.0 to http://localhost/test/discweb. (a dreaded fp extensions web). Create post....amazing. It work

Now I have a non-extension disc web on D: and an extension server? web on C:inetpub/wwwroot & both are workin

9. Now for a discussion web on D: FP2002 file/new/discussion web at D:My documents\My Webs\discwe
10. In IIS, right click Default Web Site/New/Virtual Directory named "discweb" at above D location. Don't seem here to have to move index.htm up to to
11. IE 6.0 http://localhost/discweb. Discussion web opens. Create post. Get dreaded FP component erro
12. IIS right click on discweb/check extensions. Message _vti_txt doesn't exist-Corrected. _vti_bin not executable-making it correctible. Now I try 11 again. Same erro

Obviously creating a fp extensions web as a disc based web on D: and not C:inetpub/wwwroot is different & a virtual directory entry doesn't work the same way as for a non-fp web. While I'm close in that I have both webs working, I can't get the fp extension web onto my D drive. As I have two drives with progams on one and data on the other, & I do all my backup on D, I'd like to understand what I'm missing in getting the discussion web to work if it's on D, rather than C

Regards, Ro
 
Ad

Advertisements

T

Thomas A. Rowe

You can not run any FP run-time bots from a disk-based web.

--

==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, Forums, WebCircle,
MS KB Quick Links, etc.
==============================================


cove3 said:
Ok, I think I'm getting close. I uninstalled IIS & reinstalled with
default extensions. Default directory inetpub/wwwroot
Here's what I've found

1. Create non-fp extension disc based web at D: FP 2002 file/new/1 page
web at D:My Documents/My Webs/nofp. Put sample text in index.htm page.
2. In IIS, right click Default Web Site/New/Virtual Directory named "nofp" at above D location.
3. Right click nofp/properties/documents & moved index.htm to top. Seems 4 below needs this to find
4. Open IE 6.0 to http://localhost/nofp. Web opens & all is well. All my
non-fp webs can be created & saved on D drive
5. Create fp extension server? based web. FP 2002/open
web/http://localhost. View/folders
6. File/new/folder "test". Right click on test/convert folder to web.
7. Dble click test & file/new/discussion web at
http://localhost/test/discweb. Finish without going through defaults
8. Open IE 6.0 to http://localhost/test/discweb. (a dreaded fp
extensions web). Create post....amazing. It works
Now I have a non-extension disc web on D: and an extension server? web on
C:inetpub/wwwroot & both are working
9. Now for a discussion web on D: FP2002 file/new/discussion web at D:My documents\My Webs\discweb
10. In IIS, right click Default Web Site/New/Virtual Directory named
"discweb" at above D location. Don't seem here to have to move index.htm up
to top
11. IE 6.0 http://localhost/discweb. Discussion web opens. Create post. Get dreaded FP component error
12. IIS right click on discweb/check extensions. Message _vti_txt
doesn't exist-Corrected. _vti_bin not executable-making it correctible.
Now I try 11 again. Same error
Obviously creating a fp extensions web as a disc based web on D: and not
C:inetpub/wwwroot is different & a virtual directory entry doesn't work the
same way as for a non-fp web. While I'm close in that I have both webs
working, I can't get the fp extension web onto my D drive. As I have two
drives with progams on one and data on the other, & I do all my backup on D,
I'd like to understand what I'm missing in getting the discussion web to
work if it's on D, rather than C:
 
G

Guest

This is helpful, indeed & right on that the principle is what's key here. Now my understanding is this
1. Any webs I create & save on my D drive are disc based webs and are not reachable by browsers. However, if in IIS I create a virtual directory to them, IIS makes them "pseudo server based webs" and treats them the same as if they were created right off as a server based web location http://localhost/test/myweb and stored in inetpub/wwwroot . These webs on D: are therefore browser reachable by http://myip/myweb. Is this correct

2. webs created from the getgo with http://localhost/test/discweb as the location are true server based local webs, are stored in inetpub/wwwroot and are by definition reachable by browsers. Is this correct

3. If the above two are correct, why when I create a server extensions discussion web on D, and tthen create a virtual directory in IIS pointing to it, do I get fp component error in trying to reach it via http? I know on D it's not creating all the files fp extensions needs/uses. I thought if I changed the default directory from inetpub/wwwroot to D:my webs/wwwroot, I might be able to configure/enable server extensions there similar to inetpub/wwwroot, but it didn't seem to work. I think there was no command to do so

So what I have is a server based discussion web at inetpub/wwwroot working fine, but an identical "pseudo server" web at D:My webs/wwwroot with an IIS virtual directory pointing to it, but not working at all

You can see what I'm driving at. If #1 is true, then I should be able to keep all my webs on D:, including those requiring fp extensions. I feel I'm very close to this, and need a little more insight to push me over the top

Thanks & regards, Ron
 
Ad

Advertisements

T

Thomas A. Rowe

See inline below.

--

==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, WebCircle,
MS KB Quick Links, etc.
==============================================


cove3 said:
This is helpful, indeed & right on that the principle is what's key here. Now my understanding is this:
1. Any webs I create & save on my D drive are disc based webs and are not
reachable by browsers. However, if in IIS I create a virtual directory to
them, IIS makes them "pseudo server based webs" and treats them the same as
if they were created right off as a server based web location
http://localhost/test/myweb and stored in inetpub/wwwroot . These webs on
D: are therefore browser reachable by http://myip/myweb. Is this correct?

Yes, they are then server-based web since IIS is now managing the folders
and permissions, etc.
All webs under localhost are server-based webs.
2. webs created from the getgo with http://localhost/test/discweb as the
location are true server based local webs, are stored in inetpub/wwwroot and
are by definition reachable by browsers. Is this correct?

All webs under localhost are server-based webs, with localhost being the
root web, test is a subweb under the root web, and discweb is a subweb of
the test subweb.
3. If the above two are correct, why when I create a server extensions
discussion web on D, and tthen create a virtual directory in IIS pointing to
it, do I get fp component error in trying to reach it via http? I know on D
it's not creating all the files fp extensions needs/uses. I thought if I
changed the default directory from inetpub/wwwroot to D:my webs/wwwroot, I
might be able to configure/enable server extensions there similar to
inetpub/wwwroot, but it didn't seem to work. I think there was no command
to do so.

You need to first create a empty folder on D:, then under IIS MMC, create a
FP web and point the home directory location to the empty folder on drive D,
then open the web in FP as http://localhost/emptywebname (the name you gave
the web in IIS when you created it, it doesn;t have to match the folder's
name)
So what I have is a server based discussion web at inetpub/wwwroot working
fine, but an identical "pseudo server" web at D:My webs/wwwroot with an IIS
virtual directory pointing to it, but not working at all.
You can see what I'm driving at. If #1 is true, then I should be able to
keep all my webs on D:, including those requiring fp extensions. I feel I'm
very close to this, and need a little more insight to push me over the top.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top