its kinda cool too bad the deot stuff is in japanese :<
Its in Chinese, not Japanese.
shows what I know, I get them confused
Just confirmed; Updating the DEOT OS via the regular channels is fine, as its files are installed in the “launcher” directory.
Upon trying to update “launcheroriginal” (according to the instructions linked above), it expects the directory to be be “launcher”, which is populated by the DEOT variant.
This in turn will result in the DEOT OS being overwritten by the pushed update files invoked by doing a launcher update.
I just keep a backup of the DEOT OS, in a separate folder (eg, “launcherbak” that can be used as a recovery if needed.
This would mean that updates wouldn’t always end up properly updating the correct launcher. I’m going to experiment with SSHing into the game shell, changing launcher’s directory I want to update to “launcher” (ie not launcheroriginal or launchergo", update the launcher, then restore the name to whatever it was before.
By far, this is not elegant at al, but for now it will do.
If there’s any interest, I was thinking of making a clean image with:
- Clockwork OS 0.4 DEOT with menu items to change to the stock launcher (as per above)
- Global volume hotkeys
- Mupen64+ Installed and configured
- Retroarch 1.7.9 with XMB menu, and correct key bind time outs fixed/mame direction keys functional
- Doom, Hexen and Heretic configured, and ready to have WAD files added to games directory
- I will potentially comment out the launcher update in the “list_page.py”, to ensure no one accidentally breaks their installation, and launcher go - does anyone actually use this?? (Of course you can just remove the # tag, to restore it if you want)
- A clean DEOT launcher backed up, in case anything goes wrong, or if anyone wants to fiddle with it/reverse engineer its files.
These seem to be the biggest things that people have had problems with getting to work from what I’ve read and responded to. I’ll be making it myself anyway, as a quick way to restore an image as a backup.
consider me interested, I have the DEOT loaded, looks cool, not sure what some of the menu options are for
I see this has freedoom, which doesnt seem to allow it to read other *.wad files (I loaded the ones from my normal .4 microsd) still just sees freedoom 1
The doom/heretic wrappers are in another directory. You need to make a custom action file to make it run. There’s a tutorial in the link below, however it’s out of date, given the change in directory structure since it was written.
Probably best to continue any queries there, since it’s a bit off topic.
The image I’ll be putting up soon will have a bunch of action files pre configured, ready to have WAD files injected.
ill wait, for now I went back to my 64GB .4 normal setup (was using a 128 I had extra to test DEOT)
the other areas of the DEOT setup, that are in chinese, will these ever be translated to english? just wondering
They’re just edge lord faux hacker screens. Nothing you’re really missing out on. As far as I can tell, all the text is basically drawn in the screens. So I mean, I could fiddle and get an english translation? But probably isn’t really worth it to be honest.
In other news, I’ve fiddled with my custom image for about a week. Got it to a “useable” standard.
- DEOT 1.0 installed, with the launcher switcher as listed above.
- Global Volume (not brightness) installed - stepping changed to 4 from 10.
- Mupen64+ installed as per the this forum’s thread.
- Retroarch 1.7.9 installed. Decided to change the default Retroarch Menu to the GLes one, as it had far less compatibility problems compared to XMB switching drivers, and is still fast yet prettier than RGUI. Haven’t bothered setting up the MAME Directional keys. Didn’t get time to test it/redownload BIOSes. I did however reconfigure the Cave Story default key set to be far more friendly for non light key users.
- Doom, Hexen, Heretic and Strife action files created, with basic input configuration set for non lighter users. (you can change it via the config within the system) It’s found in Play>Misc>ChocoDM and Heretic. (You can use the ChocoDM wrapper to run most of the WAD files. Heretic, Hexen and Strife use a separate one, and is found in the Heretic folder. (couldn’t think of something better to name it)
- I didn’t bother commenting out the launcher update scripts, or changing to Launcher Go; again to maintain as much authenticity to the original image. Stock DEOT OS 1.0 has however been updated to the latest version as of 18/10/19. Basically, just don’t be silly and try to update the launcher unless you know how to fix it up. In short, it’s an absolute pain to update anything other than the stock DEOT OS. You can kinda get away with the stock DEOT OS, just having to change two files. Lets cross that bridge when it happens.
- I didn’t bother doing a backup of a clean DEOT OS launcher. I did a test deliberately breaking the launcher boot sequence, and tried to restore it with a folder backup/restore via SSH. It did nothing. So I removed the backup to save space. I have however kept a backup of the stock Retroarch 1.7.6 in case you’re not happy with 1.7.9 and want to change it back. (found in .config/retroarch.original
- In addition, I’ve restored the Utilities folder that was removed from DEOT OS from some reason. You can now use DingUX Commander and Bean. I also added my own tiny script to empty the mail box, in case you don’t like seeing the “You’ve got mail” notification upon booting up.
Some side notes:
Retroarch wise, it’s just as unstable as ever using Lima drivers with 1.7.9, so just use the FBTurbo software driver.
Realistically, nothing in retroarch benefits that much from using Lima. Mupen 64+ does though. That’s set up using the settings as per the thread in the forums. I’ve only tested it with Banjo Kazooie.
Some of the icons aren’t there for emulators. I was going to include a custom skin with some things added, but changed my mind; trying to keep this as much a clean image as possible.
It’s a 4GB compresses bzip file. Decompress it (16GB) before burning the img file fo an SD card. You’ll need at least a 16GB SD card; just like the stock DEOT OS image. You can expand it to take up space on a larger card using the regular means. I didn’t use a script in this, since I’m only using 16GB SD cards to test, but could do so in a future version if needed.
Here’s the link. It is live.
Let me know how it goes.
(ah crud! Just burnt a copy to test, and just noticed two BIOS files still present, and a stray WAD file! Argh! I’ll deal with that in a few days)
I have made a new thread to continue discussions regarding this here:
Oh it looked like some sort of playable thing, the mail section and all, but again not being able to read Chinese, I didn’t know
downloading it now, i’ll keep you posted
ok what are you using to make the sd, I have used etcher and win32diskimager, neither results in a working microsd
Check to make sure you’ve decompressed the bzip file first. That said, if you could write the original DEOT image, this should be the same. Hmm. Strange.
I use etcher personally.
DM me with screen shots etc of what’s happening. I can see this conversation clogging up this thread. I’ll start a new thread later.
thatsd just it, each time I try my gameshell crashes (doesnt even power on),
I’m starting a new thread. I’ll tag you @John_Bach. This is getting ridiculously messy.
Also, @John_Bach, you can edit your posts if you ever need to add something to what you’ve posted, instead of making another post a few hours later; especially if no one else has replied between posts.
In other news, I’m in the process of uploading a new image. The leftover BIOS and Rims I forgot to remove will be removed. It will take the place of the previous one. I probably should put version numbers/dates. Yup. I’m going to do that. Give it a few hours.
I have made a new thread to continue discussions regarding this here:
ok sounds good, been having a time with my Gameshell, wouldnt boot after swapping cards, car wasnt readable (using same hardware to write cards I been using), tested on a linux box, not recognized (the deot one I mean) I had a previous deot on it (the one posted elsewhere)
Hey @Veronica (and anyone else in the know), just wondering re: pushed launcher updates. Is the DEOT OS Launcher being maintained at the same rate as the original clockwork OS Launcher?
Just wondering for a custom image I’ve made; whether or not to have DEOT OS as my base launcher that can be updated, or having it as a side loaded one; with the stock Clockwork OS as the base.
Besides some extra home screen items, shifted icon locations, and removed/hidden features (utilities, skin chooser and Launcher Go), it appears to be very similar.
Just bringing up a previous query: Will DEOT edition front and rear shells ever be available to buy by themselves? We wouldn’t have to worry about the shortages of other parts, or waiting to have them in stock. I’m quite interested, and I’m sure a few others
people would be too!
Last time I saw the commit tree of the main launcher repo, DEOT is behind the main head
Hurm. That is annoying. Thanks for the info @Petrakis.
Looks like it’s probably better to just extract whatever assets we can from the DEOT UI etc, and inject them into a modified vanilla Clockwork OS image, if we want the “Thematic UI”
Heck, it would make it a hell of a lot easier.
On a side note, I wonder where @Veronica has gone to? They were quite active here, initiating threads, and helping people. They even got the new member of the month badge. Some things will just remain a mystery.