TITLE: THE EVOLUTION AND MECHANICS OF JOYSTICKS: FROM GAMING TO AEROSPACE INTRODUCTION: JOYSTICKS HAVE TRANSCENDED THEIR ORIGINS AS MERE GAMING PERIPHERALS TO BECOME INTEGRAL COMPONENTS IN VARIOUS INDUSTRIES, FROM AVIATION AND SPACE EXPLORATION TO MEDICAL EQUIPMENT AND INDUSTRIAL MACHINERY. THESE VERSATILE INPUT DEVICES HAVE EVOLVED SIGNIFICANTLY SINCE THEIR INCEPTION, OFFERING PRECISE CONTROL AND ERGONOMIC DESIGN. THIS ARTICLE DELVES INTO THE EVOLUTION, MECHANICS, AND DIVERSE APPLICATIONS OF JOYSTICKS ACROSS DIFFERENT FIELDS. HISTORY OF JOYSTICKS: THE CONCEPT OF THE JOYSTICK DATES BACK TO THE EARLY 20TH CENTURY WHEN IT WAS INITIALLY USED IN AVIATION FOR CONTROLLING AIRCRAFT. THE EARLIEST JOYSTICKS WERE SIMPLE MECHANICAL DEVICES CONSISTING OF A LEVER MOUNTED ON A PIVOT, WHICH PILOTS USED TO MANEUVER THEIR PLANES. OVER TIME, JOYSTICKS FOUND THEIR WAY INTO ARCADE GAMES, HOME CONSOLES, AND EVENTUALLY PERSONAL COMPUTERS, REVOLUTIONIZING THE GAMING INDUSTRY. MECHANICS OF JOY...
WHAT IS WINDOWS TO GO?
WINDOWS
TO GO IS AN IMPORTANT DEPLOYMENT OPTION IN WINDOWS 8.1 AND ABOVE. WINDOWS TO GO ASSIST TO DEPLOY THE WINDOWS
8.1 ENTERPRISE TO A SPECIALY PREPARED USB STORAGE DEVICE AND THEN USE THIS USB
STORAGE TO START ANY COMPATIBLE COMPUTER.
WHEN
A WINDOWS TO GO DEVICE IS STARTED ON A NEW COMPUTER, THE BOOT PROCESS DETECTS
THE COMPUTER HARDWARE AND INSTALLS APPROPRIATE DRIVERS.
WHEN
THE SAME WINDOWS TO GO TO START A SAME COMPUTER, THEN WINDOWS TO GO STARTS
NORMALLY AUTOMATICALLY BY LOADING THE APPROPRIATE DRIVERS. IT STORES THE HARDWARE CONFIGURATIONS OF
MULTIPLE COMPUTERS.
WINDOWS TO GO RESTRICTION
WINDOWS
TO GO FUNCTIONS IN A WAY THAT IS VERY SIMILAR TO A TRADITIONAL WINDOWS 8.1
DESKTOP DEPLOYMENTS, BUT WITH THE FOLLOWING RESTRICTIONS:
·
IN
THE WINDOWS TO GO DEFAULT SETTING SLEEP AND HIBERNATION IS DISABLED. THE FUNCTIONALITY CAN BE ENABLED BY
CONFIGURING GROUP POLICY BUT IT CAN LEAD TO DATA CORRUPTION.
·
AS
A SECURITY MEASURE, FIXED INTERNAL DISCS ON THE HOSTS COMPUTER ARE OFFLINE TO
ENSURE THAT BY USING WINDOWS TO GO, THIRD PARTIES DO NOT GAIN ACCESS TO FILES
ON THE HOST COMPUTER FILE SYSTEM BY BOOTING COMPUTERS.
·
AS
WINDOWS TO GO DEVICE WILL BE USED ACROSS MULTIPLE COMPUTERS BIT LOCKER USES A
BOOT PASSWORD RATHER THAN A TPM PASSWORD.\
·
IN
WINDOWS TO GO, WINDOWS RECOVERY ENVIRONMENT (RE) AND PUSH BUTTON RESET ARE
DISABLED.
·
WINDOWS
TO GO DEVICES SUPPORTS ONLY WINDOWS 8.1 ENTERPRISE EDITION.
·
COMPUTER
WITH AN X86 OR AN X64 PROCESSOR CAN USE USB STORAGE DEVICE PREPARED WITH AN X86
VERSION OF WINDOWS TO GO.
·
A
COMPUTER HAVING AN X64 COMPATIBLE PROCESSOR CAN ONLY USE AN COMPUTER PREPARED
WITH AN X64 VERSION OF WINDOWS TO GO.
·
WINDOWS
TO GO DOESNOT SUPPORT WINDOWS RT DEVICES.
·
IN
WINDOWS TO GO DEFAULT SETTING, THE WINDOWS STORE IS DISABLED.
·
THE
USB STORAGE DEVICE WITH THE WINDOWS TO GO DEPLOYMENT CAN BE REMOVED FROM THE
COMPUTER FOR UP TO 60 SECONDS. THE
COMPUTER RESTARTS, IF THE USB DEVICE IS NOT RECONNECTED AT THE TIME OF
DEPLOYMENT.
WINDOWS TO GO
REQUIREMENTS
WINDOWS
TO GO ONLY WORKS WITH MICROSOFT CERTIFIED USB STORAGE DEVICES AND THE OPERATING
SYSTEM SHOULD RECOGNIZE THE USB DEVICE AS
A FIXED DISK. CREATE WINDOWS TO
GO DEVICES BY USING THE WINDOWS TO GO WIZARD.
SYSTEMS RUNNING WINDOWS 8.1 ENTERPRISE EDDITION CAN ONLY PROVIDES THIS
WIZARD. THE COMPUTERS CONNECTED TO AUSB
2.0 OR USB 3.0 PORT CAN BE STATED WITH WINDOWS TO GO DEVICE.
COMPARING WINDOWS
TO GO AND TRADITIONAL WINDOWS 8.1 DEPLOYMENTS
WINDOWS
TO GO AND TRADITIONAL DEPLOYMENTS DIFFER IN SEVERAL WAYS AND BOTH METHODS HAVE
THEIR BENEFITS AND DRAWBACKS. SOME OF THE KEY DIFFERENCES AS FOLLOWS:
·
WINDOWS
TO GO REQUIRED THE COMPUTER TO BOOT FROM AUSB DEVICE. ENABLING BOOT FROM USB POSES A SECURITY
RISK BECAUSE IT CAN ALLOW ACCESS TO A
COMPUTERS VOLUMES IF TECHNOLOGIES SUCH AS BITLOCKER ARE NOT IN USE. ORGANIZATIONS SHOULD BE WARY OF ALLOWING NON
ADMINISTRATIVE USERS TO BOOT FROM USB DEVICES.
·
IN
A TRADITIONAL DEPLOYMENT, BIT LOCKER CAN BE CONFIGURED TO USE TPM. WINDOWS TO GO DOESN’T HAVE THIS SECURITY AND
ONLY ALLOWS BIT LOCKERS TO USE A PASSPHRASE.
THE WINDOWS TO GO BOOT ENVIRONMENT MIGHT BE MODIFIED BY MALACIOUS
SOFTWARE.
·
THE
WINDOWS STORE IS DISABLED BY DEFAULT IN WINDOWS TO GO. CHANGING THIS IS
POSSIBLE BY EDITING THE ALLOW STORE TO INSTALL APPLICATIONS ON THE WINDOWS TO
GO WORKSPACES POLICY SETTINGS LOCATED IN THE COMPUTER CONFIGURATION
\ADMINISTRATIVE TEMPLATES\WINDOWS COMPONENTS\STORE NODE OF THE GROUP POLICY
MANAGEMENT EDITOR. IN WINDOW 8.1 WINDOW
STORE IS ENABLED BY DEFAULT.
·
WINDOWS
TO GO DEFAULT SETTING DISABLES SLEEP AND HIBERNATION AND ENABLED ON
TRADITIONALLY DEPLOYED WINDOWS 8.1 SYSTEMS.
IF WINDOWS TO GO DEVICE IS LEFT IN RUNNING COMPUTER ACCIDENTLY THE
COMPUTER WILL NOT SHUT DOWN.
·
IN
A TRADITIONAL INSTALLATION, DATA IS STORED LOCALLY ON HARD DISKS. IN WINDOWS TO GO DATA IS STORED IN USB
DEVICE. USB DEVICES ARE MORE LIKELY TO FAIL WHICH MEANS THE LOCAL DATA IS MORE
LIKELYU TO BE LOST. USERS ARE ALSO ARE
MORE LIKELY MISPLACE AUSB DEVICE THAN A PORTABLE COMPUTER.
·
WITH
A COMPATIBLE HARDWARE USER CAN ACCESS
THEIR APPLICATIONS AND DATA. WINDOWS TO
GO ALLOWS USERS TO TASKE THEIR APPLICATIONSAND DATA.
·
WINDOWS
TO GO ASSISTS INFORMATION TECHNOLOGY (IT) DEPARTMENTS THAT WANT TO ALLOW USERS
TO USE THEIR OWN DEVICES, BUT ALSO WANT TO ENSURE THAT ONLY SECURELY MANAGED
OPERATING SYSTEM CAN INTERACT WITH SENSITIVE SERVICES ON A NETWORK.
BOOTING FROM A
NATIVE BOOT VIRTUAL HARD DISK
VIRTUAL
HARD DISK WITH FOR NATIVE BOOT ASSISTS IN CONFIGURING WINDOWS 8.1 PRO AND
ENTERPRISE EDITIONS WHICH HAVE A .VHD OR .VHDX EXTENSIONS.
CONFIGURE
A COMPUTER TO START FROM A SINGLE VIRTUAL HARD DISK OR FROM DIFFERENT VIRTUAL
HARD DISKS. IN COMPARISION TO
CONFIGURING TRADITIONAL DUAL BOOT, BOOTING FROM A VIRTUAL HARD DISK IS
BENEFICIAL BECAUSE IT DOES NOT REQUIRE CREATING A NEW VOLUME WHILE DEPLOYING AN
ADDITIONAL OPERATING SYSTEMS.
CONFIGURATION IS POSSIBLE TO BOOT BETWEEN MULTIPLE VIRUTAL HARD DISK
FILES STORED ON THE SAME INTENSITY.
PLANNING FOR
VIRTUAL HARD DISK WITH NATIVE BOOT
CONFIGURING
A VIRTUAL HARD DISK WITH NATIVE BOOT INCLUDES THE FOLLOWING PROCESS:
·
CREATING
AND PERFORMING A VIRTUAL HARD DISKS,
·
INSTALLING
OR APPLYING WINDOWS IMAGE,
·
ADDING
THE VIRTUAL HARD DISK NATIVE BOOT OPTION TO THE STARTUP MENU AND,
·
RESTARTING
THE COMPUTER.
WITH
DISK MANAGEMENT OR DISKPART.EXE CREATE A VIRUTAL HARD DISK DEPLOY WINDOW IMAGES
BY USING DISM.EXE AND ADD THE BOOT OPTION BY USING BEDBOOT.EXE.
THE
MAIN POINTS TO CONSIDER WHENPOLANNING FOR VIRTUAL HARD ARE VOLUME SIZE,
DEPLOYMENT OPTIONS AND OPERATING SYSTEMS.
Comments
Post a Comment