Extended Error Code

(This is a question about running in MSDOS from a Win98 bootdisk ... I
couldn't find a more appropriate looking Microsoft group to use. If
it's inappropriate here, perhaps someone could direct me to the
correct group).

I'm trying to set up a dos boot with network access so that I can
backup my systems to a network storage device using Ghost. After some
initial difficulties I now have the setup booting correctly and
mapping the network storage share to a drive letter.

I can change to that drive letter, I can change directories on the
share and I can copy files to the share. However, when I do a DIR on
the share or its subdirectories I get no listing. All I get is:

Volume in drive X has no label
Extended Error 123

I've been searching both google and ms support to determine what this
error code means but can find no information. Any help would be most
appreciated.

On Sun, 02 Jan 2005 15:23:20 -0500, WoofWoof
wrote:

(This is a question about running in MSDOS from a Win98 bootdisk ... I
couldn't find a more appropriate looking Microsoft group to use. If
it's inappropriate here, perhaps someone could direct me to the
correct group).

I'm trying to set up a dos boot with network access so that I can
backup my systems to a network storage device using Ghost. After some
initial difficulties I now have the setup booting correctly and
mapping the network storage share to a drive letter.

I can change to that drive letter, I can change directories on the
share and I can copy files to the share. However, when I do a DIR on
the share or its subdirectories I get no listing. All I get is:

Volume in drive X has no label
Extended Error 123

I've been searching both google and ms support to determine what this
error code means but can find no information. Any help would be most
appreciated.

Found this:
Code Description Name
123 The filename, directory
name, or volume label
syntax is incorrect ERROR_INVALID_NAME

The mounted file system does not support extended attributes ...

Regards,

Bill Watt
Computer Help and Information http://home.epix.net/~bwatt/

Bill Watt wrote:

On Sun, 02 Jan 2005 15:23:20 -0500, WoofWoof
wrote:

(This is a question about running in MSDOS from a Win98 bootdisk ... I
couldn't find a more appropriate looking Microsoft group to use. If
it's inappropriate here, perhaps someone could direct me to the
correct group).

I'm trying to set up a dos boot with network access so that I can
backup my systems to a network storage device using Ghost. After some
initial difficulties I now have the setup booting correctly and
mapping the network storage share to a drive letter.

I can change to that drive letter, I can change directories on the
share and I can copy files to the share. However, when I do a DIR on
the share or its subdirectories I get no listing. All I get is:

Volume in drive X has no label
Extended Error 123

I've been searching both google and ms support to determine what this
error code means but can find no information. Any help would be most
appreciated.

Found this:
Code Description Name
123 The filename, directory
name, or volume label
syntax is incorrect ERROR_INVALID_NAME

The mounted file system does not support extended attributes ...

Thanks, Bill. The storage device I'm using is the Linksys NSLU2 which
is actually a small Linux (tiny) server. I suspect that the developers
concentrated on Windows9x/2000/XP and Linux connections and didn't
seriously check it out from a dos connection - which is a shame
because it is (or would be) an ideal device for backing up Windows
partitions using Ghost run from dos.

In fact, I have run Ghost and it will actually backup and restore from
the device. But here again, the file window for the device is empty so
you have to kind of do it "in the dark" .... specify a filename to
save to which you know doesn't already exist and when restoring you
have to know ahead the filename that you want and type it in. Not an
ideal situation.

I've discovered that there's quite a bit of activity on the internet
with hacked (replacement) firmware for this device so perhaps I'll
give that a try.

Does DIR/B work?
--
Jeff Richards
MS MVP (Windows - Shell/User)
"WoofWoof" wrote in message
...

snip

I've discovered that there's quite a bit of activity on the internet
with hacked (replacement) firmware for this device so perhaps I'll
give that a try.

No, 'fraid not. I still get the "Extended Error 123" result with no
listing. (The "Volume in drive X has no label" message is absent with
this
switch).

Interesting though: if I put a file, say test.txt on this drive and do
a " DIR test.txt ", I get a normal directory listing without an error
message. However, if I do a " DIR *.txt ", I get the error message and
no listing as before.

Jeff Richards wrote:

Does DIR/B work?
--
Jeff Richards
MS MVP (Windows - Shell/User)
"WoofWoof" wrote in message
...

snip

I've discovered that there's quite a bit of activity on the internet
with hacked (replacement) firmware for this device so perhaps I'll
give that a try.

So the problem goes deeper than a volume or directory name. Any sensible
backup procedure is going to need to be able to list the current contents of
a folder, so unless you can map to a folder that is specially created to
avoid the extended attributes, you're going to need an intermediate layer
that can translate between the two systems. This is usually part of the
network software, but I don't know which end.
--
Jeff Richards
MS MVP (Windows - Shell/User)
"WoofWoof" wrote in message
...
No, 'fraid not. I still get the "Extended Error 123" result with no
listing. (The "Volume in drive X has no label" message is absent with
this
switch).

Interesting though: if I put a file, say test.txt on this drive and do
a " DIR test.txt ", I get a normal directory listing without an error
message. However, if I do a " DIR *.txt ", I get the error message and
no listing as before.

Jeff Richards wrote:

Does DIR/B work?
--
Jeff Richards
MS MVP (Windows - Shell/User)
"WoofWoof" wrote in message
...

snip

I've discovered that there's quite a bit of activity on the internet
with hacked (replacement) firmware for this device so perhaps I'll
give that a try.

sure seems that way .... which may mean it will get a bit beyond my
capabilities but in the meantime what are (or where can I find out
about) "extended attributes"?

