0
ssps stands for "speed sensitive Power Steering". My light has been coming on for about a year now. When I start the car, everything is fine. After a few miles, sometimes the light comes on. Sometimes, it goes back off, sometimes it stays on for a long time.
I've checked a few forums and from what I can figure out, there seems to be an issue with a faulty sensor, but nothing is actually wrong with the power steering. You can take your car to the dealer and pay $100 for them to tell you exactly what's wrong. If your car is still under warranty, they might fix it for free.
Or, you can take it to an Advance Auto store and they'll check it out for free.
Wiki User
∙ 15y ago
Add your answer:
Earn +20 pts
What does SSP stands for?
SSPS stands for Solid State Protection System.
The value proposition for participating as a CIKR partner within the NIPP framework refers to?
a- grants offered by the federal government to state and local jurisdictions for the implementations of the NIPP b- the premise that federal, state and local government are better equipped to handle terrorist attacks than the private sector c- the benefits that individual companies or organizations derive from voluntary participation in the implementation in the NIPP and the sector- specific plans (SSPs) d- the proposition that infrastructure protection should be privatized and responsibility should be shifted to the private sector.
What is the authentication protocol used in 2008?
The Windows operating systems implements a default set of authentication protocols-Kerberos, NTLM, TLS/SSL, Digest, and PKU2U-as part of an extensible architecture. In addition, some protocols are combined into authentication packages such as the Credential Security Support Provider (CredSSP), Negotiate, and Negotiate Extensions. These protocols and packages enable authentication of users, computers, and services; the authentication process, in turn, enables authorized users and services to access resources in a secure manner. Windows authentication protocols are conventions that control or enable the connection, communication, and data transfer between computers in a Windows environment by verifying the identity of the credentials of a user, computer, or process. The authentication protocols are security support providers (SSPs) that are installed in the form of dynamic-link libraries (DLLs). Negotiate Microsoft Negotiate is an SSP that acts as an application layer between the Security Support Provider Interface (SSPI) and the other SSPs. When an application calls into SSPI to log on to a network, it can specify an SSP to process the request. If the application specifies Negotiate, Negotiate analyzes the request and selects the best SSP to handle the request based on the configured security policy. Currently, the Negotiate SSP selects either the Kerberos or NTLM protocol. Negotiate selects the Kerberos protocol unless it cannot be used by one of the systems involved in the authentication or if the client application did not provide a target name as a service principal name (SPN), a user principal name (UPN), or a NetBIOS account name. Otherwise, Negotiate will select the NTLM protocol. A server that uses the Negotiate SSP can respond to client applications that specifically select either the Kerberos or NTLM protocol. However, a client application must first query the server to determine if it supports the Negotiate package before using Negotiate. (Negotiate is supported on Windows operating systems beginning with Windows Server 2003 and Windows XP.) A server that does not support Negotiate cannot always respond to requests from clients that specify Negotiate as the SSP Kerberos :The Kerberos version 5 (v5) authentication protocol provides a mechanism for authentication-and mutual authentication-between a client and a server, or between one server and another server NTLM The NTLM version 2 (NTLMv2) authentication protocol is a challenge/response authentication protocol. NTLM is used when exchanging communications with a computer running Windows NT Server 4.0 or earlier. Networks with this configuration are referred to as mixed-mode. NTLM is also the authentication protocol for computers that are not participating in a domain, such as stand-alone servers and workgroups. Negotiate Extensions NegoExts (NegoExts.dll) is an authentication package that negotiates the use of SSPs for applications and scenarios implemented by Microsoft and other software companies. Pku2u.dll is one of the supported SSPs that is installed by default, and developers can create custom providers. PKU2U The PKU2U protocol in Windows 7 and Windows Server 2008 R2 is implemented as an SSP. The SSP enables peer-to-peer authentication, particularly through the Windows 7 media and file sharing feature called Homegroup, which permits sharing between computers that are not members of a domain. Credential Security Support Provider Windows Vista introduced a new authentication package called the Credential Security Support Provider (CredSSP) that provides a single sign-on (SSO) user experience when starting new Terminal Services sessions. CredSSP enables applications to delegate users' credentials from the client computer (by using the client-side SSP) to the target server (through the server-side SSP) based on client policies TLS/SSL The TLS/SSL protocols are used to authenticate servers and clients, and to encrypt messages between the authenticated parties. The TLS/SSL protocols, versions 2.0 and 3.0, and the Private Communications Transport (PCT) protocol are based on public key cryptography. The secure channel (Schannel) authentication protocol suite provides these protocols. All Schannel protocols use a client/server model and are primarily used for Internet applications that require secure Hypertext Transfer Protocol (HTTP) communications Digest The Digest authentication protocol is a challenge/response protocol that is designed for use with HTTP and Simple Authentication Security Layer (SASL) exchanges. These exchanges require that parties requesting authentication must provide secret keys.
Why is 64-bit architecture an advantage in Windows Server 2008?
· Physical memoryA 32-bit system architecture can directly address only a 4-GB address space. A 64-bit system architecture that is running a 64-bit edition of Windows Server can support up to 1,024 GB of both physical and addressable memory.· Virtual memoryThe 64-bit editions of Windows Server can address 16 terabytes of virtual memory by using a flat addressing model. Virtual memory is divided equally between virtual address space for applications and the operating system. Even 32-bit applications can benefit from increased virtual memory address space when they are running in a 64-bit environment. For example, although a 32-bit application is still restricted to 4 GB of virtual memory, it no longer has to share that memory space with the operating system. As a result, it receives an effective increase in available virtual memory.· Continuous memoryPoor performance in 32-bit systems is often not the result of a lack of available memory, but the unavailability of large enough blocks of continuous memory. In a typical Windows SharePoint Services 3.0 deployment, Windows, Internet Information Services (IIS), common language runtime (CLR), ASP.NET, SharePoint Products and Technologies, SSPs, and MDACs can all claim a portion of a server's available virtual memory and can leave a 32-bit address space quite fragmented. When the CLR or SharePoint services request new memory blocks, it can be difficult to find a 64-MB segment in the crowded 32-bit address space. A 64-bit system offers practically unlimited address space for user mode processes.· Better parallel processingA server that is using 32-bit architecture is limited to 32 CPUs. Improvements in parallel processing and bus architectures enable 64-bit environments to support as many as 64 processors and provide almost linear scalability with each additional processor.· Faster bus architectureA 64-bit architecture provides more and wider general-purpose registers, which contribute to greater overall application speed. When there are more registers, there is less need to write persistent data to memory and then have to read it back just a few instructions later. Function calls are also faster in a 64-bit environment because as many as four arguments at a time can be passed in registers to a function.· More secureThe 64-bit editions of Windows Server offer the following enhanced security features· Buffer overflow protectionA buffer overflow occurs when a data buffer is congested with more data than it is designed to handle. In 64-bit editions of Windows Server, the first parameters of a procedure call are passed in registers. As a result, it is less likely that the buffer will overflow, because the correct values have to be set up in registers and the variables and addresses have to be aligned on the stack.· Data execution protectionThe 64-bit processors made by AMD and Intel include hardware support for data execution prevention (DEP). Windows Server uses DEP to prevent malicious code from being able to execute, even when a buffer overrun occurs. Even without a processor that supports DEP, Windows Server can detect code that is running in memory locations where it should not be.· Patch GuardMicrosoft Patch Guard technology prevents non-Microsoft programs from patching the Windows kernel. This technology prevents kernel mode drivers from extending or replacing kernel services, including system service dispatch tables, the interrupt descriptor table (IDT), and the global descriptor table (GDT). Third-party software is also prevented from allocating kernel stacks or patching any part of the kernel.· Better scalabilityIn a 64-bit environment, not only can database servers gain nearly unlimited virtual memory address space, but they also gain support for more physical memory. It is possible for a 64-bit server that is running 64-bit editions of Windows Server and SQL Server to get very large working data sets entirely into RAM, thereby improving performance and scalability. In addition, the number of application servers that are required to support a given user base can be substantially reduced because a 64-bit environment does not require worker processes to cycle as often. This reduced cycling results in fewer lost connections, improved I/O handling, and a better user experience.· Lower total cost of ownershipAll the benefits of 64-bit operation that are listed in the previous sections enable you to do more with less. A 64-bit environment allows you to manage more data, serve more users, and run more applications while using less hardware. By reducing hardware, you are also able to reduce license, operations, and infrastructure costs. It takes up less floor space in your data center and costs less to maintain. Finally, because a Windows SharePoint Services 3.0 farm that uses 64-bit hardware and software provides more room for growth, you can spend less over time on equipment because the life cycle of your equipment is likely to be longer.
Why is 64 bit architecture an advantage in window server 2008?
· Physical memoryA 32-bit system architecture can directly address only a 4-GB address space. A 64-bit system architecture that is running a 64-bit edition of Windows Server can support up to 1,024 GB of both physical and addressable memory.· Virtual memoryThe 64-bit editions of Windows Server can address 16 terabytes of virtual memory by using a flat addressing model. Virtual memory is divided equally between virtual address space for applications and the operating system. Even 32-bit applications can benefit from increased virtual memory address space when they are running in a 64-bit environment. For example, although a 32-bit application is still restricted to 4 GB of virtual memory, it no longer has to share that memory space with the operating system. As a result, it receives an effective increase in available virtual memory.· Continuous memoryPoor performance in 32-bit systems is often not the result of a lack of available memory, but the unavailability of large enough blocks of continuous memory. In a typical Windows SharePoint Services 3.0 deployment, Windows, internet Information Services (IIS), common language runtime (CLR), ASP.NET, SharePoint Products and Technologies, SSPs, and MDACs can all claim a portion of a server's available virtual memory and can leave a 32-bit address space quite fragmented. When the CLR or SharePoint services request new memory blocks, it can be difficult to find a 64-MB segment in the crowded 32-bit address space. A 64-bit system offers practically unlimited address space for user mode processes.· Better parallel processingA server that is using 32-bit architecture is limited to 32 CPUs. Improvements in parallel processing and bus architectures enable 64-bit environments to support as many as 64 processors and provide almost linear scalability with each additional processor.· Faster bus architectureA 64-bit architecture provides more and wider general-purpose registers, which contribute to greater overall application speed. When there are more registers, there is less need to write persistent data to memory and then have to read it back just a few instructions later. Function calls are also faster in a 64-bit environment because as many as four arguments at a time can be passed in registers to a function.· More secureThe 64-bit editions of Windows Server offer the following enhanced security features· Buffer overflow protectionA buffer overflow occurs when a data buffer is congested with more data than it is designed to handle. In 64-bit editions of Windows Server, the first parameters of a procedure call are passed in registers. As a result, it is less likely that the buffer will overflow, because the correct values have to be set up in registers and the variables and addresses have to be aligned on the stack.· Data execution protectionThe 64-bit processors made by AMD and Intel include hardware support for data execution prevention (DEP). Windows Server uses DEP to prevent malicious code from being able to execute, even when a buffer overrun occurs. Even without a processor that supports DEP, Windows Server can detect code that is running in memory locations where it should not be.· Patch GuardMicrosoft Patch Guard technology prevents non-Microsoft programs from patching the Windows kernel. This technology prevents kernel mode drivers from extending or replacing kernel services, including system service dispatch tables, the interrupt descriptor table (IDT), and the global descriptor table (GDT). Third-party software is also prevented from allocating kernel stacks or patching any part of the kernel.· Better scalabilityIn a 64-bit environment, not only can database servers gain nearly unlimited virtual memory address space, but they also gain support for more physical memory. It is possible for a 64-bit server that is running 64-bit editions of Windows Server and SQL Server to get very large working data sets entirely into RAM, thereby improving performance and scalability. In addition, the number of application servers that are required to support a given user base can be substantially reduced because a 64-bit environment does not require worker processes to cycle as often. This reduced cycling results in fewer lost connections, improved I/O handling, and a better user experience.· Lower total cost of ownershipAll the benefits of 64-bit operation that are listed in the previous sections enable you to do more with less. A 64-bit environment allows you to manage more data, serve more users, and run more applications while using less hardware. By reducing hardware, you are also able to reduce license, operations, and infrastructure costs. It takes up less floor space in your data center and costs less to maintain. Finally, because a Windows SharePoint Services 3.0 farm that uses 64-bit hardware and software provides more room for growth, you can spend less over time on equipment because the life cycle of your equipment is likely to be longer.
Why is 64 bit an advantage in windows server 2008?
· Physical memoryA 32-bit system architecture can directly address only a 4-GB address space. A 64-bit system architecture that is running a 64-bit edition of Windows Server can support up to 1,024 GB of both physical and addressable memory.· Virtual memoryThe 64-bit editions of Windows Server can address 16 terabytes of virtual memory by using a flat addressing model. Virtual memory is divided equally between virtual address space for applications and the operating system. Even 32-bit applications can benefit from increased virtual memory address space when they are running in a 64-bit environment. For example, although a 32-bit application is still restricted to 4 GB of virtual memory, it no longer has to share that memory space with the operating system. As a result, it receives an effective increase in available virtual memory.· Continuous memoryPoor performance in 32-bit systems is often not the result of a lack of available memory, but the unavailability of large enough blocks of continuous memory. In a typical Windows SharePoint Services 3.0 deployment, Windows, internet Information Services (IIS), common language runtime (CLR), ASP.NET, SharePoint Products and Technologies, SSPs, and MDACs can all claim a portion of a server's available virtual memory and can leave a 32-bit address space quite fragmented. When the CLR or SharePoint services request new memory blocks, it can be difficult to find a 64-MB segment in the crowded 32-bit address space. A 64-bit system offers practically unlimited address space for user mode processes.· Better parallel processingA server that is using 32-bit architecture is limited to 32 CPUs. Improvements in parallel processing and bus architectures enable 64-bit environments to support as many as 64 processors and provide almost linear scalability with each additional processor.· Faster bus architectureA 64-bit architecture provides more and wider general-purpose registers, which contribute to greater overall application speed. When there are more registers, there is less need to write persistent data to memory and then have to read it back just a few instructions later. Function calls are also faster in a 64-bit environment because as many as four arguments at a time can be passed in registers to a function.· More secureThe 64-bit editions of Windows Server offer the following enhanced security features· Buffer overflow protectionA buffer overflow occurs when a data buffer is congested with more data than it is designed to handle. In 64-bit editions of Windows Server, the first parameters of a procedure call are passed in registers. As a result, it is less likely that the buffer will overflow, because the correct values have to be set up in registers and the variables and addresses have to be aligned on the stack.· Data execution protectionThe 64-bit processors made by AMD and Intel include hardware support for data execution prevention (DEP). Windows Server uses DEP to prevent malicious code from being able to execute, even when a buffer overrun occurs. Even without a processor that supports DEP, Windows Server can detect code that is running in memory locations where it should not be.· Patch GuardMicrosoft Patch Guard technology prevents non-Microsoft programs from patching the Windows kernel. This technology prevents kernel mode drivers from extending or replacing kernel services, including system service dispatch tables, the interrupt descriptor table (IDT), and the global descriptor table (GDT). Third-party software is also prevented from allocating kernel stacks or patching any part of the kernel.· Better scalabilityIn a 64-bit environment, not only can database servers gain nearly unlimited virtual memory address space, but they also gain support for more physical memory. It is possible for a 64-bit server that is running 64-bit editions of Windows Server and SQL Server to get very large working data sets entirely into RAM, thereby improving performance and scalability. In addition, the number of application servers that are required to support a given user base can be substantially reduced because a 64-bit environment does not require worker processes to cycle as often. This reduced cycling results in fewer lost connections, improved I/O handling, and a better user experience.· Lower total cost of ownershipAll the benefits of 64-bit operation that are listed in the previous sections enable you to do more with less. A 64-bit environment allows you to manage more data, serve more users, and run more applications while using less hardware. By reducing hardware, you are also able to reduce license, operations, and infrastructure costs. It takes up less floor space in your data center and costs less to maintain. Finally, because a Windows SharePoint Services 3.0 farm that uses 64-bit hardware and software provides more room for growth, you can spend less over time on equipment because the life cycle of your equipment is likely to be longer.
Explain how would you proceed in designing a waste disposal system for a steel plant?
The world steel industry produces about 780 Mt of crude steel and simultaneously approximately 300 Mt of solid wastes products are also produced. Thus an average of about 400 Kg of solid by products is generated in the steel industry per tonne of crude steel. Major share of this (70-80%) consists of Blast Furnace Slag and basic Oxygen Furnace Slag. These wastes are an ecological hazard. The total steel production in India is about 25 million tones and the waste generated annually is around 8 million tones (considerably higher than the world average). Though the report has highlighted the associated ecological problems and suggested management, the main purpose of the report is to highlight the business opportunities available in utilization of the generated wastes into commercial products. Technologies have been developed in most the developed nations of the world for utilization of the generated wastes. and there are nations, which have total utilization of the wastes. In India though utilization of wastes have begun it is still quite some time before there is total utilization. The report has focused on the wastes generated - quality and quantity- by integrated steel plants, secondary steel sector and electric arc furnaces in India. Technologies developed for utilization of the generated wastes into useful products have been covered along with the technology sources, in India and abroad, and estimated project costs. The report has also presented a plan for zero waste programmeOne of the major concerns of world steel industry is the disposal of wastes generated at various stages of processing. The global emphasis on stringent legislation for environmental protection has changed the scenario of waste dumping into waste management. Because of natural drive to be cost-effective, there is a growing trend of adopting such waste management measures as would convert wastes into wealth, thereby treating wastes as by-products. This has led to aiming at of zero-waste technologies. The technologies developed to economically convert wastes of steel plants into wealth provide new business opportunities for prospective entrepreneurs. Such technologies which have been identified in the report through adequate deliberations are indicated below in two categories, namely technologies for gainful utilisation of wastes in manufacture of conventional products and those for gainful conversion of wastes into altogether new productsEcological problems and their managementThe major solid wastes of steel plants that are dumped namely, BF sludge, spent refractories and fly ash, pose ecological problem and parallel initiatives are required for eco-friendly management of solid wastes. The following two ways have been identified and dealt with in this chapter for management of ecological problems.* Plantation for green cover* Plantation of flowering and tree species.There are conflicting reports of effects of soil amended by fly ash on vegetables. Pending confirmation and reconfirmation of no harmful effects on vegetables, fly ash is prohibited in production of vegetables or food grains. Therefore, fly ash may be used for plantation of flowering plants and tree species'.Practices and technologies of steel plant solid waste management.Practices and technologies of steel plant solid waste management have been classified into three groups as follows.Minimisation of wastesRecycling of wastesReuse ( including sale to outside parties) of wastesFor minimisation of wastes, minimisation measures have been indicated. For recycling / reuse, the technologies have been briefly described with the name of the developing agency and the commercial status in this chapter. Cost data for implementation of the technologies could not be made available, because, normally, foreign parties reply only to queries about specific projects. It is suggested that research proposals may be made for the technology packages involved for indigenous through technology absorption and commercialisation, end then exemplary facilities based on cost-effective technologies may be set up for other entrepreneurs to follow suit. Problems and prospects of managing key by-products which are substantially dumped at present like steelmaking slag, BOF dust/sludge, fly ash and spent refractories have been dealt with at length.Plan for zero waste programmeIt is emphasised that all the industries, including the steel industry, are to be committed to 'sustainable '. Therefore, steel plants have no option but to plan immediately for a zero waste programme and implement the same. Aim of zero waste programme is make the total dumped quantity and so the individual waste quantities dumped to zero or near zero, or in other words, to produce 100% or almost 100% products. Wastes generated in all the model plants have been analysed and measures have been suggested to eliminate or minimize dumping.The chapter solicits initiatives from Govt. of India for creation of community cement plant to be built, owned and operated by a third party to take care of EAF slag's and community 2-stage Waelz kiln of adequate capacity to take care of zinc-rich EAF dust from a cluster of SSPs (EAF). To achieve the goal of zero waste programme on national basis as a part of 'sustainable ' initiative from Govt. of India is necessary to provide community ferruginous waste processing plants based on technologies like REDSMELT, FASTMET, ROMELT, Hamborn Shaft Furnace or process developed by RDCIS for utilisation of ferruginous wastes, to be built, owned and operated by third parties
