讓Windows 7 32bit 支援4GB 以上的記憶體

最近裝了一台 i5-760 的主機，正逢Ram 大降價之際，不買感覺對不起自己，索性裝了兩條4G的 Ram 。

另一個問題又來了，32位元又吃不到3.25G 以上的Ram，詢問 & Google 過後，已經有人寫出強制開啟限制的程式。

M$透過「PAE」（Physical Address Extension, 實體位址延伸）模式，增加了 4 條定址線，也就是最大的記憶體定址上限擴充到2^36=64GB。

只要作業系統也支援此技術，就能使用4GB以上的記憶體，像32位元的Linux、FreeBSD都可以。

相關使用方式與說明請參照下方連結。

※注意：此修改方式可能會影響到系統穩定度或導致系統損壞，據說在使用到XP相容性的模式情況下會無法使用；若仍要修改請自行做好相關配套措施，本人不負任何相關責任。

參考Link：

讓Windows 7 X86支援4GB以上的記憶體

32位元的XP、Vista 都抓不到4GB記憶體？

一些常見關於32位元及PAE的誤解

修改步驟的部分解釋

聖誕節是什麼？可以吃嗎？(中文字幕)

一位本職是音樂人但在Nico上偽裝成素人的歌手「hyadain」發表了一首怨念十足的聖誕歌曲「クリスマス？なに­それ美味しいの？ 」

雖然已經過了，不過還是記錄一下留著下一年的聖誕節用 ( 希望不會再用到.... )

名詞解釋：BRAS 與 DSLAM

BRAS：Broadband Remote Access Server 寬頻存取伺服器

BRAS是什麼？

他是負責你的計時制ADSL帳號登錄和啟用功能，跟以前用的modem撥接帳號Server一樣。

這就是固定制和即時制不同，運作目的是讓你的電腦跟BRAS主機做PPP通訊協定的溝通。

特殊的任務包括：
* 聚合DSLAM發出的信息
* 提供用戶PPP會話承載在IP上或者ATM 會話
* 實行服務質量（QoS）政策
* 在ISP的骨幹網上進行路由調度


DSLAM：Digital Subscriber Line Access Multiplexer 數位用戶線路連接復用設備。

為電信業者局端的DSL接取多工器，是一種安裝在近客戶端的網路設備，利用多工技術將大量用戶的DSL線路連接至高速骨幹網路。

電信公司通過將DSLAM安裝在離電話交換機較遠距離上，讓那些原本因為離電話交換機的距離超出DSL最大工作距離的客戶，得以使用DSL技術。



有空再補齊好了...


參考資料：

數字用戶線接入復用設備 by Wiki

寬頻遠程接入服務 by Wiki

IP路由器的DSLAM by 聚散之間

BRAS by 阿彭的網路日誌

Operating System Study Guide

一個 Operating System 的學習筆記

http://www.csie.ntnu.edu.tw/~swanky/os/

Router Log：%NHRP-3-PAKREPLY: Receive Registration Reply packet with error - unique address registered already(14) 的Error Message

