LAN Requester would not start - HELP please!!!
Michal Jerabek
I know some short time ago there was a discussion about the
``LAN Requester'' the would not start.
Well, I have the problem, too, but what helped then is of no use
for me.
My system is a portable Compaq Armada 4100, PCMCIA Trust Netlink
Combo PC-Card, Warp 4, there used to be FP 9 installed.
I installed the File and Print Sharing and the driver for my card.
But when starting the Peer to Peer I got just the message
``LAN Requester could not be started'' message.
Withe ``net start'' command from the command line it was
``Requester service could not be started. NET3060:
The service did not respond to a control signal and was
stopped with the DosKillProc function.''
After 1001 experiments I deleted my well runnging OS/2 system
and reinstalled, but still the problem was not resolved and
I got the same error message whenever I tried to start the net.
In a moment of the deepest possible frustration I wiped again the
newly installed OS/2 and installed Win95: just to see what would happen
(I could not be sure that the cables, terminators and even the cards
are OK). Well, after Win95 installation on the notebook and rebooting
the
desktop to Win95 the win network was ready and running in less then 10
minutes. Therefore I believe the HW is OK.
Then I deleted the Win95 and reinstalled the OS/2. I am almost dead
after
3 days of unsuccesful attempts but the problem is still well alive
and kicking (me).
What to do? Any idea. Many thanks
Michal Jerabek
fo7...@public.uni-hamburg.de
cha...@isonline.com
at 02:21 PM, Michal Jerabek
<Michal_...@public.uni-hamburg.de> said:
>I installed the File and Print Sharing and the driver for
>my card. But when starting the Peer to Peer I got just the
>message ``LAN Requester could not be started'' message.
>Withe ``net start'' command from the command line it was
>``Requester service could not be started. NET3060: The
>service did not respond to a control signal and was stopped
>with the DosKillProc function.''
I am having the same problem so let me know if you hear
anything that works. One person recommmended that I put the
pc on the other end and turn it on as he had a similar
problem where the card wasn't fully initializing without
something on the other end. But that didn't work for me so
I am still looking. :(
--
Michal Jerabek
I am game, let us team up. In the meantime I have read (as I believe)
everything about the
PROTOCOL.INI and IBMLAN.INI in the on-line documentation, but still - I
am a looser. I am loosing
my optimismus, so to say. But there must definitely be something we
missed in the configuration.
In the meantime (3 hours since my last checking the news) I installed
the the thing (MPTS and Peer to
peer) 3x (at least)!!!!.
But I still hope
Michal
Michal Jerabek
option, then set everything up (including shared resources) and then
``change'' the no-adapter for the driver to the adapter I actually have.
With ``no-adapter'' starting of the LAN Requester was without problems -
and quick.
After changing the card - the LAN Requster could not start anymore.
I am using BNC coax, but I think the problem is not there.
Frank Beythien
<Michal_...@public.uni-hamburg.de> wrote:
> > >Withe ``net start'' command from the command line it was
> > >``Requester service could not be started. NET3060: The
> > >service did not respond to a control signal and was stopped
> > >with the DosKillProc function.''
Does \ibmcom\lantran.log give any clue?
what about NET ERROR output?
CU/2
--
Frank Beythien efbe @ prima.de
Michal Jerabek
the lantran.log is as follows
--------------------------------------
IBM OS/2 LANMSGDD [08/01/96] 5.05 is loaded and operational.
IBM - OS/2 Socket/MPTS Common Transport Semantics
IBM OS/2 NETBEUI 5.00.0
NETBEUI: Using a 32-bit data segment.
Installing NETWKSTA.200 Version 5.0. IBM LAN Redirector (Sep 24, 1996)
IBM OS/2 NETBIOS 4.0
Adapter 0 has 105 NCBs, 154 sessions, and 14 names available to NETBIOS
applications.
NETBIOS 4.0 is loaded and operational.
IBM LANVDD is loaded and operational.
IBM OS/2 LAN Netbind
IBM - OS/2 Socket/MPTS NetBios Service Driver
Adapter 0 is using node address 0080C88B49A7. The Token-Ring format is
000113D192E5.
--------------------------------------------------------------------
I tried also to install and configure TCP/IP but it did not help. Still
the LAN Requester would not
start
the NET ERROR is as follows:
-----------------------------------------
Program Message Time
-------------------------------------------------------------------------------
REQUESTER 3197 07.02.99 20:27:40
NET3197: A reset of driver NETBEUI$ failed to complete the NCB. The
NCB is
the data.
00 02 00 00 20 FF 00 02 10 D0 E2 00 80 01 00 00 ....
...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 56 4F
..............VO
59 41 47 45 52 20 20 20 20 20 20 20 20 00 00 00 YAGER
...
20 FF 00 00 00 FF 00 00 00 00 00 00 00 00 00 00
...............
REQUESTER 3197 07.02.99 20:28:56
NET3197: A reset of driver NETBEUI$ failed to complete the NCB. The
NCB is
the data.
00 02 00 00 20 FF 00 02 10 80 E1 00 80 01 00 00 ....
...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 56 4F
..............VO
59 41 47 45 52 20 20 20 20 20 20 20 20 00 00 00 YAGER
...
20 FF 00 00 00 FF 00 00 00 00 00 00 00 00 00 00
...............
REQUESTER 3197 07.02.99 21:49:56
NET3197: A reset of driver NETBEUI$ failed to complete the NCB. The
NCB is
the data.
00 02 00 00 20 FF 00 02 10 10 E3 00 80 01 00 00 ....
...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 56 4F
..............VO
59 41 47 45 52 20 20 20 20 20 20 20 20 00 00 00 YAGER
...
20 FF 00 00 00 FF 00 00 00 00 00 00 00 00 00 00
...............
REQUESTER 3197 07.02.99 22:35:10
NET3197: A reset of driver NETBEUI$ failed to complete the NCB. The
NCB is
the data.
00 02 00 00 20 FF 00 02 10 E0 33 00 80 01 00 00 ....
.....3.....
00 00 00 00 00 00 00 00 00 00 00 00 00 00 56 4F
..............VO
59 41 47 45 52 20 20 20 20 20 20 20 20 00 00 00 YAGER
...
20 FF 00 00 00 FF 00 00 00 00 00 00 00 00 00 00
...............
The command completed successfully.
------------------------
It is still enigma to me.
On the desktop (with another ethernet card but from the same vendor)
everything seems to be OK and was quite easy to install.
By the way, the ``Adapter 0 is using node address 0080C88B49A7''. What
is here called ``node address'' is something I added during the
configuration as a adaptor network address; this value gave me a DOS
test program from the PC-Card vendor (in all other cases I have just
accepted defaults offered by MPTS, excluding TCP/IP, which I installed
later, just now, with the help of the document ``LAN Setup'' by Judy
McDermott, http://www.gt-online.com/~bri).
Any suggestion would be really appreciated
Michal Jerabek
fo7...@public.uni.hamburg.de
Stephen Monteith
Replying to a message Michal Jerabek on 1999/02/07, 13:29:28 said:
MJ> I am game, let us team up. In the meantime I have read (as I believe)
MJ> everything about the
MJ> PROTOCOL.INI and IBMLAN.INI in the on-line documentation, but still -
MJ> I
MJ> am a looser. I am loosing
MJ> my optimismus, so to say. But there must definitely be something we
MJ> missed in the configuration.
Here is my Protocol.ini file, which is working, so this may help as a
reference:
[PROT_MAN]
DRIVERNAME = PROTMAN$
[IBMLXCFG]
NETBEUI_nif = netbeui.nif
TCPBEUI_nif = tcpbeui.nif
TCPIP_nif = tcpip.nif
EP325_nif = EP325.nif
ETHPCI_nif = ETHPCI.nif
[NETBIOS]
DriverName = netbios$
ADAPTER0 = netbeui$,0
ADAPTER1 = tcpbeui$,1
[NETBEUI_nif]
DriverName = netbeui$
Bindings = EP325_nif
ETHERAND_TYPE = "I"
USEADDRREV = "YES"
OS2TRACEMASK = 0x0
SESSIONS = 130
NCBS = 225
NAMES = 21
SELECTORS = 50
USEMAXDATAGRAM = "YES"
ADAPTRATE = 1000
WINDOWERRORS = 0
MAXDATARCV = 4168
TI = 30000
T1 = 1000
T2 = 200
MAXIN = 1
MAXOUT = 1
NETBIOSTIMEOUT = 500
NETBIOSRETRIES = 3
NAMECACHE = 1000
RNDOPTION = 1
PIGGYBACKACKS = 1
DATAGRAMPACKETS = 50
PACKETS = 300
LOOPPACKETS = 8
PIPELINE = 5
MAXTRANSMITS = 6
MINTRANSMITS = 2
DLCRETRIES = 10
FCPRIORITY = 5
NETFLAGS = 0x0
[TCPBEUI_nif]
DriverName = tcpbeui$
Bindings = ,EP325_nif
NODETYPE = "B-Node"
OS2TRACEMASK = 0x0
SESSIONS = 130
NCBS = 225
NAMES = 21
SELECTORS = 15
USEMAXDATAGRAM = "NO"
NETBIOSTIMEOUT = 500
NETBIOSRETRIES = 2
NAMECACHE = 1000
PRELOADCACHE = "NO"
NAMESFILE = 2
DATAGRAMPACKETS = 20
PACKETS = 50
INTERFACERATE = 300
[TCPIP_nif]
DriverName = TCPIP$
Bindings = ,EP325_nif,FXWRAP_nif
[EP325_nif]
DriverName = EP325$
RamAddress = 0x0D0000
AdapterID = "0000216126C6"
[ETHPCI_nif]
DriverName = PCIND$
AdapterID = "0040053DD32C"
[FXWRAP_nif]
Drivername = FXWRAP1$
Bindings = ETHPCI_nif
This is my IBMLAN.INI:
; OS/2 Peer initialization file
[networks]
net1 = NETBEUI$,0,LM10,34,70,14
; This information is read by the redirector at device initialization time.
[requester]
COMPUTERNAME = JUXTA
DOMAIN = MYNETWORK
; The following parameters generally do not need to be
; changed by the user.
charcount = 16
chartime = 250
charwait = 3600
keepconn = 600
keepsearch = 600
maxcmds = 16
maxerrorlog = 100
maxthreads = 10
maxwrkcache = 256
numalerts = 12
numcharbuf = 10
numservices = 7
numworkbuf = 15
numdgrambuf = 14
othdomains =
printbuftime = 90
sesstimeout = 45
sizcharbuf = 512
sizerror = 1024
sizworkbuf = 4096
useallmem = no
; The wrkheuristics parameter sets a variety of requester fine-tuning
; options. Brief descriptions are provided here for each digit. More
; complete descriptions, along with explanations of relationships between
; digits can be found in the OS/2 Peer Technical Reference.
;
; When not otherwise specified, a value of 0 means off (inactive) and 1 means
; on (active).
;
; 0 opportunistic locking of files (default is 1)
; 1 performance optimization for batch (.CMD) files (default is 1)
; 2 asynchronous unlock and asynchronous write-unlock
; 0 = never 2 = only on a LAN Server virtual circuit
; 1 = always (default)
; 3 asynchronous close and asynchronous write-close
; 0 = never 2 = only on a LAN Server virtual circuit
; 1 = always (default)
; 4 buffer all named pipes and serial devices (default is 1)
; 5 combined read-lock and write-unlock
; 0 = never 2 = only on a LAN Server virtual circuit
; 1 = always (default)
; 6 open and read optimization (default is 1)
; 7 reserved
; 8 use of the chain-send NETBIOS NCB
; 0 = never
; 1 = when a server's buffer is larger than the workstations buffer
; 2 = always (default)
; 9 buffer small read and write requests until the buffer is full
; 0 = never 2 = only on a LAN Server virtual circuit
; 1 = always (default)
; 10 buffer mode
; 0 = always read buffer size amount of data if the request is smaller
; than the buffer size (sizworkbuf) and data is being read
; sequentially
; 1 = use full buffer if file is open for reading and writing
; 2 = use full buffer if reading and writing sequentially
; 3 = buffer all requests smaller than the buffer size (if hits occur)
; (default)
; 11 RAW read and RAW write SMB protocols (default is 1)
; 12 RAW read-ahead buffer (default is 1)
; 13 RAW write-behind buffer (default is 1)
; 14 read multiplexing SMB protocols (default is 1)
; 15 write multiplexing SMB protocols (default is 1)
; 16 use of big buffers for large core (non-RAW) reads (default is 1)
; 17 same-size read-ahead or read-to-sector boundary (default is 1)
; 18 same-size small record write-behind or write-to-sector boundary
; (default is 0)
; 19 reserved and must be 0
; 20 flush pipes and devices on a DosBufReset or DosClose operation
; 0 = Flush only files and devices opened by the caller. Spin until
; flushed. Wait for confirmation before processing with other
; tasks. (default)
; 1 = Flush only files and devices opened by the caller. Flush only
; once. Do not wait for confirmation.
; 2 = Flush all files and all input and output of short-term pipes
; and devices. Spin until flushed.
; 3 = Flush all files and all input and output of short-term pipes
; and devices. Flush only once.
; 4 = Flush all files and all input and output of all pipes and devices.
; Spin until flushed.
; 5 = Flush all files and all input and output of all pipes and devices.
; Flush only once.
; 21 LAN Server encryption of passwords (default is 1)
; 22 control log entries for multiple occurrences of an error
; 0 = log all occurrences (default)
; 1-9 = limit occurrences that are logged (1-9 define size of table
; that is used to track errors)
; 23 buffer all files opened with deny-write sharing mode (default is 1)
; 24 buffer all files opened with the read-only attribute set (default is 1)
; 25 read ahead when opening for execution (default is 1)
; 26 handle the interrupt (ctrl+c) key
; 0 = allow no interrupts
; 1 = allow interrupts only on long-term operations
; 2 = always allow interrupts (default)
; 27 force correct open mode when creating files on a core server (reserved
; for DBCS users) (default is 1)
; 28 NETBIOS NoAck mode
; 0 = NoAck is disabled.
; 1 = NoAck is set on send only. (default)
; 2 = NoAck is set on receive only.
; 3 = NoAck is set on send and receive.
; 29 send data along with SMB write-block RAW requests (default is 1)
; 30 send a message to the screen when the requester logs an error
; 0 = never
; 1 = on write-fault errors only (no time out) (default)
; 2 = on write-fault and internal errors only (no time out)
; 3 = on all errors (no time out)
; 4 = reserved
; 5 = on write-fault errors only (time out)
; 6 = on write-fault and internal errors only (time out)
; 7 = on all errors (time out)
; 8 = on all errors (time out) and pop up an error if a session
; to a server is abnormally disconnected
; 9 = on all errors (time out) and generate an INT24 (critical
; error) to applications running under DOS emulation if a
; network hard error is encountered
; 31 reserved
; 32 behavior of DosBufReset on a redirected file (not pipes or devices).
; When the call to the API returns, the data in the buffer has been
; handled as follows:
; 0 = Changed data in the buffer was sent from the requester to the
; server. The server has written the data to disk.
; 1 = Changed data in the buffer was sent from the requester to the
; server. The server has not yet written the data to disk.
; 2 = DosBufReset was ignored. (default)
; 33 time interval for performing logon validation from the domain
; controller
; 0 = 5 seconds 4 = 60 seconds 8 = 8 minutes
; 1 = 15 seconds (default) 5 = 90 seconds 9 = 15 minutes
; 2 = 30 seconds 6 = 2 minutes
; 3 = 45 seconds 7 = 4 minutes
; 34 date validation
; 0 = PCLP date format (default)
; 1 = MSNET date format
; 2 = assume date is correct
; 35 free disk space reported to DOS and Windows applications
; 0 = return true value (default)
; 1 = return a value less than two gigabytes
; 36 time and date synchronization with the domain controller at logon
; (default is 1)
; 37 type of verification for the LAN Server logon
; 0 = no verification
; 1 = verify against local NET.ACC (default)
; 2 = verify against domain NET.ACC
; 38 display warning messages for the LAN Server logon
; 0 = do not display warning messages
; 1 = display all warning messages (default)
; 2 = do not display LAN Server specific warning messages
; 3 = display all warning messages, including password expiration date
; 39 buffer all files opened in compatibility mode
; 0 = buffer only files opened for read access in compatibility mode
; 1 = buffer all files opened in compatibility mode (default)
; 40 allow a user to logon multiple times in the same domain (default is 1)
;
; The next lines help you to locate bits in the wrkheuristics entry.
; 1 2 3 4
; 012345678901234567890123456789012345678901
wrkheuristics = 111111112131111111000101112011122100111110
wrkservices = PEER,MESSENGER
wrknets = NET1
[messenger]
logfile = messages.log
sizmessbuf = 4096
[peer]
auditing = resource
; The following parameters generally do not need to be
; changed by the user. NOTE : srvnets= is represented in
; the server info struct as a 16-bit lan mask. Srvnet names
; are converted to indexes within [networks] for the named nets.
guestacct = guest
autodisconnect = -1
forwardauth = no
maxauditlog = 100
maxchdevjob = 6
maxchdevq = 2
maxchdevs = 2
maxconnections = 128
maxlocks = 64
maxopens = 160
maxsearches = 150
maxsessopens = 120
maxsessreqs = 25
maxsessvcs = 1
maxshares = 64
maxusers = 32
numbigbuf = 3
numfiletasks = 1
numreqbuf = 48
sizreqbuf = 4096
srvanndelta = 3000
srvannounce = 180
srvcomment = JUXTAPOSITION BBS PC
srvhidden = no
; The srvheuristics parameter sets a variety of server fine-tuning
; options. Brief descriptions are provided here for each digit. More
; complete descriptions, along with explanations of relationships between
; digits can be found in the OS/2 Peer Technical Reference.
;
; When not otherwise specified, a value of 0 means off (inactive) and 1 means
; on (active).
;
; 0 opportunistic locking of files (default is 1)
; 1 read-ahead when the requester is performing sequential access
; 0 = do not use read-ahead
; 1 = use single read-ahead thread (default)
; 2 = use asynchronous read-ahead thread
; 2 write-behind (default is 1)
; 3 use of the chain-send NETBIOS NCB (default is 1)
; 4 check all incoming SMBs for correct format (default is 0)
; 5 support FCB opens (default is 1)
; 6 set priority of server (default is 4)
; 0-9 = 0 is highest priority, 9 is lowest priority
; 7 automatically allocate additional memory for directory searches
; (default is 1)
; 8 write records to the audit log only when the scavenger wakes up
; (default is 1)
; 9 do full buffering when a file is opened with deny-write sharing mode
; (default is 1)
; 10 set the interval for the scavenger to wake up
; 0 = 5 seconds 4 = 25 seconds 8 = 45 seconds
; 1 = 10 seconds (default) 5 = 30 seconds 9 = 50 seconds
; 2 = 15 seconds 6 = 35 seconds
; 3 = 20 seconds 7 = 40 seconds
; 11 allow compatibility-mode opens of certain types of files by translating
; them to sharing mode opens with deny-none
; 0 = Always use compatibility-mode opens.
; 1 = Use deny-none sharing mode if read-only access to .EXE or .COM
; files.
; 2 = Use deny-none sharing mode if read-only access to .EXE or .COM
; files. Use deny-write sharing mode if read-only access to .BAT
; files is requested.
; 3 = Use deny-none sharing mode on all compatibility-mode opens.
; (default)
; 12 allow DOS LAN Services workstations to use a second NETBIOS session when
; sending printer requests (default is 1)
; 13 number of 64KB buffers used for read-ahead
; 0-9 = number of buffers (default is 1)
; 14 convert incoming path specifications into most basic format (default is
0)
; 15 Oplock Timeout and NETBIOS Acknowledgment Timeout (default is 0)
; 0 = 35 second Oplock Timeout; 34 second NETBIOS Acknowledgment Timeout
; 1 = 70 second Oplock Timeout; 69 second NETBIOS Acknowledgment Timeout
; 2 = 140 second Oplock Timeout; 127 second NETBIOS Acknowledgment
Timeout
; 3 = 210 second Oplock Timeout; 127 second NETBIOS Acknowledgment
Timeout
; 4 = 280 second Oplock Timeout; 127 second NETBIOS Acknowledgment
Timeout
; 5 = 350 second Oplock Timeout; 127 second NETBIOS Acknowledgment
Timeout
; 6 = 420 second Oplock Timeout; 127 second NETBIOS Acknowledgment
Timeout
; 7 = 490 second Oplock Timeout; 127 second NETBIOS Acknowledgment
Timeout
; 8 = 560 second Oplock Timeout; 127 second NETBIOS Acknowledgment
Timeout
; 9 = 640 second Oplock Timeout; no NETBIOS Acknowledgment Timeout
; 16 validate IOCTLs (default is 1)
; 17 how long the server maintains unused, dynamic big buffers before freeing
; the memory.
; 0 = 0 seconds 4 = 5 minutes 8 = 1 hour
; 1 = 1 second 5 = 10 minutes 9 = indefinitely
; 2 = 10 seconds 6 = 20 minutes
; 3 = 1 minute (default) 7 = 40 minutes
; 18 how long the server waits after failing to allocate a big buffer before
; trying again.
; 0 = 0 seconds 3 = 1 minute (default)
; 1 = 1 second 4 = 5 minutes
; 2 = 10 seconds 5 = 10 minutes
; 19 RAW read and RAW write SMB protocols (default is 1)
; 20 server responds to announcement requests (default is 1)
;
; The next lines help you to locate bits in the srvheuristics entry.
; 1 2
; 012345678901234567890
srvheuristics = 111101411113110013311
SRVSERVICES =
srvnets = NET1
[replicator]
replicate = IMPORT
importpath = C:\ibmlan\repl\import
tryuser = yes
password =
[services]
; Correlates name of service to pathname of service program.
; The pathname must be either
; 1) an absolute path (including the drive specification)
; OR
; 2) a path relative to the IBMLAN root
messenger = services\msrvinit.exe
peer = services\peerinit.exe
replicator = services\replicat.exe
requester = services\wksta.exe
Stephen Monteith
1988 Jeep YJ with 30" tires and RE 4" lift
The Operating System/2 Version is 4.00 Rev. 9.033
There are 59 Processes with 260 Threads.
This machine's uptime is 0d 5h 41m 49s 648ms.
--
| Return Address: stephen....@mnet.pubnix.ten
| Standard disclaimer: The views of this user are strictly her/his own.
| From addresses mangled solely to block spamming.
| Apologies to those trying to respond, correct suffix with .net
Jack Troughton
<Michal_...@public.uni-hamburg.de> wrote:
àHi
à
àno Iam definitely not on a Token Ring network! Just 2 PC connected with BNC
àcoax. But I don't remember saying this thing it should consider the
à``network'' a Token Ting. How could I change it?
à
àMichal Jerabek
àfo7...@public.uni-hamburg.de
à
àJack Troughton wrote:
à
à> Hmmm... are you actually on a Token Ring network? If not, it might be
à> crapping out thanks to unexpected data being returned from the network
à> card...
à>
à> Jack Troughton ICQ:7494149
à> http://207.96.209.68:8000/
à> jack.troughton at videotron.ca
à> jaft at adan.kingston.net
à> MontrÈal PQ Canada
Use the Network Adapters and Protocol Services object in system setup;
this points at mpts.exe if you're too impatient to go any further than
a command line:)
You should be able to tell it the type of network in there... you need
to change it from token-ring to ethernet.
Good Luck!
Jack Troughton ICQ:7494149
http://207.96.209.68:8000/
jack.troughton at videotron.ca
jaft at adan.kingston.net
MontrÈal PQ Canada
askbill*AT*ibm.net
newly installed Aurora beta, every attempt to sart requester resulted in
two "dots" then total freeze-up of system - stopped clock, dead mouse &
kbd, had to use hardware reset switch to reboot.
Noticed that it always hung with the FDD drive light on.................
Stuck the closest floppy disk in the drive (an HP scanner install disk
FWIW) - tried again.
Requester & Server interrogated the floppy drive, and started normaly.
??????
Go figure!
Good luck!
Bill Hacker
--
-----------------------------------------------------------
ask...@ibm.net (William B. Hacker, III)
Titanic '12 NYSE '29 Windows '95 and subsequent.....
-----------------------------------------------------------
Tony Saucedo
What does your Protocol.ini look like?
Do you have sockets confiured?
What are the settings for the NIC? Use the Mfg supplied
disk software to vbiew the settings.
It seems like the problem maybe related to the card settings
since it cannot reset the card, therefore the requester is
failing to start.
Please post your Protocol.ini and adapter settings.
Thanks
--
Tony,
******************************************************
| Tony Saucedo |
| EAGLE Traffic Control Systems |
| Austin, Texas |
| |
| E-mail: Tony.S...@eagletcs.com |
| |
| For E-mail Reply make the id singular (- the s) |
******************************************************
Frank Beythien
<Michal_...@public.uni-hamburg.de> wrote:
> Hi and thanks
>
> the lantran.log is as follows
> --------------------------------------
> IBM OS/2 LANMSGDD [08/01/96] 5.05 is loaded and operational.
> IBM - OS/2 Socket/MPTS Common Transport Semantics
Why did you configure socket /netbios support. Do you really need it?
> IBM - OS/2 Socket/MPTS NetBios Service Driver
> Adapter 0 is using node address 0080C88B49A7. The Token-Ring format is
> 000113D192E5.
What mpts fixpack do you use? Looks a bit old,. try to install
WR?G8423
show your ibmcom\protocol.ini and ibmlan\ibmlan.ini and config.sys.
Jack Troughton
<Michal_...@public.uni-hamburg.de> wrote:
àIBM OS/2 LANMSGDD [08/01/96] 5.05 is loaded and operational.
àIBM - OS/2 Socket/MPTS Common Transport Semantics
àIBM OS/2 NETBEUI 5.00.0
àNETBEUI: Using a 32-bit data segment.
àInstalling NETWKSTA.200 Version 5.0. IBM LAN Redirector (Sep 24, 1996)
à
àIBM OS/2 NETBIOS 4.0
àAdapter 0 has 105 NCBs, 154 sessions, and 14 names available to NETBIOS
àapplications.
àNETBIOS 4.0 is loaded and operational.
àIBM LANVDD is loaded and operational.
àIBM OS/2 LAN Netbind
àIBM - OS/2 Socket/MPTS NetBios Service Driver
àAdapter 0 is using node address 0080C88B49A7. The Token-Ring format is
à000113D192E5.
à
Hmmm... are you actually on a Token Ring network? If not, it might be
crapping out thanks to unexpected data being returned from the network
card...
Michal Jerabek
Tony Saucedo wrote:
> What does your Protocol.ini look like?
>
> Do you have sockets confiured?
>
> What are the settings for the NIC? Use the Mfg supplied
> disk software to vbiew the settings.
>
> It seems like the problem maybe related to the card settings
> since it cannot reset the card, therefore the requester is
> failing to start.
>
> Please post your Protocol.ini and adapter settings.
> Thanks
>
Hi and thanks
What follows in my PROTOCOL.INI (the default made by MPTS; I tried also some
modifications but to no avail.)
-------------------------------
[PROT_MAN]
DRIVERNAME = PROTMAN$
[IBMLXCFG]
netbeui_nif = netbeui.nif
tcpip_nif = tcpip.nif
ICARDPI_nif = ICARDPI.NIF
[NETBIOS]
DriverName = netbios$
ADAPTER0 = netbeui$,0
[netbeui_nif]
DriverName = netbeui$
Bindings = ICARDPI_nif
NETADDRESS = "0080C88B49A7"
ETHERAND_TYPE = "I"
USEADDRREV = "YES"
OS2TRACEMASK = 0x0
SESSIONS = 254
NCBS = 255
NAMES = 29
SELECTORS = 15
USEMAXDATAGRAM = "YES"
ADAPTRATE = 1000
WINDOWERRORS = 0
MAXDATARCV = 4168
TI = 30000
T1 = 1000
T2 = 200
MAXIN = 1
MAXOUT = 1
NETBIOSTIMEOUT = 500
NETBIOSRETRIES = 3
NAMECACHE = 1000
RNDOPTION = 1
PIGGYBACKACKS = 1
DATAGRAMPACKETS = 10
PACKETS = 335
LOOPPACKETS = 8
PIPELINE = 5
MAXTRANSMITS = 6
MINTRANSMITS = 2
DLCRETRIES = 10
FCPRIORITY = 5
NETFLAGS = 0x0
[tcpip_nif]
DriverName = TCPIP$
Bindings = ICARDPI_nif
[ICARDPI_nif]
DriverName = ICARDP$
NETADDRESS = "0080C88B49A7"
; IOADDRESS = 0x320
; INTERRUPT = 11
---------------------------
the last two lines were not in the ``original'' protocol.ini, I added it later as an
attempt to control the setting of the NIC. I tried it both with it and without.
Without any I/O and IRQ specification the NIC driver claims during the boot:
IOBase=0300H IRQ=10 MemoryBase=0d000H PCMCIASLOT=0.
The DOS diagnostic program supplied with the card claims the adapter is on I/O 320,
IRQ 11 to be find: with these parameters, which I cannot change with this program,
everything seems to me OK, all tests passed:
====================================================================
Trust Netlink Combi PC-Card Diagnostic Program Ver1.05 (970318)ÿ
--------------------------
Your Current Configuration Main Menu
CS Vendor ---------- None SetUp Configuration
CS Revision -------- None Adapter Basic Diagnostics
Node ID ------------ 00 80 C8 8B 49 A7 Network Diagnostics
I/O Base Address --- 320
Interrupt Number --- 11
----------------------------------------------------------
Setup Configuration
Full Duplex ---------> Disabled
Auto Negotiation ----> Enabled
===================================================================
Trust Netlink Combi PC-Card Diagnostic Program Ver1.05 (970318)ÿ
--------------------------------------------------------------------
Adapter Diagnostic
Node ID : 00 80 C8 8B 49 A7
I/O Base Address : 320
Interrupt Number : 11
Cycle 0
Current I/O Base Address ................... PASS
DC-DC Convert, Oscillator, Crystal T7213 ... PASS
EEPROM ..................................... PASS
LAN Setup Registers ........................ PASS
Memory ..................................... PASS
LAN Control Functions ...................... PASS
Loopback Mode Testing ...................... PASS
=================================================================
This DOS program I started in a DOS window (in OS/2, of course).
When doing the Loopback Mode Testing I see flashing on the card control, it should be
a visible sign of some ``network traffic''
I did not find any other way to change the parameters but the statement in
PROTOCOL.INI.
With IOADDRESS = 0x320, INTERRUPT = 11 in PROTOCOL.INI the driver loads with I/O 320,
IRQ 11. But even then I have got the same:
-----------------------
[C:\]net start
No network services are started.
Do you want to start the requester service? (Y/N) [Y]: y
The REQUESTER service is starting..........................
The REQUESTER service could not be started.
NET3060: The service did not respond to a control signal and was stopped with
the DosKillProc function.
For more information, type HELP NET3060.
-----------------------------
Here is my IBMLAN.INI (again, the ``original'' created during the File and Print
sharing installation.
-------------------------------
; OS/2 Peer initialization file
[networks]
net1 = NETBEUI$,0,LM10,100,150,14
; This information is read by the redirector at device initialization time.
[requester]
; The following parameters generally do not need to be
; changed by the user.
charcount = 16
chartime = 250
charwait = 3600
keepconn = 600
keepsearch = 600
maxcmds = 16
maxerrorlog = 100
maxthreads = 10
maxwrkcache = 64
numalerts = 12
numcharbuf = 10
numservices = 4
wrknets = NET1
wrkservices = MESSENGER,PEER
Computername = VOYAGER
Domain = HOMEBASE
[messenger]
[peer]
numbigbuf = 6
numfiletasks = 1
numreqbuf = 48
sizreqbuf = 4096
srvanndelta = 3000
srvannounce = 180
srvcomment = Portable
[replicator]
replicate = IMPORT
importpath = C:\ibmlan\repl\import
tryuser = yes
password =
[services]
; Correlates name of service to pathname of service program.
; The pathname must be either
; 1) an absolute path (including the drive specification)
; OR
; 2) a path relative to the IBMLAN root
messenger = services\msrvinit.exe
peer = services\peerinit.exe
replicator = services\replicat.exe
requester = services\wksta.exe
-----------------------------------------------
I tried several modifications but the problem did not disappear.
The NetBIOS Sockets Parameters:
Maximum values
Sessions: 50 254
NCBs: 80 255
Names 29 29
NetBios hostname VOYAGER
Any help or suggestins would be much appreciated.
Michal Jerabek
fo7...@public.uni-hamburg.de
Michal Jerabek
Frank Beythien wrote:
> Why did you configure socket /netbios support. Do you really need it?
>
I have no idea! But I believe at the beginning it was not configured. I did
it later as an attempt. I think also someone suggested to do that.
> What mpts fixpack do you use? Looks a bit old,. try to install
> WR?G8423
>
No FixPack (for MPTS) at all. I am not trying to find some on the net. Who
knows. Good idea!I hear there is also a fixpack for Peer to Peer. Is it worth
downloading. Some about 5 MB I believe!
> show your ibmcom\protocol.ini and ibmlan\ibmlan.ini and config.sys.
>
> CU/2
> --
> Frank Beythien efbe @ prima.de
I have just posted the PROTOCOL.INI and IBMLAN.INI. Here is the CONFIG.SYS
IFS=C:\OS2\HPFS.IFS /CACHE:2048 /CRECL:64 /AUTOCHECK:CD
rem RUN=C:\OS2\cache.exe /maxage:60000 /diskidle:40000 /bufferidle:20000
/READAHEAD:ON /Lazy:1
REM PROTSHELL=C:\OS2\PMSHELL.EXE
PROTSHELL=C:\PC\BIN\PMSHELL.EXE
SET USER_INI=C:\OS2\OS2.INI
SET SYSTEM_INI=C:\OS2\OS2SYS.INI
SET OS2_SHELL=C:\OS2\CMD.EXE
SET AUTOSTART=PROGRAMS,TASKLIST,FOLDERS,WARPCENTER
SET RESTARTOBJECTS=STARTUPFOLDERSONLY
SET RUNWORKPLACE=C:\OS2\PMSHELL.EXE
SET KILLFEATUREENABLED=ON
SET SCCANBENUKEN=ON
SET SCFINDUTILITY=C:\OS2\APPS\PMSEEK.EXE
SET COMSPEC=C:\OS2\CMD.EXE
SET TMP=C:\TMP
SET TEMP=C:\TMP
AUTOFAIL=YES
LIBPATH=C:\PC\DLL;C:\OS2\PCDLL;.;C:\NETSCAPE\PROGRAM;C:\IBMLAN\NETLIB;C:\MUGLIB\DLL;.;C:\OS2\DLL;C:\MPTN\DLL;C:\IBMCOM\DLL;C:\IBMI18N\DLL;C:\OS2\MDOS;C:\;C:\OS2\APPS\DLL;C:\javaos2\dll;C:\MMOS2\DLL;C:\IBMINST;C:\NSC\DLL;c:\tcpip\dll;c:\tcpip\pcomos2;C:\TCPIP\UMAIL;C:\SOF;C:\Emblsh;c:\emx\dll;c:\epm\dll;
SET
PATH=C:\MPTN\BIN;C:\IBMCOM;C:\NETSCAPE\PROGRAM;C:\IBMLAN\NETPROG;C:\MUGLIB;C:\OS2;C:\OS2\SYSTEM;C:\OS2\MDOS\WINOS2;C:\OS2\INSTALL;C:\;C:\OS2\MDOS;C:\OS2\APPS;C:\javaos2\bin;C:\MMOS2;C:\NSC;c:\tcpip\bin;c:\tcpip\pcomos2;C:\TCPIP\UMAIL;C:\SOF;c:\utils;c:\sys;c:\utils\pack;C:\Emblsh;c:\emx\bin;c:\epm;C:\PC\BIN;
SET
DPATH=C:\MPTN;C:\IBMCOM;C:\IBMLAN\NETPROG;C:\IBMLAN;C:\MUGLIB;C:\OS2;C:\OS2\SYSTEM;C:\OS2\MDOS\WINOS2;C:\OS2\INSTALL;C:\;C:\OS2\BITMAP;C:\OS2\MDOS;C:\OS2\APPS;C:\MMOS2;C:\MMOS2\INSTALL;C:\IBMINST;C:\NSC;C:\TCPIP\PCOMOS2;C:\PC\LANGUAGE;
SET PROMPT=$i[$p]
SET
HELP=C:\MPTN;C:\OS2\HELP;C:\MMOS2\HELP;c:\tcpip\help;C:\TCPIP\UMAIL;C:\PC\HELP;
SET GLOSSARY=C:\OS2\HELP\GLOSS;
SET
EPMPATH=C:\EPM;C:\EPM\DLL;C:\EPM\DIC\;C:\EPM\CSTEX;C:\EPM\CZ;C:\EPM\EPMMAC;C:\EPM\EPMMAC2;C:\EPM\REXX;C:\EPM\EPMSMP;
SET HELPNDX=+LaTeX2e.NDX
SET EPM_DICTIONARIES=C:\EPM\DIC
SET IPF_KEYS=SBCS
PRIORITY_DISK_IO=YES
FILES=20
BASEDEV=IBMKBD.SYS
DEVICE=C:\IBMCOM\PROTOCOL\LANPDD.OS2
DEVICE=C:\IBMCOM\PROTOCOL\LANVDD.OS2
DEVICE=C:\IBMCOM\LANMSGDD.OS2 /I:C:\IBMCOM /S
DEVICE=C:\IBMCOM\PROTMAN.OS2 /I:C:\IBMCOM
DEVICE=C:\OS2\BOOT\TESTCFG.SYS
DEVICE=C:\OS2\BOOT\DOS.SYS
DEVICE=C:\OS2\BOOT\PMDD.SYS
BUFFERS=20
IOPL=YES
rem DISKCACHE=D,LW
MAXWAIT=2
MEMMAN=SWAP,PROTECT
SWAPPATH=C:\OS2\SYSTEM 2048 30720
BREAK=OFF
THREADS=256
PRINTMONBUFSIZE=134,134,134
COUNTRY=421,C:\OS2\SYSTEM\COUNTRY.SYS
SET KEYS=ON
SET
BOOKSHELF=C:\IBMLAN\BOOK;C:\OS2\BOOK;C:\MMOS2;c:\tcpip\help;c:\emx\book;C:\PC\BOOK;
SET
SOMIR=C:\OS2\ETC\SOM.IR;C:\OS2\ETC\WPSH.IR;C:\OS2\ETC\WPDSERV.IR;C:\OS2\ETC\REXX.IR
SET SOMDDIR=C:\OS2\ETC\DSOM
SET ULSPATH=C:\LANGUAGE
SET LOCPATH=C:\IBMI18N\LOCALE;C:\LANGUAGE\LOCALE
BASEDEV=TIMER0.SYS
REM SET DELDIR=C:\DELETE,512;D:\DELETE,512;
BASEDEV=PRINT01.SYS
BASEDEV=IBM1FLPY.ADD
rem BASEDEV=IBM2FLPY.ADD
BASEDEV=IBM1S506.ADD /V
BASEDEV=XDFLOPPY.FLT
BASEDEV=OS2DASD.DMD
PROTECTONLY=NO
SHELL=C:\OS2\MDOS\COMMAND.COM C:\OS2\MDOS
FCBS=16,8
RMSIZE=640
DEVICE=C:\OS2\MDOS\VEMM.SYS
DOS=LOW,NOUMB
DEVICE=C:\OAD\OS2.SYS
DEVICE=C:\OS2\MDOS\VXMS.SYS /UMB
DEVICE=C:\OS2\MDOS\VDPMI.SYS
DEVICE=C:\OS2\MDOS\VDPX.SYS
DEVICE=C:\OS2\MDOS\VWIN.SYS
DEVICE=C:\OS2\MDOS\VW32S.SYS
DEVICE=C:\OS2\BOOT\APM.SYS
DEVICE=C:\OS2\MDOS\VAPM.SYS
DEVICE=C:\OS2\BOOT\OS2CDROM.DMD /Q
IFS=C:\OS2\BOOT\CDFS.IFS /Q
DEVICE=C:\OS2\MDOS\VCDROM.SYS
BASEDEV=IBMIDECD.FLT
DEVICE=C:\OS2\MDOS\VMOUSE.SYS
DEVICE=C:\OS2\BOOT\POINTDD.SYS
DEVICE=C:\OS2\BOOT\MOUSE.SYS
SET LANG=CS_CZ
SET TZ=CET-1
SET DEVICEFONTDISABLED=YES
CODEPAGE=852,850
rem DEVINFO=KBD,CZ,C:\OS2\KEYBOARD.DCP
DEVINFO=KBD,US,C:\OS2\KEYBOARD.DCP
BASEDEV=PCMCIA.SYS /P
DEVICE=C:\OS2\MDOS\VPCMCIA.SYS
DEVICE=C:\OS2\BOOT\COM.SYS
DEVICE=C:\OS2\MDOS\VCOM.SYS
DEVICE=C:\path\DSCD.OS2 /IOP:320 /IRQ:11
DEVICE=C:\icardp\DSCD.OS2
rem device=c:\icardp\DSCDOPEN.OS2
BASEDEV=IBM2CMQ1.SYS /s0=2
BASEDEV=AUTODRV2.SYS
DEVINFO=SCR,VGA,C:\OS2\BOOT\VIOTBL.DCP
SET VIDEO_DEVICES=VIO_SVGA
SET VIO_SVGA=DEVICE(BVHVGA,BVHSVGA)
DEVICE=C:\OS2\MDOS\VSVGA.SYS
SET DMIPATH=C:\DMISL\BIN
RUN=C:\OS2\SMSTART.EXE
RUN=\OS2\BOOT\APMDAEMN.EXE
SET CLASSPATH=C:\javaos2\lib\jempcl10.zip;.\.
DEVICE=C:\MMOS2\ES1788DD.SYS /B:220 /D:1 /I:5 /C:4 /M:300,7 /N:ES17881$
DEVICE=C:\MMOS2\VAUDDRV.SYS ES17881$
SET MMBASE=C:\MMOS2;
SET DSPPATH=C:\MMOS2\DSP;
SET NCDEBUG=4000
RUN=C:\MMOS2\MIDIDMON.EXE
DEVICE=C:\MMOS2\SSMDD.SYS
DEVICE=C:\MMOS2\R0STUB.SYS
DEVICE=C:\MMOS2\MIDI.SYS
RUN=C:\MMOS2\QRYMMCD.EXE
CALL=C:\IBMCOM\PROTOCOL\NETBIND.EXE
RUN=C:\IBMCOM\LANMSGEX.EXE
SET NLSPATH=C:\MPTN\MSG\NLS\%N;c:\tcpip\msg\enus850\%N;
SET ETC=C:\MPTN\ETC
DEVICE=C:\MPTN\PROTOCOL\SOCKETS.SYS
DEVICE=C:\MPTN\PROTOCOL\AFOS2.SYS
DEVICE=C:\MPTN\PROTOCOL\AFINET.SYS
DEVICE=C:\MPTN\PROTOCOL\IFNDIS.SYS
DEVICE=C:\MPTN\PROTOCOL\AFNB.SYS /S:50 /C:80 /N:29
RUN=C:\MPTN\BIN\AFNBINI.EXE
RUN=C:\MPTN\BIN\CNTRL.EXE
CALL=C:\OS2\CMD.EXE /Q /C C:\MPTN\BIN\MPTSTART.CMD >NUL
DEVICE=C:\IBMCOM\PROTOCOL\NETBEUI.OS2
DEVICE=C:\IBMLAN\NETPROG\RDRHELP.200
IFS=C:\IBMLAN\NETPROG\NETWKSTA.200 /I:C:\IBMLAN /N
DEVICE=C:\IBMCOM\PROTOCOL\NETBIOS.OS2
DEVICE=C:\IBMCOM\MACS\ICARDP.OS2
SET I18NDIR=C:\IBMI18N
RUN=C:\IBMLAN\NETPROG\LSDAEMON.EXE
DEVICE=C:\IBMLAN\NETPROG\VNETAPI.OS2
RUN=C:\IBMLAN\NETPROG\VNRMINIT.EXE
SET NWDBPATH=C:\IBMLAN\NETPROG
SET LANINSTEP=E:\CID\IMG\IBMPEER
SET TMP=c:\tcpip\tmp
DEVICE=c:\tcpip\bin\vdostcp.vdd
DEVICE=c:\tcpip\bin\vdostcp.sys
RUN=c:\tcpip\bin\VDOSCTL.EXE
DEVINFO=SCR,VGA,C:\OS2\VIOTBL.DCP
DEVICE=c:\OS2\BOOT\CPQPOWER.SYS
SET HOSTNAME=voyager
Michal Jerabek
no Iam definitely not on a Token Ring network! Just 2 PC connected with BNC
coax. But I don't remember saying this thing it should consider the
``network'' a Token Ting. How could I change it?
Michal Jerabek
fo7...@public.uni-hamburg.de
Jack Troughton wrote:
> Hmmm... are you actually on a Token Ring network? If not, it might be
> crapping out thanks to unexpected data being returned from the network
> card...
>
> Jack Troughton ICQ:7494149
> http://207.96.209.68:8000/
> jack.troughton at videotron.ca
> jaft at adan.kingston.net
> Montréal PQ Canada
Michal Jerabek
Print Sharing Client; Peer; LAN Requester form the IBM site. But alas! It is
not better. Nothing has changed!
Michal
Frank Beythien wrote:
> On Sun, 7 Feb 1999 21:54:46, Michal Jerabek
> <Michal_...@public.uni-hamburg.de> wrote:
>
> > Hi and thanks
> >
> > the lantran.log is as follows
> > --------------------------------------
> > IBM OS/2 LANMSGDD [08/01/96] 5.05 is loaded and operational.
> > IBM - OS/2 Socket/MPTS Common Transport Semantics
>
> Why did you configure socket /netbios support. Do you really need it?
>
> > IBM - OS/2 Socket/MPTS NetBios Service Driver
> > Adapter 0 is using node address 0080C88B49A7. The Token-Ring format is
> > 000113D192E5.
>
> What mpts fixpack do you use? Looks a bit old,. try to install
> WR?G8423
>
Tony Saucedo
I gather this system is a laptop.
Looking at the previous Config.sys I noticed that some sort
of DOS or diagnostic driver is loaded.
What shows up for the NIC Resources under Plug and Play for PCMCIA?
(Base I/O, IRQ, etc)
The card should have status OK and Ready, if not check
the status for the error and post it.
Have tried REMing out those statements?
"DEVICE=C:\path\DSCD.OS2 /IOP:320 /IRQ:11"
"DEVICE=C:\icardsp\DSCD.OS2"
... do you really have a path called "path"?
Leave the "C:\IBMCOM\MACS\ICARDP.OS2" statement.
To change the settings of the NIC you may need to first
boot from a regular DOS (not from within OS/2) and run
the Setup supplied by Trust Netlink.
Hope this helps.
Michal Jerabek
Tony Saucedo wrote:
> I gather this system is a laptop.
>
> Looking at the previous Config.sys I noticed that some sort
> of DOS or diagnostic driver is loaded.
> What shows up for the NIC Resources under Plug and Play for PCMCIA?
> (Base I/O, IRQ, etc)
>
> The card should have status OK and Ready, if not check
> the status for the error and post it.
>
Yes, it is always OK and Ready.
> Have tried REMing out those statements?
> "DEVICE=C:\path\DSCD.OS2 /IOP:320 /IRQ:11"
> "DEVICE=C:\icardsp\DSCD.OS2"
> ... do you really have a path called "path"?
> Leave the "C:\IBMCOM\MACS\ICARDP.OS2" statement.
>
Yes, I tried the rem the devices out. Many times. the DEVICE .. \path\ is of
course incorect. In the Config.sys it was just by chance and only very short time
(I am changing my config every boot these days, I am getting tired). Both lines
refer to the same driver. I used the first (with correct path) when I tried to set
the IO and IRQ for the PCMCIA card. The second was remmed (normally) out. Then I
tried it without the IO and IRQ (=second line, first remmed out) etc. In
documentation I did not find anything about what this DSCD.OS2 driver does: but
after many experiments I think it really can set the parameters for the card.
Without it the IO and IRQ is handled directly by system, system sees the card both
with the driver and without it.
The C:\IBMCOM\MACS\ICARDP.OS2 is a NDIS driver for this particular NIC. I believe
without it the network can only harly start. I tried to reproduce the the same
error on the desktop by removing its NDIS NIC driver, but the error was not the
same.
> To change the settings of the NIC you may need to first
> boot from a regular DOS (not from within OS/2) and run
> the Setup supplied by Trust Netlink.
>
This is something I did not tired. I run the DOS program only in the DOS window in
OS/2.
> Hope this helps.
> --
>
Me too!!!
Michal Jerabek
fo7...@public.uni-hamburg.de
Tony Saucedo
That sounds right the IDCARDP.OS2 should be the NDIS driver.
If you will, REM those statements above once again and then
check with RMVIEW from the command line and see what it shows.
Do the following from an OS/2 window; "RMVIEW /IO"
and then "RMVIEW /IRQ".
Does your laptop have any PNP settings in it's HW setup or
IR ports? If so what are they.
Different cards respond differently to the setting in the
HW Setup.
Post results or email as well.
Also send the ICARDP.NIF file.
What resulted in trying to change the setting after booting
from a Real DOS mode diskette?
If the status showed the proper resources for the NIC
under Plug and Play for PCMCIA, then you probably have a
driver problem. Since the requester is unable to reset that
card.
Did I understand that the system works fine with another card?
Thanks.
Michal Jerabek
Well, when I started the DOS setup program form the PCMCIA ethernet card
it assigned
I/O 300 and IRQ 11 by default. The test program did not find any problem
under DOS
and all tests passed.
Also under Win95 the card was assigned 300/11 and worked perfectly.
Under OS/2, when I don't change anything and do not attempt to override
the default
assignements, the driver C:\IBMCOM\MACS\ICARDP.OS2 claims it is on
300/10. The Plug and Play for
PCMCIA in OS/2 assign to the card 320/10 in this situation.
OK, during the DOS setup for the card I said - let the values be 320/10
and install the
NDIS OS/2 drivers. I deleted the ``old'' driver, reboot, MPTS, Add
another card, etc.
But it did not change anything, the driver claims it is on 300/10 and
the Pnp for PCMCIA assigns happily 320/10.
Then I added the DEVICE=C:\icardp\DSCD.OS2 /IOP:300 /IRQ:11 statement to
the config.sys and to the Protocol.ini
[ICARDPI_nif]
DriverName = ICARDP$
IOADDRESS = 0x300
INTERRUPT = 11
which allows me (as I believe) to override the defaults (only then the
ICARDP.OS2 accept the specified
values, the statement in config.sys do not change it.) The role of the
DSCD.OS2 driver seems to be
to tell the PnP for PCMCIA which values to assign: when I don't load
this driver or I load it
without any parameters OS/2 assigns ALWAYS 320/10. When I add /IOP:300
/IRQ:10 for example
the PnP for PCMCIA accepts these values and shows also 300/10. But the
IRQ:11 is, as it seems,
never accepted by PnP for PCMCIA.
Then, during the boot time, I can see the driver
C:\IBMCOM\MACS\ICARDP.OS2 seems to
accept 300/11. But the PnP for PCMCIA in OS/2 never assigns these
values. In this situation
it assigns always 320/9.
In any situation the status in Pnp for PCMCIA is OK and READY.
The requester still do not start.
The REQUESTER service is starting..........................
The REQUESTER service could not be started.
NET3060: The service did not respond to a control signal and was stopped
with
the DosKillProc function.
There is no PnP HW settings available (via BIOS) for this computer.
I have only one other PCMCIA card - the USR modem. This works excellent.
I have never have to care for any settings with it. Just I plugged it
for the 1st time to the slot and I could go to check my mail.
Well, various problems with hardware / software is nothing new to me. I
am using computers since 1990, everyday and most of the day.
Nevertheless I could only hardly remember when I was so frustrated for
the last time. Usualy, when worst comes to worst, I need some three days
to resolve the problem or to be sure the thing will never work. This
time everything (theoretically) seems to be just OK. The HW is working.
There is even an OS/2 driver! But alas!!
Alreay on Sunday I have sent a problem report to the Trust support but
they did not reply yet. I have sent today one more report, thanks to you
any many other people I have had to bother, very long and with with many
details. If they only send a reply!
=================
ICARDPI.NIF
----------------
[ICARDP]
Type = NDIS
Title = "Trust Netlink Combi PC-Card"
Version = 2.01
Drivername = ICARDP$
Xports = NETBEUI LANDD
[FILE]
Name = ICARDP.OS2
Path = IBMCOM\MACS
; Parameter start
[NETADDRESS]
tag = NETADDRESS
display = "Network adapter address"
type = Hexstring
Strlength = 12
optional = YES
editable = YES
help = "This parameter overrides the network address of the network
adapter card. The value of this parameter is a hexadecimal string of
12 digits, as in 020001020304. The address
must be unique among all other network adapter addresses on the
network."
==============================
RMVIEW /IO
RMVIEW: Physical view
I/O = 0X01CE Len = 2 Flg = EXCLUSIVE VGA
I/O = 0X01F0 Len = 8 Flg = MULTIPLEXED IDE_0 ST506/IDE Controller
I/O = 0X0220 Len = 16 Flg = EXCLUSIVE AUDIO_0 ESS AudioDrive
I/O = 0X0300 Len = 2 Flg = EXCLUSIVE AUDIO_0 ESS AudioDrive
I/O = 0X0320 Len = 32 Flg = EXCLUSIVE Socket_1
I/O = 0X0378 Len = 8 Flg = MULTIPLEXED PARALLEL_0 Parallel Port
Adapter
I/O = 0X03B4 Len = 2 Flg = EXCLUSIVE VGA
I/O = 0X03BA Len = 2 Flg = EXCLUSIVE VGA
I/O = 0X03C0 Len = 10 Flg = EXCLUSIVE VGA
I/O = 0X03CC Len = 1 Flg = EXCLUSIVE VGA
I/O = 0X03CE Len = 2 Flg = EXCLUSIVE VGA
I/O = 0X03D4 Len = 2 Flg = EXCLUSIVE VGA
I/O = 0X03DA Len = 2 Flg = EXCLUSIVE VGA
I/O = 0X03DD Len = 1 Flg = EXCLUSIVE VGA
I/O = 0X03F0 Len = 6 Flg = MULTIPLEXED FLOPPY_0 Floppy Controller
I/O = 0X03F6 Len = 1 Flg = MULTIPLEXED IDE_0 ST506/IDE Controller
I/O = 0X03F7 Len = 1 Flg = MULTIPLEXED FLOPPY_0 Floppy Controller
I/O = 0X03F8 Len = 8 Flg = MULTIPLEXED SERIAL_0 Serial Controller
=======================
RMVIEW /IRQ
----------------------
RMVIEW: Physical view
IRQ Level = 0 PCI Pin = NONE Flg = EXCLUSIVE TIMER_CH_0
IRQ Level = 1 PCI Pin = NONE Flg = EXCLUSIVE KBD_0 Keyboard
Controller
IRQ Level = 2 PCI Pin = NONE Flg = EXCLUSIVE PIC_1
IRQ Level = 4 PCI Pin = NONE Flg = MULTIPLEXED SERIAL_0 Serial
Controller
IRQ Level = 5 PCI Pin = NONE Flg = EXCLUSIVE AUDIO_0 ESS
AudioDrive
IRQ Level = 6 PCI Pin = NONE Flg = MULTIPLEXED FLOPPY_0 Floppy
Controller
IRQ Level = 7 PCI Pin = NONE Flg = EXCLUSIVE AUDIO_0 ESS
AudioDrive
IRQ Level = 8 PCI Pin = NONE Flg = EXCLUSIVE RTC
IRQ Level = 10 PCI Pin = NONE Flg = EXCLUSIVE Socket_1
IRQ Level = 12 PCI Pin = NONE Flg = EXCLUSIVE AUX_0 PS/2
Auxiliary Device Controller
IRQ Level = 14 PCI Pin = NONE Flg = MULTIPLEXED IDE_0 ST506/IDE
Controller
====================================
Frank Beythien
<fo7...@public.uni-hamburg.de> wrote:
> Hi and sorry to bother you again
>
> Well, when I started the DOS setup program form the PCMCIA ethernet card
> it assigned
> I/O 300 and IRQ 11 by default. The test program did not find any problem
> under DOS
> and all tests passed.
[...]
> I have only one other PCMCIA card - the USR modem. This works excellent.
> I have never have to care for any settings with it. Just I plugged it
> for the 1st time to the slot and I could go to check my mail.
What happens if you take the USR modem and and try with only the
ethernet card inserted?
I remember there was at least one card, which had drivers that only
supported itself and prevented any other PCMCIA card from working.
Michal Jerabek
Due the the problem with the ``requester'' I spent last 7 days in the
deepest and hottest hell. Now it is all over. The system is working -
networking in OS/2 environment is beautiful thing!
I want to say LOUDLY - THANK YOU! I appreciate your help. It helped me
terribly to address the problem, exclude my various suspicions and to solve
the enigma.
Well, it was not a problem with the network configuration at all (sorry
``requester''). The devil in the machine was the
BASEDEV=IBM2CMQ1.SYS Compaq PCMCIA Socket driver - this driver I installed
some long time ago according to the information from the ``Compaq
Supplemental Programs for IBM OS/2''. The driver (known under Compaq
Concerto) is a standard part of the OS/2 installation. It performed
beautifully with my PCMCIA modem card, and because it did not have any
problems to recognize the new LAN PCMCIA card (status was always READY and
OK) I did not suspect this driver at all. But alas - it is definitely
incompatible with the NDIS driver supplied with the LAN PC-Card.
After reading all your suggestions and ideas I was finally quite persuaded
that the problem is not in the OS/2 networking setup. Some of you touched
the problem almost directly. It made (finally) to REM the
BASEDEV=IBM2CMQ1.SYS /S0=2 line of my config sys and replace it with
BASEDEV=IBM2SS01.SYS /S0=2. Since the moment (after reboot, of course)
everything works just fine. No more ``requester'' problems!
So if you happen to have the same (or similar card) and Compaq laptop - do
not install the Concerto driver! If you are looking for some relatively
inexpesive PCMCIA ethernet card - the ``Trust Netlink Combi PC-Card''
works well in OS/2 (tested with Warp 4, Compaq Armada 4100) but you shoud
install the (most probably standard) IBM2SS01.SYS driver. With other PCMCIA
Socket drivers you may expect problems.
Michal Jerabek
fo7...@public.uni-hamburg.de
Michal Jerabek wrote:
> Hi,
>
> I know some short time ago there was a discussion about the
> ``LAN Requester'' the would not start.
>
> Well, I have the problem, too, but what helped then is of no use
> for me.
>
> My system is a portable Compaq Armada 4100, PCMCIA Trust Netlink
> Combo PC-Card, Warp 4, there used to be FP 9 installed.
>
> I installed the File and Print Sharing and the driver for my card.
> But when starting the Peer to Peer I got just the message
> ``LAN Requester could not be started'' message.
>
> Withe ``net start'' command from the command line it was
> ``Requester service could not be started. NET3060:
> The service did not respond to a control signal and was
Tony Saucedo
In your setup for the NIC under you mentioned it saw it as
I/O 300 IRQ=11.
It appears you already have Base I/O 300 assigned to your
audio, change one of them in the hardware settings. That could
definitely cause a problem if the software is trying to locate the
device.
By the way, the parameters that are specified for the drivers do
not really override the hardware settings, only the default settings
of the software. So if your hardware is set to 320 and the software
is looking for 300 it will load into 300 not 320 where it really is.
If you want to try something quick, maybe you can diable your audio
through your hardware setup. I believe that conflict is with the
address of the audio and the address of the NIC. At least that is
what I gather from what you noted you got from the configuration
program and the Rmview status
Also you may want change the NIC settings to Base I/O=320 IRQ=10.
Post the hardware settings and rmview after making the changes.
Try that let me know what results.