English Amiga Board


Go Back   English Amiga Board > Support > support.Hardware > Hardware mods

 
 
Thread Tools
Old 23 September 2023, 23:31   #1
AmigaMark
Registered User
 
Join Date: Jan 2023
Location: Winsford, UK
Posts: 32
timing fix

Hi all, I am trying to find E123C and E125C on my Amiga 1200 rev 1d4. I have found E121c, and E122c on the reverse side but not the ones i need.


My understanding is that removing these will help the board see my TF1260, and they are not needed anyway.


There is surprisingly little for novices showing exactly where these microscopic capacitors live.



Can any body indicate exactly where they are ( I assume on reverse side of mobo)? or point to a image or video that pinpoints them exactly.
AmigaMark is offline  
Old 24 September 2023, 01:10   #2
giantclam
Registered User
 
giantclam's Avatar
 
Join Date: Jan 2015
Location: australia
Posts: 486
http://www.ianstedman.co.uk/amiga-a1...erboard-fixes/
giantclam is online now  
Old 24 September 2023, 14:41   #3
AmigaMark
Registered User
 
Join Date: Jan 2023
Location: Winsford, UK
Posts: 32
brilliant - thanks giantclam
AmigaMark is offline  
 


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools

Similar Threads
Thread Thread Starter Forum Replies Last Post
Games with Timing Issues - Fix ? Nibbler support.Games 17 05 March 2018 11:16
A1200 Timing fix for my Escom Amiga? manic23 support.Hardware 46 19 August 2014 12:38
How do I know if I need a timing fix? stu232 support.Hardware 4 05 October 2013 01:47
timing fix question ACA trydowave support.Hardware 5 19 August 2013 18:21
ACA1230 timing fix bx20 support.Hardware 17 24 August 2011 09:58

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +2. The time now is 08:56.

Top

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.
Page generated in 0.07906 seconds with 13 queries