Share Drive in Win98 MS-DOS Mode

I read that share.exe was eliminated from Win98 because of compatibility
issues. Has anyone been able to share a drive on a network from "MS-DOS Mode"
(the exit to dos window) ? If so how ?
--
Wesley

"Wesley" wrote in message
...

I read that share.exe was eliminated from Win98 because of compatibility
issues. Has anyone been able to share a drive on a network from "MS-DOS
Mode"
(the exit to dos window) ? If so how ?

1. Windows Networking was programmed much later
than MS-DOS SHARE.EXE for rather different purposes.
2. Most Win98 users who for some reason need to
use DOS SHARE.EXE seem to report success if
they create a zero-byte file (i.e. filename with no
contents) and rename it SHARE.EXE. I.e. Windows
does by itself what it is supposed to.

--
Don Phillipson
Carlsbad Springs
(Ottawa, Canada)

Share.exe has nothing to do with sharing network drives. It is a utility
that is needed to support some forms of simultaneous access to files.

Do you need this access from a boot to DOS or from a DOS session running
under Windows?

The simplest way to make a network drive available to a DOS session under
Windows is to map a drive letter to the network folder from within Windows.
The network folder will then be available, using that drive letter, in the
DOS session. In Windows, right click the network folder to be shared,
select Mapping and nominate the drive letter to use.

If you need access from a boot to DOS then you need to install the correct
networking components in the appropriate startup files and then map the
network resource to a drive letter - a much more complicated process..
--
Jeff Richards
MS MVP (Windows - Shell/User)
"Wesley" wrote in message
...
I read that share.exe was eliminated from Win98 because of compatibility
issues. Has anyone been able to share a drive on a network from "MS-DOS
Mode"
(the exit to dos window) ? If so how ?
--
Wesley

Jeff,

I have a dos app. that runs in Win98 MS-DOS Mode (via "exit to dos"). The
app doesn't run properly in a Win98 command window. The app. is able to shell
to DOS in order to run various utilities. From this DOS shell within the
application I can run net.exe and access the network from the DOS shell.
However, because I cannot share the drive (via share.exe as I did previously
(see below)) other machines on the network can not see this drive.

Prior to moving my app. from a DOS machine to a Win98 machine, I connected
the DOS machine to my network via "Workgroup add-on for MS-DOS". In order for
the WinXX machines on the net to see the DOS machine, I was required to run
share.exe on the DOS machine.

In my last attempt to connect my machine to a network, I downloaded from
ftp://ftp.micro........./msclient/DSK3-1.exe and DSK3-2.exe. I also obtained
wb1049.exe to update "net.exe". I ran DSK3-1.exe but when prompted for a
network adapter, my "intel 21140 based 10/100 mpbs ethernet controller" could
not be found on the list. So, I tried several other types without success
(maybe I am a bad guesser) and finally installed the software with no
selection. (I even downloaded the Intel driver but could not get setup to
recognize it (perhaps in part because I did not know where to place it or how
to use the files (DC21X4.DOS and PROTOCOL.INI))). I was not prompted for the
second disk. I installed the updated version of net.exe and ran "net /?".
Help indicated a "net share ......" command line option. However after trying
this, net.exe responded with "can not find share ......". I assumed that it
was looking for the DOS utility share.exe and gave up this approach.

I need access to a Win98 machine that is "boot to DOS".

--
Wesley


"Jeff Richards" wrote:

Share.exe has nothing to do with sharing network drives. It is a utility
that is needed to support some forms of simultaneous access to files.

Do you need this access from a boot to DOS or from a DOS session running
under Windows?

The simplest way to make a network drive available to a DOS session under
Windows is to map a drive letter to the network folder from within Windows.
The network folder will then be available, using that drive letter, in the
DOS session. In Windows, right click the network folder to be shared,
select Mapping and nominate the drive letter to use.

