T.R | Title | User | Personal Name | Date | Lines |
---|
1133.1 | At least two that I know work | ROGER::GAUDET | Because the Earth is 2/3 water | Mon Jun 20 1994 14:19 | 6 |
| I know for a fact that the DEPCA and the EtherWorks 3 NICs will work with DECndu
Plus for DOS. I have a floppy that I've used in systems with either card and
with a simple edit of the CONFIG.SYS and PROTOCOL.INI files I can load devices
with DECndu Plus. For other supported NICs, the gurus will have to jump in here.
...Roger...
|
1133.2 | Please Thinks to field People................ | CLPR01::PEYRACHE | Jean-Yves Peyrache Country Support Group France | Tue Jun 21 1994 08:34 | 13 |
| ok Roger,
and which ethernet board for Portable PC,laptop, etc,
and best wishes from the field is a Pc with Hubwatch,Probewatch,Decnduplus
for Troubleshoot/debug/upgrade Dechub Stuff on customer site..
Finding the good PC that's works with all products directly on site
isnt really easy ...
rgds
Jean-Yves
|
1133.3 | DEPEA for laptops | ROGER::GAUDET | Because the Earth is 2/3 water | Tue Jun 21 1994 16:19 | 6 |
| One of our engineers went to Networld+Interop in Las Vegas with a DECpc 425SE
laptop that had the DEPEA network interface. According to his report, he
successfully ran DECndu Plus to update hubs/modules and HUBwatch for Windows
V2.0. He did not have Probewatch for Windows installed on this machine.
...Roger...
|
1133.4 | config.sys autoexec.bat please | PRSSOS::PEYRACHE | Jean-Yves Peyrache Country Support Group France | Wed Jun 22 1994 05:01 | 13 |
|
Roger,
i have tested yesterday with depea on my PC, and i have the same problem
Decnduplus does'nt works ..
can you add some others informations regarding the setup of files
in this PC (autoexec,config.protocol...)
thanks
Jean-Yves
|
1133.5 | Here are the files for the DECpc 425 SE with a DEPEA adapter | ROGER::GAUDET | Because the Earth is 2/3 water | Wed Jun 22 1994 14:55 | 85 |
| ==============
= CONFIG.SYS =
==============
shell=\command.com /P /E:526
device=PROTMAN.SYS /I:A:\
REM ** DEPCA.DOS below is used mainly for example (of course it is useful if
REM ** you have a DEPCA) replace it with the path and NDIS driver filename for
REM ** the ethernet adapter installed in your system and make the apropriate
REM ** changes to the protocol.ini file.
REM device=\ewrk3.dos
REM device=\depca.dos
device=\depea.dos
================
= AUTOEXEC.BAT =
================
echo off
break on
prompt $p$g
set path=C:\DOS
doskey /insert
dllndis
netbind
================
= PROTOCOL.INI =
================
; PROTOCOL.INI
; for DECndu
[protocol manager]
DRIVERNAME = PROTMAN$
[DATALINK]
DRIVERNAME = DLL$MAC
LG_BUFFERS = 16
SM_BUFFERS = 6
OUTSTANDING = 32
HEURISTICS = 0
MOP = 0
;** Specify IRQ level used by workstations network adapter.
;** Default is 5.
;NI_IRQ = 5
;** Replace DEPCA.DOS with the name of the driver you wish to use
;** with the ethernet adapter installed in your system.
;BINDINGS = DEPCA.DOS
;BINDINGS = EWRK3.DOS
BINDINGS = DEPEA.DOS
; ** You can leave these two lines alone. Use it as an example for the
; ** section which follows.
[DEPCA.DOS]
DRIVERNAME = DEPCA$
; ** Here is where you have to fill in the information for your driver.
; ** Insert the appropriate names and fill in any other neccessary parameters.
; ** See your adapter documentation for additional information. You should
; ** replace YOURDRIVER.HERE with the filename of your NDIS driver.
; ** Replace YOURDRIVER$ with the filename$, as in the example above.
[YOURDRIVER.HERE]
DRIVERNAME = YOURDRIVER$
;** Ignore this section if you do not have the DIGITAL ewrk3 ethernet adapter.
;** Change "BINDINGS = " statement above if your system has the new EtherWorks 3
;** Ethernet adapter.
[EWRK3.DOS]
DRIVERNAME = EWRK3$
IOADDRESS = 0X300
RAMADDRESS = 0XD000
MEMORYMODE = 2
INTERRUPT = 5
[DEPEA.DOS]
DRIVERNAME = DEPEA$
IOADDRESS = 0X378
INTERRUPT = 7
PMODE=3
DIAGNOSTIC = 1
|
1133.6 | same problem again.. | PADNOM::PEYRACHE | Jean-Yves Peyrache Country Support Group France | Thu Jun 23 1994 12:13 | 9 |
| Roger,
thanks for your files, but i have already same configurations, can you
add it version of DEPEA drivers ..
thanks again for your help
jean-yves
|
1133.7 | Latest files for DEPEA | ROGER::GAUDET | Because the Earth is 2/3 water | Thu Jun 23 1994 13:10 | 7 |
| Here are the dates of the files we are using in our DECpc 425SE:
DEPEA DOS 52,442 01-25-94 9:45a
DLLNDIS EXE 8,915 05-04-92 8:47a
NETBIND EXE 15,639 05-04-92 8:47a
...Roger...
|
1133.8 | DECpc 425SL/e + XIRCOM works | YUPPY::GAY | David Gay - (7)847 6543 | Sat Jul 09 1994 19:16 | 13 |
| Hi,
I've got NDUplus to work on DECpc 425SL/e with the XIRCOM PCMIA card.
I've also tried to get it working on a DECpc 325 with the same software
and it doesn't work!
PLease mail me if you want the relevant files as I don't read this
conference very often.
Regards,
David.
|
1133.9 | decndup kit?? | MSBCS::HURLEY | | Thu Feb 06 1997 15:15 | 2 |
| Any Idea where I can get the decndup kit for dos?? I need to upgrade
the firm on the dec900 repeater.
|
1133.10 | | UTRTSC::GROOT_R | Ronald de Groot | Fri Feb 07 1997 06:32 | 9 |
| Hello,
I don't no why you will use the decndup kit because you can use tftp
(hubloader) to upgrade the dec900 repeater.
You can find the decndup kit on,
NETCAD::PROJ$706:[NDU.V3.RELEASE.DOS.SSB]
NDUPLUS.ZIP 15-SEP-1993
Ronald
|
1133.11 | | MSBCS::HURLEY | | Fri Feb 07 1997 08:08 | 3 |
| I tried the load from clearvision to the repeater and it came back
saying its not supported. I was looking for something to run from my
pc. You mentioned hubloader tftp?? Can you fill me in on that process?
|
1133.12 | | NETCAD::MILLBRANDT | answer mam | Fri Feb 07 1997 09:58 | 10 |
| Older versions (V1.0G) of the DECrepeater900 can be loaded via
TFTP if you assign an IP address to the repeater and use a
connection from the TFTP server to front port on the repeater.
Give clearVISN Flash Loader the repeater's IP address, hit Show,
and see if the repeater's sysDescripter pops up. Then start the
load. Or use the hub setup console, and redirect to the repeater's
menu, then choose its downline upgrade option.
Dotsie
|
1133.13 | | MSBCS::HURLEY | | Fri Feb 07 1997 11:45 | 9 |
| I tried it with giving the repeater an address, I hit show and the
sysDescripter popws up. I then tried the load and it looked like it
started and then went into the reseting mode and then came back with
the same older version. (v1.0g)..
I'll play around on them this saturday and try and figure out
whats up..
Thanks..
|
1133.14 | Are you use Hubloader under ClearVISN? | CSC32::B_GOODWIN | MCI Mission Critical Support Team | Fri Feb 07 1997 13:37 | 7 |
| There is a box under where you specifiy the load image name in
Hubloader, "TFTP Server", or something like that. Did you put in the
address of the TFTP server there? For some reason, it doens't default
to the PC TFTP server when using ClearVISN. Also, you need to start the
TFTP server by clicking on the Router Manager in the ClearVISN apps.
|
1133.15 | thanks | MSBCS::HURLEY | | Mon Feb 10 1997 07:29 | 16 |
| Well after playing around this weekend I finally got MOST of them to
load via tftp. For some reason and I'm not sure why I had to reset the
repaters to factory default first then set the ip address and then they
all load fine.. All but one..
So my next question is...
What can I do to a repeater that started the load and 20 minutes lately
timed out will not pass selftest??
1 out of 10 had this problem but the other 9 are up and running with
the new firmware..
Thanks for your help also..
JOHn
|