- Feb 21 Thu 2019 21:54
-
大市方向 02/2019 看美股仍是牛市, HSI 又開始牛市
- Aug 18 Sun 2013 03:24
-
取消多远程桌面限制(对所有VISTA版本)
1) Change the termsrv.dll system DLLs. See chapter how.
2) For the Home Premium version, modifying registry keys (which is incorporated Vista Ultimate), we will building us one. Reg. This is only for Vista Home Premium. See the chapter on how to do it.
Once the above points, we proceed to installation. To do this, we must work on a console in elevated mode, ie Start, Accessories, right click on Command Prompt and "Run as Administrator". I guess we have the new and modified dll. Reg in a folder called TMP hanging from c: \
3) We in the console:
cd \ tmp
net stop "Terminal Services"
takeown / a / f% SystemRoot% \ System32 \ termsrv.dll
icacls% SystemRoot% \ System32 \ termsrv.dll / Grant Administrators: F
(If your version of Windows is the Spanish version, change the line above "Administrators" to "Administrators"
ren% SystemRoot% \ System32 \ termsrv.dll termsrv.dll. bak
termsrv.dll copy% SystemRoot% \ System32 \ termsrv.dll
4) If our version is Home Premium, ejecutams the. Reg created in step 2) as follows:
regedit / s ts.reg
5) If we want each user can have separate sessions (ie, if a user is already logged, logging in with another user, instead of taking your session, you create a new clean session), we must incorporate key record we can do as follows:
REG ADD "HKLM \ SYSTEM \ CurrentControlSet \ Control \ Terminal Server" / v fSingleSessionPerUser / t REG_DWORD / d 0 / f
If we turn this feature off at any time and take control of the existing session, we may at any time modify the password again by changing the value 0 to a 1 by:
REG ADD "HKLM \ SYSTEM \ CurrentControlSet \ Control \ Terminal Server" / v fSingleSessionPerUser / t REG_DWORD / d 1 / f
6) Because we do not appear in the Home on the remote connections, the ability to enable remote desktop or not, we do this through a registry key. To activate the Remote Desktop:
REG ADD "HKLM \ SYSTEM \ CurrentControlSet \ Control \ Terminal Server" / v fDenyTSConnections / t REG_DWORD / d 0 / f
and at any time can be disabled by:
REG ADD "HKLM \ SYSTEM \ CurrentControlSet \ Control \ Terminal Server" / v fDenyTSConnections / t REG_DWORD / d 1 / f
7) Start and the service we previously stopped at point 3)
net start "Terminal Services"
- May 24 Fri 2013 00:36
-
簡單增加參數將 Chrome 的 Cache 轉移到 RamDisk

http://brilifes.blogspot.tw/2013/03/chrome-cache-ramdisk_13.html
Google 瀏覽器本身並不直接提供使用者自訂快取空間大小以及資料夾位置的設定, 使用者必須還得透過新增參數在捷徑裡頭才能發揮作
- May 16 Thu 2013 22:24
-
DS4700 通過串口修改出廠設置和IP地址

好像7.0以後的都改了串口連接時的用的口令和密碼
用戶:shellUsr
密碼:wy3oo&w4
串口登錄到控制器,然後執行下面的命令
-> loadDebug
value = 113082072 = 0x6bd7ed8
11/03/10-05:19:26 (tShell0): NOTE: loading flash file: Debug
-> setSAPassword_MT ""
ReturnCode = 0x1
value = 1 = 0x1
-> unld "ffs ebug"
value = 0 = 0x0
- May 16 Thu 2013 22:18
-
IBM DS 控制器串口命令文档 dell也一样
When you connect to the disk controller using a serial interface port, the controller status is reported as locked.
使用超級終端進行連接,輸入回車,然後Ctrl+Break(有時需要多按幾次),屏幕會出現設置波特率的提示:
Send for shell access or baud rate change
Set baud rate: press within 5 seconds
- May 16 Thu 2013 22:09
-
IBM DS3200 and DS3400 SAN Reset – Syswipe
Recently we needed to expand an array from 700GB to 1.4TB, the array build went horribly wrong, the IBM software would not let us delete the old array or logical drives, as we had an exact copy of the SAN data, we decided to reset the IBM DS3200 sub system, this leaves the IP as normal, and allows us to rebuild the arrays correctly.
- May 16 Thu 2013 22:06
-
Clearing a SAN lockdown state
- May 16 Thu 2013 22:02
-
IBM Storage DS3512 does not boot: Error: LU & E0

