Yes, it is chkdisk that should be used with the -r parameter, there may be an issue with the file system.
Windows does not use a swap partition, it uses a file named pagefile.sys located in the OS’s partition at the root level (i.e., usually under “c:”). The default is to allow Windows to dynamically set its size, which is not a good idea anyway. XP and before use a lousy memory manager which overuses virtual memory, but it is problematic to permanently remove it altogether. Usually 500MB is more than adequate, and if the machine is used lightly, 256MB should do fine. Having a smaller page file will enable to do the swapping it unnecessarily insists on doing, while with other processes force Windows to use all available RAM (which is how Vista’s new memory manager work, as does Linux).
Reference booting, assuming Windows has no boot manager, just check during the install that openSUSE Linux says it will be placing “grub” (the Linux boot manager) on the MBR. If it is NOT doing that, then do not let the install proceed.
I don’t understand this advice. If anything with the messages the installer is throwing, I would try to avoid the MBR if possible because what could be confusing the installer is something weird in the partition table or the recovery partition - manufacturers are more and more doing undocumented proprietary things with the table, and bios recovery extensions and/or recovery partitions - following the continuing practice of Microsoft (most recently, Vista’s unexpected use of the MBR disk signature). I know what the sticky says, but frankly I agree with the wiki article written by the dev’s:
We recommend to keep the MBR “neutral”, that is, not consider it part of any operating system. For that purpose, a generic MBR can be used, that simply determines one of the 4 primary partitions by a bit flag, and then loads the first block of that partition in turn, to continue the boot process. The Yast installation offers the option to install such generic code in the MBR; do it when in doubt.
@eeijlar - My suggestion is that you manually control the partitioning if you can. Take a look in Windows under Computer Management/Disk Management to verify how many partitions you already have - you have one for the Windows OS, one for recovery; make sure there isn’t a 3rd which may be used for the recovery program code. If 3 are already taken, your only choice is to create a 4th “primary” which must be an “extended” primary, and then create 3 “logical” partitions within the extended to place the openSUSE swap, root, and home partitions. (The machine limits you to 4 primaries, one of which can be an extended) - in this case, you will need to install grub to the MBR. But if you only have 2 already taken, you can create a 3rd primary for the openSUSE root, then as above a 4th extended primary in which you create 2 logicals, one for swap and one for home. Or, perhaps better yet, you can just put all of openSUSE on the 3rd primary, swap on the 4th primary, and not get into an extended with logicals at all - this is the simplest setup. Then - and this is critical - during installation at the Boot Loader step, go into the dialog and under the Installation tab in the Location section, check the box for “boot from root partition” and un-check any other boxes (particularly the MBR). Then click Boot Loader Options which will give a new screen, and in the upper left click on “set active flag for boot partition”. This will result in the grub boot loader being installed in openSUSE root partition, and leave the Windows MBR code untouched. The Windows code will choose grub for booting (that is what the active flag does), and grub can in turn boot Windows. This is by far the safest approach.
By the way, you have one other alternative. If you work in a Unix shop and use Unix a lot, and your Windows needs are limited to occasional use of a few programs, and your machine has at least 1GB of RAM, you can consider running Windows in a virtual machine on top of openSUSE. This has become a widely used technique in the last couple of years, and generally works superbly. Note that this would require your having a Windows installation CD, to install in the virtual machine. Just fwiw.