The einSDein interface is quite versatile. At its connector it is simply a very basic set of Z80 bus and control lines.
RD, WR,IORQ, M1. A[0..7] and D[0..7].
So it shouldn't be hard to interface to other Z80-based computers, right?
Here is an issue 2 einSDein wired up to a Video Genie, the UK version of the popular TRS-80 clone made by the EACA corporation. It is variously known by other names such as the Dick Smith System 80, PMC-80, TRZ-80 and so on.
The expansion connector breakout was custom made one rainy afternoon, and while it looks a mess it does the business.
A small machine language program was written to perform a directory listing of the SD card. This was converted into a cassette image format, then loaded using PlayCAS.
Here is a video on arguably the best known video distribution channel in the western hemisphere. It shows the aforementioned program pulling a listing from the interface pictured above.
The more eagle-eyed may recognise that the programs on the card are not Genie programs. This is being attended to, dear reader. I have written a converter program which takes cassette image format files and spits out a raw-ish binary dump which can be loaded from SD card. It only works with 'system' or machine language programs at the moment, but a gander at the Level II ROM reference book will soon see to that restriction.
Armed with a copy of MAME and its fine debugger I will spend a few quality hours stepping through the cassette loading functions to see what I need to do in order to craft a work-alike in order to load BASIC from the SD card.
I have a few Mercurial repositories in BitBucket that I wanted to convert to Git, after undergoing something of a conversion myself. After a lot of onlinesearchengining for automated solutions, and being disappointed with the amount of effort involved, I came up with a rather nifty way of doing this without having to install and configure the HG command line tools. Sure enough, the hggit plugin sounds very quick and convenient - assuming you have HG installed. My way is undoubtedly clunky and a bit of a hack, but that's the way I like it, baby!
I will assume that if you want to do this you have a BitBucket account already set up and you have, or will soon have, a GitHub account. The GitHub account is only used temporarily.
Step 0. BitBucket
Rename the convertee BitBucket repo, unless you will give the new git-i-fied version a different name. Click the gear icon in the left hand panel on your repository details page to get to the repo settings page where this can be achieved.
Edit the repo name and click the large 'Save Repository Settings' button.
Step 1. GitHub.
Click on the '+' icon at the top right of your GitHub home page.
Select 'Import Repository'.
Enter the URL of the BitBucket repo you wish to convert.
Give a name to the GitHub copy. Choose anything, it won't live for long.
Begin the import by clicking the big green button.
You may be prompted to enter your BitBucket credentials. GitHub will not store these.
The repo will now be imported.
If there are questions about contributors, you can safely ignore them if you wish.
Step 2. BitBucket.
Select the Repositories button in the menu at the top of the page, and choose the Import option.
Enter the URL of the newly created GitHub repo.
Nominate a new name for the converted repo.
Click the 'Import Repository' button.
And that's it! This process has worked for me quite successfully on a number of projects.