OK, I'm no linux guru, but I'm no KNOPPIX NOOB either. So, don't get upset when I post the following query:

I maintain a Linux Lab for my AP Computer Science students. Over the past several years, I've had occasion to install all versions of KNOPPIX to hdd from 3.2 with knx-hdinstall to 3.8.1 with knoppix-installer a LAN of 25 PCs. I never had to install 3.9 to hdd until today. And, I have to say that I have never encountered such a knoppix-installer nighmare before!

First, I had lots of read errors on my cdd's which has happened only rarely. I suppose it could be bad media or bad drives. So, I can't even boot the KNOPPIX CD on those stations (2Pcs down, 23 to go).

However, this LAN was reinstalled just a few years ago with all new hadware (fast ethernet, PIV PCs with 750MB RAM and 40GB hdds = Dell GX270s). Further, I don't usually have media problems. I always use Memorex 700MB data CDRs without a problem. BTW, I check my ISO downloads with md5sums and burns CDs with the
Code:
knoppix testcd
cheat code.

Second, I had several errors when using qtparted to resize the XP partitions before running knoppix-installer which never happened before. I guess it could be over-used hdds. So I can't install anything on those stations (6 more PCs down, 17 to go). Please note that this is not an NTFS issue. All XP installs were done on VFAT32 to begin with.

BTW, my partitions, where qtparted worked, are hda1=35MB WIMPdoze rescue partition which I didn't touch, hda2=20GB WIMxP partition which I had resized from 40GB, hda3=19GB ext3 partition for the hdd install and hda4=178MB (that's all that's left) linuxswap partition created from the new space after resizing.

Third, I had several PCs stop, during the knoppix-installer step where it copies files to my new ext3 partitions, at about 96% which has happened only rarely. In the past several years, I only recall this happening a few times but I could simply retry knoppix-installer and all was fine - not this time! So the install is incomplete on those stations (2 more PCs down, 15 to go).

Fourth, I didn't realize lilo was gone to be replaced by grub which clearly never happened before! It took me a little while to figure out I had to edit
Code:
/boot/grub/menu.lst
to get my dual-boot hdd installs to default to an XP boot. Sorry, don't flame me, I have to do this to coexist with the other teachers at my school....

Fifth, netcardconfig didn't work for autoconfiguring my DHCP network on any of the 15 remaining PCs which never happened before. However,
Code:
pump -i eth0
fixed that problem!

Lastly, but not least, to add insult to injury, when a user logs-in with KDM on the 15 installed PCs, the KDE boot screen gets stuck at the second icon and just hangs the whole PC which never happened before! On a few PCs, the KDE boot screen does actually finish after 10-20 minutes!

What the heck can I do about this latest error??? I have no more hairs to pull out, any suggestions will be greatly appreciated!!!

TIA,
AJG