A.1. Frequently Asked Questions

Windows 98 does not recognize the effect of fips-0.9e. fips-2.0 has successfully been used to split a Windows98 partition. According to an unreliable source, Windows 98 reads partition data from the first 512 bytes of the partition itself and considers this more reliable data than the partition table.

This means that the partition table is inconsistent, and may be inaccurate. Modifying a disk with an inaccurate partition table usually requires an expert to reduce the almost certain chance of data loss.

The severity of this message is dependent on the size of the disk. Due to historical limitations, most (but not all) computer BIOSs only support disks with less than 1024 cylinders. Booting the operating system depends on the bios, therefore (on such systems), the entire operating system must fit within this 1024 cylinders.. For the same historical reasons, the partition table format only supports reporting disk sizes of 1024 or less cylinders. Many disks today have more than 1024 physical cylinders but by convention the partition table records exactly 1024 cylinders. The operating system still needs to know where the actual partitions begin an end beyond the first 1024 cylinders and this is recorded in the partition table.

A large disk with more than 1024 cylinders will have a logical size (sum of partition sizes) that exceeds 1024 and matches the actual size, though the partition table reports a physical size of exactly 1024 cylinders. In the case of a large disk, this message is essentially useless.

One or more of the following should tell you what version of Windows you have.

• C:\>ver

• {My Compuer} [Properties] [General]

• [Start] [Run...] Open: command [OK]

• [Start\Run...] Open: ver [OK]

• [Start\Run...] Open: cmd ver [OK]

bash> uname -a

The question may have no meaningful answer. Since unix dialects (e.g. linux) use many interchangeable parts, it makes little difference to this HOWTO what distribution you have. The applications loaded on most linux hosts varies with time and the tastes of the owner, so that they seldom match any distribution for more than a very brief period.

Most distributions are loosely classed by the package manager that they use.

• pkgtool - slackware

• rpm - RedHat

bash> uname -a

In general, no. For this reason, meticuluous care is required, especially at certain stages. Some of the operations are idempotent. An idempotent operation is one which either fails and has no effect, or succeeds and has no effect after its first success. Some of the operations are reversible. A reversible operation has an inverse operation so that you can return things to what they were and start over.

Formatting is especially dangerous because it is neither idempotent nor reversible. If formatting succeeds, the original data is lost. If formatting fails, the original data is probably lost (since indices are usually destroyed early).

Swap partition size (or even its existence) is a hotly debated issue beyond the scope of this HOWTO. Many books on performanc tuning provide guidelines on swap partition size and how to recognize a need to expand or shrink it. At press time, the author recommends 64M as a safe size.

A reader of this HOWTO presumably wants to benefit from the strengths of both Windows and linux, and suffer the shortcomings of neither.

Most linux distributions allow you to cleanly remove any package. unix dialects support permissions so that each package gets a well defined share of the computer and this share can be identified and taken back in its entirety. unix dialects support symbolic links so that the package can appear to be in a convenient place without actually occupying space from the convenient place. The distributions that do not support easy removal are usually tiny specialized distributions like tomsrtbt. The risk that an unwanted package will plague your linux indefinitely is small since you can remove it at any time.

Most Windows packages can never be uninstalled cleanly under Windows, as they usually leave dll updates and registry entries. It is therefore important to add packages only when you are sure that you need them, since your only way of removing them may be to reinstall Windows and every package that you want.

Sharing a machine between Windows and linux, means that linux can aid clean removal of packages from Windows. Since it only identifies but does not predict, linux cannot insure clean removal. Since linux find resolves to the second rather than Windows find to the day, it can much more accurately identify what was changed.

1. Record the date and time before you install a package to Windows.

2. Install the package.

3. Record the date and time after you install the package.

4. Under linux, use touch to create a file timestamped at the start of installation.

5. Under linux, use touch to create a file timestamped at the end of installation.

6. Under linux, use find to identify every Windows file and folder that was altered during installation.

7. Store the list of altered files and folders to identify what has to be removed or restored.