AIX, Linux, virtualization and storage
"Patch Management
Brocade / IBM SAN switches model »
DS3512 does not boot: Error: LU & E0 ->lemClearLockdown
- May 01 Wed 2013 04:16
-
實踐與共享:實現Windows7系統全自動安裝的“無人值守應答文件”及其“使用方法”

http://hi.baidu.com/zbezj/item/55e3209d50a165d07a7f0155
實踐與共享:實現Windows7系統全自動安裝的“無人值守應答文件”及其“使用方法”
- May 01 Wed 2013 04:09
-
實踐與交流:“$OEM$”在製作OEM版系統中的作用及其配合“應答文件”的使用方法
實踐與交流:“$OEM$”在製作OEM版系統中的作用及其配合“應答文件”的使用方法
製作OEM版的Windows 7系統,前面介紹過很多次,不管哪種方法都離不開“$OEM$”這個文件夾,“$OEM$”文件夾下通常存在“$$”、“$1”文件夾,在安裝系統的過程時(以系統安裝到C盤為例說明),安裝程序會自動把“$$”文件夾下的所有文件複製到C:\Windows下,將“$1”下的所有文件複製到C盤根目錄。然後安裝程序會自動檢測相應目錄下的OEM證書導入系統,然後導入密鑰、按照“應答文件”及批處理等進行安裝。
通常“$OEM$”文件夾有三種使用方法:1.集成到boot.wim;2.集成到install.wim;3.直接複製到鏡像的Sources目錄下,這三種方法前面都詳細的講過。現再簡單介紹一下——
首先請看之前寫過的OEM版系統製作方法以及應答文件使用:
製作“自動選擇品牌”的OEM版Windows7鏡像
製作“隨機”版(OEM版)的Windows 7鏡像+安裝方法
答疑解惑:回复網友在使用“Windows 7無人值守應答文件”過程中出現的幾個問題
實踐與共享:實現Windows7系統全自動安裝的“無人值守應答文件”及其“使用方法”
★集成到Sources目錄下
直接將“$OEM$”文件夾複製到Sources目錄下即可。
★集成到install.wim
1.在F盤新建boot文件夾(作為例子),把install.wim複製到f盤根目錄。
2.運行命令imagex /mountrw f:\install.wim 5 f:\boot
——以32位的旗艦版為例
3.將“$$”裡的文件複製到f:\boot\windows下,將“$1”裡的文件複製到f:\boot。
4.運行命令imagex /unmount f:\boot /commit
★集成到boot.wim
1.在F盤新建boot文件夾(作為例子),把boot.wim複製到f盤根目錄
2.運行命令imagex /mountrw f:\boot.wim 2 f:\boot
3.將lenovo文件夾複製到boot文件夾下
4.新建記事本,命名為“winpeshl.ini”,放到f:\boot目錄下的windows\system32目錄下,其內容如下:
[LaunchApp]
AppPath = %SYSTEMDRIVE%\sources\setup.exe /unattend:%SYSTEMDRIVE%\lenovo\autounattend.xml
5.運行命令imagex /unmount f:\boot /commit
友情提示:本文的三種方法各有優缺點,應視不同情況進行選擇。
-------------------------------------------------- -----------------------------------
- May 01 Wed 2013 04:05
-
推薦下載使用:“單一可執行的綠色軟件”製作工具Cameyo最新版+簡明使用方法
推薦下載使用:“單一可執行的綠色軟件”製作工具Cameyo最新版+簡明使用方法
Cameyo是一款可以製作綠色軟件的工具,運行Cameyo後會自動創建一個系統的“快照”,然後安裝應用軟件後會再次創建一個系統“快照”,最後打包成單一可執行的EXE程序。
官方網站:http://www.cameyo.com/index.aspx
- May 01 Wed 2013 04:02
-
實踐與探索:使用虛擬機VMware模擬“UEFI BIOS主板電腦”來安裝Windows 7系統

http://hi.baidu.com/zbezj/item/ed1ef5f034a2d0dd43c36a56
實踐與探索:使用虛擬機VMware模擬“UEFI BIOS主板電腦”來安裝Windows 7系統

