I have an Ampro Little Board Plus that I've done the mod listed in the smartclk.asm source and installed a No-Slot Clock from Reactive Micro.
This worked for quite a while, then I didn't use it for a couple of weeks. When I did power it on again and ran SMARTCLK I got the error message "error reading SmartWatch".
I got busy and didn't have a chance to look at it. Tonight I opened it up and found a bent pin on the No-Slot Clock. I thought it probably had just made intermittent contact before and had worked a little loose. I straightened the pin, reinstalled everything, and tested. I was able to set and read the clock with SMARTCLK.
I screwed everything back together and powered it back up and tested again. Everything worked. I disconnected the console and power cable, moved it from the desk back to the shelf it sits on, connected the console and power, and started it up. Now I'm getting the "error reading SmartWatch" message. This is puzzling me. It's in the Integrand case so it's a bit of a pain to take it all apart for debugging, so I thought I'd throw it out there to see if anyone had any ideas why it's doing this before I put it back on the desk and tear it apart again.
This worked for quite a while, then I didn't use it for a couple of weeks. When I did power it on again and ran SMARTCLK I got the error message "error reading SmartWatch".
I got busy and didn't have a chance to look at it. Tonight I opened it up and found a bent pin on the No-Slot Clock. I thought it probably had just made intermittent contact before and had worked a little loose. I straightened the pin, reinstalled everything, and tested. I was able to set and read the clock with SMARTCLK.
I screwed everything back together and powered it back up and tested again. Everything worked. I disconnected the console and power cable, moved it from the desk back to the shelf it sits on, connected the console and power, and started it up. Now I'm getting the "error reading SmartWatch" message. This is puzzling me. It's in the Integrand case so it's a bit of a pain to take it all apart for debugging, so I thought I'd throw it out there to see if anyone had any ideas why it's doing this before I put it back on the desk and tear it apart again.