Good spot, hadn't occurred to me that there was no CMOS batt - I think you're right and it was doing RAM training!

My ASUS Fx-504 has a CMOS battery and every time a have a reset BIOS, for instance BIOS update it power cicles 3 times, first time i scared out

I've also experienced this on some MSI laptops. They also don't power on from battery alone after reassembly. They need the charger plugged in to get going. It then does it's weird power cycling before operating normally. Scared the crap outta me at first.

I've written code for Phoenix, General Software, and AMI BIOS packages. From Core2Duo up to Haswell. Besides the microcode needed (that's secret sauce from Intel) and the IDE/Language, they are pretty similar in over-all structure. The more things change the more they stay the same. The differences in language are pretty minor as well. Phoenix SCT used their own made in house Visual Studio add-on, General Software was kind of a roll your own/compile from command line with several linkers running in the background (heavy use of Notepad++ and batch files), and recent AMI uses their own "made in house" IDE. General software requires you to edit a bit more assembly language but still mostly C for all the "normal" modifications. Phoenix and AMI was almost 100% a C subset, though there is some assembly that can be modified. Minor differences in syntax existed, of course, but they are all quite similar. I have a small chuckle sometimes when I hear people refer to BIOS as UEFI, because it's not. UEFI is more or less an add-on for BIOS. The code is no different and UEFI is shoehorned in there. Made possible by memory density increases. Well dammit, I'm rambling a tad (it's going to happen again probably, I tend to over explain far to often....) On bootup, devices are detected in multiple stages. Certain devices are "brought to life" first followed by others in a well orchestrated dance. As you can imagine the CPU and chipset is pretty high on the list, followed by memory, buses, devices on buses, etc etc... A "normal" BIOS gets the config data for each device and stores this data in an internal database. Next boot, read database, plug in values, and life moves forward MUCH faster. I've brought up many fresh from the factory PCBs during prototype stages, normally BIOS is flashed at the factory so we don't have to dick with it, but during prototype, things are different. What you are experiencing in this multi-boot process is a rebuilding and verifying of the internal database, it really is as simple as that. The power went blank and the database went with it. There's other shit happening but that's the short of it all.

@@ianide2480 Thank you for the detailed response. I think I can safely speak for most people on here in saying that there is no such thing as too much information. There is one core unanswered question, and perhaps it has nothing to do with the BIOS, but how does the laptop know to self power. Some will do it as soon as a battery is hooked up. Others only when mains is connected. While still others, who's BIOS has been cleared, just wait for the user. This isn't YOUR responsibility to answer lol, just the general question I would love to know the answer to. :D

Hmmmm

Lol late comment but that’s kinda funny

It's not really much of an issue, although admittedly I could've used a little kapton tape to protect the electrolytic caps. Other components won't really budge until you knock them with the tweezers though. Flux also helps keep things in place, as it'll make the solder attract to the pads more.

Yéep

That CAP is called MARRY... BLOODY MARY

Go for a Jakemy, its just a bit bigger but twice the rpm with a adjustable clutch 👍👍

I corrected because it sounded like I said Acer - but that's still interesting!

The problem with in-circuit is that everything else is in-circuit with it, so you can never be sure if you're measuring the device between the probes, or the route going around through a lower-resistance device nearby. However, caps don't always fail short - and that's where an ESR meter will come in handy. It's not an issue I regularly see though, so hard to demonstrate it. I think old caps going high-ESR is a fault you often see in retro gear though.

@@Adamant_ITThanks - If it's too good to be true - would have been nice though.

no, because the first two mosfets are controled by the charging ic, this ic will check also a fault on the motherboard, so it will not switch the second mosfet. See them as the protected mosfets. Also the voltage on the source of the those mosfetss are higher then the input voltage, thats normal and the working of the system. Always inject voltage after the current resistor, u will bypass the protection circuit.

I don't think it actually makes a meaningful difference to performance, and might cause unexpected issues with certain services like Xbox Live, etc. I do uninstall guff myself, but I just do what you can see in plain sight on the start menu and such.

@@Adamant_IT thank you sir for the quick reply , have all the plain sight stuff switched off ...mostly !! will keep looking ...thanks !

GOOD job buddy

Cool

He did a review of it about a week ago.

Yea, recent video on it with more info and links!

Thanks dumb me I missed that one ill go looksy now.

You can't use the original adapter to find a short, because it will cut out. The bench PSU is a regulated power supply that I control, so I can force it to keep injecting power even under a fault condition. As for finding test points, you need to follow traces from the adapter input through the board, sometimes with the aid of schematics. It takes some practise to 'read the board'. See this video for more information: kzfaq.info/get/bejne/mtCFrbWFqMDWk58.html

@@Adamant_IT oh thank you so much ㅡ.,ㅡb

@@Adamant_IT you said that if i use original adapter then i cant find short for cut out. Just observe point which adapter attached then i can find +and - cirquits then follow trace +cirquits if you pass cut out elements which are mosfet or ic chips or tr then connect wire to ptoper point but this is difficult to find and - cirquits are probably board itself then by these 2 wire i can keep injecting power and current flow through these 2 wire and find worming places where short elements are existed ok thank you but it feels that tough to find point part that +wire attached because If i were use original adapter to find worming part then it is cut out by itself then should have find the point +wire attached in circuits this is high level. And during injecting power by force then perhaps volt is 5V and ampere is 5A i can fix the construction machinery by Reading cirquits but this is more deeper and delicate ...really thank for your teaching And i like Charles platt for his easy explains and service and i want to know the serial communication which is communacate between two computer through 4~5wires But the effect is it has 100 wires are connected each other of coure sure that you know it far more than me.

check the voltage on the second mosfet of the charging circuit.

Yup, or kapton tape.