If you need access from a boot to DOS then you need to install the correct
networking components in the appropriate startup files and then map the
network resource to a drive letter - a much more complicated process..
--
Jeff Richards
MS MVP (Windows - Shell/User)
"Wesley" wrote in message
...
I read that share.exe was eliminated from Win98 because of compatibility
issues. Has anyone been able to share a drive on a network from "MS-DOS
Mode"
(the exit to dos window) ? If so how ?
--
Wesley

If your W98 machine is connected to the network and is visible to other
machines on the network, then all that's needed in order to allow other
machines to access a drive or folder on the DOS machine is to execute the
NET SHARE command. Is this what you could be referring to when you mention
SHARE.EXE?

Eg,
Net Share DosDrive=C:\
Will make the root folder of the C drive visible to other network users
under the name dosdrive.
--
Jeff Richards
MS MVP (Windows - Shell/User)
"Wesley" wrote in message
...
Jeff,

I have a dos app. that runs in Win98 MS-DOS Mode (via "exit to dos"). The
app doesn't run properly in a Win98 command window. The app. is able to
shell
to DOS in order to run various utilities. From this DOS shell within the
application I can run net.exe and access the network from the DOS shell.
However, because I cannot share the drive (via share.exe as I did
previously
(see below)) other machines on the network can not see this drive.

Prior to moving my app. from a DOS machine to a Win98 machine, I connected
the DOS machine to my network via "Workgroup add-on for MS-DOS". In order
for
the WinXX machines on the net to see the DOS machine, I was required to
run
share.exe on the DOS machine.

In my last attempt to connect my machine to a network, I downloaded from
ftp://ftp.micro........./msclient/DSK3-1.exe and DSK3-2.exe. I also
obtained
wb1049.exe to update "net.exe". I ran DSK3-1.exe but when prompted for a
network adapter, my "intel 21140 based 10/100 mpbs ethernet controller"
could
not be found on the list. So, I tried several other types without success
(maybe I am a bad guesser) and finally installed the software with no
selection. (I even downloaded the Intel driver but could not get setup to
recognize it (perhaps in part because I did not know where to place it or
how
to use the files (DC21X4.DOS and PROTOCOL.INI))). I was not prompted for
the
second disk. I installed the updated version of net.exe and ran "net /?".
Help indicated a "net share ......" command line option. However after
trying
this, net.exe responded with "can not find share ......". I assumed that
it
was looking for the DOS utility share.exe and gave up this approach.

I need access to a Win98 machine that is "boot to DOS".

--
Wesley


"Jeff Richards" wrote:

Share.exe has nothing to do with sharing network drives. It is a
utility
that is needed to support some forms of simultaneous access to files.

Do you need this access from a boot to DOS or from a DOS session running
under Windows?

The simplest way to make a network drive available to a DOS session under
Windows is to map a drive letter to the network folder from within
Windows.
The network folder will then be available, using that drive letter, in
the
DOS session. In Windows, right click the network folder to be shared,
select Mapping and nominate the drive letter to use.

If you need access from a boot to DOS then you need to install the
correct
networking components in the appropriate startup files and then map the
network resource to a drive letter - a much more complicated process..
--
Jeff Richards
MS MVP (Windows - Shell/User)
"Wesley" wrote in message
...
I read that share.exe was eliminated from Win98 because of compatibility
issues. Has anyone been able to share a drive on a network from "MS-DOS
Mode"
(the exit to dos window) ? If so how ?
--
Wesley

Its the other way around. The Win98 machine (in boot to DOS) can see the net.
The other machines on the net can not see the Win98 machine. I need the other
machines to access the Win98 machine.
--
Wesley


"Jeff Richards" wrote:

If your W98 machine is connected to the network and is visible to other
machines on the network, then all that's needed in order to allow other
machines to access a drive or folder on the DOS machine is to execute the
NET SHARE command. Is this what you could be referring to when you mention
SHARE.EXE?

