• Welcome to OS2World OLD-STATIC-BACKUP Forum.
 

News:

This is an old OS2World backup forum for reference only. IT IS READ ONLY!!!

If you need help with OS/2 - eComStation visit http://www.os2world.com/forum

Main Menu

Warp 4 startup issue: TRAP 000E in module SOCKETS

Started by ppgrainbow, 2011.05.15, 20:21:08

Previous topic - Next topic

ppgrainbow

Okay, I have this issue after I restart OS/2 Warp on VPC and it's been going off and on.

After applying updates to the CONFIG.SYS file and upon reboot, I get a TRAP 000e error referencing the offending module SOCKETS. The file is located in C:\MPTN\PROTOCOL\SOCKETS.SYS and has a date stamp of 27 March 2000. Here's a copy of the error message that I'm getting:

QuoteException in module: SOCKETS
TRAP 000e       ERRCD=0000  ERACC=****  ERLIM=********
EAX=00000200  EBX=f9817d08  ECX=ffffffff  EDX=fabdf81c
ESI=00000200  EDI=000d6ffc  EBP=00005b9c  FLG=00012086
CS:EIP=0168:f71ced06  CSACC=c09b  CSLIM=ffffffff
SS:ESP=0030:00005b60  SSACC=1097  SSLIM=00004ebf
DS=0160  DSACC=c0f3  DSLIM=ffffffff  CR0=8001001b
ES=0160  ESACC=c0f3  ESLIM=ffffffff  CR2=0000000b
FS=0000  FSACC=****  FSLIM=********
GS=0000  GSACC=****  GSLIM=********

The system detected an internal processing error at
location ##0168:fff1da1f - 000e:ca1f.
60000, 9084

0886090f
Internal revision 14.104a_W4

The system is stopped.  Record all of the above information and
contact your service representative.

After this message, the system does not continue booting and I have to use the right CTRL+DELETE key to reboot. And on the second (or third reboot) the TRAP 000e error referencing to SOCKETS does not occur until the next modification.

I did a search for TRAP 000e and SOCKETS on Google and a lot of things could be causing the network on startup to be not 100% perfect.

Is this error message caused by a serious bug in the 32-bit TCP/IP Point-to-Point Protocol (PPP) or remnants of 16-bit code in the MPTS?

If that's case, I installed TCP/IP 4.1, then I applied MPTS 5.4 (WR08610) and then MPTS (WR08621). Should I uninstall TCP/IP and MPTS completely and reinstall it (including the WR08621 update) again?

Update: I'm currently making a backup of the first hard disk image incase I screw things up. Reinstalling TCIP/IP 4.1 and MPTS would require a reinstallation of both Netscape and Java 1.1, I recall.

RobertM

I suspect you are not up to date in your updates. It's possible you applied something in the wrong order.

On a machine I have not yet fully updated, I have the following:
sockets.sys  11/02/2001

On a machine I have mostly updated:
sockets.sys  05/21/2004


On a machine I have fully updated:
sockets.sys  09/20/2005

Not sure if updating it will fix your issue, but as the fixpacks that have the updated sockets.sys file also have other updated files, it may be helpful. Actually, I'm not sure what, if anything, is updated in the actual sockets.sys file - but I do know other prerequisite files are updated in the fixpacks it comes in.




Next question. What NIC does the VM virtualize for the session? And what OS/2 driver version is being used?

Best,
Rob


|
|
Kirk's 5 Year Mission Continues at:
Star Trek New Voyages
|
|


ppgrainbow

Quote from: RobertM on 2011.05.15, 20:49:52
I suspect you are not up to date in your updates. It's possible you applied something in the wrong order.

On a machine I have not yet fully updated, I have the following:
sockets.sys  11/02/2001

On a machine I have mostly updated:
sockets.sys  05/21/2004


On a machine I have fully updated:
sockets.sys  09/20/2005

Not sure if updating it will fix your issue, but as the fixpacks that have the updated sockets.sys file also have other updated files, it may be helpful. Actually, I'm not sure what, if anything, is updated in the actual sockets.sys file - but I do know other prerequisite files are updated in the fixpacks it comes in.




Next question. What NIC does the VM virtualize for the session? And what OS/2 driver version is being used?

Best,
Rob


That's what I'm thinking. I'm either still not fully up to date or I somehow applied something wrong that caused problems with SOCKETS.

The updated SOCKETS.SYS can be found in disk 2 of the MPTS 5.5 update disk (WR08621) under the \MPT.1 directory. The older version (dated 6 October 1998) is found in disk 2 of the MPTS 5.4 file and is in a MPROT2.ZIP file under the \MPTS\BIN directory. So...this clearly means that the SOCKETS.SYS file might be outdated.

As for the NIC that the VM is virtualising, it's using a Digital Semicon DC21X4-based ethernet adapter. The version numbers for the TCP/IP protocol drivers are as follows: SOCKETS.SYS: 6.2004, AFOS2.SYS: 6.2000 and AFINET.SYS: 6.2013.

I'm wondering if applying the files from the NEWSTACK.ZIP will fix this or not. :\

RobertM

ok... we've got to get you upgraded to TCP/IP 4.3x

Not much you can do about the DC NIC. I have run some previously without problems - hopefully that's the case for you as well (there were other cards, where other drivers were more suitable to those that came with OS/2 and eCS, such as the BC57 series).

Somewhere I have a link to a post on how to update the entire OS. Perhaps it's author will see this and provide the link. If not, I will dig. In the meantime, check this out:

http://www.os2world.com/forum/index.php/topic,3128.msg19210.html#msg19210


|
|
Kirk's 5 Year Mission Continues at:
Star Trek New Voyages
|
|


ppgrainbow

#4
Quote from: RobertM on 2011.05.15, 21:43:00
ok... we've got to get you upgraded to TCP/IP 4.3x

Not much you can do about the DC NIC. I have run some previously without problems - hopefully that's the case for you as well (there were other cards, where other drivers were more suitable to those that came with OS/2 and eCS, such as the BC57 series).

Somewhere I have a link to a post on how to update the entire OS. Perhaps it's author will see this and provide the link. If not, I will dig. In the meantime, check this out:

http://www.os2world.com/forum/index.php/topic,3128.msg19210.html#msg19210

Update 1: I don't know if it completely got rid of the TRAP 000e error, but now I'm receiving this message before Warp 4 boots up:

ROUTE: command failed: Network is unreachable
Press Enter to continue...

How can I get rid of that non-annoying error message? The network connection in the guest OS works without any problems regardless of this error.

Update 2: Well...I managed to upgrade the TCP/IP stack to version 4.3 and I'm still either getting the "ROUTE: command failed: Network is unreachable" or a TRAP 000e (up to two times) referencing to SOCKETS.

Should I look in the CONFIG.SYS or the TCP/IP configuration to see what could be causing this?

(I had to go offline, because a technician was trying to fix my computer.)

Update 3: I solved the error by using the correct destination IP address within the 192.168.254.* range. Since I'm using DHCP, it's assigned to 192.168.254.5 so I had to add this line to the C:\MPTN\BIN\SETUP.CMD file:

route add -net 192.168.254.5 192.168.254.254 -netmask 255.255.255.0 -hopcount 1

I truly hope that this will also eliminate the TRAP 000E errors referencing to SOCKETS. :)

Update 4: Apparently, that still didn't solve the "ROUTE: Command failed" warning. But what I did to solve this was to extract the IBM Peer diskettes from the OS/2 Warp 4 ISO, install IBM Peer and use a static IP address rather than DHCP. I hoping that there won't be anymore updates to this situation. :)

Now, it's time to hopefully move on to other things.