Thanks Phillipe, I will take a look at ur documentation, and thanks for the work u did do (and try) on XaAES, there are not many who return alive.
I especially like ur work inside ARAnyM filesystem to control Hatari and hard shutdown/reboot. I did similar with ARAnyM, MiNT and FVDI configs inside ST filesytem, to be able to reboot different setups, including using (or not) MiNT, XaAES or MyAES, and TOS versions. I like how urs can control ARAnyM startup tho.
I just remember now, there is maybe another online documentation on removers wiki, I will see if I can find site and if I added any XaAES stuff.
OK there is links to tuts and stuff, the sparemint wiki content is changed since I did original additions, find it here:http://removers.free.fr/wikipendium/wak ... wiki=XaAES
re: my development stuff
.. and stuff previously online (not on web.archive.org). Its on a chrashed 1TB NTFS5 formatted drive that may still be reserectable (last time I checked it need a fsck from windows), the (usb+e-sata) drives power died during read, so it may not be destroyed.
I too would like to see some of that data back online, as I'm missing my v2 MyAES windfram dev, z(orro)Pro winfram, and an a modified ers windfram (Eric Reboux), not to mention all the XaAES stuff (gradients, skins, widgets, themes) and TeraDesk stuff (50 icon beta on SF, missing a full 200+ deskicons resource and config), and the icon sets I had online.
Unfortunately I dont have a desktop setup anywhere available, and I use 12v in a vehicle, which is why I use the Raspberry Pi's. After quick check (and download) BeeKey/BeePi, I see it is very similar to my MiNT 1.16 HD image I used for initial XaAES testing and gradient/extended texture dev, with full sparemint. The 1TB also have filesystems for: 1.17 afros, 1.17 afros-update (minimal cli scripting grep,sed, etc plus apps), 1.18 compact sparemint (reduced filesystem structure/hack) and 1.18 GentooMiNT.
re: dev setup
However, I dont like what is happening with Jessie on Pi (boot times, kswap, bloat), and I want "real feel" ST out of Pi, which is why I started original AFROS-update project (there are lots people still not like CLI on ST) but want MiNT power and flexibility. I am almost there, I have updated (firmware + wifi) of Amibian sd-image, just need to compile new ARAnyM with new SCSI and NativeFeatures support. I can get Amibian boot with wifi in about 3 sec's, but atm any apt-get upgrade seriously screws up its performance.
Although I dont have decktop PC setup, I do have the 2 machines with some dev on them, and one has (AFROS) SLAX "livecd". ATM because of Jessie (and presumably SystemD) issues, I look at Voidlinux, which can USB + LiveCD boot on PC. I also have customised LXDE with 2nd "top-menu" taskbar that is very Atari-ish (incl. ST console font). I intend to use this as cross-dev environment with Vincents Ubuntu sources, of which I found useful OS on BerryBoot that can used their arm/source repos.
I am keeping an eye on TOSemu (github), Apollo 68080, EmuTOS and want to update FVDI as soon as possible. And I am conjuring a way to use NF to allow Chrome browser from host OS (without protocol connection like VNC etc), while looking at making AES linux lib using SDL1.2
As u can see, this has to be done on (mostly reliable) Pi in 12v situation, which is differcult to say the least (cramped, confined, limited Amps), but doable.
Most of the ideas I had from time of Extended Texture and Gradients dev work (like gradient design tool) are still fresh in my head, so its a matter of getting things done. For this was the same reason for AFROS-update is first place, an off the shelf, get started "running" portable ST envorinment, with both ST and cross-tools development expansion as option.
BTW I also look at CF 5480 & Apollo 68080 CPU in ARAnyM, and useing UAE-ARM core (for Pi).
B4 I am willing to do any major work, I need to address data integrity & heat issues with Pi, and use of "portable home directory". PiDrive with BerryBoot should solve most of the problems (but this I have to save for). I have stockpiled a few of new sd-card for dev & release work, and I have permanent space for archives.
So I'm almost there, its just difficult without a permanent setup, 24/7, Desktop machines, and "office" space.
Will edit this later