昨天,同事的机器有中文上网插件和一些本马,
杀掉以后用360安装了微软的补丁,
结果再也进不去了,
每次到了WINDOWS菜单就自动重启

我可以做的只有按F8,选启动模式
但选安全模式,或最后一次正确配置,一样重启
只好重装,
同事哪里还好多资料,找回来用了半天多时间,
怕了,下次不知道该不该更新了,


ps.还好不是老板的机器,要不然...........

个人感觉这个问题不应该是上网更新造成的
有可能是使用病毒或杀毒造成的原因
公司电脑用户权限越大问题就越多
定期对公司资料进行备份是必要的事情

不会吧,只是些木马,我用的还是专杀工具.

说起来,之前倒是偶而会蓝屏....

就是因为你没有经常更新，就出现这些问题。

garnett_wu你好,很想认识你,可以吗?你给我的印象是技术很好的.楼主的问题我也有同感是因杀毒不当所致．

[ 本帖最后由 nable008 于 2007-9-16 00:17 编辑 ]

这样啊,哪就定期更新好了,公司的资料,备份起来很难的,都是几G/个人,...

资料一般不会掉，实在不行就把硬盘取下来上台干净的计算机，杀毒，把资料拷出来

DOS实模式下进入C盘根目标,edit boot.ini文件到正常值.


进入安全模式时也不断重启是因为boot.ini被破坏了.

顺便问一下,vista的boot.ini不可修改吗

我试着找了些资料

引用:

二、在XP下设置默认操作系统
　　在Windows XP下调整默认启动系统的方法非常简单，相信很多朋友都不陌生，右击桌面上的“我的电脑”图标打开系统属性窗口，切换到“高级”标签页，在这里单击“启动和故障恢复”小节中的“设置”按钮，打开启动和故障恢复对话框，不过我们在“默认操作系统”下拉列表框中并没有看到与Vista有关的引导项(见图7)，这是怎么一回事呢？
图7
　　原来，Vista引入了全新的引导管理器，与Windows XP大不相同的是将以前保存在BOOT.INI中的启动配置参数转移到了启动配置数据存储包中，这也就是为什么我们在BOOT.INI文件中无法查看到Vista引导选项的原因所在。那么，难道我们再也无法在Windows XP下将XP设置为Vista/XP的默认启动系统了吗？
　　当然不是，我们可以借助第三方软件来完成这个任务，这里介绍两款比较好用的软件：
　　1.VistaBootPRO [点击下载]
　　VistaBootPRO是第一个被设计用来对Vista进行调整和优化的软件，提供了一个图形化的操作界面，可以非常方便的对Vista的引导管理器进行各种调整，而且还是完全免费的，目前最新版本是3.1 Beta，目前只能被安装在Windows 2000/XP/Server 2003/Vista系统下，而且运行时需要.NET 2.0 Framework的支持。

　需要说明的是，VistaBootPRO采用了类似于Office 2007风格的界面，单击窗口顶部的按钮切换到“Manage OS Entries”标签页，如图8所示，可以看到“OS List”列表框中给出了目前已安装的操作系统，遗憾的是对中文字符的支持不是太好，总算不影响正常使用。
图8
　　现在的操作很简单，选中需要设置为默认操作系统的项目，然后在下面勾选“Set as Default”复选框，如果有需要的话，可以单击右侧的双箭头按钮调整各个项目的次序，通过“Up”和“Down”两个按钮进行调整，最后单击右下角的“Apply”按钮即可生效。假如需要对系统项进行重命名，首先需要勾选“Rename selected operating system”复选框，然后下面会增加Rename To和Deive Letter的相关选项。
　　2.EasyBCD
　　EasyBCD的作用与VistaBoostPRO大致相仿，也是一个完全免费的软件，目前最新版本是1.5，当然也需要.NET 2.0 Framework的支持。
　　运行程序，切换到“Configure Boot”标签页，如图9所示，在右侧窗格的“Default OS”下拉列表框中选择“早期版本的Windows”，这里还可以重置显示引导管理器的默认时间，最后单击下面的“Save Settings”按钮即可生效，以后引导时就会默认以Windows XP启动。
　
图9
　　如果你需要对引导管理器中的项目重命名，那么可以在下面的“Entry-Based Settings”小节中完成，首先选中相应的引导项，然后在“Name”后面的文本框中自由命名即可。
　　三、修复引导管理器
　　有一个问题是比较令人讨厌的，当按照正常的步骤完成Windows Vista/Windows XP的安装后，此时当然双引导菜单已经自动生成，一般情况下我们不用去改变什么。但如果由于某些原因对Windows XP进行了修复或重新安装，那么原有的引导管理器会遭受破坏，双引导菜单也已消失不见，换句话说也就是将无法进入Windows Vista，但Vista系统却是实实在在的还呆在原来的地方，只不过是缺少了相关的启动配置参数。
　　此时，我们仍然可以借助VistaBootPRO或EasyBCD来修复引导管理器，方法也很简单：
　　1.VistaBootPRO [点击下载]
　　切换到“Bootloader”标签页，如图10所示，在这里选择“Reinstall the Vista Bootloader”，然后单击下面的“Apply”按钮，确认后会自动重启系统，很快就可以修复Vista的引导管理器。当然，如果什么时候不再需要Vista，可以选择“Uninstall the Vista Bootloader”删除引导管理器，这样就可以不用去手工删除C盘根目录下的BOOT文件夹，而且是绝对的安全方便。
提示：如果“Apply”按钮呈灰色不可用状态，可以先选择“Uninstall the Vista Bootloader”，然后再切换回去再选择就可以了。
图10
　　2.EasyBCD
　　EasyBCD当然也可以修复Vista的引导管理器，不过现在需要的是切换到“Manage Bootloader”标签页，如图11所示，在这里选择“Reinstall the Vista Bootloader”， 然后单击下面的磁盘状按钮“Write MBR”写入即可。不过，建议在进行此项操作之前，最好先备份当前的引导数据，以确保万无一失。
图11
　　四、删除多余的引导项目
　　我们知道，如果需要删除双引导菜单中的多余项目，在Windows XP时代是非常简单的，只要用记事本打开BOOT.INI文件进行手工编辑后保存即可，但遗憾的是这一招在Vista下已经失效，因此我们仍然需要借助第三方软件来完成这一任务。
　　1.VistabBootPRO [点击下载]
　　这个任务仍然需要在“Manage OS Entries”标签页下完成，首先在“OS List”列表框中选择一个待删除的操作系统，然后单击右侧红色的删除按钮，此时会弹出图12所示的对话框，再次确认后即可将其删除。
图12
　　2.EasyBCD
　　切换到“Add/Remove Entries”标签页，在这里选择需要删除的引导项，然后单击“Delete”按钮即可(见图13)，这里当然也可以调整引导项的次序，够简单的吧？
图13
　　当然，VistaBootPRO和EasyBCD这两款软件还有很多的功能，例如备份和导出引导数据、调整引导参数等，具体操作这里就不多介绍了，感兴趣的朋友不妨一试。
转载请注明出自MSCD技术社区 本贴地址：http://bbs.mscode.cc/viewthread.php?tid=37292

如果VISTA的boot.int不会被修改的乱七八糟,安全性会有了很大提高,其实vista采用了ntfs5.1,手工修改boot.ini也许会有些问题.

在VISTA和longhorn中,使用bdedit来对boot.ini进行修改,删除,增加的操作.
bdedit.exe在\windows\system32目录下.您可以在命令行下使用bdedit.exe /?来查看帮助.

引用:

Vista启动配置数据编辑器的使用



Boot Configuration Data Editor Frequently Asked QuestionsBoot Configuration DataWhat is the BCD store?The Boot Configuration Data (BCD) store contains boot configuration parameters and controls how the operating system is started in Microsoft® Windows Vista™ and Microsoft® Windows Server® Code Name "Longhorn" operating systems. These parameters were previously in the Boot.ini file (in BIOS-based operating systems) or in the nonvolatile RAM (NVRAM) entries (in Extensible Firmware Interface–based operating systems). You can use the Bcdedit.exe command-line tool to affect the Windows® code which runs in the pre-operating system environment by adding, deleting, editing, and appending entries in the BCD store. Bcdedit.exe is located in the \Windows\System32 directory of the Windows Vista partition.
Note
Even though this document focuses primarily on Windows Vista, this information applies to both Windows Vista and Windows Server "Longhorn".
Note
For detailed command and option information at the command prompt, type bdedit.exe /? command. For example, type bcdedit.exe /? CREATESTORE.
Why was there a change to BCD from Boot.ini?BCD was created to provide an improved mechanism for describing boot configuration data. With the development of new firmware models (for example, the Extensible Firmware Interface (EFI)), an extensible and interoperable interface was required to abstract the underlying firmware. This new design provides the foundation for a variety of new features in Windows Vista (for example, the Startup Repair tool and Multi-User Install shortcuts).
Where is the BCD file located in the registry?•BIOS-based operating systems. The BCD registry file is located in the \Boot\Bcd directory of the active partition.

•EFI–based operating systems. The BCD registry file is located on the EFI system partition.

Can any user modify BCD?No. You need administrative credentials to modify BCD.
What are the ways that I can modify BCD?Depending on what you want to change, you can use the following tools to modify BCD:
•Startup and recovery. The Startup and recovery dialog box enables you to select the default operating system to start if you have multiple operating systems installed on your computer. You can also change the time-out value. These settings are located on the Advanced tab in the System Properties dialog box.

•System Configuration utility (Msconfig.exe). Msconfig.exe is a more advanced tool with capabilities that include the following options: /debug, /safeboot, /bootlog, /noguiboot, /basevideo, and /numproc.

•BCD WMI provider. The BCD Windows Management Instrumentation (WMI) provider is a management interface that you can use to script utilities that modify BCD. This is the only programmatic interface available for BCD. For more information, see Boot Configuration Data (BCD) at the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=56792).

•BCDEdit.exe. BCDEdit.exe is a command-line utility that replaces Bootcfg.exe in Windows Vista. For more information, see What can I do with Bcdedit.exe?.
Note
You cannot use Bootcfg.exe to modify BCD. However, Bootcfg.exe will remain in the operating system in order to support older operating systems.


Why don’t I see any Windows entries in the EFI boot manager? And why are there two boot managers?All Windows entries are stored in the BCD store. On an EFI-based operating system, there is a single entry in the EFI firmware boot manager called “Windows Boot Manager”. This file is located in \EFI\Microsoft\Boot\Bootmgfw.efi. If you start Windows Boot Manager using the EFI boot manager, you should get a common look and feel on both your EFI-based and PC/AT-based operating systems. For example, the advanced boot options menu should work. The default timeout for the EFI boot manager is 2 seconds to make it easier to boot back and forth between Windows Server 2003 with Service Pack 1 and Windows Vista.
Top of page
Multiboot EnvironmentsCan I install Windows Vista on a computer that already contains an operating system?Yes. You can install Windows Vista on a different partition. It is best to install Windows Vista after you install the older operating systems. Older operating systems will continue to use Boot.ini for boot configuration.
Should I replace the code that used to work with Boot.ini to now use BCD on Windows Vista?No. You will need to alter your code so that it uses Boot.ini for the older operating systems, and so that it uses BCD on Windows Vista.
In a multiboot environment, does modifying BCD on the pre-Windows Vista operating system modify the boot configuration?No. You need to modify BCD to alter the boot configuration for Windows Vista. You also need to modify Boot.ini (for BIOS-based operating systems) or NVRAM (for EFI-based operating systems) to alter boot configuration for the older operating systems.
Can I disable BCD entirely when I am not booting to Windows Vista?No. The boot manager for Windows Vista runs first to determine which operating system to start. Therefore, if you want to boot to the older operating system, you must set the default order to the older operating system in the BCD store. For more information, see How to change the default operating system entry.
Top of page
BCDedit.exeWhat is Bcdedit.exe?You can use Bcdedit.exe to modify the Windows code which runs in the pre- operating system environment by adding, deleting, editing, and appending entries in the BCD store. Bcdedit.exe is located in the \Windows\System32 directory of the Windows Vista partition.
What can I do with Bcdedit.exe?Bcdedit.exe currently enables you to do the following:
•Create a BCD store for a later installation of Windows Server "Longhorn".
•Add entries to a existing BCD store
•Modify existing entries in a BCD store.
•Delete entries from a BCD store.
•Export entries to a BCD store.
•Import entries from a BCD store.
•List currently active settings.
•Query entries of a particular type.
•Apply a global change (to all the entries).
•Change the default time-out value.

When I run bcdedit /enum, why do I get a Windows Boot Manager entry, a few Windows Boot Loader entries, and a legacy entry?The boot environment has been split into two categories: Windows Boot Manager and various boot applications that run in the boot environment. Windows Boot Manager is basically a mini-operating system that controls your boot experience and enables you to choose which boot application to run. There are various boot applications (for example, Windows Boot Loader) and each one does something different. For example, a Windows Boot Loader application loads Windows.
When you specify /enum, you will get the following:
•One Windows Boot Manager entry (because there is only one boot manager).

•A Windows Boot Loader application for each Windows Vista operating system you have installed on the computer. For example, if you have two different versions of Windows Vista installed on different partitions, you will see two Windows Boot Loader entries.

•One legacy entry. This entry is not a boot application, but instead uses NTLDR and Boot.ini to boot into an operating system that is older than Windows Vista. You will use this entry to boot into Windows Server 2003, Windows XP, and earlier operating systems (if installed on the computer).

Is there command-line Help for Bcdedit.exe?Yes. For detailed command and option information at the command prompt, type bdedit.exe /? and bdedit.exe /? Command. For example, type bcdedit.exe /? CREATESTORE.
Top of page
New Ways To Do Familiar TasksHow to change the global debugger settingsAt the command prompt type:
bcdedit /dbgsettings DebugType [debugportort] [baudrate:Baud]
[channel:Channel] [targetname:TargetName]

OptionExplanation
DebugType
Specifies the type of debugger. DebugType can be one of SERIAL, 1394 or USB. The remaining options
depend on the debugger type selected.

Port
For SERIAL debugging, specifies the serial port to use as the debugging port.

Baud
For SERIAL debugging, specifies the baud rate to be used for debugging.

Channel
For 1394 debugging, specifies the 1394 channel to be used for debugging.

TargetName
For Universal Serial Bus (USB) debugging, specifies the USB target name to be used for debugging.

ExamplesThe following command sets the global debugger settings to serial debugging
over com1 at 115,200 baud:
bcdedit /dbgsettings serial debugport:1 baudrate:115200
The following command sets the global debugger settings to 1394 debugging
using channel 23:
bcdedit /dbgsettings 1394 CHANNEL:32
The following command sets the global debugger settings to USB debugging
using target name "debugging":
bcdedit /dbgsettings USB targetname:debugging
How to check the debugger settingsAt the command prompt, type:
bcdedit /enum Type /v

OptionExplanation
Type
Specifies the type of entries to be listed. Type can be one of the following:
•ACTIVE

•FIRMWARE

•BOOTAPP

•BOOTMGR

•OSLOADER

•INHERIT

•ALL


For example, the following command lists all entries:
bcdedit /enum all /v
How to change the default operating system entryAt the command prompt, type:
bcdedit /default ID

OptionExplanation
ID
Specifies the default GUID to be used when the time-out expires.
{466f5a88-0af2-4f76-9038-095b170dc21c} is the predefined GUID for NTLDR.
You can find the ID for a particular object by specifying bcdedit /enum all.

ExamplesThe following command sets the specified entry as the default boot manager
entry:
bcdedit /default {cbd971bf-b7b8-4885-951a-fa03044f5d71}
The following command sets the legacy Windows loader (Ntldr) as the default
entry: {466f5a88-0af2-4f76-9038-095b170dc21c} is the predefined GUID for Ntldr.
bcdedit /default {466f5a88-0af2-4f76-9038-095b170dc21c}

How to change the boot sequence for the next rebootAt the command prompt, type:
bcdedit /bootsequence {ID} {ID} {ID} …

OptionExplanation
ID
Specifies the GUID(s) that make up the boot sequence for the next restart. After this one-time boot it will revert back to the default boot order.

ExamplesThe following command sets the specified operating system as the default for the next restart. After that restart, it will be reset to DISPLAYORDER.
bcdedit /bootsequence {cbd971bf-b7b8-4885-951a-fa03044f5d71}
The following command sets two operating system entries and the
legacy Windows loader (Ntldr) in the boot manager one-time boot sequence:
bcdedit /bootsequnce {802d5e32-0784-11da-bd33-000476eba25f}
How to change boot manager time-outTo change the length of time the computer waits until the default operating system is selected, type the following:
bcdedit /timeout TimeOut

OptionExplanation
TimeOut
Specifies the time to wait, in seconds, before the boot manager selects a default entry.

For example, the following command sets the boot manager TimeOut to 15 seconds:
bcdedit /timeout 15
How to set the boot manager display orderAt the command prompt, type:
Bcdedit.exe /display {ID} {ID1} {ID2} …
or
Bcdedit.exe /displayorder {ID} [/addlast|/addfirst|/remove]

OptionExplanation
ID
Specifies one GUID or a list of GUIDs that make up the display order. You must specify at least one ID.
For more information about identifiers, type bcdedit /? ID.

ExamplesThe following command sets three operating system entries in the boot manager display order:
Bcdedit.exe /displayorder {c84b751a-ff09-11d9-9e6e-0030482375e6} {c74b751a-ff09-11d9-9e6e-0030482375e4} {c34b751a-ff09-11d9-9e6e-0030482375e7}
The following command sets two operating system entries and the legacy Windows loader in the boot manager display order:
bcdedit /displayorder {802d5e32-0784-11da-bd33-000476eba25f}
The following command adds the entry represented by the GUID to end of the boot menu display order.
bcdedit.exe /displayorder {c84b751a-ff09-11d9-9e6e-0030482375e6}-addlast
How to delete a boot entryAt the command prompt, type:
bcdedit /delete ID [/f]

OptionExplanation
ID
Specifies the GUID of the boot entry you want to delete. If ID is not specified, the current boot entry ID will be deleted.
If you specify a well-known GUID, you will have to force the deletion by specifying /f. For example:
bcdedit /delete {default} /f

For example, the following command deletes the entry with id {802d5e32-0784-11da-bd33-000476eba25f}.
bcdedit /delete {802d5e32-0784-11da-bd33-000476eba25f}
How to turn the kernel debugger on or offAt the command prompt, type:
bcdedit /debug [{ID}] {on|off}

OptionExplanation
ID
Specifies the GUID of the boot entry you want to modify. If ID is not specified, it modifies the current boot entry ID.

For example, the following command enables boot debugging for the specified operating system boot entry:
bcdedit /debug {cbd971bf-b7b8-4885-951a-fa03044f5d71} on
Note
For more information about IDs, run bcdedit /? ID.
How to set Physical Address Extension (PAE)At the command prompt, type:
bcdedit /set {ID} pae [Default|ForceEnable|ForceDisable]

OptionExplanation
ID
Specifies the ID of the operating system entry you want to change. If you do not specify ID, the current operating system settings will be modified.

For example:
bcdedit /set {802d5e32-0784-11da-bd33-000476eba25f} pae forceenable
How to set REMOVEMEMORYAt the command prompt, type the following. Removememory removes memory from the total available memory that the operating system can use.
bcdedit /set {GUID} removememory bytes

OptionExplanation
ID
Specifies the ID of the operating system entry you want to change. If you do not specify ID, the current operating system settings will be modified.

bytes
The number of bytes to remove.

ExampleThis example removes 256 MB of memory from the total available:
bcdedit /set {802d5e32-0784-11da-bd33-000476eba25f } removememory 256
How to set MAXMEM/TRUNCATEMEMORYAt the command prompt, type the following. Truncatememory disregards all memory at or above the specified physical address.
bcdedit /set {ID} truncatememory bytes
Note
We recommend that you use removememory instead. It does a better job of restricting the operating system to use the specified memory while accounting for memory holes.

OptionExplanation
ID
The ID of the operating system entry you want to change. If you don't specify ID, the current operating system settings will be modified.

bytes
Specifies the number of bytes to truncate.

ExampleThis example sets the truncate memory to 1024 MB:
bcdedit /set {802d5e32-0784-11da-bd33-000476eba25f} truncatememory 1073741824
How to add a private kernelAt the command prompt, type:
bcdedit /set {ID} kernel "ath"

OptionExplanation
ID
Specifies the identifier of the operating system entry you want to change. If you do not specify ID, then the current operating system settings will be modified.

For example:
bcdedit /set {802d5e32-0784-11da-bd33-000476eba25f} kernel "mykrnl.dll"
How to create a new Windows Vista operating system entryTo create a new Windows Vista operating system entry, use the following procedure:
To create a new Windows Vista operating system entry1.
First, copy the operating system entry you want to replicate and name it NewEntryDescription.
bcdedit /copy {GuidToCopy} /d “NewEntryDescription”

2.
This command will split the new GUID. Use the new GUID to modify the partition information by specifying:
bcdedit /set {NewGuid} device partition=x:
bcdedit /set {NewGuid} osdevice partition=x:

3.
Add the new operating system entry created to the display by specifying:
bcdedit /displayorder {NewGuid} /addlast

How to list entries of a particular typeThe /enum command lists entries in the BCD store. To list entries, type:
bcdedit /enum [Type]

OptionExplanation
Type
Specifies the type of entries to list. Type can be one of the following:
•active (default). Lists all entries in the boot manager display order.

•Firmware. Lists all firmware applications entries.

•Bootapp. Lists all boot environment applications entries.

•Bootmgr. Lists all Boot manager entries.

•Osloader. Lists all operating system entries.

•Inherit. Lists all inherit type entries.

•All. Lists all entries.


