windows 7 下金山词霸取词变慢的原因和解决方法 李忠木 博士 windows 7 下金山词霸的取词会变得非常慢。经过测试原因是由视觉效果中在窗口和按钮上使用视觉样式功能造成。去掉这一选项即可使金山词霸取词速度恢复正常。 具体操作过程为：右键单击计算机-属性-高级系统设置-性能点设置，在视觉效果项中去掉在窗口和按钮上使用视觉样式，点击应用即可。
转自： http://opensuse.swerdna.org/suseboot.html －－－－－－－－－－ HowTo Boot / Multiboot openSUSE and Windows (2000, XP, Vista - any mix) using the GRUB bootloader Versions: Suse/openSUSE 10.x, 11.x Scenario: You have openSUSE and one or more Windows installations on your drives and multibooting using GRUB isn't working. This tutorial leads you through reinstalling the Grub multiboot. You might be interested in a companion tutorial about using the Windows bootloader for multibooting openSUSE and Windows: HowTo Boot Multiboot openSUSE and Windows (2000, XP, Vista - any mix) using the Windows bootloader . If you have no Windows installations, only Linux, you might want to read a companion tutorial for repairing a bootloader with focus on openSUSE, leaving out Windows: HowTo Boot into openSUSE when it won't Boot from the Grub Code on the Hard Drive . If you just want to get the repair done without any introductory palaver, skip to the section HowTo Repair your Grub Multiboot. About Booting Booting Windows with Microsoft Code: Windows 2000 and XP require you to have a primary partition on the first drive for the Microsoft bootloader codes; Microsoft call this the system partition . That's an inappropriate name so I'll call it by the correct name here: the bootloader partition. Windows will only boot from a bootloader partition that is a primary partition on the first drive. You can in fact cause a different drive to appear to Windows XP/2000 as the first drive by using the Grub map function, but your bootloader partition must still be a primary partition. Once the requirement for a bootloader partition (as a primary partition) is met, you may install Windows to higher order partitions, either primary or logical. For 2000, XP and Vista the bootloader partition must be made active or else booting from Microsoft code in the Master Boot Record (MBR) will fail. When you install Vista, it will seek out any existing active partition and make that Vista's bootloader partition. If an active partition does exist and it is a Linux partition, the Vista install will fail. If an active partition doesn't exist, Vista will make it's root partition the bootloader partition and make that partition active. Spare me! Booting openSUSE with Grub Code: Grub can be configured to boot either from the Master Boot Record (MBR) or from a custom partition like /boot or /root. I demonstrate only the method of booting from the MBR in this tutorial. The second configuration is for advanced users because sometimes tweaking is required to get non-MBR booting to work OK after Yast is finished with it. Booting Windows with Grub Code: This simply hands control over to the Microsoft bootloader in the bootloader partition. Curiously, in this instance it isn't necessary for the partition to be marked active. In fact, during installation of openSUSE the active partition is switched from the Windows bootloader partition to Suse's root partition. This is fine provided you switch it back if you want to revert to booting via Microsoft codes (e.g. if you uninstall Linux). HowTo Repair Your Grub Multiboot : Two common problems can arise. The most disconcerting is when you cannot boot to anything. A lesser problem is that you can boot to Suse OK but not to Windows. There are a couple of methods for correcting these problems but I'll only cover one here that I think is good for new users. It's a three step process. First you get an assisted boot to the Suse installation. Then in step 2 you use Yast to completely recalculate and rewrite the Grub installation including rewriting the MBR. Finally, in step 3, you check and maybe alter Yast's new configuration for booting into Windows. Step 1 for Suse/openSUSE 10.x - Assisted Boot into openSUSE: Insert Suse's installation DVD and reboot the computer. Commence the installation process but only carry it forward a few steps. Click Next thought the Language screen. In the Media Check screen, do not click Start Check but simply click Next to skip to the the next screen. Agree to the Licence and Next to the Installation Mode screen. Here you select Other Options. That will allow you to select to Boot Installed System. Select that and click next to proceed. GoTo step 2 Step 1 for openSUSE 11.x - Assisted Boot into openSUSE: Insert Suse's installation DVD and reboot the computer. On the boot screen choose to Repair Installed System. On the page titled Repair Method, select Expert Tools. Then click option Install New Boot Loader. Select the partition where you installed Suse (if asked). You'll get the Grub GUI setup screen. Check under the Tab Boot Loader Installation that the checkmark is in Boot from Master Boot Record and remove any other checkmarks. Click Finish. Wait for message The boot loader was installed successfully. Click OK -- Next -- Finish. Ignore any error messages and reboot. That should install an elementary Grub and allow you to boot to openSUSE. So do that and it will take you to step 2 Step 2 - Reinitialise and Reinstall Grub: Once Suse has fully booted and settled down, go to Yast -- System -- Boot Loader. The Grub configuration screen comes up with the Tab Section Management activated. In the lower right is a drop-down selector labelled Other. Select from Other the option Propose New Configuration and then wait for Grub to analyse your partitions and display a new configuration. This may take a while. Important: When that finishes, activate the tab labelled Boot Loader Installation and select to Boot from the Master Boot Record. Then click Finish to save the changes and install the reconfigured Grub into the hard drive's MBR. If you get a message that The bootloader boot sector will be written to a floppy disk ......... don't bother with the floppy -- just click OK to proceed and install to the MBR. Reboot and you should be able to boot to openSUSE using the Grub menu screen. Frequently you can also boot to Windows after completing Step 2, so try that too and maybe you won't need Step 3 Step 3 - Check/Repair Yast's Grub Configuration for Booting into Windows: The symptoms are that when you boot you can see Grub's menu and can select to boot to openSUSE successfully but if you select to boot to Windows, it fails. The solution is to boot into openSUSE and edit the Grub menu configuration file (menu.lst) located at /boot/grub/menu.lst. Menu.lst is a simple text file so you can use the following command in a console to open the file in a text editor with superuser permissions: kdesu kwrite /boot/grub/menu.lst The line above is for Kwrite in KDE while the line below is for Gedit in Gnome. gnomesu gedit /boot/grub/menu.lst Open menu.lst and locate the entry for Windows; there will generally be as many entries as there are VFAT and NTFS partitions on your drives. The trick is to identify the entry corresponding to the Windows Bootloader partition -- and then you can delete the spurious extra entries. I will show correct entries for some common cases to help you identify your situation and the correct entry for that situation: Bootloader in partition 1 of drive 1 : This is the most commonly occurring location. It matches most OEM desktops where 2000 and/or XP and/or Vista are installed in a straightforward fashion: title Windows bootloader menu # -- put whatever you want here rootnoverify (hd0,0) chainloader (hd0,0)+1 Bootloader in partition 2 of drive 1 : Some laptops and some mass-produced name-brand desktops have a special Utility partition as the first partition of the first drive. It's hidden from Windows. Windows makes the second partition the bootloader partition: title Windows bootloader menu rootnoverify (hd0,1) chainloader (hd0,1)+1 A Windows 2000/XP Bootloader is in partition 1 of drive 2 because you swapped drives : If you install 2000 or XP on the primary drive and then swap drives; i.e. you swap a hard drive with 2000 and/or XP on it from the primary drive channel to the secondary drive channel -- you need to include the Grub map function to rectify the switch for the 2000/XP file boot.ini: title Win 2000/XP bootloader menu for switched drive map (hd0) (hd1) map (hd1) (hd0) rootnoverify (hd1,0) chainloader (hd1,0)+1 A Vista Bootloader is in partition 1 of drive 2 because you swapped drives : If you install Vista alone on a primary drive and then swap drives OR if you first install 2000 or XP on the drive and then Vista and then swap drives; i.e. you swap a hard drive with Vista on it from the primary drive channel to the secondary drive channel -- NOTE that Vista completely ignores the map function that XP/2000 needed in the example above, so leave it out: title Vista bootloader menu for switched drive rootnoverify (hd1,0) chainloader (hd1,0)+1 If you really want to verify which is the bootloader partition, then find the partition that contains the bootloader files: In Windows 2000/XP they are ntldr , ntdetect.com and boot.ini . Vista's visible bootloader files are bootmgr and the directory boot . Well that should get you booting again. If you are still puzzled, browse on over to openSUSE Forums and recount your problem in the Install/Boot Forum. APPENDIX: Some Common Error Messages : Here are some of the error messages you might see on your boot screen after a failed boot. You check and correct them in menu.lst at /boot/grub/menu.lst. My advice is first check the error out in menu.lst and see if it's real, second to reinstall Grub as per the section above regardless of what you found in menu.lst, third then see whether the flaw persists in the new menu.lst and correct it by editing if it does persist. Error 13: Invalid or unsupported executable format : Is the entry pointing to a non-bootable partition (e.g. storage)? Error 15: File not found : Is the entry designating the correct file (e.g. kernel entry)? Error 22: No such Partition : Is the entry pointing to a real partition. This can happen after you alter your partitions. No error number, just a message like this: rootnoverify (hd0,1) chainloader (hd0,1)+1 This is not a bootable disk ...... Is the entry pointing to a Windows system32 partition that is not a bootloader partition? Bootloader files must be on the first partition for Windows 2000/XP to boot. No error number, just a message like this: rootnoverify (hd1,0) chainloader (hd1,0)+1 A disk read error occurred Press Ctrl+Alt+Del to restart Is the entry for a second or higher drive without the drive mapping function map (hd0) (hd1) etc? Recommended reading: GRUB bootloader - Full tutorial and also Gnu Grub Manual . Circa April 2006; last revised July 16 2009 －－－－－－－－－－－－－－－ http://opensuse.swerdna.org/suseboot.html
cygwin是一个在windows平台上运行的unix模拟环境，是cygnus solutions公司开发的自由软件（该公司开发了很多好东西，著名的还有eCos，不过现已被Redhat收购）。它对于学习unix/linux操作环境，或者从unix到windows的应用程序移植，或者进行某些特殊的开发工作，尤其是使用gnu工具集在windows上进行嵌入式系统开发，非常有用。随着嵌入式系统开发在国内日渐流行，越来越多的开发者对cygwin产生了兴趣。 cygnus当初首先把gcc，gdb，gas等开发工具进行了改进，使他们能够生成并解释win32的目标文件。然后，他们要把这些工具移植到windows平台上去。一种方案是基于win32 api对这些工具的源代码进行大幅修改，这样做显然需要大量工作。因此，他们采取了一种不同的方法他们写了一个共享库(就是cygwin dll)，把win32 api中没有的unix风格的调用（如fork,spawn,signals,select,sockets等）封装在里面，也就是说，他们基于win32 api写了一个unix系统库的模拟层。这样，只要把这些工具的源代码和这个共享库连接到一起，就可以使用unix主机上的交叉编译器来生成可以在windows平台上运行的工具集。以这些移植到windows平台上的开发工具为基础，cygnus又逐步把其他的工具（几乎不需要对源代码进行修改，只需要修改他们的配置脚本）软件移植到windows上来。这样，在windows平台上运行bash和开发工具、用户工具，感觉好像在unix上工作。 关于cygwin实现的更详细描述，请参考 http://cygwin.com/cygwin-ug-net/highlights.html. 安装网络版的cygwin，可以到 http://cygwin.com ，点击Install Cygwin Now!。这样会先下载一个叫做setup.exe的GUI安装程序，用它能下载一个完整的cygwin。按照每一屏的指示可以方便的进行安装。 开始运行bash之前，应该设置一些环境变量。cygwin提供了一个.bat文件，里面已经设置好了最重要的环境变量。通过它来启动bash是最安全的办法。这个.bat文件安装在cygwin所在的根目录下。 可以随意编辑该文件。 CYGWIN变量用来针对cygwin运行时系统进行多种全局设置。开始时，可以不设置CYGWIN或者在执行bash前用类似下面的格式在dos框下把它设为tty C:\ set CYGWIN=tty notitle glob PATH变量被cygwin应用程序作为搜索可知性文件的路径列表。当一个cygwin进程启动时，该变量被从windows格式(e.g. C:\WinNT\system32;C:\WinNT)转换成unix格式(e.g., /WinNT/system32:/WinNT)。如果想在不运行bash的时候也能够使用cygwin工具集，PATH起码应该包含x:\cygwin\bin，其中x:\cygwin 是你的系统中的cygwin目录。 HOME变量用来指定主目录，推荐在执行bash前定义该变量。当cygwin进程启动时，该变量也被从windows格式转换成unix格式，例如，作者的机器上HOME的值为C:\（dos命令set HOME就可以看到他的值，set HOME=XXX可以进行设置），在bash中用echo $HOME看，其值为/cygdrive/c. TERM变量指定终端型态。如果美对它进行设置，它将自动设为cygwin。 LD_LIBRARY_PATH被cygwin函数dlopen()作为搜索.dll文件的路径列表，该变量也被从windows格式转换成unix格式。多数Cygwin应用程序不使用dlopen,因而不需要该变量。 Cygwin程序缺省可以分配的内存不超过384 MB(program+data)。多数情况下不需要修改这个限制。然而，如果需要更多实际或虚拟内存，应该修改注册表的HKEY_LOCAL_MACHINE或HKEY_CURRENT_USER区段。田家一个DWORD键heap_chunk_in_mb并把它的值设为需要的内存限制，单位是十进制MB。也可以用cygwin中的regtool完成该设置。例子如下： regtool -i set /HKLM/Software/Cygnus\ Solutions/Cygwin/heap_chunk_in_mb 1024 regtool -v list /HKLM/Software/Cygnus\ Solutions/Cygwin 这一段讲一下cygwin和传统unix系统的不同之处。 cygwin同时支持win32和posix风格的路径，路径分隔符可以是正斜杠也可以是反斜杠。还支持UNC路径名。（在网络中，UNC是一种确定文件位置的方法，使用这种方法用户可以不关心存储设备的物理位置，方便了用户使用。在Windows操作系统，Novell Netware和其它操作系统中，都已经使用了这种规范以取代本地命名系统。在UNC中，我们不用关心文件在什么盘（或卷）上，不用关心这个盘（或卷）所在服务器在什么地方。我们只要以下面格式就可以访问文件： \\服务器名\共享名\路径\文件名 共享名有时也被称为文件所在卷或存储设备的逻辑标识，但使用它的目的是让用户不必关心这些卷或存储设备所在的物理位置。） 符合posix标准的操作系统（如linux）没有盘符的概念。所有的绝对路径都以一个斜杠开始，而不是盘符（如c:）。所有的文件系统都是其中的子目录。例如，两个硬盘，其中之一为根，另一个可能是在/disk2路径下。 因为许多unix系统上的程序假定存在单一的posix文件系统结构，所以cygwin专门维护了一个针对win32文件系统的内部posix视图，使这些程序可以在windows下正确运行。在某些必要的情况下，cygwin会使用这种映射来进行win32和posix路径之间的转换。 cygwin中的mount程序用来把win32盘符和网络共享路径映射到cygwin的内部posix目录树。这是与典型unix mount程序相似的概念。对于那些对unix不熟悉而具有windows背景的的人来说，mount程序和早期的dos命令join非常相似，就是把一个盘符作为其他路径的子目录。 路径映射信息存放在当前用户的cygwin mount表中，这个mount table 又在windows的注册表中。这样，当该用户下一次登录进来时，这些信息又从注册表中取出。mount 表分为两种，除了每个用户特定的表，还有系统范围的mount表，每个cygwin用户的安装表都继承自系统表。系统表只能由拥有合适权限的用户（windows nt的管理员）修改。当前用户的mount表可以在注册表HKEY_CURRENT_USER/Software/Red Hat, Inc./Cygwin/mounts v 下看到。系统表存在HKEY_LOCAL_MACHINE下。posix根路径/缺省指向系统分区，但是可以使用mount命令重新指向到windows文件系统中的任何路径。cygwin从win32路径生成posix路径时，总是使用mount表中最长的前缀。例如如果c:被同时安装在/c和/，cygwin将把C:/foo/bar转换成/c/foo/bar. 如果不加任何参数地调用mount命令，会把Cygwin当前安装点集合全部列出。在下面的例子中，c盘是POSIX根，而d盘被映射到/d。本例中，根是一个系统范围的安装点，它对所有用户都是可见的，而/d仅对当前用户可见。 c:\ mount f:\cygwin\bin on /usr/bin type system (binmode) f:\cygwin\lib on /usr/lib type system (binmode) f:\cygwin on / type system (binmode) e:\src on /usr/src type system (binmode) c: on /cygdrive/c type user (binmode,noumount) e: on /cygdrive/e type user (binmode,noumount) 还可以使用mount命令增加新的安装点，用umount删除安装点。 当Cygwin不能根据已有的安装点把某个win32路径转化为posix路径时，cygwin会自动把它转化到一个处于缺省posix路径/cygdrive下的的一个安装点. 例如，如果Cygwin 访问Z:\foo，而Z盘当前不在安装表内，那么Z:\将被自动转化成/cygdrive/Z. 可以给每个安装点赋予特殊的属性。自动安装的分区显示为auto安装。安装点还可以选择是textmode还是 binmode，这个属性决定了文本文件和二进制文件是否按同样的方式处理。 cygpath工具提供了在shell脚本中进行win32-posix路径格式转换的能力。 HOME, PATH,和LD_LIBRARY_PATH环境变量会在cygwin进程启动时自动被从Win32格式转换成了POSIX格式(例如，如果存在从该win32路径到posix路径的安装，会把c:\cygwin\bin转为/bin)。
标签: windows
