# PicoMite 6.00.02 RC17 for PicoCalc

**URL:** <https://forum.clockworkpi.com/t/picomite-6-00-02-rc17-for-picocalc/16943>\
**Category:** PicoCalc\
**Created:** [April 22, 2025, 6:16am UTC](https://forum.clockworkpi.com/t/picomite-6-00-02-rc17-for-picocalc/16943 "2025-04-22T06:16:09Z")\
**Posts on this page:** 1\
**Showing post:** 46

<div class="post-metadata">

**Author:** ![adcockm](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/adcockm/32/1664_2.png) [@adcockm](https://forum.clockworkpi.com/u/adcockm)\
**Post date:** [May 8, 2025, 9:28am UTC](https://forum.clockworkpi.com/t/picomite-6-00-02-rc17-for-picocalc/16943/46 "2025-05-08T09:28:26Z")

</div>

Good suggestion. I changed it to something hopefully better now:

> [@Unofficial PicoCalc PicoMite/WebMite firmware release thread (V6.00.02RCxx)](https://forum.clockworkpi.com/t/unofficial-picocalc-picomite-webmite-firmware-release-thread-v6-00-02rcxx/16513):
>
> The official [ClockworkPi repository](https://github.com/clockworkpi/PicoCalc/tree/master/Code/PicoMite) and patch were not very clean or easy to understand, so I decided to merge in the changes and create a new repo based on the official [PicoMite repository](https://github.com/UKTailwind/PicoMiteAllVersions). I don’t necessarily plan to keep this up to date, but merging changes from the official PicoMite repo should be easier now. This could also be used as a basis for submitting PicoCalc changes back to the PicoMite repo, but currently, while the source files are relatively clean, it’s still not organized ver…

I thought about dropping the “Unofficial”, but it’s still not a Clockwork release, so it applies, even if the “thread” is the official thread. 😉

---

_[View the full topic](https://forum.clockworkpi.com/t/picomite-6-00-02-rc17-for-picocalc/16943)._
