Mr Robot

I didn't need to do anything You've no idea I don't believe you have either. Put up or shut up Finally!

I've no idea what 'it' is, is it another secret? You know what they say... Put up or shut up.

So the grand total of your contribution to the thread is "I know but it's a secret and I'm not telling you", you know nothing but it sounds better than "I don't know"

The question still hasn't been answered. The reason this open source project has closed source firmware is because of 'politics' but no one has said what politics, it may as well just say 'reasons'. It's a non-answer. Why did Jakub decide to close his source? Those sorts of things don't usually happen for no reason.

I don't always get what I want. That's life I don't care how you know this. If people contributed and didn't assert that contribution, they didn't contribute. If Jakub decided to close his source and others had contributed, if they didn't prosecute at the time they were free to fork and continue updating, no one did.

My first post says that Jakub Husak says politics is the reason later source is not available. I do And this is where you try to use buzzword bingo and go wrong. Any other contributions from the author are not a fork, neither are any contributions from anyone to the main source tree. Nobody has forked anything (except Jakub Husak, and he released his updated source fork) If you are not credited, in the source, on the cvs commit history or in the changelog, it doesn't matter if you contributed, you don't exist. Will you please stop derailing my thread. I don't need lessons on the GPL, I think I know it better than you. All that condescending linking to the four freedoms and other irrelevant crap is just passive aggressive posturing, stop deflecting, own the mistake and move on.

Right. I have now done that. Every file is ©Jakub Kruszona-Zawadzki no other author is credited anywhere. There is no changelog. It is the sole property of Jakub Kruszona-Zawadzki. If anyone else worked on the code, they did not assert any ownership over it. NOW I am saying that if Jakub Kruszona-Zawadzki wants to close source his software after releasing v2.5 and only release v3 and upwards as closed source binary only, that is entirely up to him, it's his. I wish he wouldn't but he has that right. All of this word salad is incorrect, please delete it. No one worked on the firmware for this project (and if anyone did, they made no such claim in the source code). Your point is not just wrong, it is also moot.

I make no such assumption. I merely said if the original author wants to close his source he can. I did not say that that is what had happened and that Jakub Kruszona-Zawadzki was the only contributor. To make that claim I'd have had to have checked every source code header to see who is credited and I havent done that, have you?

My new screen arrived today... Perfect fit, that isn't necessarily a good thing but it does look good Still waiting on the new UNO

Looks like you just doubled your locations to publicise

You really hate being told you are wrong don't you! If you release as GPL, notice you spelled your name wrong and fix it, changing the licence while you are at it, your name will now forever be spelled wrong in the GPL version and right in the closed source version. You are trying really really hard to make this difficult and it isn't. Yes, that is EXACTLY what I said at first. I have posted nothing to mitigate my original CORRECT post. You were wrong, just own it and move on.

No thats not how it works. If I release v2.5 as GPL. It's now forever GPL. If I release v2.6, version 2.5 is still GPL, no matter what I licence 2.6 If I release v2.5 as GPL and I then release a bugfix of v2.5 and call it v2.6 but choose to licence it as closed source and private. I am not breaking the terms of the licence. It's all my code I do not have to give away those bug fixes if I don't want to. If I release v2.5 and _you_ release a bugfix of it and call it v2.6 you have to licence it as GPL too. If I then take _your_ code and produce v2.7 I cannot close the source unless I take your code out. If any of the code written by someone other than you has been GPL'd, you have to release as GPL too, but if _all_ the code is yours, regardless of whether you released it as GPL or not, it is your to re-licence as you see fit.

Close but no cigar. The bottom sheared off the front panel during print, probably need a solid infill for that little part, it'll make it stronger. The silver strip doesn't fit properly, and the bottom door is a bit tight. I need to redesign the front bits mating surfaces and give the door a little room, and maybe make it a bit thicker. I can't test fit my sdrive, the cable is wired out the wrong side, it looks about right, the pegs on the bottom door fit perfectly and the SDM slides in to the hole, I just cant push it all the way with the cable there, I have more bits on order from afar which I shall use to make a new sdrive and test fit before I print again.

As @DrVenkman says, use drivesort or something similar. The Atari menus use the files in the order they were written to the disk, drivesort writes them one by one in order, just to fix the problem.

Yes that is how it works. If I licence something as GPL and release it, then decide the next version isn't going to be GPL'd that's up to me as the author. I am the only one who has that right as I am the original author. I cannot rescind the licence for earlier versions I had already licensed, but I don't have to release newer versions with the same licence. Of course, anyone else releasing a fork of my code has to licence the same as my original licence, they don't get to change the licence until they remove any code created and licensed by others as GPL. Privilege of being the original author. This is how you get shareware software that goes commercial, the original authors change the licence.

Well if it's the original author who is keeping later revisions closed that's up to him, I wonder why he changed his mind? I thought it would be a nice idea to make an sio2sd with a larger screen but I guess this is why lothareks new larger one still only has a 2 line screen.

You lookin' at me?

There are quite a few and people like tix are adding new ones all the time. They tend to get lost in this forum or the 5200 hacks sub forum.

An 8-bit hacks sub forum would be good too, it's pretty conspicuous by its absence in the hacks forum

It's all GPL 2 or newer

That's v2.5, better than nothing but the changelog since then is like 3.0rc1 -> 3.0rc2 Fixed LCD handling bug (RC1 doesn't work without LCD) Added "swap" command (K3 in VDISK MODE swaps mappings of D1 and D2) Added "rol4" command (K4 in VDISK MODE moves mappings D1<D2<D3<D4<D1) Added "ror4" command (SHIFT+K4 in VDISK MODE moves mappings D1>D2>D3>D4>D1) 3.0rc2 -> 3.0rc3 Fixed xex-loader. Added new key combinations OPTION+SELECT and OPTION+START to turbo-loader (new turbo IRQ locations: $700 and $500). 3.0rc3 -> 3.0rc4 Fixed SIO routines (mainly incompatibilities with software made for TOMS turbo) 3.0rc4 -> 3.0rc5 Changes in SD initialization routines ("card init error" should appear much less frequently) SD speed is choosen automatically (SD speed option was removed) Fixed card insertion/removal logic Added ability to go directly to setup when card is not present (using dbl-shift) 3.0rc5 -> 3.1rc1 Virtual disks simplification Fixed turbo routines - emulation of Top-Drive (aka TOMS) and XF551 More compatible SIO routines (return to timings from version 2.x - slower, but more reliable) Ordinary files and empty disks are emulated as SD disks if possible (size < 90k) 3.1rc1 -> 3.1rc2 Fixed bug in file handle (mainly XEX files) Fixed warmstart issue in xex-loader There is a v2.5 modified for an smd version here https://github.com/jhusak/sio2sd_2.5_smd Looks like none of the v3 sources were released.

Lovely cuppa rosie

So, is there a reason this open source project has closed source firmware? I’ve been looking everywhere and all I can find is binary releases and some old code that doesn’t work with current hardware the author on GitHub said there was some politics around it.

Like I said, altogether way too many addons That's awesome Bernd!

This 800XL has altogether too many things added to it