Reply 60 of 72, by maxtherabbit
- Rank
- l33t
Reference Material
https://ftp.zx.net.nz/pub/Patches/ftp.microso … n-us/93/736.HTM
Reference Material
https://ftp.zx.net.nz/pub/Patches/ftp.microso … n-us/93/736.HTM
maxtherabbit wrote on 2024-12-16, 16:01:Reference Material https://ftp.zx.net.nz/pub/Patches/ftp.microso … n-us/93/736.HTM […]
Reference Material
https://ftp.zx.net.nz/pub/Patches/ftp.microso … n-us/93/736.HTM
Great work!
Does your WfW 3.1 configuration work as is for WfW 3.11?
For reference, do you have a mem /c capture of this configuration?
I like the idea of having TCP/IP networking and file and print sharing available in both DOS 6.22 and WfW 3.11.
The first part is getting the functionality working. Also important is finding the optimal way to load the drivers/TSRs, so networking can be used in a practical way.
Banner Mania on a networked dot matrix printer might be interesting.
thisIsLoneWolf wrote on 2024-12-16, 17:02:Great work! […]
maxtherabbit wrote on 2024-12-16, 16:01:Reference Material https://ftp.zx.net.nz/pub/Patches/ftp.microso … n-us/93/736.HTM […]
Reference Material
https://ftp.zx.net.nz/pub/Patches/ftp.microso … n-us/93/736.HTMGreat work!
Does your WfW 3.1 configuration work as is for WfW 3.11?
For reference, do you have a mem /c capture of this configuration?I like the idea of having TCP/IP networking and file and print sharing available in both DOS 6.22 and WfW 3.11.
The first part is getting the functionality working. Also important is finding the optimal way to load the drivers/TSRs, so networking can be used in a practical way.
Banner Mania on a networked dot matrix printer might be interesting.
Here's the MEM /C for my config - including all the other crap I load for DOS
Regarding using 16bit TCP with WfW3.11, I'm pretty sure it should work the same way, but I have not tried it. Not sure how it would handle coexisting with 32bit TCP either. I would hope they could coexist the same way other NDIS2 and NDIS3 drivers can.
Fascinating...
I'm going to try it later this week.
Meanwhile...
So, for WfW 3.1, Microsoft recommends to use the TCP/IP from LAN Manager - why not from the "TCP/IP for Microsoft Windows for Workgroups diskette"?
Also, what's that "TCP/IP Utility pack"? Where to find it?
Zaglądali do kufrów, zaglądali do waliz, nie zajrzeli do dupy - tam miałem klimatyzm.
I'm not sure exactly what the utility diskette is. I can say that the final release of the lanman client as well as the Net Client 3.0 contain the same TCP stack. (The omission of UNLOADT in the client 3 notwithstanding)
This is a really useful guide, thanks for that! I do like how relatively simple Trumpet Winsock 1.0a is (with 1.0 beta 24 applied on top) to set up, but I'll have to give this a spin at some point and see what I can do with it.
So I'm confirming: WfW 3.1 indeed works with TCP/IP.
My installation procedure:
1. Microsoft Network Client version 3.0 for MS-DOS:
- TCP/IP instead of IPX
- everything else default, which includes full redirector
2. Windows for Workgroups 3.1:
- don't let it modify CONFIG.SYS and AUTOEXEC.BAT
- everything else default, which includes NetBEUI
3. Editing CONFIG.SYS and AUTOEXEC.BAT, as described by @maxtherabbit
Results:
- WORKGRP.SYS complains: "No NETBEUI section found in configuration information", but loads anyway
- Windows complains on startup:
You started the workgroup software for MS-DOS before you started Windows. To make more memory available to your applications and use the network components built into Windows for Workgroups instead, type NET STOP before starting Windows.
Do you want to display this message in the future?
[Yes] [No] [Help]
- "Connect Network Drive..." shows my Samba 4.7.1 server, and I can connect a shared directory
- "Share As..." also seems to work, I can list the shares from my modern Linux box:
# smbclient -L pc486
Enter WORKGROUP\user's password:
Sharename Type Comment
--------- ---- -------
WINDOWS Disk
IPC$ IPC Remote IPC
Reconnecting with SMB1 for workgroup listing.
Server Comment
--------- -------
Workgroup Master
--------- -------
I can't mount them:
# mount.cifs //pc486/windows /mnt/windows
mount error: could not resolve address for pc486: Unknown error
# mount.cifs //192.168.0.42/windows /mnt/windows
Password for user@//192.168.0.42/windows:
mount error(112): Host is down
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
...but it doesn't work for WfW 3.11, either.
- in Standard mode, "Connect Network Drive..." still works, but there's no "Share As..." option
Zaglądali do kufrów, zaglądali do waliz, nie zajrzeli do dupy - tam miałem klimatyzm.
Grzyb wrote on 2024-12-23, 06:01:Results:
- WORKGRP.SYS complains: "No NETBEUI section found in configuration information", but loads anyway
Yes this is expected and can be safely ignored as mentioned in the MS docs
Grzyb wrote on 2024-12-23, 06:01:- Windows complains on startup:
You started the workgroup software for MS-DOS before you started Windows. To make more memory available to your applications and use the network components built into Windows for Workgroups instead, type NET STOP before starting Windows.
Do you want to display this message in the future?
[Yes] [No] [Help]
This one is new to me. I never saw this message when running the MS Net 3 redirector with WfW3.1. I can only assume it's coming from an enhanced mode driver. I'd suggest you use the NET.EXE shipped with WfW3.1 in lieu of the Net3 one. All you have to do is substitute the path in the command where you call NET START, everything else can be left as is. It will in fact save you some conventional memory as it says.
Grzyb wrote on 2024-12-23, 06:01:- in Standard mode, "Connect Network Drive..." still works, but there's no "Share As..." option
Thanks for confirming my guess about sharing requiring enhanced mode is correct
maxtherabbit wrote on 2024-12-23, 12:35:This one is new to me. I never saw this message when running the MS Net 3 redirector with WfW3.1. I can only assume it's coming from an enhanced mode driver. I'd suggest you use the NET.EXE shipped with WfW3.1 in lieu of the Net3 one. All you have to do is substitute the path in the command where you call NET START, everything else can be left as is. It will in fact save you some conventional memory as it says.
You're right - no such warning in Standard mode.
And no such warning after replacing "C:\NET\net start" with "C:\windows\net start".
"C:\windows\net start", however, displays: "Error 2182: The requested service has already been started.", and doesn't map network drives in DOS.
With "C:\NET\net start", in the "Show Shared Directories on:" window, I can only see the Samba server.
With "C:\windows\net start", I can see both the Samba server and the WfW machine.
Zaglądali do kufrów, zaglądali do waliz, nie zajrzeli do dupy - tam miałem klimatyzm.
On the CD of Windows NT 4.0 Server there are some clients in the CLIENTS directory:
LANMAN
LANMAN.OS2
MSCLIENT
RAS
RPL
SRVTOOLS
SUPPORT
TCP32WFW
UPDATE.WFW
WIN95
Grzyb wrote on 2024-12-23, 13:32:"C:\windows\net start", however, displays: "Error 2182: The requested service has already been started.", and doesn't map network drives in DOS.
I cannot duplicate this, and it doesn't make sense. Are you saying you ran the command "NET START" for the first and only time at bootup and received this error?? Or do you have a "NET START" in AUTOEXEC.BAT and were then trying to run it again for some odd reason?
Perhaps you were looking for "NET LOGON"?
Below is my current config.
I didn't touch any of the PROTOCOL.INI files.
device=C:\dos\HIMEM.SYS
DEVICE=C:\DOS\SETVER.EXE
DOS=HIGH,UMB
STACKS=9,256
FILES=40
LASTDRIVE=f
device=C:\NET\ifshlp.sys
device=c:\net\protman.dos /i:c:\net
device=c:\net\nemm.dos
device=c:\net\tcpdrv.dos /i:c:\net
device=c:\windows\workgrp.sys
device=c:\net\elnk3.dos
@echo off
rem C:\NET\net initialize
set path=c:\windows;c:\dos;c:\bin;c:\vc;c:\mtcp;c:\bp\bin
PATH C:\NET;C:\NU;%PATH%
SET SYMANTEC=C:\SYMANTEC
SET NU=C:\NU
set mtcpcfg=c:\mtcp\mtcp.cfg
set TZ=CET-1CEST-2,M3.5.0/02:00:00,M10.5.0/03:00:00
set tmp=c:\tmp
set temp=c:\tmp
rem Hehe, how do you think I can make a screenshot of AUTOEXEC.BAT ?
cd pzp
pzp
cd \
cls
C:\NET\netbind.com
C:\NET\umb.com
C:\NET\tcptsr.exe
C:\NET\tinyrfc.exe
C:\NET\nmtsr.exe
C:\NET\emsbfr.exe
C:\windows\net start
Zaglądali do kufrów, zaglądali do waliz, nie zajrzeli do dupy - tam miałem klimatyzm.
Perhaps it has something to do with the commands I entered right after DOS Client installation:
net use d: \\server\download
net use e: \\server\upload
It makes "c:\net\net start" map the drives every time.
After replacing "c:\net\net start" with "c:\windows\net start", the drives are no longer mapped.
I can map them with "c:\windows\net use ...", but it starts the WORKSTATION service, which brings back the warning on starting WfW.
Zaglądali do kufrów, zaglądali do waliz, nie zajrzeli do dupy - tam miałem klimatyzm.