Cant Open ANY web at a device ROOT like drive G:

[news.frontiernet.net]

Since this afternoon, I am not able to even OPEN my root directory at device
G:. Nor can I open ANY root directory. Win 98 system.

I get an error message telling me that there is NO Web at device "/G".
NOTICE THE SLASH prior to the device letter.

Prior to this afternoon, I was able to open any root directory. My main web
site is at device G:

I applied the current Office XP service packs to my system this afternoon as
per the instructions I got from the experts in this room.

I am, lost as to what to do.

Reboots dont clear it up.

Do I need to uninstall FP and reinstall? or (God help me) do I need to
reinstall the Operating system? And if I do need to reinstall the OS, what
do I do about the Office XP service packs that were necessary to fix a
problem with FP Web Component Include Content Page?

 

[Thomas A. Rowe]

If it is possible for you to publish all of the current subwebs to another
drive, then using Windows Explorer copy the root web to another a folder on
another drive, then re-format your G drive, then create a new root web, but
as a folder under your G drive, then add subwebs under this folder.

There is a limit to the maximum number of files that can be in the root of a
HD under windows, and you may have hit that number, so by using folders you
can handle a lot more files.

And before anyone ask, I don't recall the maximum number of files allowed in
the root of a drive or if it is still a valid concern with Windows ME, 2000,
or XP.
--

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

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

 

[news.frontiernet.net]

There are LESS THAN 100 files in this root directory. Non were added today
which is when the problem began.

Furthermore, it is no longer possible to open ANY device root with FrontPage
2002. This has always been possible until this afternoon.

The error meggage I get "Server error. There is no web named "/G". Notice
the slash BEFORE the drive letter.

I am suspecting a corruted system. I am suspecting that it happened when I
applied the service packs. I tried to apply one in error and had some
unusual halts.

But, I dont know how to recover.

The suggestion of making the root a folder is a circumvention that I had
already thought about. But it is impractical, because I utilize a
navigations system based upon the root files being in the root on my
authoring system and on the server and refer to files with a URL like
"/Shopping/shop.htm" from all navigation bars on all pages with all
directories. It allows me to develop and test things weel on my local PC.
It works well.

Isnt the error message telling me that I have a corrupted device letter
("/G")?

 

[Thomas A. Rowe]

Does Windows see the drive letter correctly? If so the only thing I can
think of would be to scan the register for /G and try to correct it, but
make sure you have a back up of your G drive.

You might want to try the appropriate Windows Newsgroup for help as well.

--

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

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

 

[news.frontiernet.net]

Windows File Explorer sees the drive correctly. So do other applications. It
is only FrontPage that i have this problem with.

Normally Frontpage will allow one to open any folder or drive and at some
point ask if you want to make it a web. Frontpage wont even do the open now.
I get that message saying "Server error. There is no web named "/G" and it
wont let me even see the drive root.

Frontpage wont even let me access ANY of the drive roots: it has the same
problem with "/C", "/D", "/E","/F","/G","/H" and "/I" which is the last
drive I have defined. Each and every drive root has become inaccessible
since abouth the time that I installed the Office Xp service packs, although
I have no way of knowing if something that happened during that process was
the cause of the problem I am having.

Since other applications do not have a similar problem, I am assuming that
the problem is isolated to FrontPage.

But how do I fix it?