Quick links
FAQ
Register
Login
Voici les deux ordis que j'ai utilisé :
1 - HP Vectra (486 DX33)
SB pro 2
3Com Etherlink III (3c509)
MS-DOS 6.22
2 - Pentium 3 450MHz
- Voodoo 2 SLI
- Riva TNT2 m64
- Abit BH6
- 3Com etherlink XL PCI (3c905B)
- Yamaha YMF744
- MS-DOS 7.1/Windows 98
Sur le 1er ordi, je lance d'abord LSL.com puis 3c5x9 et enfin ixpodi. Tout se passe bien
Voici le fichier NET.CFG que j'utilise (qui est une version altérée de celui qui est fourni sur les disques d'installation de la carte)
Code: Select all ; *************************************************************************
; This sample NET.CFG file is meant to supply some rudimentary understanding
; of parameters in NET.CFG and how they affect network operations.
; For a full description and explanation of the parameters, see the
; manual for the ODI shell for DOS, which ships with the NetWare package
; or is available from Novell part # 100-000871-001.
;
; Please pay attention to column spacing for the lines. The section header
; line MUST start in column 0 with subsequent lines in that section being
; indented. Comments are designated by semi-colons (;). The NET.CFG is not
; caps-sensitive.
;
; *************************************************************************
;
LINK DRIVER 3C5X9
;
; The following two parameters are required when using two or more EtherLink
; III adapters in a single machine. This parameter specifies which specific
; EtherLink III adapter the driver is to attach itself to.
; PORT NNN, where NNN is the hex base address of the 3C509 ISA adapter
; SLOT NN, where NN is the slot number containing the 3C529, 3C579, or
; 3C509 configured as an EISA adatper.
;
; PORT 200
; SLOT 3
;
; The next few lines specify the frame type. 3C5X9.COM is a 4.0 DOS ODI
; driver. The default frame type is 802.2. To connect to a 3.11 server
; the frame type needs to be changed to 802.3. The following two lines
; perform that change.
;
; FRAME ETHERNET_802.3
; PROTOCOL IPX 0 ETHERNET_802.3 (binds IPX protocol to frame)
;
;
; This is the driver default
;
FRAME ETHERNET_802.2
PROTOCOL IPX E0 ETHERNET_802.2
;
;
;
; %VER NET.CFG - sample Netware DOS ODI configuration file V4.1a
|
Voici le NET.CFG
Code: Select all ; *************************************************************************
; This sample NET.CFG file is meant to supply some rudimentary understanding
; of parameters in NET.CFG and how they affect network operations.
; For a full description and explanation of the parameters, see the
; manual for the ODI shell for DOS, which ships with the NetWare package
; or is available from Novell part # 100-000871-001.
;
; Please pay attention to column spacing for the lines. The section header
; line MUST start in column 0 with subsequent lines in that section being
; indented. Comments are designated by semi-colons (;). The NET.CFG is not
; caps-sensitive.
;
; *************************************************************************
;
LINK DRIVER 3C90X
PORT E400
IRQ 10
;
; When using two or more adapters in a single machine, it is necessary to
; specifiy which adapter should be used. The following two parameters are
; used for this purpose:
;
; SLOT NN, where NN is the specific PCI BIOS identification number of the
; 3C90X PCI adapter.
;
; BUS NN, Where NN is the Bus number.
;
; The next few lines specify the frame type. 3C90X.COM is a 4.10 DOS ODI
; driver. The default frame type is 802.2. To connect to a 3.11 server
; the frame type needs to be changed to 802.3. The following two lines
; perform that change.
;
; FRAME ETHERNET_802.3
; PROTOCOL IPX 0 ETHERNET_802.3 (binds IPX protocol to frame)
;
;
; This is the driver default
;
FRAME ETHERNET_802.2
PROTOCOL IPX E0 ETHERNET_802.2
;
;
;
;(%VER NET.CFG - sample Netware DOS ODI configuration file V1.0) |
Quand je lance doom sur les deux ordis avec ipx, l'ordi n°1 continue sans soucis, mais l'ordi n°2 plante avec un message d'erreur "transfert stack overflow" et ça me ramène au prompt MS-DOS ... qui plante après quelques secondes
Je suis repassé sous Windows 98SE sur l'ordi n°2 et j'ai refait la procédure (en utilisant donc l'ipx de windows 98) et là ça fonctionne sans soucis ! Les deux versions du jeu proviennent de mon raspberry pi, donc il n'y a pas de soucis de config du jeu, le jeu en solo fonctionne sur les deux machines.
Qu'est-ce qui peut clocher dans la config du réseau sur l'ordi 2 sous MS-DOS ?
Sur internet, je suis tombé sur un fichier d'aide au sujet de doom qui est intérressant ...
... mais au final il ne m'avance pas à grand chose ...
Quote: An incorrectly installed packet driver often crashes when it *receives* a packet, rather than when it transmits one. Your packet driver might look like it's installed ok, and you might be sitting there "Looking for a node......" for a while. When another node replies to this (incorrectly installed) packet driver, it causes it to crash. Be careful and mindful of what traffic there is or could be on the network at all times! This can be put to your advantage, though. If you have a node that is *guaranteed* to be working fine and one that locks up when you install IPXPD, you can debug it thus: Set the good node "Looking for a node.....", and then install the packet driver on the suspect node. If the suspect node then crashes/hangs at the same time that that good node prints another ".", then the packet driver you just installed wasn't installed correctly. Reboot the faulty node and try different settings on the packet driver and/or card until the node no longer crashes in this manner.
