The "General Games Chat" forum, which includes Retro Game Reviews, has been archived and is now read-only. You cannot post here or create a new thread or review on this forum.
"He's more man than machine" Says Obi-Wan Kenobi to Luke Skywalker in one of the Star Wars movies, but what if that machine that makes up most of Darth Vader was running on Windows?
0x0001 Incorrect function. Vader attempts to use his Jedi mind powers to stangle a failing commander, but end up putting a hole in his leg by turning his light sabre on
0x0002 The system cannot find the file specified. So there he is, confronting Luke for the first time in Cloud City, when his light sabre won't come on.
0x0005 Access is denied. Vaders lungs are denied access to his breathing aparatus, with near disasterous results.
0x0007 The storage control blocks were destroyed. No wonder he couldn't remember C3PO
0x0008 Not enough storage is available to process this command. I'm not sure that the Emperor would see this as a good excuse.
0x000A The environment is incorrect. All that sand on Tatooine plays havoc with his system.
0x0010 The directory cannot be removed. Buried deep within Vader is the good in him, as the Emperor failed to remove the directory, which Luke exploits in RotJ.
0x0014 The system cannot find the device specified. Another excuse for light sabre failure.
0x0015 The device is not ready. And again...
0x0016 The device does not recognize the command. And again... doesn't Vader look silly now?
0x001C The printer is out of paper. Which would only bother Vader when he went to the loo.
0x00x0024 Too many files opened for sharing. He would have been much more generous otherwise.
0x0036 The network is busy. This occured in A New Hope, and explains why his helmet was not as shiny as in the following movies, the network polisher was busy.
0x0037 The specified network resource or device is no longer available. Vader suddenly realises that Luke has hacked off his hand.
0x003B An unexpected network error occurred. For Vader, all errors are not only unexpected, but unacceptable.
0x0080 There are no child processes to wait for. So where did Luke and Leia go then...
0x03F1 The configuration registry database is corrupt. Like everything else in the Empire then.
0x047E The specified program requires a newer version of Windows. Unfortunately Vader was never able to upgrade to a purple light sabre.
0x0480 Cannot start more than one instance of the specified program. And he could only have one light sabre at a time too.
0x04B1 The device is not currently connected but it is a remembered connection. Vader does vaguelly remember his time as a Jedi.
0x057E Cannot create a top-level child window. Not being able to convert Luke to the Dark Side was actually pre-programmed.
0x06CF The string is too long. Vader comments on George Lucas' model, and why the ship is so low.
0x06F3 The stub is unable to get the remote procedure call handle. After loosing his hand, he couldn't handle anything.
0x0701 The user's account has expired. The Emperor programmed this in for when he was ready to replace Vader.
0x0001 Incorrect function. Vader attempts to use his Jedi mind powers to stangle a failing commander, but end up putting a hole in his leg by turning his light sabre on
0x0002 The system cannot find the file specified. So there he is, confronting Luke for the first time in Cloud City, when his light sabre won't come on.
0x0005 Access is denied. Vaders lungs are denied access to his breathing aparatus, with near disasterous results.
0x0007 The storage control blocks were destroyed. No wonder he couldn't remember C3PO
0x0008 Not enough storage is available to process this command. I'm not sure that the Emperor would see this as a good excuse.
0x000A The environment is incorrect. All that sand on Tatooine plays havoc with his system.
0x0010 The directory cannot be removed. Buried deep within Vader is the good in him, as the Emperor failed to remove the directory, which Luke exploits in RotJ.
0x0014 The system cannot find the device specified. Another excuse for light sabre failure.
0x0015 The device is not ready. And again...
0x0016 The device does not recognize the command. And again... doesn't Vader look silly now?
0x001C The printer is out of paper. Which would only bother Vader when he went to the loo.
0x00x0024 Too many files opened for sharing. He would have been much more generous otherwise.
0x0036 The network is busy. This occured in A New Hope, and explains why his helmet was not as shiny as in the following movies, the network polisher was busy.
0x0037 The specified network resource or device is no longer available. Vader suddenly realises that Luke has hacked off his hand.
0x003B An unexpected network error occurred. For Vader, all errors are not only unexpected, but unacceptable.
0x0080 There are no child processes to wait for. So where did Luke and Leia go then...
0x03F1 The configuration registry database is corrupt. Like everything else in the Empire then.
0x047E The specified program requires a newer version of Windows. Unfortunately Vader was never able to upgrade to a purple light sabre.
0x0480 Cannot start more than one instance of the specified program. And he could only have one light sabre at a time too.
0x04B1 The device is not currently connected but it is a remembered connection. Vader does vaguelly remember his time as a Jedi.
0x057E Cannot create a top-level child window. Not being able to convert Luke to the Dark Side was actually pre-programmed.
0x06CF The string is too long. Vader comments on George Lucas' model, and why the ship is so low.
0x06F3 The stub is unable to get the remote procedure call handle. After loosing his hand, he couldn't handle anything.
0x0701 The user's account has expired. The Emperor programmed this in for when he was ready to replace Vader.
Blimey! that al quaida gets about a bit, dunnee!
Its called the VaderY2K bug :)
Do not open the thread called Vader.exe because it is an EVIL VIRUS created by AL QUAIDA designed to fly your COMPUTER into a nearby OFFICE BLOCK!!!!!
Microsoftvader 2002 .... just think about it... your screensaver is a game. your background is an Automatic Playing movie of miniseries of Starwars... Oh That will be so much fun!
What makes it even more funny, is that Mircosoft will probably steal this idea now - along with the others - for their new OS.
heh heh heh :)
'your vader has recovered from a serious crash' - when vader goes spinning off at the end of new hope
'your vader has recovered from a serious crash' - when vader goes spinning off at the end of new hope
I'm not a Star Wars fan.. but it's funny :-D
Oh... and about you're tagline.. I'm not one yet (I don't think)
Oh... and about you're tagline.. I'm not one yet (I don't think)
"He's more man than machine" Says Obi-Wan Kenobi to Luke Skywalker in one of the Star Wars movies, but what if that machine that makes up most of Darth Vader was running on Windows?
0x0001 Incorrect function. Vader attempts to use his Jedi mind powers to stangle a failing commander, but end up putting a hole in his leg by turning his light sabre on
0x0002 The system cannot find the file specified. So there he is, confronting Luke for the first time in Cloud City, when his light sabre won't come on.
0x0005 Access is denied. Vaders lungs are denied access to his breathing aparatus, with near disasterous results.
0x0007 The storage control blocks were destroyed. No wonder he couldn't remember C3PO
0x0008 Not enough storage is available to process this command. I'm not sure that the Emperor would see this as a good excuse.
0x000A The environment is incorrect. All that sand on Tatooine plays havoc with his system.
0x0010 The directory cannot be removed. Buried deep within Vader is the good in him, as the Emperor failed to remove the directory, which Luke exploits in RotJ.
0x0014 The system cannot find the device specified. Another excuse for light sabre failure.
0x0015 The device is not ready. And again...
0x0016 The device does not recognize the command. And again... doesn't Vader look silly now?
0x001C The printer is out of paper. Which would only bother Vader when he went to the loo.
0x00x0024 Too many files opened for sharing. He would have been much more generous otherwise.
0x0036 The network is busy. This occured in A New Hope, and explains why his helmet was not as shiny as in the following movies, the network polisher was busy.
0x0037 The specified network resource or device is no longer available. Vader suddenly realises that Luke has hacked off his hand.
0x003B An unexpected network error occurred. For Vader, all errors are not only unexpected, but unacceptable.
0x0080 There are no child processes to wait for. So where did Luke and Leia go then...
0x03F1 The configuration registry database is corrupt. Like everything else in the Empire then.
0x047E The specified program requires a newer version of Windows. Unfortunately Vader was never able to upgrade to a purple light sabre.
0x0480 Cannot start more than one instance of the specified program. And he could only have one light sabre at a time too.
0x04B1 The device is not currently connected but it is a remembered connection. Vader does vaguelly remember his time as a Jedi.
0x057E Cannot create a top-level child window. Not being able to convert Luke to the Dark Side was actually pre-programmed.
0x06CF The string is too long. Vader comments on George Lucas' model, and why the ship is so low.
0x06F3 The stub is unable to get the remote procedure call handle. After loosing his hand, he couldn't handle anything.
0x0701 The user's account has expired. The Emperor programmed this in for when he was ready to replace Vader.
0x0001 Incorrect function. Vader attempts to use his Jedi mind powers to stangle a failing commander, but end up putting a hole in his leg by turning his light sabre on
0x0002 The system cannot find the file specified. So there he is, confronting Luke for the first time in Cloud City, when his light sabre won't come on.
0x0005 Access is denied. Vaders lungs are denied access to his breathing aparatus, with near disasterous results.
0x0007 The storage control blocks were destroyed. No wonder he couldn't remember C3PO
0x0008 Not enough storage is available to process this command. I'm not sure that the Emperor would see this as a good excuse.
0x000A The environment is incorrect. All that sand on Tatooine plays havoc with his system.
0x0010 The directory cannot be removed. Buried deep within Vader is the good in him, as the Emperor failed to remove the directory, which Luke exploits in RotJ.
0x0014 The system cannot find the device specified. Another excuse for light sabre failure.
0x0015 The device is not ready. And again...
0x0016 The device does not recognize the command. And again... doesn't Vader look silly now?
0x001C The printer is out of paper. Which would only bother Vader when he went to the loo.
0x00x0024 Too many files opened for sharing. He would have been much more generous otherwise.
0x0036 The network is busy. This occured in A New Hope, and explains why his helmet was not as shiny as in the following movies, the network polisher was busy.
0x0037 The specified network resource or device is no longer available. Vader suddenly realises that Luke has hacked off his hand.
0x003B An unexpected network error occurred. For Vader, all errors are not only unexpected, but unacceptable.
0x0080 There are no child processes to wait for. So where did Luke and Leia go then...
0x03F1 The configuration registry database is corrupt. Like everything else in the Empire then.
0x047E The specified program requires a newer version of Windows. Unfortunately Vader was never able to upgrade to a purple light sabre.
0x0480 Cannot start more than one instance of the specified program. And he could only have one light sabre at a time too.
0x04B1 The device is not currently connected but it is a remembered connection. Vader does vaguelly remember his time as a Jedi.
0x057E Cannot create a top-level child window. Not being able to convert Luke to the Dark Side was actually pre-programmed.
0x06CF The string is too long. Vader comments on George Lucas' model, and why the ship is so low.
0x06F3 The stub is unable to get the remote procedure call handle. After loosing his hand, he couldn't handle anything.
0x0701 The user's account has expired. The Emperor programmed this in for when he was ready to replace Vader.