Is this even possible (in user mode)?
这是可能的(在用户模式)？
And the syntax to start it in user mode is.
在用户模式下启动它的语法是。
It runs all existing homebrew program in User Mode as well.
在用户模式下已经可以很好的运行现有的自制程序了。
How can I get the value of process's timeslice in user mode?
我怎样才能在用户模式进程的时间片的价值？
Most of the code running on your computer will execute in user mode.
我们大多数的代码都是运行在用户态的。
The means that the event happens during applications executing in user mode.
表示在以用户模式执行应用程序期间发生的事件。
It is water and fire in user mode, lots of declarations overlap with the SDK headers.
这是水和火在用户模式下，大量的声明与SD K头重叠。
In user mode, programs have read and write access to the user data in the process private region.
在用户模式中，程序对进程专用区域中的用户数据具有读写访问权限。
In User mode, the executing code has no ability to directly access hardware or reference memory.
在内核态，代码拥有完全的，不受任何限制的访问底层硬件的能力。
The main difference pointed by Tanenbaum is having the drivers run in user mode conferring higher security
Tanenbaum指出其中的主要区别是令设备驱动运行在用户态能提高安全性
I'll discuss in later chapters a few techniques for accessing data buffers that originate in user mode.
在后面的章节中，我将讨论一些关于访问发生在用户模式中的数据缓冲器的一些技巧。
If the PR bit in MSR is set (Problem State), then the CPU was running in user mode, and is unlikely to be the cause of the crash.
如果在MSR中设置了pr位(问题状态)，那么CPU在用户模式下运行，并且不可能引起系统崩溃。
Process 1 then resumes execution in User Mode until a timer interrupt occurs, and the scheduler is activated in Kernel Mode.
然后，直到发生定时器中断且调度程序在内核态被激活，进程1才恢复在用户态下执行。
An application cannot bypass the OS and access hardware resources directly. It is commonly said that applications run in user mode.
应用程序已经不可能绕过现代的操作系统直接访问硬件，一种更普遍的说法就是应用程序以用户态(user mode)运行。
In user mode, the executing code has no ability to directly access hardware or reference memory. Code running in user mode must delegate to system APIs to access hardware or memory.
在用户态，代码不具备直接访问硬件或者访问内存的能力，而必须借助操作系统提供的可靠的、底层的API来访问硬件或者内存。
Above the kernel, running in user mode, are the device drivers, each one running as a separate process tightly restricted by the memory management hardware to accessing only its own memory.
设备驱动处于内核之上，运行在用户态。每个驱动都作为单独的进程运行，受到内存管理硬件的严格约束，只能访问自己拥有的内存。
In the view mode, the user sees the information for each type of message but cannot alter it.
在查看模式下，用户查看每种类型的消息的信息，但是不能改动该信息。
In this mode, the user cannot see or enter data in the output message.
在此模式下，用户无法在输出消息中查看或输入数据。
However, in this mode, the user cannot change the information that the input message delivers.
但是在此模式下，用户不能更改输入消息所交付的信息。
If the user made changes in edit mode, the changes should be reflected in view mode.
如果用户在编辑模式中进行了更改，则这些更改应该反映在查看模式中。
When a user program accesses system calls, it does so in kernel mode, not user mode.
当用户程序访问系统调用时，它将在内核模式而不是用户模式下进行。
In the edit mode, the user can see both the input and output messages.
在编辑模式下，用户可以同时查看输入和输出消息。
In this mode, no user input (name or password) will be required.
在该方式中，不需要用户的输入(用户名或密码)。
In the init mode, the user enters only the required information in the input message.
在发起模式下，用户仅在输入消息中输入所需的信息。
Some basic components are available in normal user mode, but you will need root authority to perform many commands.
普通用户模式提供一些基本组件，但许多命令都需要根权限。
Some basic components are available in normal user mode, but you will need root authority to perform many commands.
普通用户模式提供一些基本组件，但许多命令都需要根权限。
应用推荐