BSOD? (Blue Screen Of Death)

Creator, on 09 March 2016 - 08:50 PM said:

Try running OmniOS one or two times :P/>/> . Also, this code.

Lyqyd, on 09 March 2016 - 10:19 PM said:

There was less than an hour between your (removed) bump post and your previous post. Be patient. You could start to consider bumping your topic after two or three weeks without a reply.

function os.bluscreen(errorMSG)
  <formatted error message>
  sleep(2)
  os.shutdown()
end

local err = error
error = function(...)
  local _, errorMSG = pcall(err, ...)
  <formatted error message>
  sleep(2)
  os.shutdown()
end

Sewbacca, on 09 March 2016 - 10:34 PM said:

Yes:

function os.bluscreen(errorMSG)
  <formatted error message>
  sleep(2)
  os.shutdown()
end

or:

local err = error
error = function(...)
  local _, errorMSG = pcall(err, ...)
  <formatted error message>
  sleep(2)
  os.shutdown()
end

term.setBackgroundColor( colors.blue )
term.clear()
os.pullEvent( tostring({}) )

crasher925, on 09 March 2016 - 10:42 PM said:

Sewbacca, on 09 March 2016 - 10:34 PM said:

Yes:

function os.bluscreen(errorMSG)
  <formatted error message>
  sleep(2)
  os.shutdown()
end

or:

local err = error
error = function(...)
  local _, errorMSG = pcall(err, ...)
  <formatted error message>
  sleep(2)
  os.shutdown()
end

i ran the first code and it gives me

bios:14: [string "bsod"]:2: unexpected symbol

i dont know much lua so can i get the full code for a BSOD

KingofGamesYami, on 09 March 2016 - 10:45 PM said:

I suspect you want this:

 term.setBackgroundColor( colors.blue ) term.clear() os.pullEvent( tostring({}) ) 

H4X0RZ, on 09 March 2016 - 10:52 PM said:

crasher925, on 09 March 2016 - 10:42 PM said:

Sewbacca, on 09 March 2016 - 10:34 PM said:

Yes:

function os.bluscreen(errorMSG)
  <formatted error message>
  sleep(2)
  os.shutdown()
end

or:

local err = error
error = function(...)
  local _, errorMSG = pcall(err, ...)
  <formatted error message>
  sleep(2)
  os.shutdown()
end

i ran the first code and it gives me

bios:14: [string "bsod"]:2: unexpected symbol

i dont know much lua so can i get the full code for a BSOD

Wow. This level of " being-spoonfed-and-still-not-getting-it" hurts. <formatted error message> is NO code. You have to replace it with code.

Also, if you don't know much Lua there's no need for an BSOD.

Creator, on 09 March 2016 - 10:58 PM said:

Congratulations on your 1000th post. Also, code I gave you works very well. Just modify the text.

Creator, on 09 March 2016 - 11:08 PM said:

Just change the text. Make a nice term.clear too.

Lupus590, on 10 March 2016 - 01:30 PM said:

do you have any Lua knowledge?

we generally prefer to teach people how to write their own programs over writing programs on demand.

crasher925, on 10 March 2016 - 12:24 PM said:

ok its been 12 hours can please i get some help here?

Lyqyd, on 09 March 2016 - 10:19 PM said:

Be patient. You could start to consider bumping your topic after two or three weeks without a reply.

KingofGamesYami, on 10 March 2016 - 03:52 PM said:

I can manually emulate the exact thing, word-for-word. Other than that, I'm not exactly sure what you want - all of that information is irrelevant to computercraft and debugging.

Spoiler

term.setBackgroundColor( colors.blue )
term.setTextColor( colors.white )
print( [[A problem has been detected and Windows has been shut down to prevent damage to your computer.

The problem seems to be caused by the following file: kbdhid.sys

MANUALLY_INITIATED_CRASH

If this is the first time you've seen this stop error screen, restart your computer.  If this screen appears again, follow these steps:

Check to make sure any new hardware software is properly installed.  If this is a new installation, ask your hardware or software manufacturer for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware or software.  Disable BIOS memory options such as caching or shadowing.  If you need to use safe mode to remove or disable components, restart your computer, press F8 to select Advanced Startup Options, and then select Safe Mode.

Technical Information:

*** STOP: 0x000000e2 (0x00000000, 0x00000000, 0x00000000, 0x00000000)

*** kbdhid.sys - Address 0x94efd1aa base at 0x94efb000 DateStamp 0x4a5bc705]] )
os.pullEvent( "key" )
os.shutdown()

local err = error
error = function(...)
  local _, errorMSG = pcall(err, ...)
  os.pullEventRaw = os.pullEvent
  <formatted error message>
  sleep(2)
  os.shutdown()
end

Sewbacca, on 10 March 2016 - 03:58 PM said:

KingofGamesYami, on 10 March 2016 - 03:52 PM said:

I can manually emulate the exact thing, word-for-word. Other than that, I'm not exactly sure what you want - all of that information is irrelevant to computercraft and debugging.

Spoiler

term.setBackgroundColor( colors.blue ) term.setTextColor( colors.white ) print( [[A problem has been detected and Windows has been shut down to prevent damage to your computer. The problem seems to be caused by the following file: kbdhid.sys MANUALLY_INITIATED_CRASH If this is the first time you've seen this stop error screen, restart your computer. If this screen appears again, follow these steps: Check to make sure any new hardware software is properly installed. If this is a new installation, ask your hardware or software manufacturer for any Windows updates you might need. If problems continue, disable or remove any newly installed hardware or software. Disable BIOS memory options such as caching or shadowing. If you need to use safe mode to remove or disable components, restart your computer, press F8 to select Advanced Startup Options, and then select Safe Mode. Technical Information: *** STOP: 0x000000e2 (0x00000000, 0x00000000, 0x00000000, 0x00000000) *** kbdhid.sys - Address 0x94efd1aa base at 0x94efb000 DateStamp 0x4a5bc705]] ) os.pullEvent( "key" ) os.shutdown()

you can put it into the function:

 local err = error error = function(...) local _, errorMSG = pcall(err, ...) os.pullEventRaw = os.pullEvent  sleep(2) os.shutdown() end 

So ever a error occures you get a Bluescreen

KingofGamesYami, on 10 March 2016 - 11:58 PM said:

You'd put it in the spot where the non-Lua code is (<formatted …)

… is actually a thing in Lua, since functions can take any number of arguments (regardless of how many are required).