Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: JAB <noway@nochance.com>
Newsgroups: comp.sys.ibm.pc.games.action
Subject: Re: Things I Don't Need Today
Date: Tue, 12 Mar 2024 09:45:43 +0000
Organization: A noiseless patient Spider
Lines: 26
Message-ID: <usp889$7fbt$1@dont-email.me>
References: <v3afuipg2ad5u7ejbk262faghu96bp2v0t@4ax.com>
 <us8ab2$s0h$2@dont-email.me> <233huitah1cib7qar3ueifvthocev0v7bu@4ax.com>
 <usaer4$irkm$1@dont-email.me> <f6kjui15hhe4pk9pod3j25irkv5n5cc5ab@4ax.com>
 <e9bmuihav2gbhpa9c27b7gbmk6h3h84r7t@4ax.com> <usg108$1tuci$1@dont-email.me>
 <tj9pui9vepm6n0urq14q63uhsk828r5vfc@4ax.com> <usj7rt$2om0c$1@dont-email.me>
 <usjvlm$2t2nj$2@dont-email.me> <usnfli$3o65c$2@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Tue, 12 Mar 2024 09:45:45 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="4df3b5aa59ef65c64bd61a9326b450c8";
	logging-data="245117"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19qSwXZoMpghloqbiNfzunM"
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:ZpiP2/TJv2qjvi5CXVxqY1FK3vc=
Content-Language: en-GB
In-Reply-To: <usnfli$3o65c$2@dont-email.me>
Bytes: 2664

On 11/03/2024 17:40, candycanearter07 wrote:
>> Something I learned pretty early in my career was that you get two types
>> of bugs, those that you almost know where the problem is straight away
>> and those that require a more methodical approach.
> 
> That's about my experience too.
> 
>> The ones I really hated where when they turned out to be a problem with
>> the hardware.
> 
> Never really worked with hw but I'd imagine that would be really
> annoying.

Most of the time it's fine, well with old style PCB where you could 
actually do things like probe chips, but I did have an interesting one 
where the RTC just wasn't counting. So I looked at the code to make sure 
it was initialised correctly and all seemed fine. So next up look at the 
hardware signals to see if anything didn't seem right. So out with 
oscilloscope and circuit diagram and that's when I got confused. Probing 
the chip meant that it then started working. That's when you go and get 
one of the hardware guys to help you out. Turns out it was just that the 
oscillator circuit wasn't quite right and probing it, kicked it into life.

I also had one where going into transmit caused the transceiver to 
reboot itself. That turned out to be a naff power cable where the RF was 
interfering with it.