About: GUIdows

Description
Metadata
Settings
- owl:sameAs
- Inference Rule:

About: GUIdows Sponge Permalink

An Entity of Type : owl:Thing, within Data Space : 134.155.108.49:8890 associated with source dataset(s)

Started in '97 when Aperture was desperate for an easier way of controlling GLaDOS. So our scientists thought up of a GUI solution. The solution was based on a 32-bit method, using a protected-mode processor. We could make the GUI solution easier, faster and more secure. This essentially reduced the text portion of GLaDOS to being a Bootloader. As with some of our design goals, We aimed to having longer filenames. How this worked is that we had the filenames in a separate buffer and it would use a system call to call up the different name.

Attributes	Values
rdfs:label	GUIdows
rdfs:comment	Started in '97 when Aperture was desperate for an easier way of controlling GLaDOS. So our scientists thought up of a GUI solution. The solution was based on a 32-bit method, using a protected-mode processor. We could make the GUI solution easier, faster and more secure. This essentially reduced the text portion of GLaDOS to being a Bootloader. As with some of our design goals, We aimed to having longer filenames. How this worked is that we had the filenames in a separate buffer and it would use a system call to call up the different name.
dcterms:subject	Internet Computers Communication Operating Systems Corporations
dbkwik:uncyclopedi...iPageUsesTemplate	dbkwik:resource/JFLFTdAI_Ufgj-AQZZX4FA== dbkwik:resource/3yEdKoldmjNRKkGfBALzmw==
abstract	Started in '97 when Aperture was desperate for an easier way of controlling GLaDOS. So our scientists thought up of a GUI solution. The solution was based on a 32-bit method, using a protected-mode processor. We could make the GUI solution easier, faster and more secure. This essentially reduced the text portion of GLaDOS to being a Bootloader. But the Aperture Team didn't think this was the spark they were looking for so they worked with the "original" GLaDOS team to integrate it with GLaDOS. Using a complex computer algorithm, GLaDOS could appear on any computer and speak to the user. The team praised it as genius. As noted, We got integration down but we just couldn't get the GUI in our heads. So we thought and we thought and then we came up with something. One of our scientists came up to the blackboard and drew a rectangle with one box on the left and one on the right then he drew some boxes. As we pondered, We said. "Hey, This could be our new GUI." so we worked 8 months to design it. As with some of our design goals, We aimed to having longer filenames. How this worked is that we had the filenames in a separate buffer and it would use a system call to call up the different name. Also the most important goal was GLaDOS compatibility. We accomplished this by having a Window act as GLaDOS and emulate it's features, This gave it the feeling of GLaDOS. Then we had it run a GLaDOS program and with success it called out to the subsystem and launched the program. We had a stroke of brilliant luck and genius right there. The first convergence between a 16-bit operating and a 32-bit operating system. Who couldn't of done that first. We released the final version in 2000 and everyone was now using it on Aperture computers, The first GUI-based operating system had finally been completed and the home computer has been revolutionized forever.

OpenLink Virtuoso version 07.20.3217, on Linux (x86_64-pc-linux-gnu), Standard Edition
Data on this page belongs to its respective rights holders.
Virtuoso Faceted Browser Copyright © 2009-2012 OpenLink Software