Page 9 of 10
Re: Whoops, I did it again. I have a problem, Dragon 32 inbound
Posted: 10 Jun 2022 11:52
by stephen_usher
Oh yeah, they're very different. Probably easier to clean though as the contacts are exposed.
Re: Whoops, I did it again. I have a problem, Dragon 32 inbound
Posted: 10 Jun 2022 11:54
by rubber_jonnie
stephen_usher wrote: 10 Jun 2022 11:52
Oh yeah, they're very different. Probably easier to clean though as the contacts are exposed.
Indeed, just need to find something nice and fine to 'sand' them with.
Re: Whoops, I did it again. I have a problem, Dragon 32 inbound
Posted: 10 Jun 2022 12:55
by stephen_usher
Something "soft" such as a cocktail stick should work.
Re: Whoops, I did it again. I have a problem, Dragon 32 inbound
Posted: 10 Jun 2022 13:10
by rubber_jonnie
stephen_usher wrote: 10 Jun 2022 12:55
Something "soft" such as a cocktail stick should work.
I'm sure I can find something like that.
Re: Whoops, I did it again. I have a problem, Dragon 32 inbound
Posted: 23 Aug 2022 11:02
by rubber_jonnie
Ok, so I have some definite keyboard improvement after breaking out a new can of Electrolube (I think the previous can was Servisol, it's not as good), and I have managed to get SDCX (The Dragon equivalent of SofaRun for the MSX) to finally run.
It was more by luck than judgement, I mounted the SDCX.VDK file (SDRIVE 1,"SDCX.VDK"), used 'DIR' to confirm it was mounted, and used 'RUN "CONFIG.BAS" and selected all the options on, then hit ENTER to save and was able to actually start SDCX for the first time since getting the cart.

- PXL_20220823_092507740.jpg (266.89 KiB) Viewed 1683 times
However, I'm now thinking there might be other problems, specifically RAM, as it keeps crashing and doing odd stuff, so I think the Dragon is going to be back on the bench for dome more work in the near future.
It could also be SD cart wobble, so I'll take a look at the cartridge connector on the machine too.
Re: Whoops, I did it again. I have a problem, Dragon 32 inbound
Posted: 23 Aug 2022 11:30
by rubber_jonnie
Yep, definitely some problem going on, as you can see from the corruption when navigating the SDCX file browser:

- PXL_20220823_102734589.jpg (253.76 KiB) Viewed 1678 times

- PXL_20220823_104507341.jpg (306 KiB) Viewed 1673 times
So some more investigation required for the Dragon :(
Re: Whoops, I did it again. I have a problem, Dragon 32 inbound
Posted: 23 Aug 2022 12:08
by stephen_usher
More RCM (Randomly Corrupting Memory) than RAM then. :-)
Re: Whoops, I did it again. I have a problem, Dragon 32 inbound
Posted: 23 Aug 2022 13:35
by rubber_jonnie
stephen_usher wrote: 23 Aug 2022 12:08
More RCM (Randomly Corrupting Memory) than RAM then. :-)
Indeed it is!
Will have a look at the schematic, see if there are any buffers or multiplexers at play, might not be RAM at all, but definitely not right!
I think possibly a little Electrolube on the sockets too.
Re: Whoops, I did it again. I have a problem, Dragon 32 inbound
Posted: 27 Aug 2022 16:58
by rubber_jonnie
Well, it was a good day for the Dragon, the new 4164s arrived and I fitted them:

- PXL_20220827_151644956.jpg (360.06 KiB) Viewed 1642 times
And now the SDCX browser seems to run stably, and I am able to run all sorts off it now, which is great, though the keyboard is still double typing or not typing at times and for specific keys (I should check what part of the matrix they are all on), but at least the darn thing works now overall.
I have to say though, the Dragon mainboard is super fragile and my desoldering attempts ran into a few problems with lifting pads with very little heat applied.
In the end, the safest way was to snip all the legs on the old RAM and then remove the legs one at a time. Really not my favourite way of doing things, but it was that or damaging the PCB.
It was hard even with my desoldering gun.
Just be aware if you have a Dragon of your own and need to get soldering.
Re: Whoops, I did it again. I have a problem, Dragon 32 inbound
Posted: 27 Aug 2022 17:05
by stephen_usher
:dualthumbup: