Displaying keyword search results 1 - 10
Created by Dr. Xi on February 13, 2013 19:40:08 Last update: February 13, 2013 19:40:08
According to MSDN : On Windows 7 and on Windows Server 2008 R2 with the Wireless LAN Service installed, the operating system installs a virtual device if a Hosted Network capable wireless adapter is present on the machine. This virtual device normally shows up in the "Network Connections Folder" as "Wireless Network Connection 2" with a Device Name of "Microsoft Virtual WiFi Miniport adapter" if the computer has a single wireless network adapter. This virtual device is used exclusively for performing software access point (SoftAP) connections. The lifetime of this virtual device is tied to the physical wireless adapter. If the physical wireless adapter is disabled, this virtual device will be removed as well. On Windows 7, there's no UI to start or stop SoftAP....
Created by nogeek on November 16, 2011 20:47:33 Last update: November 16, 2011 20:47:33
VMWare Tools must be installed in the guest OS for shared folders to work. Configure the shared folder: Virtual Machine -> Virtual Machine Settings -> Options -> Shared Folders . Click the Add button to add a share. The share maps a host path to a name in the guest. If the guest system is Linux, the shared folder is available under /mnt/hgfs . If the guest system is Windows, the shared folder is available as \\.host\Shared Folders\<share_name>
Created by nogeek on November 16, 2011 10:16:15 Last update: November 16, 2011 10:16:15
Bring up the Control Panel system page (shortcut: Win+Pause, Win+Fn+Insert/Pause for laptop): Click "Remote settings" on the left Check "Remote Desktop" -> "Allow connection..."
Created by voodoo on September 04, 2011 14:48:52 Last update: September 04, 2011 14:49:40
If Ubuntu does not recognize the wifi adapter, use ndiswrapper and Windows XP driver instead: Install the needed Ubuntu packages:
$ sudo apt-get install ndisgtkIf there's no Internet access, the needed packages are available from the Ubuntu live CD under the directory /pool/main/n . Install both ndiswrapper and ndisgtk . Download and extract the Windows XP driver for your wifi adapter. Install the Windows XP driver: Browse to System/Administration/Windows Wireless drivers Click Install New Driver Select the .inf file, then click Install Connect to wifi networks as you normally do.
Created by voodoo on September 02, 2011 18:12:56 Last update: September 02, 2011 18:12:56
This is how to add the 3GB switch for Windows XP: Remove system and hidden attributes of C:\boot.ini :
C:\>attrib -s -h boot.iniAdd the 3GB switch to C:\boot.ini :
[boot loader] timeout=30 default=multi(0)dis...Add system and hidden attributes:
C:\>attrib +s +h boot.iniReboot
Created by freyo on August 25, 2011 09:07:40 Last update: August 25, 2011 20:45:43
This is a list of built-in Android permission values: Permission Description Since API Level android.permission.ACCESS_CHECKIN_PROPERTIES Allows read/write access to the "properties" table in the checkin database, to change values that get uploaded. 1 android.permission.ACCESS_COARSE_LOCATION Allows an application to access coarse (e.g., Cell-ID, WiFi) location 1 android.permission.ACCESS_FINE_LOCATION Allows an application to access fine (e.g., GPS) location 1 android.permission.ACCESS_LOCATION_EXTRA_COMMANDS Allows an application to access extra location provider commands 1 android.permission.ACCESS_MOCK_LOCATION Allows an application to create mock location providers for testing 1 android.permission.ACCESS_NETWORK_STATE Allows applications to access information about networks 1 android.permission.ACCESS_SURFACE_FLINGER Allows an application to use SurfaceFlinger's low level features 1 android.permission.ACCESS_WIFI_STATE Allows applications to access information about Wi-Fi networks 1 android.permission.ACCOUNT_MANAGER Allows applications to call into AccountAuthenticators. Only the system can get this permission. 5 android.permission.AUTHENTICATE_ACCOUNTS...
Created by woolf on June 25, 2011 10:55:08 Last update: June 25, 2011 10:57:15
My C drive was seriously fragmented with about 20% free space. So I ran the built-in Windows disk defrag utility. To my surprise it doesn't work at all! I tried to defragment multiple times and every time it comes back without doing much work. Then I realized that perhaps it didn't know how to get the job done and needed some help. Here's the list of things I did to help the defragmentor out: Relocate the paging file to a different drive and reboot. If the paging file ( pagefile.sys ) is seriously fragmented, it can't be defragmented, and in turn it blocks other files from being defragmented. If you only have one drive (C:), try to make it smaller or eliminate it entirely for...
Created by nogeek on April 21, 2011 20:38:31 Last update: April 21, 2011 20:39:07
Bring up the "System Properties" dialog (Start -> My Computer -> Right Click -> select Properties ) Click on the Remote tab. Check the box labeled "Allow users to connect remotely to this computer".
Created by Dr. Xi on December 12, 2007 22:57:22 Last update: March 25, 2011 15:05:40
1. Install windows resource kit . 2. Install srvany as a service:
C:\tools\putty>instsrv ssh_tunnel "C:\Program File...3. Edit the following registry template to suite your environment:
Windows Registry Editor Version 5.00 [H...4. Import the registry entry. 5. Start the service with "net start ssh_tunnel" or from the services applet. You may choose to use a batch file for srvany (instead of plink.exe ), but you won't be able to shut down the tunnel when you stop the service. Also, if the Windows SYSTEM user cannot see the host key for SSH connection, the tunnel cannot be established.
Created by voodoo on February 25, 2011 14:00:41 Last update: February 25, 2011 14:03:46
Suddenly my Windows XP failed to boot with this error message on a blank screen:
missing or corrupt <windows root>\system32\hal.dllI took out the hard drive, put it in a USB enclosure and attached it to another PC. Then I ran CHKDSK and it fixed some file system errors. But I did find that hal.dll was intact, so hal.dll was not missing or corrupt . It turned out that the file that was really missing was C:\boot.ini . It is a hidden file, so you have to use attrib boot.ini to see it. The file is missing if attrib boot.ini returns nothing (run in the root folder C:\). In my case I reconstructed the boot.ini file:
[boot loader] timeout=30 default=multi(0)dis...and changed the attributes back...