好好休息一下,旅游回来又连续上了一个多星期的班,要好好睡一下了。
Sep 28 2008
windows 2003 在AHCI sata下的安装
AHCI,全称为Serial ATA Advanced Host Controller Interface(串行ATA高级主控接口),是在Intel的指导下,由多家公司联合研发的接口标准,其研发小组成员主要包括Intel、AMD、戴尔、Marvell、迈拓、微软、Red Hat、希捷和StorageGear等著名企业。AHCI描述了一种PCI类设备,主要是在系统内存和串行ATA设备之间扮演一种接口的角色,而且它在不同的操作系统和硬件中是通用的。
AHCI通过包含一个PCI BAR(基址寄存器),来实现原生SATA功能。由于AHCI统一接口的研发成功,使得支持串行ATA产品的开发工作大为简化,操作系统和设备制造商省去了单独开发接口的工作,取而代之的是直接在统一接口上进行操作,可以实现包括NCQ(Native Command Queuing)在内的诸多功能。
很不幸,windows xp怎么弄都没有问题,windows 2003默认是没有AHCI驱动的,如果不想使用模拟ATA形式,就需要想想办法了,一共整理了几种:
1、你手头上有软盘,也有软驱。。。把AHCI的驱动拷到软盘上面(一般硬件厂商都有提供软盘版的,intel就是matrix disk),然后开始安装,F6,S指定驱动。
2、usb软驱,u盘模拟usb-fdd,需要u盘上面有模拟开关的,能够在bios里面认出usb软驱,和上面差不多,但是在我的Dell690上面,windows 2003的安装程序会检查软驱,然后u盘灯闪了几下就灭了,系统挂起,很奇怪。
3、整合驱动,有nLite,直接可以整合,如果想要修改番茄花园之类的多合一光盘,就要手动来了
http://support.microsoft.com/kb/254078
首先用ultraiso提取引导信息到bif文件,提取所有文件到文件夹,然后修改,一般就是加$OEM$/$1/Drivers/network,把文件拷进去,改txtsetup.sif
增加
[Unattended]
OemPnPDriversPath = “Drivers\network;Drivers\Modem;Drivers\Video”
有几个就加几个。。。
然后用ultraiso新建一个iso,导入原来的引导信息bif,在文件,属性那里选择优化文件,然后一个个文件夹加进去。。另存为一个新的光盘,如果没有优化文件的话iso会很大的,其实就是把名字和大小一样的文件只保存一份,剩下的在光盘上面link过去,好像不检验md5的,没试验过,不清楚,所以如果有名字大小一样,但是内容不同的文件就比较麻烦了。
这样安装盘里面就整合了你自己的驱动了,有人说番茄花园已经整合DPS驱动包,但是不知道为什么就是没有我的Dell 690的ESB2 AHCI驱动,郁闷呢。。
4、前面都是比较复杂的方法,下面来个简单的,也适合已经是模拟ATA方式的windows转换到AHCI
用模拟ATA安装了windows
第一步也是找到驱动,主板自带的一般就是看看自己的南桥是什么,用Everest 看看,然后找对应的AHCI驱动名字
然后强行安装,把硬盘管理器里面的磁盘管理器驱动更新,然后从磁盘安装,指定inf,指定名字
重启,bios切换到AHCI,启动windows,ok
如果驱动错了,windows应该会蓝屏,这样重启F8,恢复最后一次正确的配置,就可以重新进入了,没有危险
我的Dell690用最后的就搞定了。。
Sep 27 2008
2Wire 2700HG 升级固件方法
昨天淘了一只2700HG-B,可以同步adsl,用起来还不错,研究了一下貌似固件已经比较稳定了,不过还是记录一下升级固件的方法,方便日后操作,嘿嘿。
管理页面是通过url http://路由器ip/management ,里面有一些隐藏信息。
升级是通过url http://路由器ip/upgrade 进行的
2Wire各个型号的固件好像通用的。。汗一个。
各个版本的固件在下面的网页找到:
转自KoGt2S
Que tal CUM!!
Les dejo aquí varias versiones de Firmwares para el 2Wire, si pueden contribuir con su experiencia se los agradeceré, indicando el Modelo del 2Wire y el Firmware soportado.
En lo personal e trabajado con 2wire HG2700 Ver. 4.25.19 y HW1800 Ver 3.7.5.23, sin ningún problema.
Tuve problemas con un 2Wire 1070, lo tengo de pisa papeles.
Realice todas la actualizaciones vía Inalámbrica, excepto 2Wire 1070.
Driver′s y documentación http://www.2wire.com/?p=266
KeyCodes http://www.2wire.com/?p=268
KeyCode Prodigy 52AD-2AD4-6266-22NA-B27M
Paginas escondidas
Configuracion Vo IP http://192.168.1.254/?PAGE=V00
Para actualizar manualmente tu 2wire entrando a la siguiente página:
http://home/upgrade
http://gateway.2wire.net/tech/upgrade.html
Seleccionas el archivo y pulsas siguiente, recuerda “NUNCA INTERRUMPIR LA ACTUALIZACION; NO APAGAR LA PC NI EL MODEM DURANTE EL PROCESO
”
Para el caso de los Módems Inalámbricos se puede alcanzar la potencia de 400mw con el firmware compatible, la Key de Prodigy, y para el firmware 4.25.19 registrando el producto.
Firmwares 2Wire
Versión 3.5.15
http://rapidshare.com/files/36170659/3.5.15_kogt2s.firmware2wire.rar
Versión 3.15.15.4
http://rapidshare.com/files/36170666/3.5.15.4_kogt2s.firmware2wire.rar
Versión 3.7.1
http://rapidshare.com/files/36170664/3.7.1_kogt2s.firmware2wire.rar
Versión 3.7.3
http://rapidshare.com/files/36170656/3.7.3_kogt2s.firmware2wire.part1.rar
http://rapidshare.com/files/36170669/3.7.3_kogt2s.firmware2wire.part2.rar
Versión 3.7.5
http://rapidshare.com/files/36170683/3.7.5_kogt2s.firmware2wire.rar
Versión 3.7.5.23
http://rapidshare.com/files/36170672/3.7.5.23_kogt2s.firmware2wire.rar
Versión 4.21.9
http://rapidshare.com/files/36170709/4.21.9_kogt2s.firmware2wire.rar
Versión 4.25.19
http://rapidshare.com/files/36170681/4_25_19_400mw_kogt2s.firmware2wire.part1.rar
http://rapidshare.com/files/36170682/4_25_19_400mw_kogt2s.firmware2wire.part2.rar
Version 5.29.107
http://rapidshare.com/files/36227965/2700hgv_.5-29-107_kogt2s-firmware2wire.2sp
Ultima.. Mejora opciones inlambricas y agregra filtro MAC
Probado en 2Wire 2700hg
Version 5.29.117.3
http://rapidshare.com/files/105406693/2wire_reinstall_voice_5.29.117.3.2sp
Some common firmware versions (with some notes of noticeable changes) are:
3.5.5 (Out of the box on some original models)
3.5.11 (First version to include the DSL Diagnostics page in the MDC)
3.5.15
3.7.1 (Increased NAT table to 1024 sessions)
3.7.5 (Support for closed (shared-key) WEP networks. Traffic shaping for non standard upstream MTU)
3.11.1 (as seen on a 1070b homeportal July 2005)
3.17.5 (as seen in a 1701HG Aug. 2005 This is the earliest version that the 1701hg will take.)
4.21.x and up – runs both the older units (any HG/HW/some SW) and the new 270/2700 units (Jan. 2006)
Bajo su propio riesgo!!!! los firmwares 4.21 en adelante fueron dise?ados para el HG2700 y superiores.
Espero les sean utiles!!!
KoGt2S Team
Sep 26 2008
昨天又忘记写了
昨天突然发现在淘宝上面购物已经超过一万多块。。。看来是要忍一下手了。。。
孢子还挺不错,不过越高级就越复杂了点,前面有模拟人生的影子,估计后面应该会出现simcity。。。毕竟是成熟的产品,ea只要照抄就好了。。。就像一个ea大杂烩揉合在一起。。。
Sep 24 2008
arp_announce 和 arp_ignore
用来屏蔽arp请求,比较难理解,先看看linux核心2.6的定义:
arp_announce - INTEGER Define different restriction levels for announcing the local source IP address from IP packets in ARP requests sent on interface: 0 - (default) Use any local address, configured on any interface 1 - Try to avoid local addresses that are not in the target's subnet for this interface. This mode is useful when target hosts reachable via this interface require the source IP address in ARP requests to be part of their logical network configured on the receiving interface. When we generate the request we will check all our subnets that include the target IP and will preserve the source address if it is from such subnet. If there is no such subnet we select source address according to the rules for level 2. 2 - Always use the best local address for this target. In this mode we ignore the source address in the IP packet and try to select local address that we prefer for talks with the target host. Such local address is selected by looking for primary IP addresses on all our subnets on the outgoing interface that include the target IP address. If no suitable local address is found we select the first local address we have on the outgoing interface or on all other interfaces, with the hope we will receive reply for our request and even sometimes no matter the source IP address we announce. The max value from conf/{all,interface}/arp_announce is used. Increasing the restriction level gives more chance for receiving answer from the resolved target while decreasing the level announces more valid sender's information. arp_ignore - INTEGER Define different modes for sending replies in response to received ARP requests that resolve local target IP addresses: 0 - (default): reply for any local target IP address, configured on any interface 1 - reply only if the target IP address is local address configured on the incoming interface 2 - reply only if the target IP address is local address configured on the incoming interface and both with the sender's IP address are part from same subnet on this interface 3 - do not reply for local addresses configured with scope host, only resolutions for global and link addresses are replied 4-7 - reserved 8 - do not reply for all local addresses The max value from conf/{all,interface}/arp_ignore is used when ARP request is received on the {interface}
arp_ignore 设置为1,这个比较好理解,当别人的arp请求过来的时候,如果接收的设备上面没有这个ip,就不响应,默认是0,只要这台机器上面任何一个设备上面有这个ip,就响应arp请求,并发送mac地址应答。
arp_announce 这个就比较难解释了,先看一段英文的:
Assume that a linux box X has three interfaces – eth0, eth1 and eth2. Each interface has an IP address IP0, IP1 and IP2. When a local application tries to send an IP packet with IP0 through the eth2.
Unfortunately, the target node’s mac address is not resolved. The linux box X will send the ARP request to know the mac address of the target(or the gateway). In this case what is the IP source address of the “ARP request message”? The IP0- the IP source address of the transmitting IP or IP2 – the outgoing interface?
Until now(actually just 3 hours before) ARP request uses the IP address assigned to the outgoing interface(IP2 in the above example) However the linux’s behavior is a little bit different. Actually the selection of source address in ARP request is totally configurable by the proc variable “arp_announce”
If we want to use the IP2 not the IP0 in the ARP request, we should change the value to 1 or 2. The default value is 0 – allow IP0 is used for ARP request.
其实就是路由器的问题,因为路由器一般是动态学习ARP包的(一般动态配置DHCP的话),当内网的机器要发送一个到外部的ip包,那么它就会请求路由器的Mac地址,发送一个arp请求,这个arp请求里面包括了自己的ip地址和Mac地址,而linux默认是使用ip的源ip地址作为arp里面的源ip地址,而不是使用发送设备上面的 ,这样在lvs这样的架构下,所有发送包都是同一个VIP地址,那么arp请求就会包括VIP地址和设备Mac,而路由器收到这个arp请求就会更新自己的arp缓存,这样就会造成ip欺骗了,VIP被抢夺,所以就会有问题。
arp缓存为什么会更新了,什么时候会更新呢,为了减少arp请求的次数,当主机接收到询问自己的arp请求的时候,就会把源ip和源Mac放入自己的arp表里面,方便接下来的通讯。如果收到不是询问自己的包(arp是广播的,所有人都收到),就会丢掉,这样不会造成arp表里面无用数据太多导致有用的记录被删除。
What happens when a host receives an ARP request packet?
The ARP request is received and processed by all the hosts in the network, since it is a broadcast packet. The following steps are carried out when a ARP request packet is received by a host:
If the IP address to be resolved is for this host, then the ARP module sends an ARP reply packet with its Ethernet MAC address.
If the IP address to be resolved is for this host, then the ARP module updates its ARP cache with the source Ethernet MAC address to source IP address mapping present in the ARP request packet. If the entry is already present in the cache, it is overwritten. If it is not present, it is added.
If the IP address to be resolved is not for this host, then the ARP module discards the ARP request packet.
Will a host update its ARP cache upon receiving any ARP request?
A host will update its ARP cache, only if the ARP request is for its IP address. Otherwise, it will discard the ARP request.
What is the disadvantage if a host updates its ARP cache upon receiving any ARP request?
The host will exhaust the ARP cache with a lot of unused ARP entries, if it updates the ARP cache for any ARP request.
如果路由器使用静态ARP表,客户端也使用静态网关ARP的话,基本就不用管这两个值了。
也看了一下vpn,用了pppoe协议,也是不需要处理arp请求的。
查看某个设备上面绑定了多少个ip:>ip addr show dev eth0
绑定多个ip(临时,看操作系统不同加在不同的地方):>ip addr add x.x.x.x/32 dev eth0
临时修改arp_announce和arp_ignore:
echo 1 > /proc/sys/net/ipv4/conf/eth0/arp_ignore
echo 2 > /proc/sys/net/ipv4/conf/eth0/arp_announce
永久修改:
if /etc/sysctl.conf is used in the system, we have this config in /etc/sysctl.conf
net.ipv4.conf.eth0.arp_ignore = 1 net.ipv4.conf.eth0.arp_announce = 2
Sep 23 2008
创新的声卡
品种越来越多,质量越来越。。。
Supported X-Fi’s: XtremeAudio PCI (SB0790/SB0792), XtremeAudio PCI-Express (SB0820/SB1040), XtremeMusic (SB0460/SB0463/SB0464/SB0465), Platinum (SB0460), XtremeGamer Fatal1ty Professional (SB046A), XtremeGamer Fatal1ty FPS (SB0466), Fatal1ty Platinum (SB0468/SB0469), Platinum Fatal1ty Champion (SB046A), Elite Pro (SB0550/SB055A), and Auzentech X-Fi Prelude
Unsupported X-Fi’s: X-Fi notebook (SB0710/SB0711), half height XtremeGamer (SB0730/SB073A), and X-Fi Model # SB0770 (pictures of SB0770: 1, 2, and 3).
The X-Fi’s (from xtrememusic to fatal1ty) sound quality is held back mainly by poor choice in op-amps, specifically, the use of mediocre JRE NJM4556 on the Front Left/Right, and cheap STL on the rear/surround/center/sub. Even the X-Fi Elite Pro suffers, utilizing a JRE NJM2114, and JRE NJM2068’s. The High-end Auzentech Prelude and Xonar D2 / D2X cards have a LM4562 on their front channels (and is also socketable on the Prelude, allowing use of the higher quality “metal can” TO-99 style op-amp), but unfortunately, like Creative’s X-Fi’s, utilizes inferior opamps on their surround channels.
The LM4562 op-amp is a great all around op-amp, however I also have Analog Devices AD8599 at an additional $2 per op-amp.
LM4562: cold and smooth, great bass impact
AD8599: warm and exciting, very accurate
Sep 22 2008
杀不死的小强
昨晚看到洗手盘那里竟然有一堆小小强,汗啊,走了这么多天都繁殖出来了。。。毕竟是3亿年前的生物了,要灭掉看来是很困难。。。
除蟑螂绝招
蟑螂学名蜚蠊,俗称灶蚂子、曱甴等。它喜欢选择温暖、潮湿、食物丰富和多缝隙的场所栖居。在居民住宅中,虽然居室、卫生间、储藏室、通道等各类场所,甚至在庭院里都有蟑螂栖生,但各家各户的厨房通常是侵害最严重的地方。
蟑螂体表和消化道携带了多种病原体,如肝炎病毒、伤寒杆菌、痢疾杆菌等,还能引起肠道病和寄生虫卵的传播。此外蟑螂的分泌物、排泄物、呕吐物还会引起过敏反应。
如何消灭蟑螂呢?
最重要的是宣传蟑螂发生与环境卫生关系的知识。通过宣传改变有些群众杀灭蟑螂全部依赖杀虫剂,即所谓“灭虫靠药”的思想,建立综合治理的观点。
一、环境防制
首先要清理环境,因为脏、乱、差的环境以及潮湿、温暖的场所为蟑螂提供了丰富的食源、水源和栖息的场所。如果室内条件不改善,化学防制和物理防制的杀虫作用都是暂时的,只有做好环境防制才能持久地达到控制虫害的目的。环境防制是提高和巩固化学防制,防制蟑螂侵入和孳生的根本措施。
1、堵洞抹缝、修补门窗,以防蟑螂侵入室内。蟑螂喜欢钻洞藏缝,例如德国小蠊的成虫和若虫可躲进仅1.6毫米的缝隙,所以在打扫环境卫生的同时,还可以选择用石灰、水泥、硅胶以及用杀虫剂浸泡过棉花、麻绳堵洞抹缝,使蟑螂无藏身之处,这是治本的措施,同时也可防止蟑螂从外界再次侵入室内。
2、收藏好食物和动物饲料,对散落和残存的食物,用过的餐具、泔脚等都要及时清除处理,关好水笼头,使蟑螂断水、断粮也非常重要。
3、保持环境整洁,清除垃圾及杂物。
二、物理防制
消灭蟑螂最关键的方法是清除卵鞘。卵鞘的形态多数呈酱红色钱包状,每鞘内含卵16个至56个,经一段时间后,可孵化出几十个小蟑螂。家庭里的蟑螂多为大蠊,雌虫选择比较隐蔽的场所产置卵鞘,如屋顶、墙角、空的食品容器、橱柜、木(纸)箱及桌子的角落或杂物堆中。
在早春和冬季,人们更换衣服和被褥时,应该翻箱倒柜地搜查藏在里面的蟑螂和卵鞘。因为这时气温低,蟑螂活动力差,很容易捕获。找到的卵鞘可以将它压死或集中起来烧死。只喷药,不清除卵鞘是不能消灭蟑螂的。因为卵鞘有抗御药物的能力,当今世界无任何药物可杀灭卵鞘,消灭一个卵鞘相当于杀灭了几十只蟑螂。
厨房是蟑螂最集中栖息的场所,用开水浇灌缝隙、孔洞和角落,可以轻而易举的烫杀隐藏在里面的蟑螂和卵鞘,有效地降低蟑螂密度。
三、化学防制
1、药物杀灭成虫:使用长效的杀虫剂喷洒在蟑螂栖息或经常活动的场所,使它们与药面接触而中毒死亡。针对蟑螂栖息处、缝隙内喷洒。喷洒时要遵循由外至内,由上至下的原则。先关闭门窗,打开柜门,拉开抽屉,对外围先喷上一圈约20厘米的屏障药带,再对缝隙、孔洞、角落进行喷洒,一定要足量喷湿。喷洒结束后要关闭1小时,对蟑螂有良好的杀灭作用。喷药时一定要注意安全。可间隔1-2个月再施药一次。
2、毒饵:投放毒饵时要注意点多量少,将颗粒毒饵放在废弃的瓶盖里,铺上薄薄的一层就可以了。5平方米的厨房一般可以投放10个点。每克毒饵可投放4-5个点。毒饵要投放在蟑螂栖息的场所周围和蟑螂经常活动的地方,例如灶面、桌面、抽屉、水斗下面为重点,投放毒饵时要注意防潮。还可使用毒饵槽或袋粘贴在橱柜、抽屉角落等隐匿之处。
3、灭蟑螂药笔:在蟑螂栖息的缝、洞和角落以及它们经常活动的地方,用药笔划圈或划“#”字,使蟑螂进出或活动时都因沾上涂划的粉迹而被毒死。涂划的痕道不能太细,应将药笔折成2-3段,取一段横着涂划宽约2-3厘米左右的粗线。
防治蟑螂的方法很多,一定要因地制宜,综合防治,各种灭蟑螂的方法合理使用,喷洒杀虫剂、毒饵、粘蟑纸等立体投药,使蟑螂陷入天罗地网之中,蟑螂爬到哪里,都可能接触到药物,取得更好的效果。消灭蟑螂以后,不能忘记打扫环境卫生,将死蟑螂、卵鞘及蟑螂的排泄物消除干净。实践告诉我们,只要参与除害灭病的活动,运用科学的方法,持之以恒就一定能消灭蟑螂,为民除害。
Sep 13 2008
三鹿
三鹿牛奶出了问题。。。
三鹿 说是 奶农 的责任
奶农 说是 奶牛 的责任
奶牛 支吾了半天,说出了一个字:
草
草 很委屈 含泪道
怪也得怪我妈生了我
终于揪出罪魁祸首——草他妈
Next Page »