home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
World of Ham Radio 1997
/
WOHR97_AmSoft_(1997-02-01).iso
/
windows
/
win_72
/
hints3.txt
< prev
next >
Wrap
Text File
|
1997-02-01
|
12KB
|
236 lines
Fra : N3BUB
Til : FBB@USBBS
Sendt : 19-Mar 10:24
Mottatt : 27-Mar 10:03
Type/status : BF
BID (MID) : 21139_N3BUB
Meldingsnr. : 228688
Tittel : FBB-WIN NETWORK SETUP
R:960327/0856Z @:LA9GG.BRG.R.NOR.EU #:2328 [Link 3] FBB7.00a $:21139_N3BUB
R:960324/1355Z @:LA9GG.BRG.R.NOR.EU #:47718 [Link 1] $:21139_N3BUB
R:960324/0408Z @:GB7HSN.#32.GBR.EU #:42853 [Mottingham] $:21139_N3BUB
R:960321/0404Z 8707@VE4KV.#WPG.MB.CAN.NOAM [Winnipeg] FBB7.00a
R:960321/0341Z @:F6CNB.#SETX.TX.USA.NOAM #:11366 $:21139_N3BUB
R:960320/2035z @:K5ARH.#LFT.LA.USA.NOAM #:27856 $:21139_n3bub
R:960320/2007z @:KB5OGN.#NILA.LA.USA.NOAM #:73208 $:21139_n3bub
R:960320/0736z @:N2MEG.#BRONX.NY.USA.NA [JNOS] #:5204 $:21139_n3bub
R:960320/0510 5000@KB2VLX.#BRONX.NY.USA.NA $:21139_N3BUB
R:960320/0117Z @:WA2JVM.NJ.USA.NA #:2772 [West Orange] $:21139_N3BUB
R:960320/0112Z @:WA2SNA.FN21VA.NJ.USA.NA #:44389 [Oakland] $:21139_N3BUB
R:960320/0108Z @:N2ERH.FN21OE.NJ.USA.NA #:51164 [Branchville] $:21139_N3BUB
R:960320/0056Z @:N2QAE.#NNJ.NJ.USA.NA #:11569 [Long Valley,NJ] FBB5.15c
R:960319/0156Z @:N2OCW.NJ.USA.NOAM #:12088 [Bloomsbury] $:21139_N3BUB
R:960319/1024Z @:N3BUB.#EPA.PA.USA.NA #:21139 [FN20FV] $:21139_N3BUB
From: N3BUB@N3BUB.#EPA.PA.USA.NA
To : FBB@USBBS
WinFBB Tinkerers:
I have been playing with the networking features of Win3.11 and have it running
here with WinFBB7.00 and FBB5.15c.
FBB7.00 is running on a 486 with 8 meg ram, and FBB5.15c is running on a 386
with 2 meg ram. Win3.11 is installed on the 486 machine with the Microsoft
Network running. The hard drive is shared in full with the 386 machine thru use
of NET.EXE. networking program.
This setup has nothing to do with BPQ switch at this time, it is strickly a
DOS-WIN setup.
The ethernet cards are NOVELL NE1000 (810-160-002) cards using thin cable
linking. Addressing is 300H and IRQ 5. They do not eat up a com port!!
The 386 machine has only 2 meg ram, and it runs both the NET and FBB fine.
2 megs will not run a node copy of the network, so I opted for this arrangement.
The 486 is setup with networking installed. It becomes the SERVER machine.
The 386 is setup with NET.EXE and related files, a list of which are needed to
make it go included below.
The 386 can access any file, program, and data that is in the 486, but will not
run anything larger than its' own memory will allow. FBB5.15c is running one
port for my HF links, while the other is running 3 more for local connects. In
the autoexec.bat go two lines that will auto start the NET link at boot-up
after a bit of tinkering to get it going.
The files listed below are enough to get it going without a hitch.
In the config.sys, put this line:
device=<path>ifshlp.sys
Put it right after the HIMEM.SYS line.
In the autoexec.bat file, near the beginning, put these lines:
<path>net start workstation
<path>net logon <YourNetworkName> <Password>
This assumes you want the network on line at boot-up time. If not, just type
the lines from the prompt when you want to logon. You will be prompted at that
time for needed info.
Under no circumstances put any NET USE lines in your autoexec.bat file until
you know what it will do, each time the command runs successfully, it will
duplicate the routing. Not a good situation, since NET keeps a log of what you
already set up.
If you have a printer on line, type net /? > prn to print out a small help
file. This will get you started to print out the many help files included
within NET.EXE system. i.e. net start/? net use/? net view/? etc...
Make a directory...i.e. windows or network or <whatever>. Put its' PATH in the
path line of the Autoexec.Bat file. It has to have its path in there, or it
will not work. Don't forget to bring over the SYSTEM.INI file from the server
machine, it needs it to know what is in there. Look in the network] section and
edit the lines with your name, machine name, and workgroup.
yourname must be different from server
computername must be different than server
workgroup must be same as server
The .PWL files will be made when you first try to logon. I don't remember the
exact sequence, since I was in the dark to the various functions of the
network, so I hope I didn't tell any wrong info here. Don't bring them over if
you find them on the server machine.
The first time you try to logon, the net will ask you for your name, password,
and I think, workgroup. I got it going, and i'm not going to get rid of the
files to test these theories agn!! Please appreciate the hours it took me to
get it running. I had a starter boost from a ham that knew the system, but I
hacked for a while to get it all straightened out to this end.
After you get logged on, you must specify a place you want to go to.
First, go into file manager in 3.11, and tell it to SHARE the entire drive. It
will ask you for a name to call the drive. It is not lookng for a <path>, but
rather a plain name. I called my 486 c-drive CDRIVE. Now you can go back to the
machine you were setting up and type:
net use * \\<computername>\<name> in my setup, this is :
net use * \\486\winfbb <--if you want passwords, you must read the net help
files and follow the instructions. since this is a personal system, I have
everything open. If you get a line that says something like:
F: connected to \\486\CDRIVE..
The command completed successfully.
The * in the net use command, tells NET to use next available drive letter.
This will be the connect letter you will use until you change something. In the
example it was F: It might be different in your case, I have two physical
drives on my 386, and a small ramdrive, so my next drive was F:
As long as you don't wipe the files, each time you logon, you will be connected
to this path. You can have 26 different paths setup. A-Z.
Make sure you have lastdrive=Z in the outboard machine!!!
Once you have SHARED the ROOT of a drive, you have access to the whole thing
from this machine. It doesn't work the other way, because the 386 is not a
NODE. If this is a personal system, better not to password anything, and give
FULL access to everything.
FBB5.15c FBBDOS will allow access to this drive. NEAT! This means users allowed
in full access in FBBDOS on this machine can get to the 486 drives. BE CAREFUL
WITH IT
Also, you can have mail forwards sent thru the link, directly to
<NetDriveLetter>:\fbb\mail.in... This allows automatic routing of messages
between the two machines and their ports. Also, you can set up a little batch
file, to run in a forward script, to poll the 486 drive for a file, which is a
file made by a forward connect in that machine. the 386 outboard machine will
be able to put and get forwarding mail just like internal file transfers.
P.S. M_FILTER doesn't work thru the NETWORK port.
I hope this message helps someone get the link going, I had a rough time, being
pretty much on my own. I AM NOT, by any means, an expert in these matters, but
I've found that if you follow your nose, you can almost do anything with these
machines. I will answer any questions I can about what I've learned thus far.
Good luck with it, it has made my station automated again.
I will not apologize to anyone, for anything I forgot, misled, or otherwise,
told wrong. I have it running, and will share what I know, but please don't
come flaming when it doesn't work right away, it didn't for me either. All the
info in this message is personal experience, please don't take it as the
absolute truth.
Included below are the files I needed to make NET run on my 386. Don't forget
to edit the SYSTEM.INI to make it think it is not on the server machine.
Make sure at least these following lines reflect the outboard machine setup:
[NETWORK]
UserName=<DifferentThanServerMachine>
Workgroup=<SameAsServer>
ComputerName=<DifferentThanServer>
[network drivers]
devdir=<PathToFiles> <--my directories is C:\WINDOWS...it is whatever
directory you put files listed below in.
This is list of files on outboard machine...386
Volume in drive C is DISK-C-
Volume Serial Number is 1F97-7E12
Directory of C:\WINDOWS
. <DIR> 03-18-96 12:44a
.. <DIR> 03-18-96 12:44a
NDISHLP SYS 4,464 11-01-93 3:11a
IFSHLP SYS 4,548 11-01-93 3:11a
WFWSYS CFG 840 03-16-96 1:18p
PROTMAN EXE 13,782 11-01-93 3:11a
NE1000 DOS 14,020 11-01-93 3:11a
PROTMAN DOS 21,940 11-01-93 3:11a
NET MSG 75,697 11-01-93 3:11a <will run without these if
NETH MSG 122,333 11-01-93 3:11a using floopy disk>
NET EXE 433,829 11-01-93 3:11a
PROTOCOL INI 576 03-17-96 7:58a
SHARES PWL 622 03-18-96 2:53a <will make new file for you
MICHAELA PWL 606 03-18-96 2:58a <will make new file for you
SYSTEM INI 3,441 03-18-96 2:58a <from server machine-EDIT IT!!
CONNECT DAT 40 03-19-96 8:20a <makes on the fly
17 file(s) 696,738 bytes
19,791,872 bytes free
This is my memory configuration with NET and FBB running...
Modules using memory below 1 MB:
Name Total = Conventional + Upper Memory
-------- ---------------- ---------------- ----------------
MSDOS 14,413 (14K) 14,413 (14K) 0 (0K)
SETVER 608 (1K) 608 (1K) 0 (0K)
HIMEM 1,168 (1K) 1,168 (1K) 0 (0K)
IFSHLP 3,872 (4K) 3,872 (4K) 0 (0K)
EMM386 3,120 (3K) 3,120 (3K) 0 (0K)
COMMAND 3,088 (3K) 3,088 (3K) 0 (0K)
BASIC 12,000 (12K) 12,000 (12K) 0 (0K)
SERV 337,136 (329K) 336,912 (329K) 224 (0K)
COMMAND 3,152 (3K) 2,656 (3K) 496 (0K)
ANSI 4,208 (4K) 0 (0K) 4,208 (4K)
RAMDRIVE 1,296 (1K) 0 (0K) 1,296 (1K)
PROTMAN 400 (0K) 0 (0K) 400 (0K)
NE1000 9,360 (9K) 0 (0K) 9,360 (9K)
NDISHLP 1,440 (1K) 0 (0K) 1,440 (1K)
NETBEUI 37,792 (37K) 0 (0K) 37,792 (37K)
DOSKEY 4,144 (4K) 0 (0K) 4,144 (4K)
ESS 1,776 (2K) 0 (0K) 1,776 (2K)
COMMAND 3,152 (3K) 0 (0K) 3,152 (3K)
Free 338,848 (331K) 277,568 (271K) 61,280 (60K)
Memory Summary:
Type of Memory Total = Used + Free
---------------- ---------- ---------- ----------
Conventional 655,360 377,792 277,568
Upper 125,568 64,288 61,280
Reserved 131,072 131,072 0
Extended (XMS)* 1,185,152 1,185,152 0
---------------- ---------- ---------- ----------
Total memory 2,097,152 1,758,304 338,848
Total under 1 MB 780,928 442,080 338,848
Total Expanded (EMS) 1,638,400 (1,600K)
Free Expanded (EMS)* 180,224 (176K)
* EMM386 is using XMS memory to simulate EMS memory as needed.
Free EMS memory may change as free XMS memory changes.
Largest executable program size 277,456 (271K)
Largest free upper memory block 54,064 (53K)
MS-DOS is resident in the high memory area.
73 and Good Luck *BUB*