Help with my failed unlocking attempt!

[SlinkyDink]

I spend all of 3 hours last night trying to unlock my XP1600 (my 8kha and ram max out at 166mhz, and the chip could do more).

I kept trying to connect the bridges with rear window defogger, using a crayong to fill in the trenches. All of the attempts failed, with random multipliers being available. I eventually gave up and cleaned the chip off with nail polish remover, and then the chip was stuck at a 10x multiplier. I tried again to clean the bridges, and somehow I was stuck with a 12x multiplier. I couldnt see anything with contact, but somehow I got this number, which is exactly what I wanted and was running at 1800mhz fine and dandy.


Well, I turn my computer on today to find that its stuck at a 6x multiplier when I choose 12x, and everything else is still 10x.

What should I do to fix my chip? Something is still shorting the chip out I guess. Use a really aggressive acetone and remove every last bit of crude stuck in the trenches?

 

[panhead49]

your right....there is still residue in or on the chip/trenchs.......you need to clean it good like you said......the only reason im giving advice is to tell you not to clean to aggresive.......dont rub off the protective layer on top .....you will expose a copper underbelly and then you will really have fun.......

 

[jiffylube1024]

This definately goes under the "oops" category 🙂 . I'd say stick to panhead's advice, clean it just not too violently so you don't wear out the top of the chip.

 

[SlinkyDink]

I just finished my repair and remask job. I carefully used a 21 gauge injection needle while the surface of the area was covered in nail polish remover. Aparently a tiny amount of residue was covering the surface and shorting the first l1 contact out.

anyways, thanks guys its working correctly now. Buzzing along at 12x150 (1810mhz) with 1.85v

 

[johncar]

You also probably had the 3rd L1 from the left still open when you set 12X and got 6X. Here's why...

10.5X default 16600+ has .5X + 1X +2X +4X Biit Values set HI with the L3/L4/L10 bridges.

When you set 12X in bios, it tries to set "only" 1X HI, and tries to reset the others all LO. But if the 3rd L1 was still open then 2X would stay at its default HI for a 1X + 2X setting which gets 6X...what you got. Check it out at.....

http://www.beachlink.com/candjac/index.htm link to Understanding Multiplier Code article so the next time you get unexpected results you can decode the specific problems yourself, it's not rocket science.
John C.

 

[SlinkyDink]

Originally posted by: johncar
You also probably had the 3rd L1 from the left still open when you set 12X and got 6X. Here's why...

10.5X default 16600+ has .5X + 1X +2X +4X Biit Values set HI with the L3/L4/L10 bridges.

When you set 12X in bios, it tries to set "only" 1X HI, and tries to reset the others all LO. But if the 3rd L1 was still open then 2X would stay at its default HI for a 1X + 2X setting which gets 6X...what you got. Check it out at.....

http://www.beachlink.com/candjac/index.htm link to Understanding Multiplier Code article so the next time you get unexpected results you can decode the specific problems yourself, it's not rocket science.
John C.

Cool page. You were right and it was the 3rd L1 that was open and then later shorting with ground (why 12x turned into 6x, then later 10x). Its all working now, although my 1800mhz doesnt seem like to much anymore with the 2.5ghz AMD's around the corner 😛

 

[johncar]

Originally posted by: SlinkyDink

Originally posted by: johncar
You also probably had the 3rd L1 from the left still open when you set 12X and got 6X. Here's why...

10.5X default 16600+ has .5X + 1X +2X +4X Biit Values set HI with the L3/L4/L10 bridges.

When you set 12X in bios, it tries to set "only" 1X HI, and tries to reset the others all LO. But if the 3rd L1 was still open then 2X would stay at its default HI for a 1X + 2X setting which gets 6X...what you got. Check it out at.....

http://www.beachlink.com/candjac/index.htm link to Understanding Multiplier Code article so the next time you get unexpected results you can decode the specific problems yourself, it's not rocket science.
John C.

Cool page. You were right and it was the 3rd L1 that was open and then later shorting with ground (why 12x turned into 6x, then later 10x). Its all working now, although my 1800mhz doesnt seem like to much anymore with the 2.5ghz AMD's around the corner 😛

Easy to be right when the Multiplier Code is "understood". Hope this makes you a believer, and now that you know the code can do your own "fault modeling"...teach others...that's what it's all about in theses fora...right??
John C.