This is a read-only snapshot of the ComputerCraft forums, taken in April 2020.
tom2018's profile picture

LUA [ERROR] bios:267: Attempt to write global

Started by tom2018, 07 November 2012 - 11:11 AM
tom2018 #1
Posted 07 November 2012 - 12:11 PM
http://pastebin.com/3emVUXH7
how do i fix?
Kingdaro #2
Posted 07 November 2012 - 12:24 PM
On line 2, try changing
os.pullevent = os.pullEventRaw
to
os.pullEvent = os.pullEventRaw
PixelToast #3
Posted 07 November 2012 - 12:32 PM
On line 2, try changing
os.pullevent = os.pullEventRaw
to
os.pullEvent = os.pullEventRaw
yea, the OS table is protected, that sould work
Espen #4
Posted 07 November 2012 - 01:21 PM
If I run your code I don't get any error, everything seems to work fine.
What exactly doesn't work? Did you maybe just forget to enable http?

On line 2, try changing
os.pullevent = os.pullEventRaw
to
os.pullEvent = os.pullEventRaw
yea, the OS table is protected, that sould work
That typo wouldn't produce an error though.
It's just that if he'd use the correct spelling for the rest of his program, then he'd be using the original pullEvent instead of the one he defined at the top (the one with the typo), i.e. it'd just get ignored.
Kingdaro #5
Posted 07 November 2012 - 01:38 PM
In earlier CC versions, an error would pop up if you tried to write to a global table or overwrite a global variable/function. I assume he's using tekkit, because if he weren't, it wouldn't be erroring, like you said.
tom2018 #6
Posted 07 November 2012 - 01:39 PM
On line 2, try changing
os.pullevent = os.pullEventRaw
to
os.pullEvent = os.pullEventRaw
fixed it

yes this is on tekkit but I play on both tekkit and 1.3.2 version(i hate update 1.4)
Espen #7
Posted 07 November 2012 - 01:51 PM
Oh right, Tekkit. I always forget that, sorry. :P/>/>
Don't hate 1.4 though, there are a lot of nice things in there and you'll want to update eventually, hehe.
Kingdaro #8
Posted 07 November 2012 - 02:39 PM
Oh right, Tekkit. I always forget that, sorry. :P/>/>
Don't hate 1.4 though, there are a lot of nice things in there and you'll want to update eventually, hehe.
Seconded.

@tom, You're lucky 1.46 is only a version compatibility change, but wait 'till dan makes diamond computers. :D/>/>
ElvishJerricco #9
Posted 07 November 2012 - 03:29 PM
On line 2, try changing
os.pullevent = os.pullEventRaw
to
os.pullEvent = os.pullEventRaw
fixed it

yes this is on tekkit but I play on both tekkit and 1.3.2 version(i hate update 1.4)

I'm curious as to what there is to hate about 1.4
PixelToast #10
Posted 07 November 2012 - 07:22 PM
On line 2, try changing
os.pullevent = os.pullEventRaw
to
os.pullEvent = os.pullEventRaw
fixed it

yes this is on tekkit but I play on both tekkit and 1.3.2 version(i hate update 1.4)

I'm curious as to what there is to hate about 1.4
i hated updating to everything above 1.7 beta, after that i just quit updating all together and now i use technic p_p
back then aether and BTW were compatable and it was so fun, then they changed the terrain generation and the maps corrupted
i miss beta ;(
tom2018 #11
Posted 08 November 2012 - 08:43 AM
I would rather keep to minecraft 1.3.2 and not have mod updates because mine craft is not really the game I bought(or hoped for) back in alpha.
now can this thread be closed its getting off topic.
PixelToast #12
Posted 08 November 2012 - 08:56 AM
report it, or just let it collect dust

and my favorite minecraft version is 1.7 ;( le good ol days
ElvishJerricco #13
Posted 08 November 2012 - 11:11 AM
report it, or just let it collect dust

and my favorite minecraft version is 1.7 ;( le good ol days

I'm still not understanding what's bad about the newer stuff.
PixelToast #14
Posted 08 November 2012 - 11:20 AM
report it, or just let it collect dust

and my favorite minecraft version is 1.7 ;( le good ol days

I'm still not understanding what's bad about the newer stuff.
[offtopic]
things being incompatable and getting more complicated (specifically Aether and BTW)
[/offtopic]