{
    "version": "https://jsonfeed.org/version/1",
    "title": "Rod&#x27;s Shed",
    "description": "",
    "home_page_url": "https://sages.com.au/rodshed",
    "feed_url": "https://sages.com.au/rodshed/feed.json",
    "user_comment": "",
    "author": {
        "name": "Rod"
    },
    "items": [
        {
            "id": "https://sages.com.au/rodshed/microbee-512k-bios-function-keys.html",
            "url": "https://sages.com.au/rodshed/microbee-512k-bios-function-keys.html",
            "title": "Microbee 512k bios function keys",
            "summary": "Microbee function keys. These can save you a lot of reputative typing, here's an example One way to simplify mounting a spare partition with minimal effort. Hit ctrl and 9 key simultaneously A pop up window should appear. Select F to enter the function key&hellip;",
            "content_html": "<p>Microbee function keys.</p>\n<p>These can save you a lot of reputative typing, here's an example</p>\n<p>One way to simplify mounting a spare partition with minimal effort.<br>Hit</p>\n<p><span style=\"background-color: #f6f6f9; color: #ea1a16; font-family: Menlo, Monaco, Consolas, 'Courier New', monospace; font-size: 0.888889em;\">ctrl and 9 key</span></p>\n<p><br>simultaneously<br>A pop up window should appear.<br>Select</p>\n<p><code>F</code><br><br>to enter the function key menu<br>Make sure that the function keys are turned on, 'O' function.<br><br>For example I'll use F1<br>Hit</p>\n<p><code>ctrl and 1</code><br><br>Yet another editing window will pop up:<br>In the editing window type the following (assuming that we intend to replace the last mounted cf/hd drive, in my case \"D\" drive and replace it with partition #5:<br><code>hd umount d:;hd mount cf0:5</code><br>Then hit<br><code>enter, ESC, ESC</code><br>which take you back to the cpm prompt:<br>I'd suggest saving the functionkey definition here. You can have lots of function key definitions all save in different files but suggest you read the docs. You can also save just one fkey definition so it's possible to change one fkey at a time.<br>I saved mine in the default file so:<br><code>fkey s</code><br>(or you can use your own file name NOTE: don't add a file type, just the name, fkey uses .fk as file type)<br><br>Now from the command prompt hit<br><code>ctrl 1</code><br><br>the function key text should appear at the prompt, just hit<br><code>enter</code><br>and it'll be executed just as if you types again.<br><br>You can automate a lot of things with a combination of function keys and submit files like this. I would suggest that you keep some sort of documentation on what you do and how you have done it as online 'help' isn't one of the strong points of cpm.<br>And on a1: is a program called fn.com which is a larger editor for function keys</p>",
            "author": {
                "name": "Rod"
            },
            "tags": [
            ],
            "date_published": "2026-04-16T14:01:18+08:00",
            "date_modified": "2026-04-16T14:01:18+08:00"
        },
        {
            "id": "https://sages.com.au/rodshed/extended-partitions-on-microbee-512k-bios-and-cf.html",
            "url": "https://sages.com.au/rodshed/extended-partitions-on-microbee-512k-bios-and-cf.html",
            "title": "Extended partitions on Microbee 512k bios and cf",
            "summary": "Extended partitions for cf/512k bios on the Microbee How to create extra partitions and access them. There is lots of unused space on the cf images that could be used as archive or whatever but people may not know how to access or use it.",
            "content_html": "<div>Extended partitions for cf/512k bios on the Microbee</div>\n<div> </div>\n<div>How to create extra partitions and access them. There is lots of unused space on the cf images that could be used as archive or whatever but people may not know how to access or use it.</div>\n<div>There are some constraints but it is still useful storage and it's free!</div>\n<div> </div>\n<div>extended partitions of mbee 512k bios</div>\n<div> </div>\n<div>Boot</div>\n<div>check for number of mounted hd/cf partitions (flash screen shows this, or 'hd list cf0:')</div>\n<div>We will replace the last primary partition with an extended partition and then we can add aa replacement partition for the deleted one and other new partitions)</div>\n<div> </div>\n<div>unmount last partitions</div>\n<div>ie if 4 partitions A-&gt;D then</div>\n<div><code>hd umount d:</code></div>\n<div> </div>\n<div>then we need to add new partitions</div>\n<div> </div>\n<div><code>part</code></div>\n<div><code>    d</code></div>\n<div><code>    4</code></div>\n<div><code>    n</code></div>\n<div><code>    4</code></div>\n<div><code>    e</code></div>\n<div><code>    accept defaults</code></div>\n<div> </div>\n<div>doing a print (p) at this stage should show 3 primary CTOS partitions and one DOS 3.1+ extended partition</div>\n<div>Now add extra extended partitions as required. Remembering that the first sector is reserved as a partition table</div>\n<div>so accept default start and make the end value the same increment as existing partitions.</div>\n<div> </div>\n<div>'q' exits without saving any changes.</div>\n<div>'w' exists writing all changes</div>\n<div>'m' help!</div>\n<div> </div>\n<div>Example from 1 1GB CF:</div>\n<div>Info from 'part'</div>\n<div>[ptbl] 0 size 1 0/0/1 - 0/0/1</div>\n<div>[free] 1 size 62 0/0/2 - 0/0/63</div>\n<div>* 1 CTOS 63 size 9009 0/1/1 - 8/15/63</div>\n<div>2 CTOS 9072 size 9072 9/0/1 -17/15/63</div>\n<div>3 CTOS 18144 size 9072 18/0/1 - 26/15/63</div>\n<div>4 CTOS 27216 size 9072 27/0/1 - 35/15/63</div>\n<div>[free] 36288 size 1993824 36/0/1 - 2013/15/63</div>\n<div> </div>\n<div>Now to add extended partitions we need to delete the last Primary partition (4)</div>\n<div>So, delete partition #4</div>\n<div><code>    d</code></div>\n<div><code>    4</code></div>\n<div>then replace it with an extended partition using up the rest of the drive</div>\n<div>We accept the defaults for start and end values.</div>\n<div><code>    n</code></div>\n<div><code>    e</code></div>\n<div><code>    cr</code></div>\n<div><code>    cr</code></div>\n<div> </div>\n<div>If we 'p' the partition table at this point we see the change to partition 4 it's now:</div>\n<div>4 DOS 3.3+ Extended 27216 size 2002896 27/0/1 - 2013/15/63</div>\n<div>[ptbl] 27216 size 1 27/0/1 - 27/0/1</div>\n<div>[free] 27217 size 2002895 27/0/2 - 2013/15/63</div>\n<div> </div>\n<div>If we now add a new partition it will automatically be an extended partition, we just</div>\n<div>need to accept the start and set the end. To make it near enough to the same size as existing</div>\n<div>partitions if you look at the existing partition end c/h/s they increment the 'c' value by 9</div>\n<div>with the same h/s values, so our new end value is 26/15/63 + '9'/0/0 == 35/15/63, and the</div>\n<div>next partition would end at 35/15/63 + '9'/0/0 == 44/15/63 and so on.</div>\n<div> </div>\n<div>So:</div>\n<div><code>    n</code></div>\n<div><code>    cr</code></div>\n<div><code>    35/15</code></div>\n<div> </div>\n<div>And now if you 'p' the partition table it has this at the end:</div>\n<div>5 CTOS 27279 size 9009 27/1/1 - 35/15/63</div>\n<div>[free] 36288 size 1993824 36/0/1 - 2013/15/63</div>\n<div> </div>\n<div>Each extended partition creates a new partition table similar to the first primary partition.</div>\n<div> </div>\n<div>After saving this back to the disk by using the 'w' command it will tell you to reboot.</div>\n<div>At this point the new partition will mount as as the d: drive however it hasn't been formatted yet.</div>\n<div>We use 'eraram' program to format fixed disks.</div>\n<div>so if our new partition is d:</div>\n<div>we run</div>\n<div><code>eraram d:</code></div>\n<div>    </div>\n<div>All done!</div>\n<div> </div>\n<div>If you have more partitions than available space for the ALV's, when you boot the system should detect</div>\n<div>your partitions but won't mount then as it has run out of space. Note it always mounts the first cpm partitions</div>\n<div>it finds. (partition 4 won't mount as it is a different type in our example, it's replaced by partition 5).</div>\n<div> </div>\n<div>If you want to access the other partitions then you need to unmount a partition then mount the required one.</div>\n<div>So using the 'hd' program (for example) to mount a new partition (6 as an example) in the place of the D: drive,</div>\n<div>(see function keys note)</div>\n<div> </div>\n<div><code>hd umount d:</code></div>\n<div><code>hd mount cf0:6</code></div>\n<div> </div>\n<div> </div>\n<div>You can now access partition 6 as the d: drive.*</div>\n<div> </div>",
            "author": {
                "name": "Rod"
            },
            "tags": [
            ],
            "date_published": "2026-04-16T13:56:32+08:00",
            "date_modified": "2026-04-16T13:56:32+08:00"
        },
        {
            "id": "https://sages.com.au/rodshed/passthrough-parallel-port-on-proxmox.html",
            "url": "https://sages.com.au/rodshed/passthrough-parallel-port-on-proxmox.html",
            "title": "Passthrough Parallel Port on Proxmox",
            "summary": "I have an old Arlabs Eprom+ programmer that uses the old style printer port to connect to a computer. I've been using a vintage Compaq Armada E500 laptop running Windows 2000 as the host computer as it is the only laptop I have left with&hellip;",
            "content_html": "<p>I have an old Arlabs Eprom+ programmer that uses the old style printer port to connect to a computer. I've been using a vintage Compaq Armada E500 laptop running Windows 2000 as the host computer as it is the only laptop I have left with a parallel port. Unfortunately with the changes to SMB over the years it is a pain to get network file share working with it and my newer servers. Also it is getting a bit old and I don't like my changes for when it packs it in.</p>\n<p>So, long story a bit shorter, Several of my servers still have a parallel port and one of them is setup as a Proxmox host. It's pretty straight forward to passthrough the parallel port to a virtual machine and allow access to my eprom programmer. Note: USB to parallel port converters don't work for bit bashed port interfaces.</p>\n<p>It did require a command line config but pretty trivial to do.</p>\n<p>Find the parallel port (ls /dev/parport*), if no result then load the parallel port driver (modprobe ppdev, and add it to /etc/modprobe so it's still there after a reboot).</p>\n<p>then qm set vmid -parallel0 /dev/parport0 (match the port number to you hardware and vmid to your vm)</p>\n<p>That's it, the parallel port should now be useable from your vm.</p>\n<p> </p>\n<p> </p>",
            "author": {
                "name": "Rod"
            },
            "tags": [
            ],
            "date_published": "2026-03-18T16:25:26+08:00",
            "date_modified": "2026-03-18T16:25:26+08:00"
        },
        {
            "id": "https://sages.com.au/rodshed/esp32-c3-42-oled.html",
            "url": "https://sages.com.au/rodshed/esp32-c3-42-oled.html",
            "title": "ESP32-C3-4.2 OLED",
            "summary": "Just some notes/observations after using some of these ESP32-C3 with built in 0.42 oled displays. First thing is the antenna, one of those small ceramic things is crap, check out the mod on this guys site. I made same mods and went from about 5m&hellip;",
            "content_html": "<p>Just some notes/observations after using some of these ESP32-C3 with built in 0.42 oled displays.</p>\n<p>First thing is the antenna, one of those small ceramic things is crap, check out the mod on this <a href=\" https://peterneufeld.wordpress.com/2025/03/04/esp32-c3-supermini-antenna-modification/\">guys site.</a><a href=\" https://peterneufeld.wordpress.com/2025/03/04/esp32-c3-supermini-antenna-modification/\"></a>  I made same mods and went from about 5m range inside to 30m+ from inside to outside before I gave up walking further away 😅, well worth it.</p>\n<p>Second thing I found was after playing with espnow was when I reflashed the esp32 with some plain wifi code it wouldn't connect. I could scan AP's but it wouldn't connect. I then erased flash (I use platformio on VSC and it's under the advanced section in the platformio section) and reloaded the wifi test program and all was well. Didn't investigate further but something to be aware of.</p>\n<p> </p>\n<p> </p>",
            "author": {
                "name": "Rod"
            },
            "tags": [
            ],
            "date_published": "2026-02-15T14:45:47+08:00",
            "date_modified": "2026-02-15T14:55:51+08:00"
        },
        {
            "id": "https://sages.com.au/rodshed/usb-flash-drive-interface-for-the-microbee.html",
            "url": "https://sages.com.au/rodshed/usb-flash-drive-interface-for-the-microbee.html",
            "title": "USB Flash drive interface for the Microbee",
            "summary": "I've prototyped a simple interface for a usb flash drive to a microbee. It uses a CH376 interface board (about ~$5-$10 on aliexpress) and connects to the data bus of a bee and a few signals with 14 wires. I'm currently running a freebee cf&hellip;",
            "content_html": "<figure class=\"post__image\">I've prototyped a simple interface for a usb flash drive to a microbee.<br>It uses a CH376 interface board (about ~$5-$10 on aliexpress) and connects to the data bus of a bee and a few signals with 14 wires. I'm currently running a freebee cf coreboard and have it plugged into the (for me) unused ide interface with the addition of a couple of links.<br>I snaffled the software from the romwbw project and modified it for the ch376 chip. (it originally came from <a href=\"https://github.com/wwarthen/FAT\">https://github.com/wwarthen/FAT</a>)<br>The usb flash drive is formatted to fat32 and I can r/w on windoze then plug it into my bee and copy files to/from fat32 on the flash drive to cpm format on my cf.<br>I still need to clean it up and write up the connections. The code needs a little polishing and hopefully it will allow hotplug of the usb flash drive when I've finished.<br>Others have used the same ch376 chip for mouse and keyboard interfacing, so there is some potential there.<br>It is using lba mode to address the usb drive so, with some changes to the bootrom and bios in theory it would be possible to boot from a usb flash drive.<br><br>Currently I'm using the cpmtools on linux to r/w directly to the cpm formatted cf drive to transfer files. This is, hopefully, one step less in the process.<br>More to come!<br><br><br>there is two models of the ch376 interface board, one with a 3 pin header and one with a 6 pin header. I'm using the 3 pin header at the moment but have a 6 pin on order. As far as I can work out, apart from the 3/6 pin the other difference is in the dual row header where one has the data lines facing in and the other has them on the edge of the board. Functionally I believe they are the same. They use the same chip. If you were laying out a pcb to interface I've seen one version where a triple row header was used and you just plug the board one side or the other. It'll make sense when you see the boards.<br>I'm chasing a bug that the first access to the flash drive fails but the second and subsequent work fine. I've added rtc for the writes to fat. But I'll need some logic to make sure it still works with no rtc fitted.<br>I've found that you can hot plug the flash drive to the ch376 board but I'll look at adding a 'dismount' function or simply turning the power off the flash drive after access. There's a led on the interface board and I'm assuming that it comes on with power. <br>Hardest part so far has been fighting with the build systems. I initially tried to port the original code to compile under Hitech C but it got to hard when I had issue with the underlying FatFs code needing to many changes. So I moved to using SDCC as per romwbw project does and that was another experience. It currently uses a windoze script to build it rather than a make script and it wasn't rebuilding after any edits which made debugging entertaining to say the least.<br><img loading=\"lazy\"  src=\"https://sages.com.au/rodshed/media/posts/14/beeusb2.png\" alt=\"\" width=\"480\" height=\"640\" sizes=\"(max-width: 1920px) 100vw, 1920px\" srcset=\"https://sages.com.au/rodshed/media/posts/14/responsive/beeusb2-xs.png 640w ,https://sages.com.au/rodshed/media/posts/14/responsive/beeusb2-sm.png 768w ,https://sages.com.au/rodshed/media/posts/14/responsive/beeusb2-md.png 1024w ,https://sages.com.au/rodshed/media/posts/14/responsive/beeusb2-lg.png 1366w ,https://sages.com.au/rodshed/media/posts/14/responsive/beeusb2-xl.png 1600w ,https://sages.com.au/rodshed/media/posts/14/responsive/beeusb2-2xl.png 1920w\"></figure><br> <br>Sorry, no drawing but it's pretty straight forward.<br>ch376 interface board to microbee interface</p>\n<table style=\"border-collapse: collapse; width: 100%; height: 868.828px;\" border=\"1\">\n<tbody>\n<tr style=\"height: 48.5625px;\">\n<td style=\"width: 49.9288%; height: 48.5625px;\">FreeBee CF coreboard x2</td>\n<td style=\"width: 49.9288%; height: 48.5625px;\">CH376 pin</td>\n</tr>\n<tr style=\"height: 77.3594px;\">\n<td style=\"width: 49.9288%; height: 77.3594px;\">Pin 3 CFD7 - D7</td>\n<td style=\"width: 49.9288%; height: 77.3594px;\">\n<p>D7</p>\n</td>\n</tr>\n<tr style=\"height: 48.5625px;\">\n<td style=\"width: 49.9288%; height: 48.5625px;\">Pin 5 CFD6 - D6</td>\n<td style=\"width: 49.9288%; height: 48.5625px;\">D6</td>\n</tr>\n<tr style=\"height: 48.5625px;\">\n<td style=\"width: 49.9288%; height: 48.5625px;\">Pin 7 CFD5 - D5</td>\n<td style=\"width: 49.9288%; height: 48.5625px;\">D5</td>\n</tr>\n<tr style=\"height: 48.5625px;\">\n<td style=\"width: 49.9288%; height: 48.5625px;\">Pin 9 CFD4 - D4</td>\n<td style=\"width: 49.9288%; height: 48.5625px;\">D4</td>\n</tr>\n<tr style=\"height: 48.5625px;\">\n<td style=\"width: 49.9288%; height: 48.5625px;\">Pin 11 CFD3 - D3</td>\n<td style=\"width: 49.9288%; height: 48.5625px;\">D3</td>\n</tr>\n<tr style=\"height: 48.5625px;\">\n<td style=\"width: 49.9288%; height: 48.5625px;\">Pin 13 CFD2 - D2</td>\n<td style=\"width: 49.9288%; height: 48.5625px;\">D2</td>\n</tr>\n<tr style=\"height: 48.5625px;\">\n<td style=\"width: 49.9288%; height: 48.5625px;\">Pin 15 CFD1 - D1</td>\n<td style=\"width: 49.9288%; height: 48.5625px;\">D1</td>\n</tr>\n<tr style=\"height: 48.5625px;\">\n<td style=\"width: 49.9288%; height: 48.5625px;\">Pin 16 CFD0 - D0</td>\n<td style=\"width: 49.9288%; height: 48.5625px;\">D0</td>\n</tr>\n<tr style=\"height: 48.5625px;\">\n<td style=\"width: 49.9288%; height: 48.5625px;\">Pin 19 - GND</td>\n<td style=\"width: 49.9288%; height: 48.5625px;\">GND</td>\n</tr>\n<tr style=\"height: 48.5625px;\">\n<td style=\"width: 49.9288%; height: 48.5625px;\">Pin 20 - +5V</td>\n<td style=\"width: 49.9288%; height: 48.5625px;\">VCC</td>\n</tr>\n<tr style=\"height: 133.156px;\">\n<td style=\"width: 49.9288%; height: 133.156px;\">\n<p>Pin 21 - WR link to pin 2 ic19 WD2793</p>\n<p>(iorw unusable as gated with io port 60)</p>\n</td>\n<td style=\"width: 49.9288%; height: 133.156px;\">WR</td>\n</tr>\n<tr style=\"height: 48.5625px;\">\n<td style=\"width: 49.9288%; height: 48.5625px;\">Pin 25 - IORD</td>\n<td style=\"width: 49.9288%; height: 48.5625px;\">RD</td>\n</tr>\n<tr style=\"height: 75.5625px;\">\n<td style=\"width: 49.9288%; height: 75.5625px;\">Pin 27 - CS link to pin 12 ic13 74HC138</td>\n<td style=\"width: 49.9288%; height: 75.5625px;\">CS (i/o port 0x58)</td>\n</tr>\n<tr style=\"height: 48.5625px;\">\n<td style=\"width: 49.9288%; height: 48.5625px;\">Pin 35 - A0</td>\n<td style=\"width: 49.9288%; height: 48.5625px;\">A0</td>\n</tr>\n<tr>\n<td style=\"width: 49.9288%;\">n/a</td>\n<td style=\"width: 49.9288%;\">RESET leave o/c</td>\n</tr>\n</tbody>\n</table>\n<figure class=\"post__image\"><br>CH376 is at i/o port 0x58 &amp; 0x59<br><br>Pins 21 and 27 on x2 are currently unused so patched ungated wr and new cs through them.<br>I don't think the cf logic on iowr is needed but it isn't causing any problem.<br><br>Just wires, no cut tracks required. And one of these https://www.aliexpress.com/item/32877955370.html<br>This is the one with 3 pin header, the other type has a 6 pin header. dual row header swaps the data and control signals from one side to the other. I'll try the other type when it arrives to see if there is any difference between them.<br>They both have a 3.3v regulator on them but, I haven't had any problems r/w to the ch376, nor has it had any observed impact on the cf onthe coreboard.<br>Three pin header near usb socket<br> <img  src=\"https://sages.com.au/rodshed/media/posts/14/ch376_modul2.jpg\" alt=\"\" width=\"211\" height=\"300\" sizes=\"(max-width: 1920px) 100vw, 1920px\" srcset=\"https://sages.com.au/rodshed/media/posts/14/responsive/ch376_modul2-xs.jpg 640w ,https://sages.com.au/rodshed/media/posts/14/responsive/ch376_modul2-sm.jpg 768w ,https://sages.com.au/rodshed/media/posts/14/responsive/ch376_modul2-md.jpg 1024w ,https://sages.com.au/rodshed/media/posts/14/responsive/ch376_modul2-lg.jpg 1366w ,https://sages.com.au/rodshed/media/posts/14/responsive/ch376_modul2-xl.jpg 1600w ,https://sages.com.au/rodshed/media/posts/14/responsive/ch376_modul2-2xl.jpg 1920w\"></figure><br>six pin header near usb socket<br><figure class=\"post__image\"><img loading=\"lazy\"  style=\"outline: rgba(13, 139, 242, 0.55) solid 3px !important;\" src=\"https://sages.com.au/rodshed/media/posts/14/ch376_modul_bs.jpg\" alt=\"\" width=\"181\" height=\"300\" sizes=\"(max-width: 1920px) 100vw, 1920px\" srcset=\"https://sages.com.au/rodshed/media/posts/14/responsive/ch376_modul_bs-xs.jpg 640w ,https://sages.com.au/rodshed/media/posts/14/responsive/ch376_modul_bs-sm.jpg 768w ,https://sages.com.au/rodshed/media/posts/14/responsive/ch376_modul_bs-md.jpg 1024w ,https://sages.com.au/rodshed/media/posts/14/responsive/ch376_modul_bs-lg.jpg 1366w ,https://sages.com.au/rodshed/media/posts/14/responsive/ch376_modul_bs-xl.jpg 1600w ,https://sages.com.au/rodshed/media/posts/14/responsive/ch376_modul_bs-2xl.jpg 1920w\"></figure><br>Note the 16 pin dual row header pinouts are different. same connections just swapped from one side to the other.<br><br>The comment re the addition of the RTC is that FAT drives have a timestamp on them and cpm 2.2 doesn't. Without the RTC code any file copied to the usb flash drive from the bee would have a generic timestamp, by adding the code to read the bee's rtc it now displays the copy time similar to windoze/linux does.<br><br>I'm using a subset of the ch376 functionality. It supports some fat functions directly but I'm using it in 'block' mode with the FatFs software providing the FAT interface. There is a series of the chips with increasing functionality and theoretically the ch375 should work as it also supports the block mode. That said one site https://github.com/djuseeq/Ch376msc has reported different firmware versions of the ch376 having differing success. From what I can gather I have an older version of the chip on a 3 pin header board with a sandisk 32g flash drive on it and it appears to be working fine. I have another board on order with the 6 pin header so I'll check that as well. The web site quoted appears to use the ch376 in it's inbuilt fat support while I'm not. So his comments may be not relevant.<br>They are pretty cheap though.<br><br>Looks like I won't be testing the alternate ch376 board anytime soon. Supplier has shipped the completely incorrect item twice now.<br>fwiw my bee now has ~65GB of storage, cf 1GB, usb flash in gotek 32GB and usb flash on ch376 32Gb. I may have to find some different projects.<br><br>Reading from USB flash and writing to CF ~ 5 times faster than reading from USB flash and writing to gotek.<br>Reading from usb flash and writing to m drive marginally faster than writing to cf. However the transfer to/from FAT isn't optimised. It only reads a single sector at a time and then copies to cpm which has to squeeze that through 8 x 128 byte cpm sectors onto the storage medium. Without delving into cpm bdos/bios internals I think this means a factor of 8 multiplied sector writes to achieve. <br>I've been making a backup of my CF to the usb flash drive and updated my cf image (new ram arrived) then restored from usb flash. Makes updating and transferring files much easier and quicker. Probably an opportunity to make some submit files to semi automate the backup.<br><br>I haven't had a chance to try the '6 pin' module, they shipped incorrect modules to me. The extra 3 pins are used for a serial interface which I'm not using and the other difference is the '3 pin' module has a connection for reset which I'm also not using. the reset is active high rather than the bee's active low reset. The adapter board powers up fine with the circuity on the adapter so I've just left it o/c on mine. <br>The circuit for the '6 pin' is here <a href=\"https://zerowincoding.tistory.com/entry/CH376S-Arudino-Disk-Read-write-Module-USB-Flash-Disk\">https://zerowincoding.tistory.com/entry/CH376S-Arudino-Disk-Read-write-Module-USB-Flash-Disk</a> note the 0.47uF on the reset pin. I haven't found a cct for the '3 pin' version. My translation of the device spec sheet has the reset input with an internal pull down.<br><br>I've not had any issues requiring a power on reset so far. I have also hot plugged and unplugged the flash drive and it has worked without any noticeable issues.</p>\n<p>Software and source code for the <a href=\"https://sages.com.au/rodshed/media/files/FAT-master-2.rar\">FAT program</a> and some floppy images with a copy of the run time program (FAT2.COM, I renamed if for some reason) <a href=\"https://sages.com.au/rodshed/media/files/cfbios.rar\">here</a>.</p>\n<p><br>And that’s about all I wrote up about the project.</p>\n<p>addendum</p>\n<p>And I found this sub file I knocked up<br><br>Backup.sub<br><br>user $2<br>fat copy $1:*.* 0:/$1$2<br><br>usage: ss  backup.sub [src drive] [src user]<br><br>It backs up all files on src drive user to the usb drive on /src driveuser, ss backup.sub a 3, all files from cpm a3 end up on the cf in folder /a3<br>(ss -&gt; actually supersub)<br><br>Easy to backup all of your cf drive</p>\n<p> </p>",
            "author": {
                "name": "Rod"
            },
            "tags": [
            ],
            "date_published": "2026-02-13T12:40:53+08:00",
            "date_modified": "2026-02-13T13:48:17+08:00"
        },
        {
            "id": "https://sages.com.au/rodshed/the-x-bull-75cc-chainsaw-that-was-born-on-a-diet.html",
            "url": "https://sages.com.au/rodshed/the-x-bull-75cc-chainsaw-that-was-born-on-a-diet.html",
            "title": "The X-Bull 75cc chainsaw that was born on a diet.",
            "summary": "Finally succumbed to the lure of a cheap Chinese chainsaw. The cost of parts (mainly freight) to repair my very reliable vintage Stihl 015AV saw made the Chinese saws look attractive. I went all out and purchased the mighty X-Bull 75cc chainsaw. A bit of&hellip;",
            "content_html": "<p><!-- wp:paragraph --></p>\n<p>Finally succumbed to the lure of a cheap Chinese chainsaw. The cost of parts (mainly freight) to repair my very reliable vintage Stihl 015AV saw made the Chinese saws look attractive.</p>\n<p><!-- /wp:paragraph --></p>\n<p><!-- wp:paragraph --></p>\n<p>I went all out and purchased the mighty X-Bull 75cc chainsaw. A bit of a delay due to the efforts of Australia Post but the day finally arrived when my new toy had arrived. After some minor issues with assembly (the chain brake was activated and a bugger to release) I was all set to fire it up. Choke, couple of pumps of the fuel bowl thingy, gentle pull on the starter and within a couple of pulls the first firing occurred. Opened the choke, another pull and off it went. You beauty. Idles, revs, chain spins, oiler works. Just like a real one.</p>\n<p><!-- /wp:paragraph --></p>\n<p><!-- wp:paragraph --></p>\n<p>Given the earlier research online I was anticipating some QA issues, a general cheapness in build and potentially some reliability issues but time will tell. One aspect that I had seen several mentions of was the poetic license regarding the actual capacity of the chainsaw.</p>\n<p><!-- /wp:paragraph --></p>\n<p><!-- wp:paragraph --></p>\n<p>This I had to check. So spark plug removed, muffler removed, calipers in hand, measurements began.</p>\n<p><!-- /wp:paragraph --></p>\n<p><!-- wp:paragraph --></p>\n<p>Hmmm, bore 46mm, stroke 34mm, quick remembering of secondary school maths and we end up with near enough to 56cc displacement. Bit of a difference. Double check measurements and calculation, nope still end up with 56cc.</p>\n<p><!-- /wp:paragraph --></p>\n<p><!-- wp:paragraph --></p>\n<p>Contacted the vendor with this issue and they wanted photos. Bugger, I'd reassembled the chainsaw. Pulled the relevant bits off it again and photographed the measurement process (riveting stuff looking at a series of vernier caliper measurements, I declined to photograph the calculation). Vendor was now off to contact the factory. Never heard of it they said.Someone must have put the wrong chainsaw into the box was the claim (picture large bovine testicles). We have no more in stock said the vendor (apart from three ads still online all claiming stock levels &gt; 10). Please send it back, vendor offers to pay freight, and we'll refund you the full purchase price.</p>\n<p><!-- /wp:paragraph --></p>\n<p><!-- wp:paragraph --></p>\n<p>OK, I'm a little peeved that after waiting for so long to get my purchase it wasn't what was advertised and I can make up my own stories so their explanations weren't a bonus and a full refund was pretty fair.</p>\n<p><!-- /wp:paragraph --></p>\n<p><!-- wp:paragraph --></p>\n<p>Bit of a hiccup with the return process, I'd started the chainsaw, even if I drained the fuel and oil I'd have to somehow arrange for all traces of the fuel to be cleaned before it could be shipped legally. Fuel and oil are considered dangerous goods according to Australia Post and a couple of freight companies I contacted.</p>\n<p><!-- /wp:paragraph --></p>\n<p><!-- wp:paragraph --></p>\n<p>Back to the vendor with the shipping problem. I was asked if I would accept the chainsaw, with it's undersized displacement as well as a partial refund. After some pondering, I decided to accept the partial refund and the chainsaw.</p>\n<p><!-- /wp:paragraph --></p>\n<p><!-- wp:paragraph --></p>\n<p><strong>Observations:</strong><br><br>The vendor essentially responded in a positive manner with regard to the issues. I'm pretty much not convinced that the vendor ran out of stock or someone put the wrong chainsaw into the box. That if I selected any other of the chainsaws they were selling that I wouldn't find exactly the same thing regarding incorrect displacement.</p>\n<p><!-- /wp:paragraph --></p>\n<p><!-- wp:paragraph --></p>\n<p>Yes, it's a cheap chainsaw. Did I really need a larger capacity chainsaw? Not really but bigger is better right? Is it good enough for what I want? Time will tell. (I haven't named the vendor as I feel it's academic, the issue is with the factory(s)). Be aware of the potential problem, ie buyer beware.</p>\n<p><!-- /wp:paragraph --></p>\n<p><!-- wp:paragraph --></p>\n<p><!-- /wp:paragraph --></p>",
            "author": {
                "name": "Rod"
            },
            "tags": [
            ],
            "date_published": "2020-11-17T11:41:22+08:00",
            "date_modified": "2026-02-13T12:08:17+08:00"
        },
        {
            "id": "https://sages.com.au/rodshed/update-3-the-chook-is-silenced-or-the-compact-flash-works.html",
            "url": "https://sages.com.au/rodshed/update-3-the-chook-is-silenced-or-the-compact-flash-works.html",
            "title": "update #3, the chook is silenced or the compact flash works",
            "summary": "With a little bit of tweaking, some reverse engineering, wire, vero board and a magnifying glass, the microbee boots from flash. Here's how I built the hardware interface. Here is where the interface will connect the the 128k coreboard. Note the three holes near the&hellip;",
            "content_html": "<p>With a little bit of tweaking, some reverse engineering, wire, vero board and a magnifying glass, the microbee boots from flash.</p>\n<p>Here's how I built the hardware interface.</p>\n<p>Here is where the interface will connect the the 128k coreboard. Note the three holes near the front right of the 34pin floppy drive socket, next to the '40' on the overlay.</p>\n<figure class=\"post__image\"><a href=\"http://sages.com.au/wordpress/wp-content/uploads/2010/03/IMG_1505.jpg\"><img loading=\"lazy\"  src=\"https://sages.com.au/rodshed/media/posts/11/IMG_1505.JPG\" alt=\"\" width=\"3456\" height=\"2592\" sizes=\"(max-width: 1920px) 100vw, 1920px\" srcset=\"https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1505-xs.JPG 640w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1505-sm.JPG 768w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1505-md.JPG 1024w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1505-lg.JPG 1366w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1505-xl.JPG 1600w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1505-2xl.JPG 1920w\"></figure></a></p>\n<p>Solder the 3 pin header onto the coreboard. You will need to invert the header as you can only solder it from the top of the pcb as the 34pin floppy connector prevents access to the solder side of the pcb.</p>\n<figure class=\"post__image\"><img loading=\"lazy\"  src=\"https://sages.com.au/rodshed/media/posts/11/IMG_1516.JPG\" alt=\"\" width=\"3456\" height=\"2592\" sizes=\"(max-width: 1920px) 100vw, 1920px\" srcset=\"https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1516-xs.JPG 640w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1516-sm.JPG 768w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1516-md.JPG 1024w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1516-lg.JPG 1366w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1516-xl.JPG 1600w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1516-2xl.JPG 1920w\"></figure>\n<p style=\"text-align: center;\"> </p>\n<p>Remove the plastic spacer from the three pin header. I applied gentle pressure with a pair of needle nose pliers and it just slid off.</p>\n<figure class=\"post__image\"><img loading=\"lazy\"  src=\"https://sages.com.au/rodshed/media/posts/11/IMG_1517.JPG\" alt=\"\" width=\"3456\" height=\"2592\" sizes=\"(max-width: 1920px) 100vw, 1920px\" srcset=\"https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1517-xs.JPG 640w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1517-sm.JPG 768w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1517-md.JPG 1024w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1517-lg.JPG 1366w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1517-xl.JPG 1600w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1517-2xl.JPG 1920w\"></figure>\n<p>The next two pictures were mockups to show what we were doing with the various headers so they aren't construction pics, rather just showing where things go.</p>\n<p>Single row ( 20 pin ) r/a header mounted ( tip, make sure you solder all of the pins, not just a couple to hold it in place while you take pictures. I spent some time trying to work out what was wrong after i forgot to solder all of the pins )</p>\n<figure class=\"post__image\"><img loading=\"lazy\"  src=\"https://sages.com.au/rodshed/media/posts/11/IMG_1506.JPG\" alt=\"\" width=\"3456\" height=\"2592\" sizes=\"(max-width: 1920px) 100vw, 1920px\" srcset=\"https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1506-xs.JPG 640w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1506-sm.JPG 768w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1506-md.JPG 1024w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1506-lg.JPG 1366w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1506-xl.JPG 1600w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1506-2xl.JPG 1920w\"></figure>\n<p>Three pin header fitted to pins 36, 38 &amp; 40 next to existing 34 pin floppy connector.</p>\n<figure class=\"post__image\"><img loading=\"lazy\"  src=\"https://sages.com.au/rodshed/media/posts/11/IMG_1507.JPG\" alt=\"\" width=\"3456\" height=\"2592\" sizes=\"(max-width: 1920px) 100vw, 1920px\" srcset=\"https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1507-xs.JPG 640w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1507-sm.JPG 768w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1507-md.JPG 1024w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1507-lg.JPG 1366w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1507-xl.JPG 1600w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1507-2xl.JPG 1920w\"></figure>\n<p>This is where I soldered the right angle header, you can just make out the three pins from the straight header at the bottom right of the other header.</p>\n<figure class=\"post__image\"><img loading=\"lazy\"  src=\"https://sages.com.au/rodshed/media/posts/11/IMG_1518.JPG\" alt=\"\" width=\"3456\" height=\"2592\" sizes=\"(max-width: 1920px) 100vw, 1920px\" srcset=\"https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1518-xs.JPG 640w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1518-sm.JPG 768w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1518-md.JPG 1024w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1518-lg.JPG 1366w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1518-xl.JPG 1600w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1518-2xl.JPG 1920w\"></figure>\n<p>fit another piece of 5 way straight header to a piece of 8 hole by 2 hole vero board as shown below. I found the right angle socket made a good holder to prevent finger burn ;)</p>\n<p>Note the piece of vero board needs to clear the plastic holder of the right angle header so a test fit is required before soldering things together</p>\n<figure class=\"post__image\"><a href=\"http://sages.com.au/wordpress/wp-content/uploads/2010/03/IMG_1519.jpg\"><img loading=\"lazy\"  src=\"https://sages.com.au/rodshed/media/posts/11/IMG_1519.JPG\" alt=\"\" width=\"3456\" height=\"2592\" sizes=\"(max-width: 1920px) 100vw, 1920px\" srcset=\"https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1519-xs.JPG 640w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1519-sm.JPG 768w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1519-md.JPG 1024w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1519-lg.JPG 1366w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1519-xl.JPG 1600w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1519-2xl.JPG 1920w\"></figure></a></p>\n<p>this is where the small piece of vero board needs to fit ( this pic still has the plastic header on the straight header which is actually removed prior to this stage. )</p>\n<figure class=\"post__image\"><img loading=\"lazy\"  src=\"https://sages.com.au/rodshed/media/posts/11/IMG_1514.JPG\" alt=\"\" width=\"3456\" height=\"2592\" sizes=\"(max-width: 1920px) 100vw, 1920px\" srcset=\"https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1514-xs.JPG 640w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1514-sm.JPG 768w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1514-md.JPG 1024w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1514-lg.JPG 1366w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1514-xl.JPG 1600w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1514-2xl.JPG 1920w\"></figure>\n<p>This pic shows the header/connectors all together. I used the right angle socket as an alignment guide to hold things in the right place as i soldered the vero board to the 3 straight header pins. Note care need to be taken that you don't apply to much heat and cause the solder to holding the stright header pins to the pcb to melt.</p>\n<figure class=\"post__image\"><img loading=\"lazy\"  src=\"https://sages.com.au/rodshed/media/posts/11/IMG_1521.JPG\" alt=\"\" width=\"3456\" height=\"2592\" sizes=\"(max-width: 1920px) 100vw, 1920px\" srcset=\"https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1521-xs.JPG 640w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1521-sm.JPG 768w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1521-md.JPG 1024w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1521-lg.JPG 1366w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1521-xl.JPG 1600w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1521-2xl.JPG 1920w\"></figure>\n<p>An overhead shot of the right angle header and 5 pin extension that has been made from the veroboard addon thingy.</p>\n<figure class=\"post__image\"><img loading=\"lazy\"  src=\"https://sages.com.au/rodshed/media/posts/11/IMG_1522.JPG\" alt=\"\" width=\"3456\" height=\"2592\" sizes=\"(max-width: 1920px) 100vw, 1920px\" srcset=\"https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1522-xs.JPG 640w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1522-sm.JPG 768w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1522-md.JPG 1024w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1522-lg.JPG 1366w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1522-xl.JPG 1600w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1522-2xl.JPG 1920w\"></figure>\n<p>Mount another piece of veroboard onto the right angle socket as shown below. You need to take care that there is enough clearance between the veroboard and the floppy controller chip so it is possible to unplug the veroboard. I trimmed the left hand side of the veroboard to only have three rows with no pins. I then used some tinned copper wire soldered onto the unused rows to clamp the ide cable. I think this till change to use some sort of proper cable clamp before I finalise this.</p>\n<figure class=\"post__image\"><img loading=\"lazy\"  src=\"https://sages.com.au/rodshed/media/posts/11/IMG_1523.JPG\" alt=\"\" width=\"3456\" height=\"2592\" sizes=\"(max-width: 1920px) 100vw, 1920px\" srcset=\"https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1523-xs.JPG 640w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1523-sm.JPG 768w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1523-md.JPG 1024w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1523-lg.JPG 1366w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1523-xl.JPG 1600w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1523-2xl.JPG 1920w\"></figure>\n<p>This next part is a bit fiddly. I used some wire wrap wire ( just because I had some ) to connect the three straight pin header to the 5 pin extension header on the veroboard. Once again a bit fiddly as to much heat will unsolder the pins from the coreboard pcb. if you look carefully you'll see the deliberate wiring mistake where I crossed two wires over. Numbering the pins on the vero board from left to right ( looking as per the pic below ) pin 1 -&gt; pin 4, pin 2 -&gt; pin 5, pin 3 -&gt; pin 6, gnd ( all of the odd numbered floppy connector pins are gnd ) -&gt; pin7 and ( not shown in pic ) +5v ( i used pin 14 of ic27 ) -&gt; pin 8.</p>\n<p>I've described this wiring only relative to the small piece of veroboard. The wiring table described later has a pin numbering scheme relative to the 25 way socket/plug combination that you've just built.</p>\n<figure class=\"post__image\"><img loading=\"lazy\"  src=\"https://sages.com.au/rodshed/media/posts/11/IMG_1527.JPG\" alt=\"\" width=\"3456\" height=\"2592\" sizes=\"(max-width: 1920px) 100vw, 1920px\" srcset=\"https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1527-xs.JPG 640w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1527-sm.JPG 768w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1527-md.JPG 1024w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1527-lg.JPG 1366w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1527-xl.JPG 1600w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1527-2xl.JPG 1920w\"></figure>\n<p>It boots :)</p>\n<figure class=\"post__image\"><img loading=\"lazy\"  src=\"https://sages.com.au/rodshed/media/posts/11/IMG_1528.JPG\" alt=\"\" width=\"3456\" height=\"2592\" sizes=\"(max-width: 1920px) 100vw, 1920px\" srcset=\"https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1528-xs.JPG 640w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1528-sm.JPG 768w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1528-md.JPG 1024w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1528-lg.JPG 1366w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1528-xl.JPG 1600w ,https://sages.com.au/rodshed/media/posts/11/responsive/IMG_1528-2xl.JPG 1920w\"></figure>\n<p>Wiring information. The simple CF pinouts are from left to right looking from the rear of the bee. Pin 1 of the simple CF interface aligns with Pin1 of the 128k coreboard X2 connector ( see mbee-8342-4-01 cct diagram ). The IDE pins as standard IDE. There are several gnd pins on the IDE connector, the ones chosen aren't critical, just evenly spaced accross the connector.</p>\n<table border=\"1\" cellspacing=\"0\" cellpadding=\"0\">\n<tbody>\n<tr>\n<td valign=\"top\" width=\"160\">Simple CF PIN</td>\n<td valign=\"top\" width=\"160\">Microbee coreboard Pin</td>\n<td valign=\"top\" width=\"160\">IDE pin</td>\n<td valign=\"top\" width=\"160\">Description</td>\n</tr>\n<tr>\n<td valign=\"top\" width=\"160\">1</td>\n<td valign=\"top\" width=\"160\">1</td>\n<td valign=\"top\" width=\"160\">17</td>\n<td valign=\"top\" width=\"160\">D0</td>\n</tr>\n<tr>\n<td valign=\"top\" width=\"160\">2</td>\n<td valign=\"top\" width=\"160\">3</td>\n<td valign=\"top\" width=\"160\">15</td>\n<td valign=\"top\" width=\"160\">D1</td>\n</tr>\n<tr>\n<td valign=\"top\" width=\"160\">3</td>\n<td valign=\"top\" width=\"160\">5</td>\n<td valign=\"top\" width=\"160\">13</td>\n<td valign=\"top\" width=\"160\">D2</td>\n</tr>\n<tr>\n<td valign=\"top\" width=\"160\">4</td>\n<td valign=\"top\" width=\"160\">7</td>\n<td valign=\"top\" width=\"160\">11</td>\n<td valign=\"top\" width=\"160\">D3</td>\n</tr>\n<tr>\n<td valign=\"top\" width=\"160\">5</td>\n<td valign=\"top\" width=\"160\">9</td>\n<td valign=\"top\" width=\"160\">9</td>\n<td valign=\"top\" width=\"160\">D4</td>\n</tr>\n<tr>\n<td valign=\"top\" width=\"160\">6</td>\n<td valign=\"top\" width=\"160\">11</td>\n<td valign=\"top\" width=\"160\">7</td>\n<td valign=\"top\" width=\"160\">D5</td>\n</tr>\n<tr>\n<td valign=\"top\" width=\"160\">7</td>\n<td valign=\"top\" width=\"160\">13</td>\n<td valign=\"top\" width=\"160\">5</td>\n<td valign=\"top\" width=\"160\">D6</td>\n</tr>\n<tr>\n<td valign=\"top\" width=\"160\">8</td>\n<td valign=\"top\" width=\"160\">15</td>\n<td valign=\"top\" width=\"160\">3</td>\n<td valign=\"top\" width=\"160\">D7</td>\n</tr>\n<tr>\n<td valign=\"top\" width=\"160\">9</td>\n<td valign=\"top\" width=\"160\">17</td>\n<td valign=\"top\" width=\"160\">35</td>\n<td valign=\"top\" width=\"160\">A0</td>\n</tr>\n<tr>\n<td valign=\"top\" width=\"160\">10</td>\n<td valign=\"top\" width=\"160\">19</td>\n<td valign=\"top\" width=\"160\">33</td>\n<td valign=\"top\" width=\"160\">A1</td>\n</tr>\n<tr>\n<td valign=\"top\" width=\"160\">11</td>\n<td valign=\"top\" width=\"160\">21</td>\n<td valign=\"top\" width=\"160\">36</td>\n<td valign=\"top\" width=\"160\">A2</td>\n</tr>\n<tr>\n<td valign=\"top\" width=\"160\">12</td>\n<td valign=\"top\" width=\"160\">23</td>\n<td valign=\"top\" width=\"160\">Nc</td>\n<td valign=\"top\" width=\"160\">/port40</td>\n</tr>\n<tr>\n<td valign=\"top\" width=\"160\">13</td>\n<td valign=\"top\" width=\"160\">25</td>\n<td valign=\"top\" width=\"160\">23</td>\n<td valign=\"top\" width=\"160\">/xwr</td>\n</tr>\n<tr>\n<td valign=\"top\" width=\"160\">14</td>\n<td valign=\"top\" width=\"160\">27</td>\n<td valign=\"top\" width=\"160\">25</td>\n<td valign=\"top\" width=\"160\">/rd</td>\n</tr>\n<tr>\n<td valign=\"top\" width=\"160\">15</td>\n<td valign=\"top\" width=\"160\">29</td>\n<td valign=\"top\" width=\"160\">Nc</td>\n<td valign=\"top\" width=\"160\">Clk</td>\n</tr>\n<tr>\n<td valign=\"top\" width=\"160\">16</td>\n<td valign=\"top\" width=\"160\">31</td>\n<td valign=\"top\" width=\"160\">Nc</td>\n<td valign=\"top\" width=\"160\">/m1</td>\n</tr>\n<tr>\n<td valign=\"top\" width=\"160\">17</td>\n<td valign=\"top\" width=\"160\">33</td>\n<td valign=\"top\" width=\"160\">Nc</td>\n<td valign=\"top\" width=\"160\">/iorq</td>\n</tr>\n<tr>\n<td valign=\"top\" width=\"160\">18</td>\n<td valign=\"top\" width=\"160\">35</td>\n<td valign=\"top\" width=\"160\">Nc</td>\n<td valign=\"top\" width=\"160\">/halt</td>\n</tr>\n<tr>\n<td valign=\"top\" width=\"160\">19</td>\n<td valign=\"top\" width=\"160\">37</td>\n<td valign=\"top\" width=\"160\">Nc</td>\n<td valign=\"top\" width=\"160\">Fside</td>\n</tr>\n<tr>\n<td valign=\"top\" width=\"160\">20</td>\n<td valign=\"top\" width=\"160\">39</td>\n<td valign=\"top\" width=\"160\">1</td>\n<td valign=\"top\" width=\"160\">/jlatch</td>\n</tr>\n<tr>\n<td valign=\"top\" width=\"160\">21</td>\n<td valign=\"top\" width=\"160\">36</td>\n<td valign=\"top\" width=\"160\">Nc</td>\n<td valign=\"top\" width=\"160\">/int</td>\n</tr>\n<tr>\n<td valign=\"top\" width=\"160\">22</td>\n<td valign=\"top\" width=\"160\">38</td>\n<td valign=\"top\" width=\"160\">37 (ide-cs0)</td>\n<td valign=\"top\" width=\"160\">/port60</td>\n</tr>\n<tr>\n<td valign=\"top\" width=\"160\">23</td>\n<td valign=\"top\" width=\"160\">40</td>\n<td valign=\"top\" width=\"160\">Nc</td>\n<td valign=\"top\" width=\"160\">Ieo1</td>\n</tr>\n<tr>\n<td valign=\"top\" width=\"160\">24</td>\n<td valign=\"top\" width=\"160\">Gnd</td>\n<td valign=\"top\" width=\"160\">2,22,40</td>\n<td valign=\"top\" width=\"160\">Gnd</td>\n</tr>\n<tr>\n<td valign=\"top\" width=\"160\">25</td>\n<td valign=\"top\" width=\"160\">+5v</td>\n<td valign=\"top\" width=\"160\">38 (ide-/cs1)</td>\n<td valign=\"top\" width=\"160\">+5v</td>\n</tr>\n</tbody>\n</table>\n<p>I use a standard floppy power connector to provide +5 and gnd to the CF-IDE adaptor. I picked up +5 and GND from IC52, rear most 5v reg on coreboard. The other reg on the coreboard provides power for the dram.</p>\n<p>The Software and boot roms are slightly tweaked versions of Kalvis Duckmanton's CF/IDE bios</p>\n<p>Big thanks you the Kalvis and Stewart for their work, systems and advise.</p>\n<p>I'm in the process of uploading my mods back into the CVS system Kalvis has so we can keep the system software in a managed system.</p>\n<p>I'll post up again once I've done this with any relevant notes/instructions for the software.</p>\n<p>I'm also waiting on a couple of other CF cards. So far this has worked ok with a sandisk 32M CF card. A no name 1G card doesn't appear to work nor does an 8M canon CF card.</p>",
            "author": {
                "name": "Rod"
            },
            "tags": [
            ],
            "date_published": "2010-04-02T12:11:05+08:00",
            "date_modified": "2026-02-13T13:47:24+08:00"
        },
        {
            "id": "https://sages.com.au/rodshed/update-2-compact-flash-addon-deathly-quiet-but-no-smoke-this-time.html",
            "url": "https://sages.com.au/rodshed/update-2-compact-flash-addon-deathly-quiet-but-no-smoke-this-time.html",
            "title": "update #2 compact flash addon, deathly quiet but no smoke this time",
            "summary": "Well,having sorted out the smoke :) I managed to convince one of my original floppy drives to become a 'was' floppy drive. it is no more, it's deceased. Where the smoke came from. It must have been under some pressure because there was a lot&hellip;",
            "content_html": "<p>Well,having sorted out the smoke :) I managed to convince one of my original floppy drives to become a 'was' floppy drive. it is no more, it's deceased.</p>\n<p>Where the smoke came from. It must have been under some pressure because there was a lot of smoke!</p>\n<figure class=\"aligncenter size-medium wp-image-97\"><a href=\"http://westnet.net.au/sages/IMG_1486.jpg\"><img loading=\"lazy\"  title=\"IMG_1486\" src=\"https://sages.com.au/rodshed/media/posts/10/IMG_1486-300x225.jpg\" alt=\"\" width=\"300\" height=\"225\" sizes=\"(max-width: 1920px) 100vw, 1920px\" srcset=\"https://sages.com.au/rodshed/media/posts/10/responsive/IMG_1486-300x225-xs.jpg 640w ,https://sages.com.au/rodshed/media/posts/10/responsive/IMG_1486-300x225-sm.jpg 768w ,https://sages.com.au/rodshed/media/posts/10/responsive/IMG_1486-300x225-md.jpg 1024w ,https://sages.com.au/rodshed/media/posts/10/responsive/IMG_1486-300x225-lg.jpg 1366w ,https://sages.com.au/rodshed/media/posts/10/responsive/IMG_1486-300x225-xl.jpg 1600w ,https://sages.com.au/rodshed/media/posts/10/responsive/IMG_1486-300x225-2xl.jpg 1920w\"></figure></a></p>\n<p>Having recently had a big clean up, throwing out several 3.5\" drives in the process, I eventually unearthed a couple. One of which worked a treat. Just had to refit a connector on the floppy cable to allow for the 34 pin on the drive being upside down and sideways to the previous drive &lt;sigh&gt;. It's a one third height drive so it's rattling a bit in the case ( old drive was a half height ). But all is now good again.</p>\n<p>My 8 (new) 41256 dram chips arrived so I added them to the core board as per the 512k upgrade instructions by Peter Broughton. I did get caught out a little bit as the floppy drive died in the middle of all of this, my ancient eyes and shaking hand produced a dry joint ( solder ) and the PAL on the coreboard was from a CIAB which didn't support dual dram banks. I had made a variation on the 512k upgrade way back in the '80s that compnesated for this but only for a single dram bank up to 256k. So luckily the other coreboard I had was complete with the required PAL.</p>\n<p>I've also completed the 6.7 MHz speed mod.</p>\n<p>I decided to try and use the PJB system along with the IDE/CF bootroms and bios code modified by Kalvis Dukmanton as a base. So I've now switched from my original code, bios and boot roms to this.</p>\n<p>The bootrom is ok as is for the moment but it, along with the bios, will need a little tweak as my CF mod uses the 8 bit data xfer mode rather than the traditional 16 data mode.</p>\n<p>I'm just working through the h/w interface ( physical side of things ) for a CF ( only ) ide adaptor and a few of the s/w things.</p>\n<p>Keeping with the simple and cheap as possible theme, i'm using a ide to cf adaptor from ebay, some standard 40 pin ide cable from a PC, some vero board and some single row header. It should all fit onto a 128k coreboard ( 8342 ).</p>\n<p>Bare board where the header will be fitted.</p>\n<figure class=\"aligncenter size-medium wp-image-93\"><a href=\"http://westnet.net.au/sages/IMG_1500.jpg\"><img loading=\"lazy\"  title=\"IMG_1500\" src=\"https://sages.com.au/rodshed/media/posts/10/IMG_1500-300x225.jpg\" alt=\"\" width=\"300\" height=\"225\" sizes=\"(max-width: 1920px) 100vw, 1920px\" srcset=\"https://sages.com.au/rodshed/media/posts/10/responsive/IMG_1500-300x225-xs.jpg 640w ,https://sages.com.au/rodshed/media/posts/10/responsive/IMG_1500-300x225-sm.jpg 768w ,https://sages.com.au/rodshed/media/posts/10/responsive/IMG_1500-300x225-md.jpg 1024w ,https://sages.com.au/rodshed/media/posts/10/responsive/IMG_1500-300x225-lg.jpg 1366w ,https://sages.com.au/rodshed/media/posts/10/responsive/IMG_1500-300x225-xl.jpg 1600w ,https://sages.com.au/rodshed/media/posts/10/responsive/IMG_1500-300x225-2xl.jpg 1920w\"></figure></a></p>\n<p>Right angle header, left hand end will have small piece of vero board with extra pins to pick up pins 36, 38 &amp; 40, gnd and maybe +5v that are on the other row next to the 34 pin connector.</p>\n<figure class=\"aligncenter size-medium wp-image-94\"><a href=\"http://westnet.net.au/sages/IMG_1501.jpg\"><img loading=\"lazy\"  title=\"IMG_1501\" src=\"https://sages.com.au/rodshed/media/posts/10/IMG_1501-300x225.jpg\" alt=\"\" width=\"300\" height=\"225\" sizes=\"(max-width: 1920px) 100vw, 1920px\" srcset=\"https://sages.com.au/rodshed/media/posts/10/responsive/IMG_1501-300x225-xs.jpg 640w ,https://sages.com.au/rodshed/media/posts/10/responsive/IMG_1501-300x225-sm.jpg 768w ,https://sages.com.au/rodshed/media/posts/10/responsive/IMG_1501-300x225-md.jpg 1024w ,https://sages.com.au/rodshed/media/posts/10/responsive/IMG_1501-300x225-lg.jpg 1366w ,https://sages.com.au/rodshed/media/posts/10/responsive/IMG_1501-300x225-xl.jpg 1600w ,https://sages.com.au/rodshed/media/posts/10/responsive/IMG_1501-300x225-2xl.jpg 1920w\"></figure></a></p>\n<p>Right angle socket under vero board, just visible at left. vero board needs to be this short so that it clears the FDC to allow it to be unplugged. Also need to keep the height down so it clears the top of the case</p>\n<figure class=\"aligncenter size-medium wp-image-95\"><a href=\"http://westnet.net.au/sages/IMG_1502.jpg\"><img loading=\"lazy\"  title=\"IMG_1502\" src=\"https://sages.com.au/rodshed/media/posts/10/IMG_1502-300x225.jpg\" alt=\"\" width=\"300\" height=\"225\" sizes=\"(max-width: 1920px) 100vw, 1920px\" srcset=\"https://sages.com.au/rodshed/media/posts/10/responsive/IMG_1502-300x225-xs.jpg 640w ,https://sages.com.au/rodshed/media/posts/10/responsive/IMG_1502-300x225-sm.jpg 768w ,https://sages.com.au/rodshed/media/posts/10/responsive/IMG_1502-300x225-md.jpg 1024w ,https://sages.com.au/rodshed/media/posts/10/responsive/IMG_1502-300x225-lg.jpg 1366w ,https://sages.com.au/rodshed/media/posts/10/responsive/IMG_1502-300x225-xl.jpg 1600w ,https://sages.com.au/rodshed/media/posts/10/responsive/IMG_1502-300x225-2xl.jpg 1920w\"></figure></a></p>\n<p>Where i think 'll mount the CF-ide adaptor or ontop of the next connector space to the right, closer to the DIN connector. Give or tack a smidgeon, the CF bracket mounting holes are the same spacing as the x3/x4 15 way sockets for the SCC serial ports. So it should be possible to mount the CF holder on a couple of spacers and have it accessable from the rear of the case.</p>\n<figure class=\"aligncenter size-medium wp-image-96\"><a href=\"http://westnet.net.au/sages/IMG_1503.jpg\"><img loading=\"lazy\"  title=\"IMG_1503\" src=\"https://sages.com.au/rodshed/media/posts/10/IMG_1503-300x225.jpg\" alt=\"\" width=\"300\" height=\"225\" sizes=\"(max-width: 1920px) 100vw, 1920px\" srcset=\"https://sages.com.au/rodshed/media/posts/10/responsive/IMG_1503-300x225-xs.jpg 640w ,https://sages.com.au/rodshed/media/posts/10/responsive/IMG_1503-300x225-sm.jpg 768w ,https://sages.com.au/rodshed/media/posts/10/responsive/IMG_1503-300x225-md.jpg 1024w ,https://sages.com.au/rodshed/media/posts/10/responsive/IMG_1503-300x225-lg.jpg 1366w ,https://sages.com.au/rodshed/media/posts/10/responsive/IMG_1503-300x225-xl.jpg 1600w ,https://sages.com.au/rodshed/media/posts/10/responsive/IMG_1503-300x225-2xl.jpg 1920w\"></figure></a></p>\n<p>Not shown are the cabling between the cf-ide adaptor and the vero board. Nor the power cable for the CF. most likely i'll use a standard floppy power connector and plug into the cf-ide adaptor direct or I'll add another small regulator.</p>",
            "author": {
                "name": "Rod"
            },
            "tags": [
            ],
            "date_published": "2010-03-23T13:43:13+08:00",
            "date_modified": "2026-02-13T12:07:51+08:00"
        },
        {
            "id": "https://sages.com.au/rodshed/update-1-microbee-compact-flash-and-magic-smoke.html",
            "url": "https://sages.com.au/rodshed/update-1-microbee-compact-flash-and-magic-smoke.html",
            "title": "update #1 microbee compact flash and magic smoke",
            "summary": "Well the magic smoke escaped from the power supply. This stopped procedings for a couple of days while we sorted out the issue. Decided to replace the original mid '80s power supply with a new one. Got back to working with the CF and have&hellip;",
            "content_html": "<p>Well the magic smoke escaped from the power supply.</p>\n<p>This stopped procedings for a couple of days while we sorted out the issue.</p>\n<p>Decided to replace the original mid '80s power supply with a new one.</p>\n<p>Got back to working with the CF and have got the 8 bit data interface mode to work at last.</p>\n<p>So now we have the full capacity of the CF available with a trivial hardware interface. I priced some CF sockets ~ $9ea and some CF breakout boards ~$25ea (ouch).</p>\n<p>So it looks like a CF to IDE adaptor from ebay at ~$2-$5 ea is a bargain.</p>\n<p>Now looking at which way to go with the software, roll my own or tweak some existing code to suit.</p>\n<p>Suppose it depends if it's the journey or the destination that's important :)</p>",
            "author": {
                "name": "Rod"
            },
            "tags": [
            ],
            "date_published": "2010-03-16T11:54:04+08:00",
            "date_modified": "2026-02-13T12:07:38+08:00"
        },
        {
            "id": "https://sages.com.au/rodshed/microbee-simple-compact-flash-interface-the-beginning.html",
            "url": "https://sages.com.au/rodshed/microbee-simple-compact-flash-interface-the-beginning.html",
            "title": "microbee simple compact flash interface, the beginning",
            "summary": "Have been playing with my microbee and looking at a simple compact flash interface. Not 100% sure if I'll continue with it as is or alter it. The simple interface uses an 8 bit data bus. Downside is that it effectively halves the capacity of&hellip;",
            "content_html": "<p>Have been playing with my microbee and looking at a simple compact flash interface.</p>\n<p>Not 100% sure if I'll continue with it as is or alter it.</p>\n<p>The simple interface uses an 8 bit data bus. Downside is that it effectively halves the capacity of the compact flash, given their price and size for cpm use it isn't really a handicap. However the interface is trivial.</p>\n<p>I used a CF to IDE adaptor, an IDE cable, a 40 pin dil header and socket and some wire. It's plugged into the 128k ram coreboard where the SCC would sit, if fitted.</p>\n<figure class=\"aligncenter size-medium wp-image-81\"><img loading=\"lazy\"  title=\"IMG_1478\" src=\"https://sages.com.au/rodshed/media/posts/8/IMG_1478-300x225.jpg\" alt=\"\" width=\"300\" height=\"225\" sizes=\"(max-width: 1920px) 100vw, 1920px\" srcset=\"https://sages.com.au/rodshed/media/posts/8/responsive/IMG_1478-300x225-xs.jpg 640w ,https://sages.com.au/rodshed/media/posts/8/responsive/IMG_1478-300x225-sm.jpg 768w ,https://sages.com.au/rodshed/media/posts/8/responsive/IMG_1478-300x225-md.jpg 1024w ,https://sages.com.au/rodshed/media/posts/8/responsive/IMG_1478-300x225-lg.jpg 1366w ,https://sages.com.au/rodshed/media/posts/8/responsive/IMG_1478-300x225-xl.jpg 1600w ,https://sages.com.au/rodshed/media/posts/8/responsive/IMG_1478-300x225-2xl.jpg 1920w\"></figure>\n<figure class=\"aligncenter size-medium wp-image-80\"><a href=\"http://sages.com.au/wordpress/wp-content/uploads/2010/03/IMG_1477.jpg\"><img loading=\"lazy\"  title=\"IMG_1477\" src=\"https://sages.com.au/rodshed/media/posts/8/IMG_1477-300x225.jpg\" alt=\"\" width=\"300\" height=\"225\" sizes=\"(max-width: 1920px) 100vw, 1920px\" srcset=\"https://sages.com.au/rodshed/media/posts/8/responsive/IMG_1477-300x225-xs.jpg 640w ,https://sages.com.au/rodshed/media/posts/8/responsive/IMG_1477-300x225-sm.jpg 768w ,https://sages.com.au/rodshed/media/posts/8/responsive/IMG_1477-300x225-md.jpg 1024w ,https://sages.com.au/rodshed/media/posts/8/responsive/IMG_1477-300x225-lg.jpg 1366w ,https://sages.com.au/rodshed/media/posts/8/responsive/IMG_1477-300x225-xl.jpg 1600w ,https://sages.com.au/rodshed/media/posts/8/responsive/IMG_1477-300x225-2xl.jpg 1920w\"></figure></a></p>\n<figure class=\"aligncenter size-medium wp-image-82\"><img loading=\"lazy\"  title=\"IMG_1479\" src=\"https://sages.com.au/rodshed/media/posts/8/IMG_1479-300x225.jpg\" alt=\"\" width=\"300\" height=\"225\" sizes=\"(max-width: 1920px) 100vw, 1920px\" srcset=\"https://sages.com.au/rodshed/media/posts/8/responsive/IMG_1479-300x225-xs.jpg 640w ,https://sages.com.au/rodshed/media/posts/8/responsive/IMG_1479-300x225-sm.jpg 768w ,https://sages.com.au/rodshed/media/posts/8/responsive/IMG_1479-300x225-md.jpg 1024w ,https://sages.com.au/rodshed/media/posts/8/responsive/IMG_1479-300x225-lg.jpg 1366w ,https://sages.com.au/rodshed/media/posts/8/responsive/IMG_1479-300x225-xl.jpg 1600w ,https://sages.com.au/rodshed/media/posts/8/responsive/IMG_1479-300x225-2xl.jpg 1920w\"></figure>\n<p>I knocked up a simple bit of test code to see what sort of speed I could read the data from the compact flash card.</p>\n<p>Here's a couple of hitech screen dumps with two different CF cards. First half is a hex dump and 2nd half is ascii or hex for non printable characters.</p>\n<figure class=\"aligncenter size-medium wp-image-83\"><img loading=\"lazy\"  title=\"IMG_1480\" src=\"https://sages.com.au/rodshed/media/posts/8/IMG_1480-300x225.jpg\" alt=\"\" width=\"300\" height=\"225\" sizes=\"(max-width: 1920px) 100vw, 1920px\" srcset=\"https://sages.com.au/rodshed/media/posts/8/responsive/IMG_1480-300x225-xs.jpg 640w ,https://sages.com.au/rodshed/media/posts/8/responsive/IMG_1480-300x225-sm.jpg 768w ,https://sages.com.au/rodshed/media/posts/8/responsive/IMG_1480-300x225-md.jpg 1024w ,https://sages.com.au/rodshed/media/posts/8/responsive/IMG_1480-300x225-lg.jpg 1366w ,https://sages.com.au/rodshed/media/posts/8/responsive/IMG_1480-300x225-xl.jpg 1600w ,https://sages.com.au/rodshed/media/posts/8/responsive/IMG_1480-300x225-2xl.jpg 1920w\"></figure>\n<figure class=\"aligncenter size-medium wp-image-84\"><img loading=\"lazy\"  title=\"IMG_1481\" src=\"https://sages.com.au/rodshed/media/posts/8/IMG_1481-300x225.jpg\" alt=\"\" width=\"300\" height=\"225\" sizes=\"(max-width: 1920px) 100vw, 1920px\" srcset=\"https://sages.com.au/rodshed/media/posts/8/responsive/IMG_1481-300x225-xs.jpg 640w ,https://sages.com.au/rodshed/media/posts/8/responsive/IMG_1481-300x225-sm.jpg 768w ,https://sages.com.au/rodshed/media/posts/8/responsive/IMG_1481-300x225-md.jpg 1024w ,https://sages.com.au/rodshed/media/posts/8/responsive/IMG_1481-300x225-lg.jpg 1366w ,https://sages.com.au/rodshed/media/posts/8/responsive/IMG_1481-300x225-xl.jpg 1600w ,https://sages.com.au/rodshed/media/posts/8/responsive/IMG_1481-300x225-2xl.jpg 1920w\"></figure>\n<p>The data rate is (very) roughly 3 sec for 25kbytes. This was with unoptimised C code and glancing at a watch for timing.</p>\n<p>An alternative place to connect to the coreboard on the microbee is near the 34 pin floppy drive connector. Applied Technology used the same coreboard for their hard drive model and have overlaid a 40 pin connector next to the 34 pin connector. One side is used by the floppy connector but half of the pins, with all the signals needed except +5v are available by adding a 20pin single row header.</p>\n<p>The downside of the simple 8 bit interface is that it isn't so simple to move the CF card onto a linux/windoze system to move data back and forth without writing special drivers.</p>\n<p>Will post up progress and info on here as I get to it.</p>",
            "author": {
                "name": "Rod"
            },
            "tags": [
            ],
            "date_published": "2010-03-11T16:49:35+08:00",
            "date_modified": "2026-02-13T12:07:27+08:00"
        }
    ]
}
