Jump to content
  • Sky
  • Blueberry
  • Slate
  • Blackcurrant
  • Watermelon
  • Strawberry
  • Orange
  • Banana
  • Apple
  • Emerald
  • Chocolate
  • Charcoal


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Adorable-Catgirl

  1. Update: Zorya v2/Zorya NEO progress can be found here. Don't expect it to be released anytime soon, though.
  2. *His Also wot Edit: Just noticed this thread was in showcase. Probably shouldn't be in showcase.
  3. (Again, shoot me) Zorya v1.2.0 Zorya has been updated once again! What does it bring this time? Bugfixes Knowledge that this should be some of the last 1.x releases, I swear. v2 is coming. Cleaned up codebase some. Now you can get virtual device drivers! (000_vdev) Pointless addition to support patch versions.
  4. CC is a great place to start out with Minecraft computers, since you don't need to worry about a BIOS or OS.
  5. Ah, you're calling me a script kiddie. I mean, I could help out if I could understand you better and if you understood what you're getting into if you want to make an OS.
  6. If you wanted to make your own OS, you should really make it in an external editor (Like ST3 or Notepad++) and download it to the computer, or, better yet, test it in an OpenComputers VM like ocvm (Linux) or OCEmu (basically any desktop OS afaict). Anyways, it would mean you wouldn't need to install OpenOS, you could just download your files to the HDD using the OpenOS boot floppy and reboot to it.
  7. do you want to make an ass out or yourself? this is how you make an ass out of yourself. Also, what? Like, what do you mean you want people to teach you but you don't want to look at videos? If videos are a problem, then google is your friend. Lua ain't too hard to learn. also holy duck it's hard to decipher what the hell you're saying
  8. Have you ever wanted to encrypt something but couldn't afford a T2 data card? Well, look no further than icekey-lua and Igloo! Low Level: IceKey IceKey is the low level library. It's no RSA, but it should work for most purposes in OC. If you want to learn more about ICE, click here. Useful if you want to do more with the block cipher, rather than just encrypting files or whatnot. It can be found here. High Level: Igloo Igloo is the high level library, great for encrypting/decrypting files. Automatically uses a CBC and padding. It can be found here. PRs welcome!
  9. You never executed the loaded function on init.lua:13. Also, look at your print function in boot.lua. It won't work. You need to define w, h, cx, and cy outside of the "if not gpu then ... end" block.
  10. (leave a comment if you want to register an MMTI type) Multipurpose Media Type Identifier, Version 1.0 Purpose The MMTI provides a way to identify data types without an extension, and to differentiate files with the same extension. One can only make so many recognisable extensions with 4 latin characters. Some data is not to be used as a file, but still needs a way to be identified. Format An MMTI string takes the format of category/type. For example, a Lua script would be application/lua. A CPIO archive would be archive/cpio, etc. MMTI strings should only use US-ASCII characters. Unregistered MMTI strings MMTI strings that aren't registered should prefix the type with x-, such as application/x-zoryapkg. Categories As of Version 1.0, the following categories are available for use. application - Any type of format which is to be executed archive - Any type of format which is used to archive other files media - Any type of format which contains video or audio model - Any type of format which contains data used to construct a 3D model text - Any type of format which is used to transmit textual data message - Any type of format which is used to transmit data over a network other - Any type of format which is not covered in the other categories Registed MMTI types. MMTI type Extensions Registration date application/lua .lua 2019-7-30 application/lua-binary .luac 2019-7-30 application/lua-assembly .luas 2019-7-30 archive/binary-cpio .bcpio, .cpio 2019-7-30 archive/urf .urf 2019-7-30 media/dfpwm .dfpwm 2019-7-30 text/txt .txt 2019-7-30 application/json .json 2019-7-30 application/lua-table N/A 2019-7-30 text/ohml .ohml 2019-7-30
  11. .efi2 could probably be a CPIO archive. Entry point can be defined by a .cfg file in the root of the archive. Or, we could also check if it's a CPIO file or a Lua file. Dunno, it's up to you.
  12. uncpio is a rather simple binary CPIO extractor (File begins with 0x71C7 or 0xC771, made with cpio -oHbin). To acquire uncpio, run pastebin get YbrVjRwa /bin/uncpio.lua To use, make the directory you'll be extracting your CPIO archive to, cd into it, then run uncpio path/to/your/file.cpio And it will extract to the current directory. Currently only works in OpenOS, as far as I know.
  13. Fair. Also, we could use binary CPIO for bootable packages. That would probably be the best bet. It's standard and been around for a while. Also, OEFI v2 applications should end in `.efi2` to differentiate them from the OEFI v1 applications. OEFI v2 applications should also probably support a few basic arguments.
  14. So, some recommendations for OEFI v2: Storage of addresses in a binary format Maybe a standard set of commands for an OEFI shell? "oefi.loadfile(path)", which loads a file from the boot device Vendor prefixes on extensions to OEFI (ie "oefi.vendor.extensionmethod()") BIOS configuration space of 64 bytes, at the end of the EEPROM Maybe a network boot protocol? The OEFI library should be global unless booting in compatibility mode (for example, from an init.lua file) OEFI implementation must allow the OS to return Standard for passing kernel arguments (For things like Fuchas NT or Tsuki) Maybe a sample OEFI implementation? Must support compatibility mode, though maybe there can be an option to disable compatibility mode. Maybe a URF-based bootable package?
  15. (Shoot me if this is a necropost) Zorya has been updated! It now has a new, fancy installer that may still be visually buggy. It installs Zorya fine enough though. (And I plan to use it for my OS's installer.) Zorya 1.0 adds a few new features: OEFI support A new `zorya` library General improvements over 0.1. It's a feature, trust me. https://github.com/Adorable-Catgirl/Zorya-BIOS
  16. I'm using ocvm. I mainly use it because OCEmu has some weird issues, though ocvm seems to have some strange issues too.
  17. I was thinking about component IDs. Shouldn't they be minified? Like, "68ca0f59-ac2c-49f8-ba6a-3c4c7e5f069b" turns into a string of 16 bytes: {0x68, 0xCA, 0x0F, 0x59, 0xAC, 0x2C, 0x49, 0xF8, 0xBA, 0x6A, 0x3C, 0x4C, 0x7E, 0x5F, 0x06, 0x9B} Also, OEFI implementations need to have room for custom configuration, as something like Zorya needs some EEPROM space for knowing the device that the "zorya-module" and "zorya-cfg" folders are stored on. Maybe 64 bytes or so can be dedicated to custom config? 64 bytes should be plenty of space for basic configuration, yeah? 32 bytes would be too little, probably, as a component ID can only be shrunk down to 16 bytes. As for how to convert binary component ID to text component ID and back again: function binid_to_hexid(id) local f, r = string.format, string.rep return f(f("%s-%s%s", r("%.2x", 4), r("%.2x%.2x-", 3), r("%.2x", 6)), id:byte(1, 16)) end function hexid_to_binid(id) local lasthex = 0 local match = "" local bstr = "" for i=1, 16 do match, lasthex = id:match("%x%x", lasthex) bstr = bstr .. string.char(tostring(match, 16)) end return bstr end Otherwise, this looks pretty good.
  18. Also, I plan on adding DEFLATE support for URF and support for PolarisFS (From an OS I'm working on, Tsuki) if/when I get the chance.
  • Create New...

Important Information

By using this site, you agree to our Terms of Use and Privacy Policy.