異常 Log：
Sep 14 05:37:05.692 TWN: %AAA-3-BADSERVERTYPEERROR: Cannot process accounting server type radius (UNKNOWN)
Sep 14 05:37:05.708 TWN: %DIALER-6-UNBIND: Interface Vi2 unbound from profile Di1
Sep 14 05:37:05.712 TWN: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to down
Sep 14 05:37:06.688 TWN: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to down
Sep 14 05:37:06.692 TWN: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel471, changed state to down
Sep 14 05:37:27.980 TWN: %DIALER-6-BIND: Interface Vi2 bound to profile Di1
Sep 14 05:37:27.984 TWN: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to up
Sep 14 05:37:29.692 TWN: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to up
Sep 14 05:37:29.736 TWN: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel471, changed state to up
Sep 14 05:37:32.344 TWN: %NHRP-3-PAKREPLY: Receive Registration Reply packet with error - unique address registered already(14)
Sep 14 06:17:29.770 TWN: %NHRP-3-PAKREPLY: Receive Registration Reply packet with error - unique address registered already(14)
Sep 14 06:57:29.779 TWN: %NHRP-3-PAKREPLY: Receive Registration Reply packet with error - unique address registered already(14)
Sep 17 05:21:28.664 TWN: %AAA-3-BADSERVERTYPEERROR: Cannot process accounting server type radius (UNKNOWN)
Sep 17 05:21:28.684 TWN: %DIALER-6-UNBIND: Interface Vi2 unbound from profile Di1
Sep 17 05:21:28.688 TWN: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to down
Sep 17 05:21:29.664 TWN: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to down
Sep 17 05:21:29.668 TWN: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel471, changed state to down
Sep 17 05:21:50.956 TWN: %DIALER-6-BIND: Interface Vi2 bound to profile Di1
Sep 17 05:21:50.960 TWN: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to up
Sep 17 05:21:52.312 TWN: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to up
Sep 17 05:21:52.408 TWN: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel471, changed state to up
Sep 17 05:21:55.216 TWN: %NHRP-3-PAKREPLY: Receive Registration Reply packet with error - unique address registered already(14)
Sep 17 06:01:52.413 TWN: %NHRP-3-PAKREPLY: Receive Registration Reply packet with error - unique address registered already(14)
Sep 17 06:41:52.443 TWN: %NHRP-3-PAKREPLY: Receive Registration Reply packet with error - unique address registered already(14)
Sep 20 05:23:51.348 TWN: %AAA-3-BADSERVERTYPEERROR: Cannot process accounting server type radius (UNKNOWN)
Sep 20 05:23:51.368 TWN: %DIALER-6-UNBIND: Interface Vi2 unbound from profile Di1
Sep 20 05:23:51.372 TWN: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to down
Sep 20 05:23:52.348 TWN: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to down
Sep 20 05:23:52.348 TWN: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel471, changed state to down
Sep 20 05:24:13.640 TWN: %DIALER-6-BIND: Interface Vi2 bound to profile Di1
Sep 20 05:24:13.644 TWN: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to up
Sep 20 05:24:15.076 TWN: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to up
Sep 20 05:24:15.124 TWN: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel471, changed state to up
Sep 20 05:24:17.904 TWN: %NHRP-3-PAKREPLY: Receive Registration Reply packet with error - unique address registered already(14)
Sep 20 06:04:15.158 TWN: %NHRP-3-PAKREPLY: Receive Registration Reply packet with error - unique address registered already(14)
Sep 20 06:44:15.168 TWN: %NHRP-3-PAKREPLY: Receive Registration Reply packet with error - unique address registered already(14)
[點擊此處縮放]

Client 端是使用浮動 IP 來做 PPPOE，每三天更換一次 Public IP

撥接介面：
Dialer1 is up, line protocol is up (spoofing)
Hardware is Unknown
Internet address is ********
MTU 1492 bytes, BW 56 Kbit/sec, DLY 20000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation PPP, loopback not set
Keepalive set (10 sec)
DTR is pulsed for 1 seconds on reset
Interface is bound to Vi2
Last input never, output never, output hang never
Last clearing of "show interface" counters 1w6d
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: weighted fair
Output queue: 0/1000/64/0 (size/max total/threshold/drops)
Conversations 0/0/16 (active/max active/max total)
Reserved Conversations 0/0 (allocated/max allocated)
Available Bandwidth 42 kilobits/sec
30 second input rate 0 bits/sec, 0 packets/sec
30 second output rate 0 bits/sec, 0 packets/sec
302042 packets input, 17189948 bytes
113534 packets output, 1680424 bytes
Bound to:
Virtual-Access2 is up, line protocol is up
Hardware is Virtual Access interface
MTU 1492 bytes, BW 56 Kbit/sec, DLY 20000 usec,
reliability 255/255, txload 1/255, rxload 9/255
Encapsulation PPP, LCP Open
Listen: CDPCP
Open: IPCP
PPPoE vaccess, cloned from Dialer1
Vaccess status 0x44, loopback not set
Keepalive set (10 sec)
Interface is bound to Di1 (Encapsulation PPP)
Last input 00:00:00, output never, output hang never
Last clearing of "show interface" counters 17:19:17
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 2000 bits/sec, 4 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
22421 packets input, 1441224 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
6237 packets output, 101996 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 unknown protocol drops
0 output buffer failures, 0 output buffers swapped out
0 carrier transitions
[點擊此處縮放]

設定值：
!
interface Dialer1
mtu 1492
ip address negotiated
encapsulation ppp
load-interval 30
dialer pool 1
dialer watch-group 1
dialer-group 1
ppp authentication pap chap callin
ppp chap hostname ********
ppp chap password ********
ppp pap sent-username ******** password ********
!
[點擊此處縮放]

在Cisco Support Community 找到了一篇關於此問題解決方法供參考

---------- 下列轉至 Cisco Support Community ----------

( 點選標題 Link 可直接連至原頁面 )
Unable to pass traffic on the Dynamic Multipoint VPN tunnel with the "%NHRP-3-PAKREPLY: Receive Registration Reply packet with error - unique address registered already(14)" error message

Core issue

If the spoke router is configured with the dynamic IP address, the cached nonbroadcast, multiaccess (NBMA) with the Next Hop Resolution Protocol (NHRP) address on the hub does not match to a new dynamic NBMA address with the NHRP address. If this happens, the %NHRP-3-PAKREPLY: Receive Registration Reply packet with error - unique address registered already(14) error message appears on the spoke router.

Resolution

In order to resolve this issue, configure the ip nhrp registration no-unique command on the spoke router.

If the unique flag is set in the NHRP registration request packet, a Next Hop Server (NHS) must reject any registration attempts for the same private address that uses a different NBMA address. If a client receives a new IP address, for example on Dynamic Host Configuration Protocol (DHCP), and tries to register before the cache entry on the NHS times out, the NHS must reject it.

If you configure the ip nhrp registration no-unique command, the unique flag is not set, and the NHS can override the old registration information.

This command is useful in an environment where client IP addresses can change frequently such as a dial environment.
[點擊此處縮放]

演算法筆記

找到一個還不錯的演算法介紹網站

http://www.csie.ntnu.edu.tw/~u91029/index.html

名詞解釋

Boot manager
開機管理員，這是一種裝在開機區的小程式，它可以管理不同開機區所安裝的各種作業系統。

Bootstrap Loader
這是一種可以用來將OS kernel載入(Loading)到RAM內的小程式，通常寫在開機磁軌，當BIOS找到開機磁軌時第一個執行的程式就是它，而非一般人所誤解的"OS"。

Lilo
Linux loader，用來將Linux載入到mamory的Bootstrap Loader，它同時也是Boot manager。

MBR ( Master Boot Record )
每個硬碟第0軌的第一個磁區起算，掉佔Cylinder 0-1這一塊磁區的空間，它的用途是放OS Loader之用，在開機程序pass過BIOS 之後下一個指向的目標就是它，如果找不到，才會找尋Active 分割區。

OS loader
同Bootstrap Loader之意，每個作業系統有其專屬的OS Loader用來將其kernel Loading到memory中 。

關閉WinXP自動播放的功能(XP Professsional Only)

1.在 [開始] 中選擇 [執行]

2.輸入 gpedit.msc 後按下確定

3.再跳出的 [群組原則] 對話視窗中選擇 [電腦設定] → [系統管理範本] → [系統]

4.點選 [關閉自動播放]

5.在設定頁選擇 [已啟用] ，並將 [自動停用播放] 改成 [所有磁碟機] ，再按下確定即可

WinXP 預約關機指令整理

shutdown -s -t 3600 (一小時後)
shutdown -s -t 7200 (二小時後)
shutdown -s -t 10800 (三小時後)
shutdown -s -t 14400 (四小時後)
shutdown -s -t 18000 (五小時後)
shutdown -s -t 28800 (八小時後)
shutdown -a (取消關機)

===== 可搭配以下指令混合使用 =====
-l 登出
-s 電腦關機
-r 重新啟動
-t xx xx秒後關機
-c "comment" 註解
-f 強制關閉程式
-i 關區網中的電腦 有時會存取被拒

at hh:mm 在xx點mm分關機 / 每個禮拜的行程
hh裡要用24時制