❶ 運行腳本後電腦重啟
最好你換個腳本，或者運行腳本時把殺毒和防火牆關掉。
❷ 寫一個自動重啟.bat腳本,並不是重啟電腦哦
不清楚你的實際文件/情況，僅以問題中的樣例/說明為據；以下代碼復制粘貼到記事本，另存為xx.bat，編碼選ANSI
@echo off
rem bat間歇性重新運行
set #=Any question&set @=WX&set $=Q&set/az=0x53b7e0b4
title %#% +%$%%$%/%@% %z%
cd /d "%~dp0"
set sleep=1800
:loop
>"tmp.bat" echo;title #mark#
>>"tmp.bat" echo;php "%~dp0A.php"
start "" "tmp.bat"
timeout /t %sleep% /nobreak
for /f "tokens=2 delims=," %%a in ('tasklist /fi "imagename eq cmd.exe" /v /fo csv^|find "#mark#"') do taskkill /f /pid %%a /t
goto loop
❸ 簡單游一點擊啟動腳本電腦就重啟，怎麼回事怎麼解決
估計是殺毒軟體造成的，一點啟動，殺毒軟體要控制。但是不重啟又處理不了。所以自動重啟了
❹ 如何用bat命令重啟電腦或關機
關閉計算機
shutdown/s/t0
重啟計算機
shutdown/r/t0
用法：
/s 為關閉計算機參數開關
/r 為關機計算機並重啟計算機
/t 可以理解為關閉等待的時間，0等於不等待，10等於在關閉前等待10秒在關閉計算機
❺ 誰會寫一個腳本程序，雙擊重啟電腦的那種
去bat吧，那裡面有
❻ 怎麼寫個腳本 然用戶在打開某個軟體的時候電腦自動重啟呢
把下面這行保存成，"重啟.bat'文件即可
shutdown -r -t 0
這個要自己寫一個hook。每次創建進程是你都知道是那個程序，看到不喜歡的程序你就可以從新啟動了。
這里有網路介紹
http://ke..com/view/1208620.htm#sub1208620
這里有msdn介紹
SetWindowsHookEx Function
--------------------------------------------------------------------------------
The SetWindowsHookEx function installs an application-defined hook procere into a hook chain. You would install a hook procere to monitor the system for certain types of events. These events are associated either with a specific thread or with all threads in the same desktop as the calling thread.
Syntax
HHOOK SetWindowsHookEx( int idHook,
HOOKPROC lpfn,
HINSTANCE hMod,
DWORD dwThreadId
);
Parameters
idHook
[in] Specifies the type of hook procere to be installed. This parameter can be one of the following values.
WH_CALLWNDPROC
Installs a hook procere that monitors messages before the system sends them to the destination window procere. For more information, see the CallWndProc hook procere.
WH_CALLWNDPROCRET
Installs a hook procere that monitors messages after they have been processed by the destination window procere. For more information, see the CallWndRetProc hook procere.
WH_CBT
Installs a hook procere that receives notifications useful to a computer-based training (CBT) application. For more information, see the CBTProc hook procere.
WH_DEBUG
Installs a hook procere useful for debugging other hook proceres. For more information, see the DebugProc hook procere.
WH_FOREGROUNDIDLE
Installs a hook procere that will be called when the application's foreground thread is about to become idle. This hook is useful for performing low priority tasks ring idle time. For more information, see the ForegroundIdleProc hook procere.
WH_GETMESSAGE
Installs a hook procere that monitors messages posted to a message queue. For more information, see the GetMsgProc hook procere.
WH_JOURNALPLAYBACK
Installs a hook procere that posts messages previously recorded by a WH_JOURNALRECORD hook procere. For more information, see the JournalPlaybackProc hook procere.
WH_JOURNALRECORD
Installs a hook procere that records input messages posted to the system message queue. This hook is useful for recording macros. For more information, see the JournalRecordProc hook procere.
WH_KEYBOARD
Installs a hook procere that monitors keystroke messages. For more information, see the KeyboardProc hook procere.
WH_KEYBOARD_LL
Windows NT/2000/XP: Installs a hook procere that monitors low-level keyboard input events. For more information, see the LowLevelKeyboardProc hook procere.
WH_MOUSE
Installs a hook procere that monitors mouse messages. For more information, see the MouseProc hook procere.
WH_MOUSE_LL
Windows NT/2000/XP: Installs a hook procere that monitors low-level mouse input events. For more information, see the LowLevelMouseProc hook procere.
WH_MSGFILTER
Installs a hook procere that monitors messages generated as a result of an input event in a dialog box, message box, menu, or scroll bar. For more information, see the MessageProc hook procere.
WH_SHELL
Installs a hook procere that receives notifications useful to shell applications. For more information, see the ShellProc hook procere.
WH_SYSMSGFILTER
Installs a hook procere that monitors messages generated as a result of an input event in a dialog box, message box, menu, or scroll bar. The hook procere monitors these messages for all applications in the same desktop as the calling thread. For more information, see the SysMsgProc hook procere.
lpfn
[in] Pointer to the hook procere. If the dwThreadId parameter is zero or specifies the identifier of a thread created by a different process, the lpfn parameter must point to a hook procere in a dynamic-link library (DLL). Otherwise, lpfn can point to a hook procere in the code associated with the current process.
hMod
[in] Handle to the DLL containing the hook procere pointed to by the lpfn parameter. The hMod parameter must be set to NULL if the dwThreadId parameter specifies a thread created by the current process and if the hook procere is within the code associated with the current process.
dwThreadId
[in] Specifies the identifier of the thread with which the hook procere is to be associated. If this parameter is zero, the hook procere is associated with all existing threads running in the same desktop as the calling thread.
Return Value
If the function succeeds, the return value is the handle to the hook procere.
If the function fails, the return value is NULL. To get extended error information, call GetLastError.
Remarks
SetWindowsHookEx can be used to inject a DLL into another process. A 32-bit DLL cannot be injected into a 64-bit process, and a 64-bit DLL cannot be injected into a 32-bit process. If an application requires the use of hooks in other processes, it is required that a 32-bit application call SetWindowsHookEx to inject a 32-bit DLL into 32-bit processes, and a 64-bit application call SetWindowsHookEx to inject a 64-bit DLL into 64-bit processes. The 32-bit and 64-bit DLLs must have different names.
An error may occur if the hMod parameter is NULL and the dwThreadId parameter is zero or specifies the identifier of a thread created by another process.
Calling the CallNextHookEx function to chain to the next hook procere is optional, but it is highly recommended; otherwise, other applications that have installed hooks will not receive hook notifications and may behave incorrectly as a result. You should call CallNextHookEx unless you absolutely need to prevent the notification from being seen by other applications.
Before terminating, an application must call the UnhookWindowsHookEx function to free system resources associated with the hook.
The scope of a hook depends on the hook type. Some hooks can be set only with global scope; others can also be set for only a specific thread, as shown in the following table.
Hook Scope
WH_CALLWNDPROC Thread or global
WH_CALLWNDPROCRET Thread or global
WH_CBT Thread or global
WH_DEBUG Thread or global
WH_FOREGROUNDIDLE Thread or global
WH_GETMESSAGE Thread or global
WH_JOURNALPLAYBACK Global only
WH_JOURNALRECORD Global only
WH_KEYBOARD Thread or global
WH_KEYBOARD_LL Global only
WH_MOUSE Thread or global
WH_MOUSE_LL Global only
WH_MSGFILTER Thread or global
WH_SHELL Thread or global
WH_SYSMSGFILTER Global only
For a specified hook type, thread hooks are called first, then global hooks.
The global hooks are a shared resource, and installing one affects all applications in the same desktop as the calling thread. All global hook functions must be in libraries. Global hooks should be restricted to special-purpose applications or to use as a development aid ring application debugging. Libraries that no longer need a hook should remove its hook procere.
Windows 95/98/Me: SetWindowsHookEx is supported by the Microsoft Layer for Unicode (MSLU). However, it does not make conversions. To see Unicode messages, notifications, and so forth, you must subclass the window. To use this version of the application programming interface (API), you must add certain files to your application, as outlined in Installing and Releasing Hook Proceres.
Example
For an example, see Installing and Releasing Hook Proceres.
Function Information
Minimum DLL Version user32.dll
Header Declared in Winuser.h, include Windows.h
Import library User32.lib
Minimum operating systems Windows 95, Windows NT 3.1
Unicode Implemented as ANSI and Unicode versions.
See Also
Hooks Overview, CallNextHookEx, CallWndProc, CallWndRetProc, CBTProc, DebugProc, ForegroundIdleProc, GetMsgProc, JournalPlaybackProc, JournalRecordProc, LowLevelKeyboardProc, LowLevelMouseProc, KeyboardProc, MouseProc, MessageProc, ShellProc, SysMsgProc, UnhookWindowsHookEx
❼ 電腦自動重啟命令
電腦自動重啟命令是shutdown -r -t xxx（t後方的是進行重啟的時間，單位為秒）。
電腦上執行自動重啟的具體操作步驟如下：
1、首先在電腦的桌面上點擊鍵盤上的「windows+r」組合鍵，然後就可以調出運行對話框。
