Windows Update 無法更新

最近的電腦很奇怪
不知道為什麼會無法更新
執行windows update 都是沒有問題
然後會出現一堆package要更新
選擇更新後卻失敗

後來發現應該是電腦中缺少了一些檔案..
用下面的方式修復應該就可以了

1.開始->執行->輸入 cmd
2.執行下面的指令，每一行執行完後要按ENTER鍵
regsvr32 wuapi.dll
regsvr32 wuaueng.dll
regsvr32 wuaueng1.dll
regsvr32 wucltui.dll
regsvr32 wups.dll
regsvr32 wups2.dll
regsvr32 wuweb.dll

如此一來updater需要的dll應該就會都有了...問題也就解決了~~

Adding a new slice, problem with sysinstall

1. Create a new slice : sysinstall->Configure->Fdisk

2. Make sure only one ACTIVE slice ( partition )
fdisk /dev/ad0
fdisk -a -1 /dev/ad0

3. Add a 'standard' label, remember disks start from zero, but slices start
from one!:
# bsdlabel -w /dev/ad0s3

4. Edit the label:
# bsdlabel - e /dev/ad0s3
Change fstype on the line beginning a: from unknown to 4.2BSD, then save
and exit.

5. Format the new partition:
# newfs /dev/ad0s3a

6. Test mount the partition:
# mount /dev/ad0s3a /mnt

7. Edit /etc/fstab. Add a new line similar to the line for /dev/ad0s2a.
Careful! getting fstab wrong can prevent your system starting.
Test the new fstab with # mount -a.

解決 XP 硬碟轉個不停的方法

用 regedit 更改..在
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Dfrg\BootOptimizeFunction

Enable 的 Key ,改為 N 就可以了.
在Enable 上面按右鍵, 修改就可以了.

XP有一系列的自我調整功能, 這種功能的設計, 可以根據你的系統設定與使用形態, 而為你做效能的改進. 例如, XP會監視你使用什麼應用程式, 每三天當中有閒置的時候, 它就會自動在硬碟上將這些檔案放在一起, 並擺放在硬碟較密集的外圍區. 這將直接減少硬碟的搜索時間, 並且還將會提高應用程式的載入速度, 特別是在大容量的硬碟機上.

所謂Y是這樣的:XP有一系列的自我調整功能,這種功能的設計, 可以根據你的系統設定與使用形態,而為你做效能的改進, 例如, XP會監視你使用什麼應用程式, 等幾天如果有當中有閒置的時候, 它就會自動在硬碟上將這些檔案放在一起, 並擺放在硬碟較密集的外圍區. 這將直接減少硬碟的搜索時間, 並且還將會提高應用程式的載入速度, 特別是在大容量的硬碟機上.

那如果改成N的話, 就是代表這個特殊功能關閉, 也就是說, 你所裝的應用程式有閒置的時候, 作業系統是採去不做任何動作的作法, 一切都讓使用者自己來處理, 相對的檔案如果越塞越多的話, 你就會感覺的到以後一開啟任何應用程式或是檔案就會變得很慢了.

解除 Windows XP 自動壓縮/解壓縮功能

執行-->regsvr32 /u zipfldr.dll

設定 "我最近的文件"

(1) Windows XP 結束時清除最近開啟文件的歷程紀錄的方法
以電腦系統管理員的權限登錄
開始/執行
輸入 gpedit.msc 確定
本機電腦 原則/使用者設定/系統管理範本/[開始]功能表和工作列
選右邊 結束時清除最近開啟文件的歷程紀錄 進入
設為已啟用

(2) 如果要把記錄的功能關閉
選 不保留最近檔案開啟的記錄

(3) 如果不想顯示 "我最近的文件" 選項出現在開始功能表
選 [開始] 功能表中移除 [文件] 功能表

恢復 windows XP 的system loader

(linux)

fdisk /mbr

(xp)
xp光碟開機
使用者修復模式
fixmbr

Installing dri drivers on FreeBSD

Installing dri drivers on FreeBSD

Friday, November 26 2004 @ 04:17 PM CET Contributed by: bart Views: 3724 I am getting quite a few questions with regards to installing dri enabled graphics drivers on FreeBSD. In this article I'll discuss the general setup, and it shoudl enable you to get this to work for every card that is supported. Supported hardware: Older Matrox hardware (g200 - g550), everything before the P series Older ATI hardware (8xxx and 9000 upto 9400, basicly everything with a rv2xx chipset) Some S3 hardware What is inmediately clear from this is that it almost exclusively concerns older hardware. WHat is also clear is the complete lack of NVIDIA in the list. Why do you need dri? Accelerated 3d graphics, ie: OpenGL support. OpenGL support is usefull for more then a bit of gaming. Makign previews in renderign software is just one of the more serious uses for it. What do you need? Of course you need a supported video card. Beyond that, you will need the sources for the kernel and you need XFree86 v4.x or Xorg 6.7 or later. Installation After installing the kernel sources, do the following: cd /usr/src/sys/modules/drm make make install Now you have the direct rendering modules installed, and you can load the one appropriate for your video card. The best way to do this is by adding it to the boot loader configuration, to do so, you have to add a line to /boot/loader.conf similar to: radeon_load="YES" Replace radeon with the proper module name for your card (mga for Matrox, s3 for.. s3) Known issues It is worth noting that you really should load the module at boot time or at least make absolutely sure that you have either agp enabled in your kernel, or load the agp module at boot. The issue here is that the agp module can not be loaded after the kernel booted, and the dri modules depend on agp. So if you don't have agp support when your kernel boots, dri is NOT going to work ever. Installing X Once the module works, you will get a message during startup that will tell you that drm is enabled and has found soem graphics hardware. Now it is time for configuring the X server. This should be pretty straightforward, just make sure you have the dri and glx modules loaded, and select a driver appropriate for your card, and things should be fine. You can verify if your setup indeed uses direct rendering with the glxinfo command. Not getting X to start? If you do not get a working X at all but the dri modules are loaded by the kernel and give the expected output on boot, it might well eb that you have a problem with your AGP setup. The first thing to do in such a case is goto your bios and DISABLE fast write and any other advanced AGP features. Try again and see if it works now. If it does, enable the features one by oen and try each time if the X server still starts and works. Especially ATI Radeon cards on boards with a VIA chipset are extremely picky about AGP setup, and will fail in mysterious ways when you enable fast write, so unless you like such mysteries, you better just disable this.