I have a MS-DOS machine which needs to share a drive to Win XP machine. After reading quite a few messages, it seems installing a couple of files from Microsoft did the trick. But on running "net share" i get the following error :
The SERVER service is not yet started. Is it ok to start it ? Service failed to initialize Error 2114: The Server service is not started.
| Hi, | | I have a MS-DOS machine which needs to share a drive to Win XP | machine. After reading quite a few messages, it seems installing a | couple of files from Microsoft did the trick. But on running "net | share" i get the following error : | | The SERVER service is not yet started. | Is it ok to start it ? | Service failed to initialize | Error 2114: The Server service is not started. | | Is there a workaround to this. | | Thanks in advance, | vivekian
You need to run pure DOS with a NDIS2 stack.
Please define EXACTLY how you are setup.
This should include the version of DOS, and the contents of the CONFIG.SYS, AUTOEXEC.BAT files as well as the PROTOCOL.INI file.
> | Hi, > | > | I have a MS-DOS machine which needs to share a drive to Win XP > | machine. After reading quite a few messages, it seems installing a > | couple of files from Microsoft did the trick. But on running "net > | share" i get the following error : > | > | The SERVER service is not yet started. > | Is it ok to start it ? > | Service failed to initialize > | Error 2114: The Server service is not started. > | > | Is there a workaround to this. > | > | Thanks in advance, > | vivekian
> You need to run pure DOS with a NDIS2 stack.
> Please define EXACTLY how you are setup.
> This should include the version of DOS, and the contents of the CONFIG.SYS, AUTOEXEC.BAT > files as well as the PROTOCOL.INI file.
DOS Version : 7.10 Microsoft DOS TCP/IP Protocol Driver 1.0a MS_DOS LAN Manager v2.1 NetBind
Contents of Configy.sys : FILES=20 device=c:\windows\ifshlp.sys LASTDRIVE=Z device=c:\windows\himem.sys
Contents of autoexec.bat
@echo off
rem mode co80,50 rem mode mono
set path=%path%;c:\net;c:\bin;c:\vim
rem Load utilities. smartdrv /X doskey /insert rem Setup serial. mode com1 96,n,8,1
rem Enable networking and map drives. call c:\net\neton.bat
4dos net share
This is what i tried from my readings across Usenet. There seems to be two files which are used to update TCP/IP for MS-DOS. These are located at : ftp://ftp.microsoft.com/bussys/Clients/MSCLIENT I executed these and they overwrote the existing client. Next there is an update called wg1049.exe which is supposed to add share capabilities to the net command. Hope this information helps. Appreciate your response.
<vivekase...@gmail.com> wrote: >The details are as follows :
>DOS Version : 7.10
That's the version of DOS that was integrated with win9x. You need to use a pure standalone dos version ie 6.22 or earlier.
Everything else you said regarding the dos client and updated net.exe from wg1049.exe was spot on.
A word or warning. Keep this machine well away from the Intenet. The single character password bug which was patched in win9x was never repaired in win3.1 or dos
> On Wed, 5 Mar 2008 19:57:19 -0800 (PST), vivekian
> <vivekase...@gmail.com> wrote: > >The details are as follows :
> >DOS Version : 7.10
> That's the version of DOS that was integrated with win9x. You need to > use a pure standalone dos version ie 6.22 or earlier.
> Everything else you said regarding the dos client and updated net.exe > from wg1049.exe was spot on.
> A word or warning. Keep this machine well away from the Intenet. The > single character password bug which was patched in win9x was never > repaired in win3.1 or dos
> Jim.
Is there any way at all to do this on the DOS version currently being used. I don't think i can change the current setup. Yes, its away from internet, its within an intranet.
|>> Hi, |>> |>> I have a MS-DOS machine which needs to share a drive to Win XP |>> machine. After reading quite a few messages, it seems installing a |>> couple of files from Microsoft did the trick. But on running "net |>> share" i get the following error : |>> |>> The SERVER service is not yet started. |>> Is it ok to start it ? |>> Service failed to initialize |>> Error 2114: The Server service is not started. |>> |>> Is there a workaround to this. |>> |>> Thanks in advance, |>> vivekian
>> You need to run pure DOS with a NDIS2 stack.
>> Please define EXACTLY how you are setup.
>> This should include the version of DOS, and the contents of the CONFIG.SYS, AUTOEXEC.BAT >> files as well as the PROTOCOL.INI file.
| | The details are as follows : | | DOS Version : 7.10 | Microsoft DOS TCP/IP Protocol Driver 1.0a | MS_DOS LAN Manager v2.1 NetBind | | Contents of Configy.sys : | FILES=20 | device=c:\windows\ifshlp.sys | LASTDRIVE=Z | device=c:\windows\himem.sys | | Contents of autoexec.bat | | @echo off | | rem mode co80,50 | rem mode mono | | set path=%path%;c:\net;c:\bin;c:\vim | | rem Load utilities. | smartdrv /X | doskey /insert | rem Setup serial. | mode com1 96,n,8,1 | | rem Enable networking and map drives. | call c:\net\neton.bat | | 4dos | net share | | This is what i tried from my readings across Usenet. There seems to be | two files which are used to update TCP/IP for MS-DOS. These are | located at : ftp://ftp.microsoft.com/bussys/Clients/MSCLIENT | I executed these and they overwrote the existing client. Next there is | an update called wg1049.exe which is supposed to add share | capabilities to the net command. Hope this information helps. | Appreciate your response. | | Thanks, | vivekian
There is NO NDIS2 driver being loaded in CONFIG.SYS.
This needs to be loaded and bound to the NIC via c:\net\protocol.ini
> | On Mar 5, 5:40 pm, "David H. Lipman" <DLipman~nosp...@Verizon.Net>| wrote: > >> From: "vivekian" <vivekase...@gmail.com>
> |>> Hi, > |>> > |>> I have a MS-DOS machine which needs to share a drive to Win XP > |>> machine. After reading quite a few messages, it seems installing a > |>> couple of files from Microsoft did the trick. But on running "net > |>> share" i get the following error : > |>> > |>> The SERVER service is not yet started. > |>> Is it ok to start it ? > |>> Service failed to initialize > |>> Error 2114: The Server service is not started. > |>> > |>> Is there a workaround to this. > |>> > |>> Thanks in advance, > |>> vivekian
> >> You need to run pure DOS with a NDIS2 stack.
> >> Please define EXACTLY how you are setup.
> >> This should include the version of DOS, and the contents of the CONFIG.SYS, AUTOEXEC.BAT > >> files as well as the PROTOCOL.INI file.
> | > | The details are as follows : > | > | DOS Version : 7.10 > | Microsoft DOS TCP/IP Protocol Driver 1.0a > | MS_DOS LAN Manager v2.1 NetBind > | > | Contents of Configy.sys : > | FILES=20 > | device=c:\windows\ifshlp.sys > | LASTDRIVE=Z > | device=c:\windows\himem.sys > | > | Contents of autoexec.bat > | > | @echo off > | > | rem mode co80,50 > | rem mode mono > | > | set path=%path%;c:\net;c:\bin;c:\vim > | > | rem Load utilities. > | smartdrv /X > | doskey /insert > | rem Setup serial. > | mode com1 96,n,8,1 > | > | rem Enable networking and map drives. > | call c:\net\neton.bat > | > | 4dos > | net share > | > | This is what i tried from my readings across Usenet. There seems to be > | two files which are used to update TCP/IP for MS-DOS. These are > | located at :ftp://ftp.microsoft.com/bussys/Clients/MSCLIENT > | I executed these and they overwrote the existing client. Next there is > | an update called wg1049.exe which is supposed to add share > | capabilities to the net command. Hope this information helps. > | Appreciate your response. > | > | Thanks, > | vivekian
> There is NO NDIS2 driver being loaded in CONFIG.SYS.
> This needs to be loaded and bound to the NIC via c:\net\protocol.ini
| | Can you please guide as to how the NDIS2 driver can be loaded, and | bound to protocol.ini ? Is there a link as to where it is available ? | | Thanks, | Vivek
> | > | Can you please guide as to how the NDIS2 driver can be loaded, and > | bound to protocol.ini ? Is there a link as to where it is available ? > | > | Thanks, > | Vivek
> What Network Interface Card (NIC) are you using ?
| | Hi Dave, | | This is what i could dig up : | | Device ID : 0x1229 | Chip Number: 82557/8/9/0/1 | Chip Description: Fast Ethernet LAN Controller | Notes: used on EtherExpress PRO/100(B) Adapter | | vivekian
| | Hi Dave, | | This is what i could dig up : | | Device ID : 0x1229 | Chip Number: 82557/8/9/0/1 | Chip Description: Fast Ethernet LAN Controller | Notes: used on EtherExpress PRO/100(B) Adapter | | vivekian
> | > | Hi Dave, > | > | This is what i could dig up : > | > | Device ID : 0x1229 > | Chip Number: 82557/8/9/0/1 > | Chip Description: Fast Ethernet LAN Controller > | Notes: used on EtherExpress PRO/100(B) Adapter > | > | vivekian
| | Hi Dave, | | Sorry for the delay. Got stuck in a bit of work. Will try this out | today and update you. Thanks for all the help. | | thanks, | vivekian
> | > | Hi Dave, > | > | This is what i could dig up : > | > | Device ID : 0x1229 > | Chip Number: 82557/8/9/0/1 > | Chip Description: Fast Ethernet LAN Controller > | Notes: used on EtherExpress PRO/100(B) Adapter > | > |vivekian
After downloading the driver -- Prodos.exe from the site, tried to run it. It gave an error -- "Can't be run in DOS mode" . Is there an alternate to this ? Should I try the Legacy driver on the same website ? Supposedly there is a driver available on www.crynwr.com but its not NDIS.
| Hi Dave, | | After downloading the driver -- Prodos.exe from the site, tried to run | it. It gave an error -- "Can't be run in DOS mode" . Is there an | alternate to this ? | Should I try the Legacy driver on the same website ? Supposedly there | is a driver available on www.crynwr.com but its not NDIS. | | Thanks a bunch, | vivekian
You can use a Packet Driver (Crynwr) to NDIS2 shim.
Don't you have a Win32 PC capable of downloading the Prodos.exe utility and the extract the needed files and then port the files to the DOS setup ?
> | Hi Dave, > | > | After downloading the driver -- Prodos.exe from the site, tried to run > | it. It gave an error -- "Can't be run in DOS mode" . Is there an > | alternate to this ? > | Should I try the Legacy driver on the same website ? Supposedly there > | is a driver available onwww.crynwr.combut its not NDIS. > | > | Thanks a bunch, > | vivekian
> You can use a Packet Driver (Crynwr) to NDIS2 shim.
> Don't you have a Win32 PC capable of downloading the Prodos.exe utility and the extract the > needed files and then port the files to the DOS setup ?
|>> Hi Dave, |>> |>> After downloading the driver -- Prodos.exe from the site, tried to run |>> it. It gave an error -- "Can't be run in DOS mode" . Is there an |>> alternate to this ? |>> Should I try the Legacy driver on the same website ? Supposedly there |>> is a driver available onwww.crynwr.combut its not NDIS. |>> |>> Thanks a bunch, |>> vivekian
>> You can use a Packet Driver (Crynwr) to NDIS2 shim.
>> Don't you have a Win32 PC capable of downloading the Prodos.exe utility and the extract >> the needed files and then port the files to the DOS setup ?
I use similar files to load DOS with net support in order to copy images to new computers on our domain at office. When tryed to load from the same flash drive at home my laptop (me home net is with DHCP enabled router) hang ups when executes:
