🚀 go-pugleaf

> Trap 000e info.

I get the same trap e when I put in an extra 8 megs of RAM (16 to 24
upgrade).  Take it out and the traps go away.  Same speed and style
of memory.  If anyone gets any more information on this I'd love to
hear about it.

In <3nrubu$rh9@hpspden.vid.hp.com>, schmitz@vid.hp.com (John Schmitz) writes:
>> Trap 000e info.
>
>I get the same trap e when I put in an extra 8 megs of RAM (16 to 24
>upgrade).  Take it out and the traps go away.  Same speed and style
>of memory.  If anyone gets any more information on this I'd love to
>hear about it.

Try making your wait states on your memory and cache longer.  make the SRAM option
longer as well (in some CMOSes)


------------------------------------------------------------------------------
Frikkie Strecker    ATM Network Manager   fstreck@marge.mikom.csir.co.za
    Mikomtek a division of CSIR
    Voice   +27 (12) 841-3774   Fax   +27 (12) 841-4065
OS/2 Warp is the best !!!
------------------------------------------------------------------------------

> >> Trap 000e info.
> >
> >I get the same trap e when I put in an extra 8 megs of RAM (16 to 24
> >upgrade).  Take it out and the traps go away.  Same speed and style
> >of memory.  If anyone gets any more information on this I'd love to
> >hear about it.
> 
> Try making your wait states on your memory and cache longer.  make the SRAM
> option longer as well (in some CMOSes)

This doesn't make sense to me.  In my case, both the 8 meg simm and
the 16 meg simm work fine separately.  When used together, I get
trap 000e.  This seems to point to a problem with the memory above
16 meg's for some reason.  Caching, perhaps?  But it doesn't seem to
be speed related.

In <3nrubu$rh9@hpspden.vid.hp.com> schmitz@vid.hp.com (John Schmitz) writes:

>> Trap 000e info.

>I get the same trap e when I put in an extra 8 megs of RAM (16 to 24
>upgrade).  Take it out and the traps go away.  Same speed and style
>of memory.  If anyone gets any more information on this I'd love to
>hear about it.

Did the same got the same results, changed my motherboard...nope...
changed my 512K cache to 256K... No problems since

schmitz@vid.hp.com (John Schmitz) wrote: 
>> Trap 000e info. 
> 
>I get the same trap e when I put in an extra 8 megs of RAM (16 to 24 
>upgrade).  Take it out and the traps go away.  Same speed and style 
>of memory.  If anyone gets any more information on this I'd love to 
>hear about it. 
 
Well, this seems to be interesting, we'll have to see what type of systems they are first, is   
it EISA, ISA, PCI or all the above and VLB. What CPU, who makes the motherboard (if no name of   
little name), how the system configured. SCSI, or ..ATAPI, how much cache (now be honest to not   
to cheat the system) what type of tag RAM (32x8, 8x8, to 64x8) 128K, 256K, or 512K or 1MB. What   
type of RAM you put in, 72 pin or 30pin. The speed of the RAM. Who makes the RAM, some RAM   
cannot be mixed. Are they 3 chips RAM or 8 chip RAM or 9 chip, or multiple (more than or less   
but not equal to what I have mentioned.) Are they tin or plated copper conteacts. **Beware, did   
you zap it. Static can kill it within (cannot see the spark mind you) nanoseconds. Did you put   
the SIMM in properly. Did you follow the instruct on which banks to fill. Most motherboards do   
not support 2MB strips. If you have a newer system with only 4 to 6 72 pins slots. Watch out   
the slots that some need 2MB, or 4MB or 16MB first on the BANK 0. Having said that if you have   
an VLB+ISA motherboard, your chances are Zero to go over 16MB. Because most makers short   
cricuit that over 16Mb although they said it will take trillion Bytes. Due to the 16bit MEM   
control over 32 bit paths. If 486 or P's most system can not take more than 256 K cacke unless   
you have the most recent MBRDs. A lot of makes can adjust BIOS to access them. Of course   
**which chip set of the motherboard, OPTI,UNIQ, UMC, INTEL, ASUS, or what. And then the video   
will kill even if the above is all okay now. If you have a vid card has two MB vid RAM on it,   
then the 16MB may come into play again. Most cards like this require addtional (mostly 4   
aliased IO address, and then it need the top of the first 16MB copped off..we call RAM hole   
some the aperture can be used.) See if you BIOS allow to disable such RAM addr. 
 
Well most SCIS device on the 16bit does not or may conflict over the 16bit, 32bit and 16MB   
boundary. More over, if cache RAM is added, such as 256K to 512K, you will have to change   
the**tag RAM** to do its control over the extra 256K. (That is to say you 'll need 9 of those   
cips and not just 4.) Static can kill SRAM's. Most systems I have tested cannot (from 486   
50-100's) and P60,66,90s cannot do 512K even a month of so ago. 
 
I may have left out something. since so much to look for...Hope you can sorts this out slowly.   
Once again, watch out for static, otherwise, you will keep loosing. Also, Cheap RAM is plenty   
out there (but the good ones are hard to find, cheap and good) or you'll get burn. Take out   
your old RAM (such as 16MB and put the 8MB to find out if you have the problem to see the 8MB   
is good or bad first. Not just power it up. Load every in you mind and system and let it run   
for minimum 4 hours and power up and down in 15 minute interval for al least 10 times. Now   
you'll know what is called burnt in. Furthermore, no one seems to care for that anymore,   
although there is ISO9000-2, who cares, when you cook your own system.Well, .. can't say much.   
And another thing is refund is almost impossible, cause, your vendor may say you phaser'ed the   
RAMs. And lastly, how good is your power supply. I have seen a VERY BIG NAME company with 4   
letters did a system loaded, loaded with a 145W power supply, I test the 12 and 5 volt rail,   
god, the volt was 11.02 and 4.86 and the drive is starting up. Forget about your sound, watch   
for the brown out on your drive in a long run. 
 
so much, hope you all can track this. Moreover, are you using the new CSD (IBM used to call it   
solely and MS do too, so I'll use what IBM calls them now SP's last one I saw was kicker and   
_05. It did quite a bit of stuff. It is about 5-6Meg. and don't forget the LOADer file. 
 
Well, I started with OS2 when it was not even announce yet back in the 86-7 times. 
 
GOOD LUCK again. 
 
-oo- 
 mf

Well, this seems to be interesting, we'll have to see what type of systems they are first, is 
it EISA, ISA, PCI or all the above and VLB. What CPU, who makes the motherboard (if no name of 
little name), how the system configured. SCSI, or ..ATAPI, how much cache (now be honest to not 
to cheat the system) what type of tag RAM (32x8, 8x8, to 64x8) 128K, 256K, or 512K or 1MB. What 
type of RAM you put in, 72 pin or 30pin. The speed of the RAM. Who makes the RAM, some RAM 
cannot be mixed. Are they 3 chips RAM or 8 chip RAM or 9 chip, or multiple (more than or less 
but not equal to what I have mentioned.) Are they tin or plated copper conteacts. **Beware, did 
you zap it. Static can kill it within (cannot see the spark mind you) nanoseconds. Did you put 
the SIMM in properly. Did you follow the instruct on which banks to fill. Most motherboards do 
not support 2MB strips. If you have a newer system with only 4 to 6 72 pins slots. Watch out 
the slots that some need 2MB, or 4MB or 16MB first on the BANK 0. Having said that if you have 
an VLB+ISA motherboard, your chances are Zero to go over 16MB. Because most makers short 
cricuit that over 16Mb although they said it will take trillion Bytes. Due to the 16bit MEM 
control over 32 bit paths. If 486 or P's most system can not take more than 256 K cacke unless 
you have the most recent MBRDs. A lot of makes can adjust BIOS to access them. Of course 
**which chip set of the motherboard, OPTI,UNIQ, UMC, INTEL, ASUS, or what. And then the video 
will kill even if the above is all okay now. If you have a vid card has two MB vid RAM on it, 
then the 16MB may come into play again. Most cards like this require addtional (mostly 4 
aliased IO address, and then it need the top of the first 16MB copped off..we call RAM hole 
some the aperture can be used.) See if you BIOS allow to disable such RAM addr. 
  
Well most SCIS device on the 16bit does not or may conflict over the 16bit, 32bit and 16MB 
boundary. More over, if cache RAM is added, such as 256K to 512K, you will have to change 
the**tag RAM** to do its control over the extra 256K. (That is to say you 'll need 9 of those 
cips and not just 4.) Static can kill SRAM's. Most systems I have tested cannot (from 486 
50-100's) and P60,66,90s cannot do 512K even a month of so ago. 
  
I may have left out something. since so much to look for...Hope you can sorts this out slowly. 
Once again, watch out for static, otherwise, you will keep loosing. Also, Cheap RAM is plenty 
out there (but the good ones are hard to find, cheap and good) or you'll get burn. Take out 
your old RAM (such as 16MB and put the 8MB to find out if you have the problem to see the 8MB 
is good or bad first. Not just power it up. Load every in you mind and system and let it run 
for minimum 4 hours and power up and down in 15 minute interval for al least 10 times. Now 
you'll know what is called burnt in. Furthermore, no one seems to care for that anymore, 
although there is ISO9000-2, who cares, when you cook your own system.Well, .. can't say much. 
And another thing is refund is almost impossible, cause, your vendor may say you phaser'ed the 
RAMs. And lastly, how good is your power supply. I have seen a VERY BIG NAME company with 4 
letters did a system loaded, loaded with a 145W power supply, I test the 12 and 5 volt rail, 
god, the volt was 11.02 and 4.86 and the drive is starting up. Forget about your sound, watch 
for the brown out on your drive in a long run. 
  
so much, hope you all can track this. Moreover, are you using the new CSD (IBM used to call it 
solely and MS do too, so I'll use what IBM calls them now SP's last one I saw was kicker and 
_05. It did quite a bit of stuff. It is about 5-6Meg. and don't forget the LOADer file. 
  
Well, I started with OS2 when it was not even announce yet back in the 86-7 times. 
  
GOOD LUCK again. 
  
-oo- 
 mf 

In <3o44kl$tp@eldborg.rhi.hi.is>, bjornr@rhi.hi.is (Bjorn Robertsson) writes:
>In <3nrubu$rh9@hpspden.vid.hp.com> schmitz@vid.hp.com (John Schmitz) writes:
>
>>> Trap 000e info.
>
I had also some trap problems, specia; when zipping big files in a DOS Box.
It turnes out that my Trident 9440 PCI card did the trick, when I switched the card back to 640 * 16 colors,
it worked O.K>

Changed it for a DIAMOND VRAM card, but still waiting for the drivers for DIAMOND.