This is done for two reasons. Indeed, moving the data is not necessary for shrinking a partition. But leaving the data in it's original place, results in unused sectors in the partition's FAT, which is lost space. The second reason is that you cannot grow a partition without growing it's FAT, and in order to grow the FAT, you have to move the data.

Yes. You have to make a little empty space in the drive by shrinking the original partition, and then create a small partition and start moving your data in it, while shrinking the old partition and growing the new one. When all the data is in the new partition, change the old partition's cluster size, and move the data back to the old partition using the same technique. This process might take a bit long, since there's a lot of moving and resizing in it.

You don't. You can as well backup all your data, use FDISK to repartition your drive, and restore the backed up data in the new partition. But while this can take sometimes many hours, and this only if you have a tape streamer (don't even think about using floppy disks), Partition Resizer will do the job in 5-30 minutes in most cases.

Best way is to get it from this page, which has a new link now, http://zeleps.com (please update your bookmarks). Also, you can always find it in any SimTel mirror site, like oak.oakland.edu, or nic.funet.fi, in the directory SimTel/msdos/diskutil under the name presz???.zip. ??? is the current version number. Another good way to locate the latest version is to perform a web or ftp search, using "presz" as the search string (ftp search can be performed at ftpsearch.ntnu.no).

A quorum disk or partition is a section of a disk that's set up for use with components of the cluster project. It has a couple of purposes. Again, I'll explain with an example. Suppose you have nodes A and B, and node A fails to get several of cluster manager's "heartbeat" packets from node B.

When you visit Hylands-GC.com you'll notice the Font Resizer displayed on the footer of every page. You can change the font size automatically for the majority of content to 4 different sizes (10 px, 12px, 14px, 16px). This will then set a cookie on your PC so when you next visit the site it will remember your viewing preferences. This facility will not adjust your browser font size preferences, neither will it affect any other websites you visit.

The program itself works fine with these, since it doesn't consider them as drives. Partition Resizer scans ONLY physical drives for partitions. But it shouldn't be run from a compressed drive that resides in a partition that will be resized or moved. If you're uncertain about that, just run Partition Resizer from a bootable floppy disk. Absolutely. Long filenames are not affected, since the program doesn't mess with directory and file descriptors.

Depends. It does not run under Windows NT/2000/XP, and it does not resize NTFS partitions, but it can move Windows NT/2000/XP partitions and it does not damage your Windows NT/2000/XP installation.

You have to boot from a bootable DOS floppy disk to run Partition Resizer under NT/2000/XP. In Windows XP you can create a bootable floppy disk from Windows Explorer by inserting the floppy in the drive, right-clicking the drive, selecting 'Format...' and checking the 'Create an MS-DOS startup disk' option. Then copy Partition Resizer in that disk and proceed as described in README.1ST.

I really do not want to invest time in creating a fancy user interface, although it would simplify a few things both for me and the users. If I get bored enough, I'll probably do something about it. The new site was created by Stathis Sideris (http://www.satspeed.gr/~im), to whom I am eternally in debt for uplifting my sorry excuse for a site. My artistic nature is comparable to that of a colorblind hedgehog (in a bag).

This is an option I consider, although it would be a bit complicated. This is because all the changes that Partition Resizer does to a hard disk are extremely dangerous (although possible - beware!) to be done while under a multitasking environment. Therefore, even if the user makes all his selections under windows, the program core must be run in DOS mode. I am considering the possibility of a Windows interface that will co-exist with the current DOS interface (probably in the same EXE file).

Run option 5 will repartition your NTFS filesystem to add an EXT3 filesystem, but you must DEFRAG your windows system first. Option 5 will then copy the ADIOS filesystem into the new partition and run the linux loader LILO, changing the active partition to the second partition. After rebooting you will be able to select Windows or Linux.

Yes, partitioning is recommended even if one is planning to use the entire disk for ocfs2. Apart from the fact that partitioned disks are less likely to be "reused" by mistake, some features like mount-by-label only work with partitioned volumes.

No problem. Live View will automatically detect this and build a Master Boot Record for your partition allowing it to boot. Yes, simply select all of the chunks in the browse dialog by using Ctrl + Click. Live View sorts the chunks by their file extensions so be sure that the chunks have either numerically or alphabetically ordered file extensions. Yes, there is full support for the primary operating system on the machine and partial support for the secondary operating system.

You have three options: dd, dump.bsd and cpio. pax may work but tar won't since it won't handle special-type files. If the two partitions are the same size, you can use 'dd' (to copy c0d0s0 to c5d0s3, e.g.): dd < /dev/rdsk/c0d0s0 > /dev/rdsk/c5d0s3 To use dump.bsd, you can use the following command (this assumes that the destination disk in mounted on /mnt and you want to copy the root file system which is on SCSI 0..

Basic data partitions correspond to primary MBR partitions 0x6 (FAT), 0x7 (NTFS), or 0xB (FAT32). Each basic partition can be mounted using a drive letter or mount point, other volume device object, or both. Each basic data partition is represented in Windows as a volume device object, and optionally as a mount point or a drive letter.

It has the following partition type GUID: DEFINE_GUID (PARTITION_BASIC_DATA_GUID, 0xEBD0A0A2L, 0xB9E5, 0x4433, 0x87, 0xC0, 0x68, 0xB6, 0xB7, 0x26, 0x99, 0xC7);

This subject comes up every time some CP/M archive on the Web vanishes, or there is some discussion of data media. Of course some CP/M original media is 20 years or more old, so it is relevant. The issue in many cases is not the degration of the media, but loss of old technology and software to READ the media. A reasonable strategy is to copy data to "current" media every few years to avoid both media damage and obsolscence.

When formatting a drive a large portion of the administrative and meta information is re-initialized, but not all of it. If recovered data will be intact highly depends on the fragmentation of the file system: since there's no way of telling exactly what clusters 'belonged' to specific files, recovery software will assume that the file system was not fragmented and files were stored in consecutive clusters.