I'm trying to net install a 'super heavyweight' windows image -- its got *a
lot* of driverpacks from driverpacks.net integrated and that's causing it to
run out of space on the disk at some point during installation. I know the
disk is large enough and I'm using the 'full disk' partitioning option but
there must be something about how the installation works I'm not
understanding...
After the system reformats the fat32 partition to ntfs and reboots, the
system boots into the windows gui and the modified driverpacks installation
process begins unpacking the compressed driverpacks. However because I have
so many packs integrated into this image I'm running out of space on the
disk.
If I reboot into knoppix and look at the partition table I see a 4gig ntfs
partition and some 200+ gigs of unallocated space... Is there some way I
can modify the installation process to make a larger partition available
during installation?
Thanks,
Ben
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
unattended-info mailing list
unattended-info@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/unattended-info
