Jim, I tried mucking around with Linux FDISK today. What I did as tests follow: First, I booted off CD #5 (the Live Filesystem CD) and ran fdisk from /sbin. I deleted all the partitions on the 4Gb hard disk in the PC (it is the only drive, and is 4097Mb in size). Then, I created a single, primary drive 4050Mb in size, and set it's type to Win95 FAT16 (LBA) - partition type e in fdisk. I wrote the partition table and booted the NT Server 4 CDROM. Installation proceeded perfectly, and I stopped the installation after it had successfully formatted as FAT (using 64Kb clusters) the partition I had created in Linux. The NT Setup program saw the partition fine, and claimed it was "Unformatted or damaged". Next, I booted the Live Filesystem CD as before and ran fdisk. This time I deleted all the partitions and created a primary 2000Mb Win95 FAT 16 (LBA) partition (/dev/hda1) and another primary Win95 FAT16 (LBA) partition of 2097Mb (/dev/hda2). I wrote the partition table and rebooted with the NT Server 4 CDROM. Setup this time detected /dev/hda1 correctly as a FAT partition (since its size <2048Mb) and saw the second partition (/dev/hda2, size 2097Mb) as "Unformatted or damaged". NT Setup successfully formatted the partition as FAT, using 64Kb clusters, and I terminated the setup following that. I would expect no problems subsequently booting either of the tested partitions to NT, because both of the partitions start less than 4096Mb into the hard disk. Only if an NT partition is created beyond this limit (because of MSDOS using a 16-bit filesystem) is it rendered inaccessible from setup (although creating a new partition beyond this limit using Disk Administrator within NT is no problem). HTH Alan. -- To get out of this list, please send email to [EMAIL PROTECTED] with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at http://www.suse.com/Support/Doku/FAQ/ and the archive at http://www.suse.com/Mailinglists/suse-linux-e/index.html
