This is my Apple //e Raspberry pi all version Operating system running linapple at fullscreen at bootup distributed under ReactiveMicro Wiki have a look here for more information:
This is my Apple //e Raspberry pi all version Operating system running linapple at fullscreen at bootup distributed under ReactiveMicro Wiki have a look here for more information:
Please support the defense of Ukraine.
Direct or via Unclutter App
No Ads.
No Trackers.
No Social Media.
All Content Locally Hosted.
Built on Free Software.
We have complied with zero government requests for information.
~ Est. 1999 ~
A pillar of corporate stability since the second millenium.
© 1999-2999 Tom Owad
Very cool thank you!
please could you confirm the default user and login, and where do the disk images go?
does it boot from hard disk images? .Po files?
TIA!
I dont think you need a user or login, but otherwhise needed use your googledrive account. It's for Raspberry pi an Operating System you have to unrar it and upload it inside the SD card with win32diskimager for example under windows.
If you need more help let me know.
You can put the disk image under Apple II folder in desktop and find them by pressing F3 inside the emulator F1 gives you an help.
press .. to navigate back of folder press desktop to find the image if you put them in desktop. Sorry for the confusion i just got the sens of your post right now!!!
ID: pi
PASS:raspberry
And thank you for download
Does your distro have the same issue with permissions that building Linapple/Linapple-Pie under X11 has? After a while it makes its configuration files read-only, and will only load its one default disk.
Which Linapple did you use? There are lots of forks. All of them have some kind of issue for me.
I don't know about the "making configuration files read only" bit, but there was another config file bug I just fixed that would erase the contents of the user configuration file. If you're having issues with command-line options and /or configuration files, I'm happy to see about helping to fix such things, since I've been hacking on that code a bit anyway.
I'm using the one from the LinApple IIGitHub org; are there others that are also under active development and are not downstream versions of that one? (I have no clue myself; this one on GitHub is just the one I came across when looking for an Apple II emulator to use for software development.)
ah, nice! So it really was deleting the config file - great to know that that has been addressed. Thank you!
The one I was using was https://github.com/dabonetn/linapple-pie which hasn't been updated in a couple of years.
No, it was leaving the config file there, just removing the contents. (If anything, more confusing.)
I see a number of related repos that seem to focus on adding "pie"-specific features to linapple. Just out of curiousity, what are these?
I suspect they are for RetroPie, the multi-system gaming emulation platform for the Raspberry Pi. RetroPie are still suggesting people use a rather ancient version, possibly because they're in the UK and the Apple II was too expensive to be popular as a games machine there. It's a shame, because with an updated Linapple and 4am's Total Recall you'd have some pretty good games.
Oh, sorry; I should have been more clear. I was wondering, what are the particular features that these forks add? Are they things that should not be in linapple itself for some reason?
The reason for the number of forks is that the original project was more or less abandoned for several years. So multiple people created their private forks, focusing on whatever they were interested in. The https://github.com/linappleii repo is finally a collaborative project and currently seems to be working well. Not super fast paced, but it's steadily moving along and accepting contributing patches. AFAIK all relevant changes from linapple-pie were also merged there (i.e. the option to exit the emulator using a joystick button, which now is a configurable option). So, to me linappleii seems to be the way ahead.
Ok, that confirms that I'm using and contributing to the most appropriate repo. Thanks for clarifying that.