🚀 go-pugleaf

Używam MS LANMANA i mam to w katalogu c:\lanman

;*****************************************************************;
;**            Microsoft LAN Manager                            **;
;**        Copyright(c) Microsoft Corp., 1993                   **;
;*****************************************************************;

;  LAN Manager initialization file, for workstation configuration.

[networks]
; This info is read by redir at device init time.  It is available to
; apps via NetBiosEnum.
  net1 = tcpnb$,0


[workstation]
  computername = SXWorkstation
  domain = energymanagment
  othdomains =

  wrkservices = messenger,netpopup
  wrknets = net1

[messenger]

[netshell]
  refresh = 15
  remote =
  username = administrator

[version]
  lan_manager = 2.2c.0

[tcpip_node]
  Hub =
  HubIPAddr =
  Domains =
  DoUAS = yes
  DoView = yes
  DoLogon = yes
  DoWho = no
  DoSend = no
  DoRepl = yes
  DoUser1 = no
  DoUser2 = no
  DoUser3 = no
  UserMailSlot1 =
  UserMailSlot2 =
  UserMailSlot3 =

[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 LanMan root

  workstation = services\wksta.exe
  tcpip_node = services\node.exe
  messenger = services\msrvinit.exe
  netpopup = services\netpopup.exe




i drugi plik:

[PROTMAN]
  DRIVERNAME = PROTMAN$

[TCPIP_XIF]

  DRIVERNAME      = TCPIP$
  IPADDRESS0 = 10 158 89 145
  SUBNETMASK0 = 255 255 255 0
  DEFAULTGATEWAY0 = 10 158 89 140
    ; the following two parameters added after documentation was completed
  TCPSEGMENTSIZE  = 1450
  TCPWINDOWSIZE   = 4350
  NBSESSIONS = 40
  NUMNCBS         = 85
  BINDINGS = "ELNK3_NIF"

[ELNK3_NIF]
;
;   3c5X9 3Com EtherLink III adapter
;
    DRIVERNAME = ELNK3$
;       2nd driver name = ELNK32$
;   IOADDRESS = 0x300
;       adapter base address (optional, no default)
;       This parameter is only used to specify a single adapter in a multi-
;       adapter configuration in an ISA computer.
;       Use 0x200 - 0x3E0 in steps of 0x10
    MAXTRANSMITS = 40
;       number of transmit queue elements (optional, default = 6)
;       Min = 2, Max = 50
;       Use the default for DOS and normal OS/2 clients
;       Set MAXTRANSMITS = 40 for OS/2 servers
;   NETADDRESS = "00608C123456"
;       network address (optional, default = network address EEPROM value)
;       the network address is 12 hex digits enclosed in quotes
;   SLOT = 5
;       EISA or MCA slot number (optional, no default)
;       This parameter is only used to specify a single adapter in a multi-
;       adapter configuration in an EISA or MCA computer.
;       Use 0 - 15




Z góry dzięki za pomoc

BR
PAweł










Użytkownik "Leszek Kubrak" <lesiok@infokub.com.pl> napisał w wiadomości 
news:mailman.295.1132664569.509.os2@man.lodz.pl...
> PawelR wrote:
>> Witam Wszystkich.
>>
>> Na początku chciałbym nadmienić, że jestem całkowicie początkujący 
>> użytkownikiem OS/2
>>
>> Muszę reaktywować stację roboczą z w/w wersją OS/2, która będzie 
>> korzystała (miała dostęp) do folderów udostępnionych na serwerze W2k, a 
>> ponad to na serwerze tym pracuje MSSQL 7 z którego będą pobierane dane.
>>
>> Do tej pory zainstalowałem OS/2 Warp 3 wersja UK
>> FixPack 32, 38 i 40
>> LanManagera w wersji 2.2a podkładając sterownik do karty sieciowej (3COM 
>> 509B jest to  3Com OS/2 EtherLink III Network Driver v3.0)
>> i do tego momentu było ok.
>> Teraz przy starcie systemu dostaję informację:
>> SYS1719: The file c:\Lanman\netprog\netwksta.sys specified in the IFS 
>> statement on line 89 of the CONFIG.SYS fie does not contain a valid 
>> device driver or file system driver. Line 89 is ignored.
>> Press Enter to continue ...
>>
>> I sieć oczywiście nie działa.
>> Jak poradzić sobie z tym błędem?
>>
>> Pozdrawiam.
>> Paweł
>>
>
> Pokaż pliki C:\IBMLAN\IBMLAN.INI oraz C:\IBMCOM\PROTOCOL.INI
>
> -- 
> ================================
> Leszek KUBRAK