Use the expand command to extract files from a .cab file: expand [-r] source [destination] [-d source.cab ... Option Description [-r] Renames expanded files. [destination] Specifies where files are to be expanded. If source is multiple files and -r is not specified, destination must be a directory. destination can consist of a drive letter and colon, a directory name, a file name, or a combination of any of these. [-d source.cab] Displays a list of files in the source location. Does not expand or extract the files. [-f:files] Specifies the files in a cabinet (.cab) file that you intend to expand. You can use wildcards (* and ?). source.cab Specifies the files to expand. source can consist of a drive letter and colon, a directory...

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.ini Add 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.ini Reboot

Use android list targets to find valid targets: C:\android-sdk-windows\tools>android list targets ...

On windows, display IPv4 routing table: route -4 print On Linux: $ route Kernel IP routing table Destination ... This works for both Linux and Windows (" -r ": display routing table, " -n ": display address and port numbers in numerical form): netstat -rn

mysql> show character set; +----------+--------...

Suddenly my Windows XP failed to boot with this error message on a blank screen: missing or corrupt <windows root>\system32\hal.dll I 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...

Same problem using Eclipse 3.6 (WTP 3.2.1) & Windows XP SP3, launching the default server. This fix solves the problem. Thanks a lot!

You can use the ntfsresize utility on Linux to shrink or expand an NTFS partition (boot, for example, with the DRBL live cd). To shrink an NTFS partition: shrink NTFS (the file system) with ntfsresize. re-create a smaller partition to hold the shrinked file system with FDisk. To expand an NTFS partition: Recreate a partition that's bigger than the previous one. expand NTFS to the full size of the new partition. The following are from excerpts from ntfsresize FAQ (Frequently Asked Questions) : ntfsresize help: [tinker:root]:(~)# ntfsresize -h ntfsresize v1.... ntfsresize example session: [tinker:root]:(~)# ntfsresize -s11000M /dev/hd... Fdisk example session: [tinker:root]:(~)# fdisk /dev/hdc ...

This one is even more weird: it worked on Windows but failed on Linux, using default tools JDK1.6.0_20 on both. The exception thrown was: java.lang.RuntimeException: Invalid conversion fro... And the stack trace: java.lang.RuntimeException: Invalid conversion fro... This was the XSL used: <?xml version="1.0" encoding="ISO-8859-1"?> <xs... The problem was , DateUtil.java had two getDate methods, one taking long parameter, the other taking a String parameter. And Java's XSLT get confused about which one to use: import java.util.Date; import java.text.SimpleD...

It happened on Windows XP with JBoss 5.1.0.GA. This is the stack trace: 2010-07-30 16:39:52,177 ERROR [org.jboss.kernel.pl... According to " (SOLVED) JBAS-7674 solution for JBoss 5.1?? (Windows lock on jnp-service.url) ", the problem seemed to be solved for JBoss 6. In the meanwhile for JBoss 5, disabling Windows Indexing Service seemed to solve the problem. Quote from aforementioned link: It seemed that a file was being locked for some reason, and that file was obviously necessary for JBoss to start. Some further investigation (ok, I admit, I just tried to delete all of JBoss with the faith that it would fail on the locked file), it turns out that file was some file called jnp-service.url in the data directory of the default server. After downloading...