Luca_S

On 8/21/2018 at 8:44 PM, ProgrammingRules said:

I really want to turn off a computer with this running...

Sorry for some reason I didn't get any notification of your reply.

What are you using to shutdown your computer? Using the shutdown program of OpenOS works perfectly fine.

Also can you please clarify what you want to do? If I understood correctly you have 1 monitor in a lower level of your house and one in a higher level and you want the higher one to mirror the lower one?

Do both monitors have the same size? If yes you might get away with just looping over all monitors, calling term.bind() and then calling your term operations, however I can't test that right now, I will do this in the evening and tell you if that works.

Also it might be a good idea download the file to /tmp instead of /, but that would require enough space in /tmp.

25 minutes ago, noahthegame said:

i allways forget how EEPROMS and OS's works a bios seach for any filesystem that have the file /init.lua right?

The default Lua bios boots by running init.lua on a filesystem. It first tries to boot from the filesystem which address is stored in the EEPROM data. If it can't find init.lua on that file system or init.lua code causes errors while being loaded it goes through all filesystems and boots the first one it can find with /init.lua on it

This BIOS allows you to choose the boot device by either using the arrow keys or clicking/touching the monitor.

When using the keyboard use Enter to boot, when using clicking/touching click an unselected entry to select it, click a selected entry to boot it.

If there is only one bootable medium, that medium is autobooted.

The default selected option is the last booted device.

This supports booting from filesystems, using /init.lua as an entry point or from drives(HDDs or Floppys in unmanaged mode), by loading code from the first sector until the first \0 character appears as lua code. (From what I've seen unmanaged drives are mostly ignored in OC, which is kinda sad.)

Screenshots:

To install: (This file contains the code needed to flash the BIOS as well as the BIOS code itself, it will ask before flashing it to the EEPROM)

pastebin run Cx4aTipt

5 minutes ago, noahthegame said:

may i add that nobody as told me exacly what to do insted, the complain i made in the start of this thread was meant as a qestion more then anything becuse i knew that somebody whould currect me

While it is not possible to tell you exactly what to do instead, here are a few things you should've done a little bit differently to make this more pleasant and helpful for everyone:

• Your title: "make opencomputers processors faster". You are asking a question in your post which you want answered, why not make that the title instead: "How do I increase or remove the limits of the CPU/RAM?"
  • This makes it easy at first glance for everyone to see what you try to accomplish
  • "make [...] processors faster" sounds like you are giving someone the command to do so, which is not good when asking questions.
  • What would've been even better is to ask a question in relation to your program(e.g. "How can I optimise a program for <this>?"), however that would require you to show the program to the community, which you seem unwilling to do so.(Also you should note that this decreases the chances of you getting help)
• Your post
  • You should've clarified better what your actual problem was. E.g. "This program(<link to program>) is running slow, I tried <this and that> to optimise it, but it doesn't seem to work. I would be grateful for any ideas"
• Your first reply: "right... how lovely... ONLY ONE COMPONENT CALL PER TICK!!! JESUS duckING CRIST... that most be a joke, right?
  • Screaming at people/Writing in all caps is not very well perceived by most and will not get you anywhere
  • This also doesn't add something really constructive to the discussion
  • Better would be something like: "This seems pretty slow. Is there any way to increase the component calls when in single player?"
  • I guess that reply was written in a lot of anger, but if you are angry at something, it might be better to write the post, not click submit, wait a few minutes until you've calmed down and think again if this post will be constructive in any way
• "so i can see that buffer api thing have the standart gpu functions so i give the infomation to the buffer (eg buffer.set(2,2,0xff0000, 0, " ")) and the buffer api will only do a gpu.set opration when it has to limting unnessary gpu.set's? is that how that works?". This was actually a pretty good post:
  • It shows that you've checked out the topic and know what you are talking about
  • It states a clear question
• The three posts here are a bit unnecessary and could've been put in one post asking "I've tried this: <code here> and it doesn't work. I have <this and that> problem."

These are just a few random thoughts about how you could've gotten/will get better help.

23 hours ago, noahthegame said:

... if i had 10 pence evrey time somebody Said that... i Got banned from reddit (i belive it was) in 4 days becuse of 4 poeple downvoted my qestion nobody Said anything. It's great to get reminded tho Thanks .  

2 hours ago, noahthegame said:

i whounder how many downvotes i need to be banned, i bet am going to find out

Doesn't that make you think if you should ask questions in a different way?

In CC you have to write your OS from /startup

In OC you have to write your OS from /init.lua (Assuming you have the default BIOS)

In CC if /disk/startup exists, it gets executed on Computer reboot

In OC if /mnt/[address]/autorun.lua exists, it get executed as soon as the hard drive/floppy gets inserted

In OC if you start an OS from scratch you do not have as many functions as in CC( Refer to this: http://ocdoc.cil.li/tutorial:custom_oses#what_s_available )

In CC pressing CTRL in edit will open a save/exit menu

In OC you need to press CTRL +  S to save and CTRL + W to close

I dont have to say much, my game randomly crashes with the following error:

Pastebin: pastebin.com/x9FmpvNi

thanks for Support,

Luca_S

Thanks, that was exactly what I searched

Hello Community,

I want to program my own OS for OC and have a problem: I don't know, how exactly the boot works. I tried to use component.anything() and it didn't worked, because the variable component doesn't exists. I can't use require('component') too. Any ideas to solve this problem?

Luca