ExamplesThe following command lists all operating system loader boot entries:
bcdedit /enum osloader
The following command lists all boot manager entries:
bcdedit /enum bootmgr
How to modify BCD when installing a previous version of Windows onto a computer running Windows VistaTo install an older Windows operating system on a computer running Windows Vista, use the following procedure.
To install a previous version of Windows onto a computer running Windows Vista1.
Install the previous version of Windows.

2.
Log on to the older operating system and restore the latest boot manager by running the following. Fixntfs.exe will be in the \boot directory of the active partition.
fixntfs /lh

3.
Create a BCD entry for the older operating system by specifying the following. Bcdedit.exe is located in the \Windows\System32 directory of the Windows Vista partition. Description is the description of the new entry for the older operating system.
Bcdedit /create {legacy} /d “Description”
Bcdedit /set {legacy} device boot
Bcdedit /set {legacy} path \ntldr
Bcdedit /displayorder {legacy} /addlast

4.
Restart the computer in order for the changes to take effect.

How to create an entry to boot a WIM image from a hard diskTo create an entry to boot a Windows Imaging Format (WIM) image, you will need to create an OSloader type entry with RAMDISK options pointing to the boot partition. To do this, use the following procedure. In this procedure, the arcpath multi(0)disk(0)rdisk(0)partition(1) refers to the C: drive on the computer, and Boot.wim is a regular Boot.wim with Winload.exe in the System32 folder inside the WIM image.
To create an entry to boot a WIM image from hard disk1.
Create the {ramdisktoptions} object in your BCD store by specifying the following. Drive should be the drive that contains the image.
bcdedit /create {ramdiskoptions} /d "Ramdisk options"
bcdedit /set {ramdiskoptions} ramdisksdidevice partition=Drive
bcdedit /set {ramdiskoptions} ramdisksdipath \boot\boot.sdi

2.
Create a new boot application entry by specifying:
bcdedit /create /d "Boot from WIM" /application OSLOADER

3.
This will return an identifier (GUID) for the newly created entry. This new entry will be referred to as {GUID} in the rest of this procedure. Next specify the following:
bcdedit /set {GUID} device ramdisk=[c:]\sources\boot.wim,{ramdiskoptions}
bcdedit /set {GUID} path \windows\system32\winload.exe
bcdedit /set {GUID} osdevice ramdisk=[c:]\sources\boot.wim,{ramdiskoptions}
bcdedit /set {GUID} systemroot \windows

4.
If you are booting into Windows Preinstallation Environment (Windows PE), then you will also need to specify:
bcdedit /set {GUID} winpe yes
bcdedit /set {GUID} detecthal yes

5.
Next specify the following to add your new entry to the display order:
bcdedit /displayorder {GUID} /addlast

How to change the debugger settings of a specific entryTo override the global entry for a specific debugger setting, type one of the following.
Note
This command does not enable or disable the debugger for the specific boot entry.
•To set serial debugging, type:
bcdedit /set {GUID} debugtype:serial
bcdedit /set {GUID} baudrate:Baudrate
bcdedit /set {GUID} debugportort

•To set USB debugging, type:
bcdedit /set {GUID} debugtype:usbbcdedit /set {GUID} targetname:debugging

•To set 1394 debugging, type:
bcdedit /set {GUID} debugtype:1394bcdedit /set {GUID} targetname:32

ExampleThe following command sets the debugger setting for c74b751a-ff09-11d9-9e6e-0030482375e4 to serial debugging over com1 at 115,200 baud:
Bcdedit /set {c74b751a-ff09-11d9-9e6e-0030482375e4} debugtype:serial
Bcdedit /set {c74b751a-ff09-11d9-9e6e-0030482375e4} baudrate:115200
Bcdedit /set {c74b751a-ff09-11d9-9e6e-0030482375e4} debugport:1
转载请注明出自MSCD技术社区 本贴地址：http://bbs.mscode.cc/viewthread.php?tid=37445

[ 本帖最后由 kenknigh 于 2007-9-20 09:18 编辑 ]

能更新的话，还是更新吧

为 kenknigh版主 的认真负责致敬

我们公司一般是把系统盘给隐藏，让大家都放到E盘中，即使重新装系统，也不会影响到个人的数据

个人认为补丁还是定期更新的好, 楼主说现象应该是杀毒时清理不不干净 把系统文件给破坏了

对公司资料进行备份是必要的事情

还是更新的好，毕竟安全些，数据要备份，而且个人电脑的资料最好不要放在系统盘里