Showing posts with label Windows Usage. Show all posts
Showing posts with label Windows Usage. Show all posts
Monday, July 6, 2015
Enable Hibernate in Win7.
Ref [1] http://www.sevenforums.com/tutorials/778-power-plan-settings-change.html
[2] http://www.sevenforums.com/tutorials/819-hibernate-enable-disable.html
Enable hibernate in advanced power plan settings.
( command line to open power settings: powercfg.cpl )
Friday, July 29, 2011
Set GateWay under Windows MS-DOS command line
C:\Documents and Settings\q.yang>route
Manipulates network routing tables.
ROUTE [-f] [-p] [command [destination]
[MASK netmask] [gateway] [METRIC metric] [IF interface]
-f Clears the routing tables of all gateway entries. If this is
used in conjunction with one of the commands, the tables are
cleared prior to running the command.
-p When used with the ADD command, makes a route persistent across
boots of the system. By default, routes are not preserved
when the system is restarted. Ignored for all other commands,
which always affect the appropriate persistent routes. This
option is not supported in Windows 95.
command One of these:
PRINT Prints a route
ADD Adds a route
DELETE Deletes a route
CHANGE Modifies an existing route
destination Specifies the host.
MASK Specifies that the next parameter is the 'netmask' value.
netmask Specifies a subnet mask value for this route entry.
If not specified, it defaults to 255.255.255.255.
gateway Specifies gateway.
interface the interface number for the specified route.
METRIC specifies the metric, ie. cost for the destination.
All symbolic names used for destination are looked up in the network database
file NETWORKS. The symbolic names for gateway are looked up in the host name
database file HOSTS.
If the command is PRINT or DELETE. Destination or gateway can be a wildcard,
(wildcard is specified as a star '*'), or the gateway argument may be omitted.
If Dest contains a * or ?, it is treated as a shell pattern, and only
matching destination routes are printed. The '*' matches any string,
and '?' matches any one char. Examples: 157.*.1, 157.*, 127.*, *224*.
Diagnostic Notes:
Invalid MASK generates an error, that is when (DEST & MASK) != DEST.
Example> route ADD 157.0.0.0 MASK 155.0.0.0 157.55.80.1 IF 1
The route addition failed: The specified mask parameter is invalid.
(Destination & Mask) != Destination.
Examples:
> route PRINT
> route ADD 157.0.0.0 MASK 255.0.0.0 157.55.80.1 METRIC 3 IF 2
destination^ ^mask ^gateway metric^ ^
Interface^
If IF is not given, it tries to find the best interface for a given
gateway.
> route PRINT
> route PRINT 157* .... Only prints those matching 157*
> route CHANGE 157.0.0.0 MASK 255.0.0.0 157.55.80.5 METRIC 2 IF 2
CHANGE is used to modify gateway and/or metric only.
> route PRINT
> route DELETE 157.0.0.0
> route PRINT
C:\Documents and Settings\q.yang>route ADD 192.168.0.0 MASK 255.255.255.0 10.10.
20.201 -p
C:\Documents and Settings\q.yang>ping 192.168.0.1
Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time=10ms TTL=255
Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 10ms, Average = 3ms
C:\Documents and Settings\q.yang>ping 192.168.0.2
Pinging 192.168.0.2 with 32 bytes of data:
Reply from 192.168.0.2: bytes=32 time=48ms TTL=254
Reply from 192.168.0.2: bytes=32 time=50ms TTL=254
Reply from 192.168.0.2: bytes=32 time=50ms TTL=254
Reply from 192.168.0.2: bytes=32 time=50ms TTL=254
Ping statistics for 192.168.0.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 48ms, Maximum = 50ms, Average = 49ms
C:\Documents and Settings\q.yang>route ADD 192.168.1.0 MASK 255.255.255.0 10.10.
20.201 -p
C:\Documents and Settings\q.yang>ping 192.168.0.3
Pinging 192.168.0.3 with 32 bytes of data:
Reply from 192.168.0.3: bytes=32 time=50ms TTL=254
Reply from 192.168.0.3: bytes=32 time=49ms TTL=254
Reply from 192.168.0.3: bytes=32 time=49ms TTL=254
Reply from 192.168.0.3: bytes=32 time=59ms TTL=254
Ping statistics for 192.168.0.3:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 49ms, Maximum = 59ms, Average = 51ms
C:\Documents and Settings\q.yang>ping 192.168.1.1
Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=48ms TTL=254
Reply from 192.168.1.1: bytes=32 time=50ms TTL=254
Reply from 192.168.1.1: bytes=32 time=50ms TTL=254
Reply from 192.168.1.1: bytes=32 time=50ms TTL=254
Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 48ms, Maximum = 50ms, Average = 49ms
C:\Documents and Settings\q.yang>ping 192.168.1.2
Pinging 192.168.1.2 with 32 bytes of data:
Reply from 192.168.1.2: bytes=32 time=64ms TTL=98
Reply from 192.168.1.2: bytes=32 time=58ms TTL=98
Reply from 192.168.1.2: bytes=32 time=58ms TTL=98
Reply from 192.168.1.2: bytes=32 time=57ms TTL=98
Ping statistics for 192.168.1.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 57ms, Maximum = 64ms, Average = 59ms
Manipulates network routing tables.
ROUTE [-f] [-p] [command [destination]
[MASK netmask] [gateway] [METRIC metric] [IF interface]
-f Clears the routing tables of all gateway entries. If this is
used in conjunction with one of the commands, the tables are
cleared prior to running the command.
-p When used with the ADD command, makes a route persistent across
boots of the system. By default, routes are not preserved
when the system is restarted. Ignored for all other commands,
which always affect the appropriate persistent routes. This
option is not supported in Windows 95.
command One of these:
PRINT Prints a route
ADD Adds a route
DELETE Deletes a route
CHANGE Modifies an existing route
destination Specifies the host.
MASK Specifies that the next parameter is the 'netmask' value.
netmask Specifies a subnet mask value for this route entry.
If not specified, it defaults to 255.255.255.255.
gateway Specifies gateway.
interface the interface number for the specified route.
METRIC specifies the metric, ie. cost for the destination.
All symbolic names used for destination are looked up in the network database
file NETWORKS. The symbolic names for gateway are looked up in the host name
database file HOSTS.
If the command is PRINT or DELETE. Destination or gateway can be a wildcard,
(wildcard is specified as a star '*'), or the gateway argument may be omitted.
If Dest contains a * or ?, it is treated as a shell pattern, and only
matching destination routes are printed. The '*' matches any string,
and '?' matches any one char. Examples: 157.*.1, 157.*, 127.*, *224*.
Diagnostic Notes:
Invalid MASK generates an error, that is when (DEST & MASK) != DEST.
Example> route ADD 157.0.0.0 MASK 155.0.0.0 157.55.80.1 IF 1
The route addition failed: The specified mask parameter is invalid.
(Destination & Mask) != Destination.
Examples:
> route PRINT
> route ADD 157.0.0.0 MASK 255.0.0.0 157.55.80.1 METRIC 3 IF 2
destination^ ^mask ^gateway metric^ ^
Interface^
If IF is not given, it tries to find the best interface for a given
gateway.
> route PRINT
> route PRINT 157* .... Only prints those matching 157*
> route CHANGE 157.0.0.0 MASK 255.0.0.0 157.55.80.5 METRIC 2 IF 2
CHANGE is used to modify gateway and/or metric only.
> route PRINT
> route DELETE 157.0.0.0
> route PRINT
C:\Documents and Settings\q.yang>route ADD 192.168.0.0 MASK 255.255.255.0 10.10.
20.201 -p
C:\Documents and Settings\q.yang>ping 192.168.0.1
Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time=10ms TTL=255
Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 10ms, Average = 3ms
C:\Documents and Settings\q.yang>ping 192.168.0.2
Pinging 192.168.0.2 with 32 bytes of data:
Reply from 192.168.0.2: bytes=32 time=48ms TTL=254
Reply from 192.168.0.2: bytes=32 time=50ms TTL=254
Reply from 192.168.0.2: bytes=32 time=50ms TTL=254
Reply from 192.168.0.2: bytes=32 time=50ms TTL=254
Ping statistics for 192.168.0.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 48ms, Maximum = 50ms, Average = 49ms
C:\Documents and Settings\q.yang>route ADD 192.168.1.0 MASK 255.255.255.0 10.10.
20.201 -p
C:\Documents and Settings\q.yang>ping 192.168.0.3
Pinging 192.168.0.3 with 32 bytes of data:
Reply from 192.168.0.3: bytes=32 time=50ms TTL=254
Reply from 192.168.0.3: bytes=32 time=49ms TTL=254
Reply from 192.168.0.3: bytes=32 time=49ms TTL=254
Reply from 192.168.0.3: bytes=32 time=59ms TTL=254
Ping statistics for 192.168.0.3:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 49ms, Maximum = 59ms, Average = 51ms
C:\Documents and Settings\q.yang>ping 192.168.1.1
Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=48ms TTL=254
Reply from 192.168.1.1: bytes=32 time=50ms TTL=254
Reply from 192.168.1.1: bytes=32 time=50ms TTL=254
Reply from 192.168.1.1: bytes=32 time=50ms TTL=254
Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 48ms, Maximum = 50ms, Average = 49ms
C:\Documents and Settings\q.yang>ping 192.168.1.2
Pinging 192.168.1.2 with 32 bytes of data:
Reply from 192.168.1.2: bytes=32 time=64ms TTL=98
Reply from 192.168.1.2: bytes=32 time=58ms TTL=98
Reply from 192.168.1.2: bytes=32 time=58ms TTL=98
Reply from 192.168.1.2: bytes=32 time=57ms TTL=98
Ping statistics for 192.168.1.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 57ms, Maximum = 64ms, Average = 59ms
Thursday, August 6, 2009
Thursday, January 22, 2009
教你新建别人进不了删不掉的文件夹
From: http://www.anzstockphoto.com/space.php?uid=3&do=blog&id=18
教你新建别人进不了删不掉的文件夹
教你新建别人进不了删不掉的文件夹
建立一个别人既无法进入又无法删除的文件夹。相信大家都遇到过自己的一些隐私文件不愿意让别人看到的情况 吧，怎么解决呢？隐藏起来？换个名字？或者加密？这些办法都可以办到，其实还有一种方法，就是建立一个别人既不能进入又不能删除的文件夹，把自己的隐私文 件放进去，别人就看不到啦，下面讲讲如何实现，很简单的。
第一步：在运行中输入cmd，回车，打开命令行窗口
第二步：在命令行窗口中切换到想要建立文件夹的硬盘分区，如D盘，输入：d: 程序开发，操作系统，服务器，源码下载，Linux,Unix,BSD,PHP,Apach,asp,下载,源码,黑客,安全,技术社区,技术论坛:K,i5m1d4v#D,s!U
第三步：输入md 123..\ 回车，注意文件夹名后有2个小数点
第二步：在命令行窗口中切换到想要建立文件夹的硬盘分区，如D盘，输入：d: 程序开发，操作系统，服务器，源码下载，Linux,Unix,BSD,PHP,Apach,asp,下载,源码,黑客,安全,技术社区,技术论坛:K,i5m1d4v#D,s!U
第三步：输入md 123..\ 回车，注意文件夹名后有2个小数点
OK，搞定，看看你的D盘下面是不是多了一个名为123.的文件夹了？它是既不能进入又不能被删除的！不信你就试试看吧。 3M5X6h5V0Y2M7n/v/T [
那么，如果自己想删除或者进入这个文件夹，又应该如何操作呢？同样也很简单。 ]4o9K2L(B7n a$L7N
如果想删除，在命令行窗口中输入 rd 123..\ 回车，即可删除，当然删除前请确认里面的文件都是不需要的，不要删错了。 程序开发，操作系统，服务器，源码下载，Linux,Unix,BSD,PHP,Apach,asp,下载,源码,黑客,安全,技术社区,技术论坛:a*\8A/K*o9X6F
如果想进入，在命令行窗口中输入 start d:\123..\ 注意这里一定要是文件夹的绝对路径，否则无法打开即可打开此文件夹，你就可以随心所欲的把不想让别人看到的资料放进去啦！
Thursday, November 20, 2008
winxp-file-Share
方法一：解除对Guest账号的限制
点击“开始→运行”，在“运行”对话框中输入“GPEDIT.MSC”，打开组策略编辑器，依次选择“计算机配置→Windows设置→安全设置→本地策略→用户权利指派”，双击“拒绝从网络访问这台计算机”策略，删除里面的“GUEST”账号。这样其他用户就能够用Guest账号通过网络访问使用 Windows XP系统的计算机了。
点击“开始→运行”，在“运行”对话框中输入“GPEDIT.MSC”，打开组策略编辑器，依次选择“计算机配置→Windows设置→安全设置→本地策略→用户权利指派”，双击“拒绝从网络访问这台计算机”策略，删除里面的“GUEST”账号。这样其他用户就能够用Guest账号通过网络访问使用 Windows XP系统的计算机了。
方法二：更改网络访问模式
打开组策略编辑器，依次选择“计算机配置→Windows设置→安全设置→本地策略→安全选项”，双击“网络访问：本地账号的共享和安全模式”策略，将默认设置“仅来宾—本地用户以来宾身份验证”，更改为“经典：本地用户以自己的身份验证”。
现在，当其他用户通过网络访问使用Windows XP的计算机时，就可以用自己的“身份”进行登录了（前提是Windows XP中已有这个账号并且口令是正确的）。
当该策略改变后，文件的共享方式也有所变化，在启用“经典：本地用户以自己的身份验证”方式后，我们可以对同时访问共享文件的用户数量进行限制，并能针对不同用户设置不同的访问权限。
不过我们可能还会遇到另外一个问题，当用户的口令为空时，访问还是会被拒绝。原来在“安全选项”中有一个“账户：使用空白密码的本地账户只允许进行控制台登录”策略默认是启用的，根据Windows XP安全策略中拒绝优先的原则，密码为空的用户通过网络访问使用Windows XP的计算机时便会被禁止。我们只要将这个策略停用即可解决问题。 五、如何共享访问 Windows XP 中的加密文件
打开组策略编辑器，依次选择“计算机配置→Windows设置→安全设置→本地策略→安全选项”，双击“网络访问：本地账号的共享和安全模式”策略，将默认设置“仅来宾—本地用户以来宾身份验证”，更改为“经典：本地用户以自己的身份验证”。
现在，当其他用户通过网络访问使用Windows XP的计算机时，就可以用自己的“身份”进行登录了（前提是Windows XP中已有这个账号并且口令是正确的）。
当该策略改变后，文件的共享方式也有所变化，在启用“经典：本地用户以自己的身份验证”方式后，我们可以对同时访问共享文件的用户数量进行限制，并能针对不同用户设置不同的访问权限。
不过我们可能还会遇到另外一个问题，当用户的口令为空时，访问还是会被拒绝。原来在“安全选项”中有一个“账户：使用空白密码的本地账户只允许进行控制台登录”策略默认是启用的，根据Windows XP安全策略中拒绝优先的原则，密码为空的用户通过网络访问使用Windows XP的计算机时便会被禁止。我们只要将这个策略停用即可解决问题。 五、如何共享访问 Windows XP 中的加密文件
一、网络协议的安装和设置
1.在WinXP中安装NetBEUI协议
对的，你没有看错，就是要在WinXP中安装NetBEUI协议。微软在WinXP中只支持TCP/IP协议和NWLink IPX/SPX/NetBIOS兼容协议，正式宣布不再支持NetBEUI协议。但是在建立小型局域网的实际使用中，使用微软支持的两种协议并不尽如人意。比如，在解决网上邻居慢问题的过程中，笔者采用了诸多方法后网上邻居的速度虽然好一点，但还是慢如蜗牛；另外，在设置多块网卡的协议、客户和服务绑定时，这两种协议还存在BUG，多块网卡必须同时绑定所有的协议（除NWLink NetBIOS）、客户和服务，即使你取消某些绑定重启后系统又会自动加上，这显然不能很好地满足网络建设中的实际需要。而当笔者在WinXP中安装好 NetBEUI协议后，以上两个问题都得到圆满的解决。
在WinXP安装光盘的“\valueADD\MSFT\NET\NETBEUI”目录下有3个文件，其中“NETBEUI.TXT”是安装说明，另外两个是安装NetBEUI协议所需的文件。安装的具体步骤如下：
复制“NBF.SYS”到“%SYSTEMROOT%\SYSTEM32\DRIVERS\”目录；
复制“NETNBF.INF”到“%SYSTEMROOT%\INF\”目录；
在网络连接属性中单击“安装”按钮来安装NetBEUI协议。
注：%SYSTEMROOT%是WinXP的安装目录，比如笔者的WinXP安装在F:\Windows目录下，就应该用F:\Windows来替换%SYSTEMROOT%。
2.在WinXP中设置好其它网络协议
笔者建议，如果你的局域网不用上Internet便只需要安装NetBEUI协议就行了。在小型局域网（拥有200台左右电脑的网络）中NetBEUI是占用内存最少、速度最快的一种协议，NWLink IPX/SPX/NetBIOS兼容协议则应当删除掉。
如果你的局域网要上Internet则必须安装TCP/IP协议。但为了网络的快速访问，建议指定每台工作站的IP地址（除非网络中有DHCP服务器），否则工作站总是不断查找DHCP服务器使网速变慢。
当然，如果网络中只安装TCP/IP协议也能够实现局域网中的互访，但是在网上邻居中要直接看到其它机器就比较困难，必须先搜索到某台机器后才能访问它，这在许多实际网络运用中显得很不方便。
1.在WinXP中安装NetBEUI协议
对的，你没有看错，就是要在WinXP中安装NetBEUI协议。微软在WinXP中只支持TCP/IP协议和NWLink IPX/SPX/NetBIOS兼容协议，正式宣布不再支持NetBEUI协议。但是在建立小型局域网的实际使用中，使用微软支持的两种协议并不尽如人意。比如，在解决网上邻居慢问题的过程中，笔者采用了诸多方法后网上邻居的速度虽然好一点，但还是慢如蜗牛；另外，在设置多块网卡的协议、客户和服务绑定时，这两种协议还存在BUG，多块网卡必须同时绑定所有的协议（除NWLink NetBIOS）、客户和服务，即使你取消某些绑定重启后系统又会自动加上，这显然不能很好地满足网络建设中的实际需要。而当笔者在WinXP中安装好 NetBEUI协议后，以上两个问题都得到圆满的解决。
在WinXP安装光盘的“\valueADD\MSFT\NET\NETBEUI”目录下有3个文件，其中“NETBEUI.TXT”是安装说明，另外两个是安装NetBEUI协议所需的文件。安装的具体步骤如下：
复制“NBF.SYS”到“%SYSTEMROOT%\SYSTEM32\DRIVERS\”目录；
复制“NETNBF.INF”到“%SYSTEMROOT%\INF\”目录；
在网络连接属性中单击“安装”按钮来安装NetBEUI协议。
注：%SYSTEMROOT%是WinXP的安装目录，比如笔者的WinXP安装在F:\Windows目录下，就应该用F:\Windows来替换%SYSTEMROOT%。
2.在WinXP中设置好其它网络协议
笔者建议，如果你的局域网不用上Internet便只需要安装NetBEUI协议就行了。在小型局域网（拥有200台左右电脑的网络）中NetBEUI是占用内存最少、速度最快的一种协议，NWLink IPX/SPX/NetBIOS兼容协议则应当删除掉。
如果你的局域网要上Internet则必须安装TCP/IP协议。但为了网络的快速访问，建议指定每台工作站的IP地址（除非网络中有DHCP服务器），否则工作站总是不断查找DHCP服务器使网速变慢。
当然，如果网络中只安装TCP/IP协议也能够实现局域网中的互访，但是在网上邻居中要直接看到其它机器就比较困难，必须先搜索到某台机器后才能访问它，这在许多实际网络运用中显得很不方便。
Remote Desktop in Winxp -- Hints
Two things to be done:
1. Enable Remote Desktop in Network Firewall settings.
2. Enable remote access in Control Panel --> System --->Remote
Subscribe to:
Posts (Atom)