Eg,
Net Share DosDrive=C:\
Will make the root folder of the C drive visible to other network users
under the name dosdrive.
--
Jeff Richards
MS MVP (Windows - Shell/User)
"Wesley" wrote in message
...
Jeff,

I have a dos app. that runs in Win98 MS-DOS Mode (via "exit to dos"). The
app doesn't run properly in a Win98 command window. The app. is able to
shell
to DOS in order to run various utilities. From this DOS shell within the
application I can run net.exe and access the network from the DOS shell.
However, because I cannot share the drive (via share.exe as I did
previously
(see below)) other machines on the network can not see this drive.

Prior to moving my app. from a DOS machine to a Win98 machine, I connected
the DOS machine to my network via "Workgroup add-on for MS-DOS". In order
for
the WinXX machines on the net to see the DOS machine, I was required to
run
share.exe on the DOS machine.

In my last attempt to connect my machine to a network, I downloaded from
ftp://ftp.micro........./msclient/DSK3-1.exe and DSK3-2.exe. I also
obtained
wb1049.exe to update "net.exe". I ran DSK3-1.exe but when prompted for a
network adapter, my "intel 21140 based 10/100 mpbs ethernet controller"
could
not be found on the list. So, I tried several other types without success
(maybe I am a bad guesser) and finally installed the software with no
selection. (I even downloaded the Intel driver but could not get setup to
recognize it (perhaps in part because I did not know where to place it or
how
to use the files (DC21X4.DOS and PROTOCOL.INI))). I was not prompted for
the
second disk. I installed the updated version of net.exe and ran "net /?".
Help indicated a "net share ......" command line option. However after
trying
this, net.exe responded with "can not find share ......". I assumed that
it
was looking for the DOS utility share.exe and gave up this approach.

I need access to a Win98 machine that is "boot to DOS".

--
Wesley


"Jeff Richards" wrote:

Share.exe has nothing to do with sharing network drives. It is a
utility
that is needed to support some forms of simultaneous access to files.

Do you need this access from a boot to DOS or from a DOS session running
under Windows?

The simplest way to make a network drive available to a DOS session under
Windows is to map a drive letter to the network folder from within
Windows.
The network folder will then be available, using that drive letter, in
the
DOS session. In Windows, right click the network folder to be shared,
select Mapping and nominate the drive letter to use.

If you need access from a boot to DOS then you need to install the
correct
networking components in the appropriate startup files and then map the
network resource to a drive letter - a much more complicated process..
--
Jeff Richards
MS MVP (Windows - Shell/User)
"Wesley" wrote in message
...
I read that share.exe was eliminated from Win98 because of compatibility
issues. Has anyone been able to share a drive on a network from "MS-DOS
Mode"
(the exit to dos window) ? If so how ?
--
Wesley

"Net Share DosDrive=c:\" responded with something like "can not find
share.exe..........."
--
Wesley


"Jeff Richards" wrote:

If your W98 machine is connected to the network and is visible to other
machines on the network, then all that's needed in order to allow other
machines to access a drive or folder on the DOS machine is to execute the
NET SHARE command. Is this what you could be referring to when you mention
SHARE.EXE?

Eg,
Net Share DosDrive=C:\
Will make the root folder of the C drive visible to other network users
under the name dosdrive.
--
Jeff Richards
MS MVP (Windows - Shell/User)
"Wesley" wrote in message
...
Jeff,

I have a dos app. that runs in Win98 MS-DOS Mode (via "exit to dos"). The
app doesn't run properly in a Win98 command window. The app. is able to
shell
to DOS in order to run various utilities. From this DOS shell within the
application I can run net.exe and access the network from the DOS shell.
However, because I cannot share the drive (via share.exe as I did
previously
(see below)) other machines on the network can not see this drive.

Prior to moving my app. from a DOS machine to a Win98 machine, I connected
the DOS machine to my network via "Workgroup add-on for MS-DOS". In order
for
the WinXX machines on the net to see the DOS machine, I was required to
run
share.exe on the DOS machine.

