Maybe this?

http://web.archive.org/web/20040727113430/htt … ip3_man_web.pdf

http://www.x86-secret.com/popups/articleswindow.php?id=29

Robin4 wrote:

Maybe this?

http://web.archive.org/web/20040727113430/htt … ip3_man_web.pdf

http://www.x86-secret.com/popups/articleswindow.php?id=29

Thank you, but couldn't find anything there 🙁

The farthest I got was the SystemSearch page on their site through Archive.Org.

Problem is when you choose Gigabyte and press next, it gives a 400 error.

If someone could decipher the code, maybe the target page for the form submit can be found.

mockingbird wrote:

The farthest I got was the SystemSearch page on their site through Archive.Org.

Problem is when you choose Gigabyte and press next, it gives a 400 error.

If someone could decipher the code, maybe the target page for the form submit can be found.

Yeah, I tried the wayback machine first off. The "robots.txt" file apparently blocked the directory (classic.powerleap.com/support) from being archived 🙁

Try emailing Powerleap.

I have two GA-6BXC modified BIOS images, with Tualatin support. Both of them work.
One of those is a "Powerleap" branded BIOS, Award version 6.00PG. It can be found here: Link

gerwin wrote:

I have two GA-6BXC modified BIOS images, with Tualatin support. Both of them work.
One of those is a "Powerleap" branded BIOS, Award version 6.00PG. It can be found here: Link

Hmmm.... Tried the one in the link. I actually like it because it added the 8-Bit Delay function in BIOS (F4b & F4c unmodded only have 16-Bit.) However, it's not powering up now (with the iP3 installed.) Before, it would show the video BIOS screen, give the POST beep, then lock up at the POST screen. Shows all the normal information, except when it displays the CPU speed, the number is wrong and it doesn't show anything past the speed. Now, all the lights come on (even the LED on the iP3,) and the fans start, but there is no beep and the monitor never powers up. I went through the troubleshooting tips again from the beginning, and none of them had any effect. I also took one of them a step farther and unplugged everything from the PS except the iP3 and the MB.

Any chance you could upload the other GA-6BXC image? I'm still looking for an archive or copy of the PowerLeap instructions, but am not having much luck 🙁

mockingbird wrote:

Try emailing Powerleap.

Yes, all the e-mails bounce 🙁 Tried tech support, consumer sales, and business sales.

I've sent an email to them (Hasn't bounced), I'll let you know if I hear anything back.

mockingbird wrote:

I've sent an email to them (Hasn't bounced), I'll let you know if I hear anything back.

Woah... I always got a "mailer-demon" "unknown recipient" on all the addresses I could find on their website. Please, let me know what they say 😀

FeedingDragon wrote:

mockingbird wrote:

I've sent an email to them (Hasn't bounced), I'll let you know if I hear anything back.

Woah... I always got a "mailer-demon" "unknown recipient" on all the addresses I could find on their website. Please, let me know what they say 😀

I have my ways.... Let's just say I didn't get this address off their website.

FeedingDragon wrote:

Any chance you could upload the other GA-6BXC image? I'm still looking for an archive or copy of the PowerLeap instructions, but am not having much luck 🙁

Will do that, but it will have to wait until the weekend.
Pretty sure another BIOS is not gonna solve the problem you are having. What CPUs did you try?

gerwin wrote:

FeedingDragon wrote:

Any chance you could upload the other GA-6BXC image? I'm still looking for an archive or copy of the PowerLeap instructions, but am not having much luck 🙁

Will do that, but it will have to wait until the weekend.
Pretty sure another BIOS is not gonna solve the problem you are having. What CPUs did you try?

Only have one. A Celeron 1.4Ghz, 100Mhz FSB model SL6C6. I'll give just about anything a shot really. First attempt was with the GigaByte F4b BIOS. Updated the BIOS to F4c and it changed what it did a bit. With the F4b it would print "Intel **46" (the ** were strange characters I don't know how to type,) and stop there. When I updated to F4c it would print "Intel 756" and stop. The numbers are ones I just picked randomly, I don't remember exactly what they were, just that the F4b had 2 digits and the F4c had 3 (without strange characters.) Of course, neither one was even close to the 1.4Ghz or 1400Mhz I was expecting. The last BIOS doesn't even get to the video BIOS display.

In all 3 cases I've tried adjusting the iP3's jumpers. Tried "Auto FSB" and "100 FSB" also tried all voltages from 1.50V to 1.60V (the CPU is 1.5V.) That's 18 different tries (3 BIOS, 2 FSB, 3 Voltage.) Don't mind trying 6 more times before giving up and going for a new MB. Don't really want to do that though. Since I cannot get a Voodoo 1 to play nice with my Voodoo 2's in DOS mode, I'd sort of like to keep the ISA/PCI spot open so I have more options in deciding what to put there. Most of the other boards I've been looking at have only 2 ISA slots (with 1 shared,) instead of 3. Alternately, I could look for a different Slotket adaptor I guess, but I haven't been able to find any so far.

I really wish those "special instructions" hadn't disappeared.

mockingbird wrote:

I have my ways.... Let's just say I didn't get this address off their website.

🤣 Hey PeterLI, look: a fellow ~~Seeker~~ 😀

I just uploaded all my BIOS files for this board to Here.
The Tualatin compatible ones were tested with Revision 2.0 motherboards and UpgradeWare Slot-T v1.1 CPU adapters, with a multitude of CPUs: Worked fine.

The Upgradeware Slot-T adapter may make a big difference. I went with the iP3 because it wasn't dependent on the MB for voltage control. My board has a VR that is capable of going down to the 1.5V of the Tualatin chip, but because of my difficulty with the 3.3V on the AGP I wanted to leave my options open for replacing the board. I don't know if the Slot-T has that capability, but I did find out (while trying to get it to work,) that the iP3 masks some of the CPU info from the BIOS. The CPU temperature definitely, which shouldn't make a difference as this BIOS doesn't have a hardware monitoring function.

I'll try out these BIOS files, and see if I can get it working. The PL BIOS with shorter string is one I might like to stick with, if none of them work. I like having the 8-Bit Delay option instead of just the 16-Bit one. Got my Adlib sound working with Windwalker again thanks to that 😀 But the long *this is a beta ect...** string is a bit of an eyesore IMHO.

Thanks 😀

Well, argh!!!

Well, went back to the very beginning, and started over with the different BIOS files. Not one of them got to POST (and 2 of them got that far before.) So, I thought maybe I had damaged something when I had removed the CPU to get all the info off of it. When I went to check, turns out the CPU wasn't seated correctly 🙁 A feverish panicked moment as I removed the CPU, checked the pins for bending, replaced the CPU (quadruple checking EVERYTHING to make sure I wasn't making the same mistake again,) and powered it up. POST is back 😀 Flashed the Powerleap BIOS (with the shorter string,) and YAY!! Works just fine now 😀

Doing a little jig... Don't look if you want to remain sane...

OK, done dancing now.....

Something curious came up... I had been using a utility someone here gave me (SMB) to alter the FSB speed for some games on the fly. Before, after a reboot, the dip set FSB came back. However, with the iP3 installed it no longer does so. Set the FSB to 50 with SMB, and after a reboot, it's still 50. I have to run SMB to change the FSB back to 100 (100.2 actually,) manually to get full speed back. Is this normal with the iP3? Do the other Slotket adapters do the same thing? Is it possibly the Powerleap BIOS that does this? I actually like the Powerleap BIOS for other reasons as well 😀 It gives me some things back that I felt were missing in the Gigabyte BIOS (8-Bit Delay, Individual control of 1st, 2nd, 3rd Boot devices instead of preset lists, etc...) So, I'm stuck with the situation anyways, but am curious as to where the cause lies.

Using a Slot-T the FSB-speed resets to the jumpered state at every reboot.
We are using the same BIOS.
If all else fails you can put SMB in your autoexec.bat.