I'd like to find out as much as I can because I'm trying to plod my
way through the network boot process on my "Bart's Network Bootdisk".
It's a convoluted series of batch files which progressively unpack
from cab-files so it's slow work. There are screenloads of activity
during the boot and I haven't found a successful way to capture, to a
file, the output of the succession of batch-files and CALLs (jeez I've
got rusty at this DOS stuff).

I was doing this because I wanted to then checkout any command line
parameters available for the various programs to see if there is any
joy there. Knowing about "extended attributes" might help when (if) I
get there.



Jeff Richards wrote:

So the problem goes deeper than a volume or directory name. Any sensible
backup procedure is going to need to be able to list the current contents of
a folder, so unless you can map to a folder that is specially created to
avoid the extended attributes, you're going to need an intermediate layer
that can translate between the two systems. This is usually part of the
network software, but I don't know which end.
--
Jeff Richards
MS MVP (Windows - Shell/User)
"WoofWoof" wrote in message
...
No, 'fraid not. I still get the "Extended Error 123" result with no
listing. (The "Volume in drive X has no label" message is absent with
this
switch).

Interesting though: if I put a file, say test.txt on this drive and do
a " DIR test.txt ", I get a normal directory listing without an error
message. However, if I do a " DIR *.txt ", I get the error message and
no listing as before.

Jeff Richards wrote:

Does DIR/B work?
--
Jeff Richards
MS MVP (Windows - Shell/User)
"WoofWoof" wrote in message
...

snip

I've discovered that there's quite a bit of activity on the internet
with hacked (replacement) firmware for this device so perhaps I'll
give that a try.

http://linux.about.com/library/cmd/blcmdl5_attr.htm


--
Jeff Richards
MS MVP (Windows - Shell/User)
"WoofWoof" wrote in message
...
sure seems that way .... which may mean it will get a bit beyond my
capabilities but in the meantime what are (or where can I find out
about) "extended attributes"?

I'd like to find out as much as I can because I'm trying to plod my
way through the network boot process on my "Bart's Network Bootdisk".
It's a convoluted series of batch files which progressively unpack
from cab-files so it's slow work. There are screenloads of activity
during the boot and I haven't found a successful way to capture, to a
file, the output of the succession of batch-files and CALLs (jeez I've
got rusty at this DOS stuff).

I was doing this because I wanted to then checkout any command line
parameters available for the various programs to see if there is any
joy there. Knowing about "extended attributes" might help when (if) I
get there.



Jeff Richards wrote:

So the problem goes deeper than a volume or directory name. Any sensible
backup procedure is going to need to be able to list the current contents
of
a folder, so unless you can map to a folder that is specially created to
avoid the extended attributes, you're going to need an intermediate layer
that can translate between the two systems. This is usually part of the
network software, but I don't know which end.
--
Jeff Richards
MS MVP (Windows - Shell/User)
"WoofWoof" wrote in message
...
No, 'fraid not. I still get the "Extended Error 123" result with no
listing. (The "Volume in drive X has no label" message is absent with
this
switch).

Interesting though: if I put a file, say test.txt on this drive and do
a " DIR test.txt ", I get a normal directory listing without an error
message. However, if I do a " DIR *.txt ", I get the error message and
no listing as before.

Jeff Richards wrote:

Does DIR/B work?
--
Jeff Richards
MS MVP (Windows - Shell/User)
"WoofWoof" wrote in message
...

snip

I've discovered that there's quite a bit of activity on the internet
with hacked (replacement) firmware for this device so perhaps I'll
give that a try.

Thanks, Jeff!

Jeff Richards wrote:

http://linux.about.com/library/cmd/blcmdl5_attr.htm

--
Jeff Richards
MS MVP (Windows - Shell/User)
"WoofWoof" wrote in message
...
sure seems that way .... which may mean it will get a bit beyond my
capabilities but in the meantime what are (or where can I find out
about) "extended attributes"?

I'd like to find out as much as I can because I'm trying to plod my
way through the network boot process on my "Bart's Network Bootdisk".
It's a convoluted series of batch files which progressively unpack
from cab-files so it's slow work. There are screenloads of activity
during the boot and I haven't found a successful way to capture, to a
file, the output of the succession of batch-files and CALLs (jeez I've
got rusty at this DOS stuff).

I was doing this because I wanted to then checkout any command line
parameters available for the various programs to see if there is any
joy there. Knowing about "extended attributes" might help when (if) I
get there.



Jeff Richards wrote:

So the problem goes deeper than a volume or directory name. Any sensible
backup procedure is going to need to be able to list the current contents
of
a folder, so unless you can map to a folder that is specially created to
avoid the extended attributes, you're going to need an intermediate layer
that can translate between the two systems. This is usually part of the
network software, but I don't know which end.
--
Jeff Richards
MS MVP (Windows - Shell/User)
"WoofWoof" wrote in message
...
No, 'fraid not. I still get the "Extended Error 123" result with no
listing. (The "Volume in drive X has no label" message is absent with
this
switch).

Interesting though: if I put a file, say test.txt on this drive and do
a " DIR test.txt ", I get a normal directory listing without an error
message. However, if I do a " DIR *.txt ", I get the error message and
no listing as before.

Jeff Richards wrote:

Does DIR/B work?
--
Jeff Richards
MS MVP (Windows - Shell/User)
"WoofWoof" wrote in message
...

snip

I've discovered that there's quite a bit of activity on the internet
with hacked (replacement) firmware for this device so perhaps I'll
give that a try.