In my last attempt to connect my machine to a network, I downloaded from
ftp://ftp.micro........./msclient/DSK3-1.exe and DSK3-2.exe. I also
obtained
wb1049.exe to update "net.exe". I ran DSK3-1.exe but when prompted for a
network adapter, my "intel 21140 based 10/100 mpbs ethernet controller"
could
not be found on the list. So, I tried several other types without success
(maybe I am a bad guesser) and finally installed the software with no
selection. (I even downloaded the Intel driver but could not get setup to
recognize it (perhaps in part because I did not know where to place it or
how
to use the files (DC21X4.DOS and PROTOCOL.INI))). I was not prompted for
the
second disk. I installed the updated version of net.exe and ran "net /?".
Help indicated a "net share ......" command line option. However after
trying
this, net.exe responded with "can not find share ......". I assumed that
it
was looking for the DOS utility share.exe and gave up this approach.

I need access to a Win98 machine that is "boot to DOS".

--
Wesley


"Jeff Richards" wrote:

Share.exe has nothing to do with sharing network drives. It is a
utility
that is needed to support some forms of simultaneous access to files.

Do you need this access from a boot to DOS or from a DOS session running
under Windows?

The simplest way to make a network drive available to a DOS session under
Windows is to map a drive letter to the network folder from within
Windows.
The network folder will then be available, using that drive letter, in
the
DOS session. In Windows, right click the network folder to be shared,
select Mapping and nominate the drive letter to use.

If you need access from a boot to DOS then you need to install the
correct
networking components in the appropriate startup files and then map the
network resource to a drive letter - a much more complicated process..
--
Jeff Richards
MS MVP (Windows - Shell/User)
"Wesley" wrote in message
...
I read that share.exe was eliminated from Win98 because of compatibility
issues. Has anyone been able to share a drive on a network from "MS-DOS
Mode"
(the exit to dos window) ? If so how ?
--
Wesley

What do you mean 'something like"? If you can quote the message verbatim
then it's possible to search the 'net for it. A DOS command starting with
"NET..." should not return a message about SHARE. The NET command, when it
executes, might complain that it can't create the share, or similar. But
without the exact message it's not possible to know what's happening.
--
Jeff Richards
MS MVP (Windows - Shell/User)
"Wesley" wrote in message
...
"Net Share DosDrive=c:\" responded with something like "can not find
share.exe..........."
--
Wesley

Jeff,

Thanks for trying to help. Have you ever accessed the drive of a Win98 PC
that is "exit to DOS", from another PC sharing a network ? If so how do you
do that ?

--
Wesley


"Jeff Richards" wrote:

What do you mean 'something like"? If you can quote the message verbatim
then it's possible to search the 'net for it. A DOS command starting with
"NET..." should not return a message about SHARE. The NET command, when it
executes, might complain that it can't create the share, or similar. But
without the exact message it's not possible to know what's happening.
--
Jeff Richards
MS MVP (Windows - Shell/User)
"Wesley" wrote in message
...
"Net Share DosDrive=c:\" responded with something like "can not find
share.exe..........."
--
Wesley

I have never used DOS networking from an exit to DOS session in Windows 98,
and I wouldn't recommend it, partly because there's no reason.

If you have to be running DOS, then by far the easiest way is to build a
network boot floppy using DOS 6.22 and boot to that.

If the response you are getting to the NET SHARE command is something like
"The command SHARE is not known..." then that indicates you are using the
wrong version of the NET command. You need to set up the workstation as a
peer (rather than a client) if you want to make local drives available to
other users. That might be possible for the DOS session created from an
exit to DOS, but would be much easier from a special boot.
--
Jeff Richards
MS MVP (Windows - Shell/User)
"Wesley" wrote in message
...
Jeff,

Thanks for trying to help. Have you ever accessed the drive of a Win98 PC
that is "exit to DOS", from another PC sharing a network ? If so how do
you
do that ?

--
Wesley


"Jeff Richards" wrote: