15.10.2011 12:35
[#1]
Problem z Mosnetem :(
Witam. Mam problem z konfiguracją MOsneta na 1.45
Dostaje takie błędy przy odpaleniu
Oraz
Mój config to klasyk 160 mb ramu karta sieciowa 3com. Działa bezstresowo na os3.x
Problem polega na tym, że te miejsca, które wskazuje błąd są puste. Tzn mosnet wskazuje na linijki z tekstem i pusty znak.
Benedykt Dziubałtowski
Dostaje takie błędy przy odpaleniu
fatal eroror in netDB file interfaces at line 77, col 90 memory exhausted mosnet will quait
Oraz
fatal eroror in netdb file netdb at line 25, col 25 memory to samo co wyżej
Mój config to klasyk 160 mb ramu karta sieciowa 3com. Działa bezstresowo na os3.x
Problem polega na tym, że te miejsca, które wskazuje błąd są puste. Tzn mosnet wskazuje na linijki z tekstem i pusty znak.
Benedykt Dziubałtowski
15.10.2011 16:09
[#4]
Re: Problem z Mosnetem :(
@AmiChris, post #2
Post Pisany z Ibrowse pod os3.x:)
@Pampers. Zerobiłem tak jak pisałeś.
A oto jak wyglądają moje pliczki
;
; netdb -- the network database file for AROSTCP
;
; Copyright Š 1993 AmiTCP/IP Group,
; Helsinki University of Technology, Finland.
; All rights reserved.
; Copyright Š 2005 - 2006 Pavel Fedin
;
; This is a main file controlling loading of other files containing network
; information (hosts, services, access list, etc). Do not change it unless you
; really know what you are doing.
;
; interfaces
;
WITH interfaces PREFIX=i;
;
; hosts
;
WITH hosts PREFIX=H
;
; Networks
;
WITH networks PREFIX=N
;
; Protocols
;
WITH protocols PREFIX=P
;
; Network services, Internet style
;
WITH services PREFIX=S
;
; Static routes
;
WITH static-routes PREFIX=R
;
; Nameservers and local domains
;
WITH resolv.conf
;
; Access control list for incoming connections.
;
WITH inet.access PREFIX=ACCESS
;
; Startup/shutdown scripts, uncomment to enable this sample.
;
;RC rc.d/rc.sample
;;;; EOF
# Network Interface Configuration for MOSNet
# ===========================================
#
# MOSNet uses the network interface to communicate with SANA-II devices,
# just like DOS uses handlers or filesystems to communicate with exec
# devices. A network interface is created and configured with `ifconfig'
# utility. AROSTCP can create several network interfaces for each SANA-II
# device; this is seldom useful, except when network has many different
# framings for IP.
#
# The new-style network interface name consists of interface device name
# concatenated with interface unit number, ie. if the interface name is
# "slip0", then the interface device name is "slip" and the interface unit
# is 0. The network interface name should not contain digits ('0' ... '9').
#
# There is a built-in interface "lo0" in MOSNet, other interfaces should
# be defined here.
#
# This configuration file is read with template:
# NAME/A, DEV=DEVICE/A/K, UNIT/N/K, IPTYPE/N/K, ARPTYPE=IPARPTYPE/N/K,
# IPREQ=IPREQUESTS/N/K, ARPREQ=ARPREQUESTS/N/K, WRITEREQ=WRITEREQUESTS/N/K,
# NOTRACKING/S, NOARP/S, ARPHDR/N/K, P2P=POINT2POINT/S, NOSIMPLEX/S,
# LOOPBACK/S
#
# Lines can be continued if their last character is '+'
# '#' and ';' are comment characters - rest of the line is ignored
#
# Parameters are interpreted as follows:
# NAME I
# new-style AmiTCP/IP network interface name
# DEV=DEVICE/A/K
# Sana-II (old-style AmiTCP/IP) device name
# UNIT/N/K
# Sana-II (old-style AmiTCP/IP) device unit number. Default value is 0.
# If no Sana-II unit number is given, the interface unit number is used
# IP/K
# IP address of the interface. If you specify "DHCP" as the value then
# DHCP protocol will be used to set up the interface
# NETMASK/K
# Netmask of the interface
# UP/S
# Put the interface online automatically
# IPTYPE/N/K (*
# Packet type (framing) for Internet Protocol (IP)
# IPREQ=IPREQUESTS/N/K
# IO requests allocated for receiving IP packets.
# ARPTYPE=IPARPTYPE/N/K (*
# Packet type (framing) for Address Resolution Protocol (ARP)
# ARPREQ=ARPREQUESTS/N/K
# IO requests allocated for receiving ARP packets
# WRITEREQ=WRITEREQUESTS/N/K
# IO requests allocated for transmitting packets
# NOTRACKING/S
# Disable the packet type tracking on SANA-II devices. This feature is
# needed to circumvent a bug in a2060.device V37.2
# NOARP/S
# Disable the ARP for this interface
# ARPHDR/N/K (*
# The ARP header version. This is 1 for Ethernet, 7 for Arcnet by default
# P2P=POINT2POINT/S
# Use the device as point-to-point device
# NOSIMPLEX/S
# Disable the copying of broadcast packets. Set this parameter if we hear
# our own broadcasts
# LOOPBACK/S
# Set this parameter if it is loopback
#
# *) Don't set these parameters if you don't know what you are doing.
# ezTCP recognizes Ethernet, Arcnet (RFC 1051 framing), SLIP and PPP
# drivers automatically. See file for the
# packet types used for these drivers.
#
# Here are a few examples:
#
# Pegasos built-in and dynamic
#
eth0 DEV=DEVS:networks/3com UNIT=0 IP=DHCP UP
#
# Realtek8139 PCI card, dynamic configuration
#
#eth1 DEV=DEVS:networks/rtl_8139pci.device UNIT=0 IP=DHCP UP
# EOF
Benedykt Dziubałtowski
@Pampers. Zerobiłem tak jak pisałeś.
A oto jak wyglądają moje pliczki
;
; netdb -- the network database file for AROSTCP
;
; Copyright Š 1993 AmiTCP/IP Group,
; Helsinki University of Technology, Finland.
; All rights reserved.
; Copyright Š 2005 - 2006 Pavel Fedin
;
; This is a main file controlling loading of other files containing network
; information (hosts, services, access list, etc). Do not change it unless you
; really know what you are doing.
;
; interfaces
;
WITH interfaces PREFIX=i;
;
; hosts
;
WITH hosts PREFIX=H
;
; Networks
;
WITH networks PREFIX=N
;
; Protocols
;
WITH protocols PREFIX=P
;
; Network services, Internet style
;
WITH services PREFIX=S
;
; Static routes
;
WITH static-routes PREFIX=R
;
; Nameservers and local domains
;
WITH resolv.conf
;
; Access control list for incoming connections.
;
WITH inet.access PREFIX=ACCESS
;
; Startup/shutdown scripts, uncomment to enable this sample.
;
;RC rc.d/rc.sample
;;;; EOF
# Network Interface Configuration for MOSNet
# ===========================================
#
# MOSNet uses the network interface to communicate with SANA-II devices,
# just like DOS uses handlers or filesystems to communicate with exec
# devices. A network interface is created and configured with `ifconfig'
# utility. AROSTCP can create several network interfaces for each SANA-II
# device; this is seldom useful, except when network has many different
# framings for IP.
#
# The new-style network interface name consists of interface device name
# concatenated with interface unit number, ie. if the interface name is
# "slip0", then the interface device name is "slip" and the interface unit
# is 0. The network interface name should not contain digits ('0' ... '9').
#
# There is a built-in interface "lo0" in MOSNet, other interfaces should
# be defined here.
#
# This configuration file is read with template:
# NAME/A, DEV=DEVICE/A/K, UNIT/N/K, IPTYPE/N/K, ARPTYPE=IPARPTYPE/N/K,
# IPREQ=IPREQUESTS/N/K, ARPREQ=ARPREQUESTS/N/K, WRITEREQ=WRITEREQUESTS/N/K,
# NOTRACKING/S, NOARP/S, ARPHDR/N/K, P2P=POINT2POINT/S, NOSIMPLEX/S,
# LOOPBACK/S
#
# Lines can be continued if their last character is '+'
# '#' and ';' are comment characters - rest of the line is ignored
#
# Parameters are interpreted as follows:
# NAME I
# new-style AmiTCP/IP network interface name
# DEV=DEVICE/A/K
# Sana-II (old-style AmiTCP/IP) device name
# UNIT/N/K
# Sana-II (old-style AmiTCP/IP) device unit number. Default value is 0.
# If no Sana-II unit number is given, the interface unit number is used
# IP/K
# IP address of the interface. If you specify "DHCP" as the value then
# DHCP protocol will be used to set up the interface
# NETMASK/K
# Netmask of the interface
# UP/S
# Put the interface online automatically
# IPTYPE/N/K (*
# Packet type (framing) for Internet Protocol (IP)
# IPREQ=IPREQUESTS/N/K
# IO requests allocated for receiving IP packets.
# ARPTYPE=IPARPTYPE/N/K (*
# Packet type (framing) for Address Resolution Protocol (ARP)
# ARPREQ=ARPREQUESTS/N/K
# IO requests allocated for receiving ARP packets
# WRITEREQ=WRITEREQUESTS/N/K
# IO requests allocated for transmitting packets
# NOTRACKING/S
# Disable the packet type tracking on SANA-II devices. This feature is
# needed to circumvent a bug in a2060.device V37.2
# NOARP/S
# Disable the ARP for this interface
# ARPHDR/N/K (*
# The ARP header version. This is 1 for Ethernet, 7 for Arcnet by default
# P2P=POINT2POINT/S
# Use the device as point-to-point device
# NOSIMPLEX/S
# Disable the copying of broadcast packets. Set this parameter if we hear
# our own broadcasts
# LOOPBACK/S
# Set this parameter if it is loopback
#
# *) Don't set these parameters if you don't know what you are doing.
# ezTCP recognizes Ethernet, Arcnet (RFC 1051 framing), SLIP and PPP
# drivers automatically. See file
# packet types used for these drivers.
#
# Here are a few examples:
#
# Pegasos built-in and dynamic
#
eth0 DEV=DEVS:networks/3com UNIT=0 IP=DHCP UP
#
# Realtek8139 PCI card, dynamic configuration
#
#eth1 DEV=DEVS:networks/rtl_8139pci.device UNIT=0 IP=DHCP UP
# EOF
Benedykt Dziubałtowski
16.10.2011 12:58
[#18]
Re: Problem z Mosnetem :(
@] SKOLMAN_MWS ˇ agrEssOr [, post #17
ja p******e........Przecież to było takie oczywiste, ze trzeba przegrać ten plik do libs............. Dzięki skolman za pomoc.
Benedykt Dziubałtowski
Łedit:
Trza się zainteresować jakąś przeglądarką www. Co radzicie?
Ostatnia aktualizacja: 16.10.2011 13:01:13 przez Benedykt Dziubałtowski
17.10.2011 01:44
[#25]
Re: Problem z Mosnetem :(
@wali7, post #24
Tak. Mam to ustawione. Zbaraniałem trochę bo już nie wiem co jest grane. Czcionki mam iso. Kaymap iso-pl. ładnie mam w owb i sputniku komunikaty po polsku ale jak próbuję pisać ą to mam charakterystyczny +- jeden pod drugim. W samym systemie natomiast nie wyświetlają mi się polskie fonty.
Benedykt Dziubałtowski
Benedykt Dziubałtowski
17.10.2011 22:39
[#28]
Re: Problem z Mosnetem :(
@Benedykt Dziubałtowski, post #27
A ustawiłeś (w systemie) polskie czcionki? Bo nie wszystkie czcionki mają w zestawie ogonki.
Tu znajdziesz opis polonizacji MOSa2 - w 1.4.5 część porad powinna być aktualna: http://morphos.pl/odpowiedzi.php?item=322
Tu znajdziesz opis polonizacji MOSa2 - w 1.4.5 część porad powinna być aktualna: http://morphos.pl/odpowiedzi.php?item=322
18.10.2011 08:04
[#30]
Re: Problem z Mosnetem :(
@grxmrx, post #29
No właśnie, przeglądnąłem te wątki, przypomniałem sobie to i owo: problemem może być także czcionka bezogonkowa w klasie MUI odpowiedzialnej za pola tekstowe (także w OWB). Objaw był dosyć ciekawy - bo dziwne znaczki pojawiają się w momencie wklepywania tekstu w pole na stronie, ale po jego wysłaniu na stronie pojawiają się już prawidłowe ogonki. Nie siedzę teraz przed MOSem, może ktoś pamięta nazwę klasy, to by sobie Benedykt sprawdził