SCOUG-HELP Mailing List Archives
Return to [ 01 | 
January | 
2004 ]
<< Previous Message << 
 >> Next Message >>
 
 
 
Content Type:   text/plain 
=====================================================  
If you are responding to someone asking for help who  
may not be a member of this list, be sure to use the  
REPLY TO ALL feature of your email program.  
=====================================================  
 
Steven Levine wrote:  
> In <3FF4E196.5090700@san.rr.com>, on 01/01/04   
>    at 07:11 PM, Tom Brown  said:  
>   
>>With this combination, I get a trap 0008 with no module specified. Would   
>>the trap info be of any use? I understand that a trap 0008 is a double   
>>fault, a trap in the trap handler. Is this right?  
>   
> Yes, this is what it means, but it it's not an atypical traps for a bad  
> driver.  
>   
>> ROM IRQ routing table found at F000h:DF10h  
>> Table Version 1.0 - OK  
>> Table size 0 bytes - Invalid Size!  
>> IRQ's dedicated to PCI : None  
>> The ROM PCI IRQ routing table appears to be faulty!!  
>   
>>Does this have any bearing on OS/2?   
>   
> I really don't know.  
>   
>>I think I found Veit's program: SPCIIRQ dated 3/21/02. Sparse   
>>documentation. It looks like I have to install the SPCIIRQ driver with   
>>parms that force the parameters for a particular card.  
>   
>>I will give it a try.  
>   
> I recommend you e-mail Veit.  He's an eCS developer and I'm sure he'll be  
> willing to help.  He's doing to need the ScanPCI output along with the  
> trap screen.  You can use:  
>   
>   <http://home.earthlink.net/~steve53/os2diags/DumpTrapScreen.zip>  
>   
> to grab the info off a diskette if you don't have a trapdump partition.  
>   
> One other thing you can do is swap the driver load order in config.sys.  
>   
> Also, are you sure you are using the most recent version of the e100b  
> driver, if I'm guessing the right name?  
>   
> You should post the trap screen.  I never know if the info will be useful  
> until I see it.  
[G:\tools]dumptrapscreen a:\dumpdata.001  
Reading a:\dumpdata.001 01-01-04  20:47:54  
##0168:fff1ea4f - 000e:ca4f    , 06860680  
9084  
 
Exception in module:  
TRAP 0008       ERRCD=0000  ERACC=****  ERLIM=********  
EAX=f26eb287  EBX=000044ce  ECX=0000000d  EDX=ffec3d70  
ESI=feea0000  EDI=feea000d  EBP=00004be0  FLG=00253013  
CS:EIP=0168:f26eb287  CSACC=c09b  CSLIM=ffffffff  
SS:ESP=0160:00004057  SSACC=c093  SSLIM=ffffffff  
DS=0160  DSACC=c093  DSLIM=ffffffff  CR0=8001001b  
ES=0160  ESACC=c093  ESLIM=ffffffff  CR2=00004053  
FS=0130  FSACC=00f3  FSLIM=000057f5  
GS=0000  GSACC=****  GSLIM=********  
 
Internal revision 14.096e_W4  
 
The NIC driver that eCS 1.1 installed is indeed E100B.OS2. On eCS 1.03,   
however, I was using IBMFE.OS2 which is what came with the card. The   
E100B driver obviously works, since I am able to connect to the   
internet, but it might not coexist well with uniaud. Apparently I don't   
have the latest version installed since Chuck's NICPAK page has a later   
version. The IBMFE.OS2 driver does not seem to be on the NICPAK page.  
 
More to come...  
 
--   
Tom Brown  
thombrown at san dot rr dot com  
Member SCOUG, V.O.I.C.E. & SDAA  
running eComStation GA + FP 3  
  eCS system uptime is 0 days 00:42 hours  
 
=====================================================  
 
To unsubscribe from this list, send an email message  
to "steward@scoug.com". In the body of the message,  
put the command "unsubscribe scoug-help".  
 
For problems, contact the list owner at  
"rollin@scoug.com".  
 
=====================================================  
 
  
<< Previous Message << 
 >> Next Message >>
Return to [ 01 | 
January | 
2004 ] 
  
  
The Southern California OS/2 User Group
 P.O. Box 26904
 Santa Ana, CA  92799-6904, USA
Copyright 2001 the Southern California OS/2 User Group.  ALL RIGHTS 
RESERVED. 
 
SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group.
OS/2, Workplace Shell, and IBM are registered trademarks of International 
Business Machines Corporation.
All other trademarks remain the property of their respective owners.
 
  |