You can fdisk the drive and create a new partition, but dos fdisk can't format it as swap. Linux's swap is a filesystem and fdisk don't know how to create it.
I think the better way to go is to mount this drive as slave in your win machine and boot it with knoppix. Once in the system, you can create the swap space, by using cfdisk or parted, native partitioning tools from knoppix.

Bruno,

Thank you for your help. I finally got it to work. I'm sure my method was a little on the roundabout side, but it was finally effective. Here is what I had to do for anyone who runs into this problem in the future.

I found no way to create the Linux swap partition using my old machine, so I resorted to pulling the hard drive and slaving it off of my new machine. I booted the machine into Knoppix 3.3 and used fdisk to create a linux swap partition on the old hard drive, leaving the rest of the drive with Win95 FAT32 partitions. I then moved the old drive back to the original machine and began the install process again with the boot disks. Once again, I encountered the insufficient memory error for Yast. I attempted to use the newly created Linux swap partition on the old drive, but once again resulted in an error detecting the swap.

I again pulled the old drive and placed it into the new machine, this time disconnecting my Win XP hard drive and making the old drive the master. I then loaded SuSe 9.1 onto the old drive using the new machine. SuSe successfully loaded. I then removed the old drive and placed it back into the original machine. When I attempted to boot SuSe, I encountered a fatal error during the boot process, causing the Kernel to hang. As a final attempt, I again began the installation process on the old machine using the boot disks. This time, when I encountered the insufficient memory for Yast message, SuSe was able to detect the swap partition I created on the first install using the new machine. It was very slow in loading, but this time I was able to fully install SuSe on the old machine. I could not use the Yast GUI, because of insufficient memory, but the non-Gui interface worked just fine. After installation, SuSe booted with no problems.

Again, thank you for all of your help.

Raveck

I'm glad to know, friend! Its nice that even with all these obstacles you didn't gave up. I hope suse prove worth the effort.

There are lighter desktop environments that you may want to take a look, if you are on a test stage. They take less memory to work, and can be an option: fluxbox, windowmaker and others. Kde is a great mem-eater.

The modern distros need a basic configuration which is kinda huge, in my opinion. They dont benefit too much on older hardware. Its a general idea that 128 mb ram is the minimum to run kde smoothly.
But if you like suse/linux and wanna install it onto your main machine in the future, be aware that these problems won't appear. I use suse in my athlon 1600 / 256 mb ram and it simply works. No more windoze/cracks/virus/worms/spys/defrags/scandisks.

Anyway, be welcome!