G
George Valkov
Vista-RC1.Setup doesn`t like the partition I choosed for vista. It won`t let
me know why, perhaps it wants me to play guessing What a playfull setup!
Whatever: I spent 5 hours moving disks, cables, switching jumpers and
reformated the partition like 10 times to make it work. Cool!
Reasons:
~ Target disk MUST be /dev/hda (primary master)
~ Target partition MUST be marked active (bootable)
~ Target disk MUST be NTFS (and not UDF)
~ Target disk MUST use default alocation unit (cluster) size. 64KB is not
permited -- strange why? My primary installation is Windows 2003-SP1
enterprise server and boots from /dev/hda1 NTFS 64KB clusters. What's the
largest supported cluster size by setup?
Cheers, after the whole pain, setup accepted /dev/hda2 (primary master,
partition 2). After the first setup phase, I moved the disk to /dev/hdd
(secondary slave) and reconnected the two other dynamic disks. Setup
completed successfully!
Finally there are two more problems:
1. I used diskpart to change the target partition's drive letter to T:, but
after the installation it was using C:. How do I force a custom drive
letter?
2 How do I create a boot menu, to select startup partition at boot time? I
want to choose between:
/dev/hdd1 (windows server)
/dev/hdd2 (windows vista)
/dev/hdd3 (linux slackware)
Please don`t tell me about 3rd party software. Can I do this from Vista or
2k3-server-SP1, or should I reconfigure the LILO (Linux Loader) and boot
from the Linux partition?
LEGEND:
/hda is primary master
/hdd is secondary slave
/hdd1 is first partition on hdd and so on. I use the unix naming because it
is short and precise.
I am asking Microsoft to fix these problems for the final release of Vista.
And if MS is to lazy to create a graphical interfase to formatting options
and choosing drive letters, at least make sure that the diskpart.exe
utility's settings and drive letter assignments) will take effect after
installation. Can`t you simply offer the Disk Management console?
me know why, perhaps it wants me to play guessing What a playfull setup!
Whatever: I spent 5 hours moving disks, cables, switching jumpers and
reformated the partition like 10 times to make it work. Cool!
Reasons:
~ Target disk MUST be /dev/hda (primary master)
~ Target partition MUST be marked active (bootable)
~ Target disk MUST be NTFS (and not UDF)
~ Target disk MUST use default alocation unit (cluster) size. 64KB is not
permited -- strange why? My primary installation is Windows 2003-SP1
enterprise server and boots from /dev/hda1 NTFS 64KB clusters. What's the
largest supported cluster size by setup?
Cheers, after the whole pain, setup accepted /dev/hda2 (primary master,
partition 2). After the first setup phase, I moved the disk to /dev/hdd
(secondary slave) and reconnected the two other dynamic disks. Setup
completed successfully!
Finally there are two more problems:
1. I used diskpart to change the target partition's drive letter to T:, but
after the installation it was using C:. How do I force a custom drive
letter?
2 How do I create a boot menu, to select startup partition at boot time? I
want to choose between:
/dev/hdd1 (windows server)
/dev/hdd2 (windows vista)
/dev/hdd3 (linux slackware)
Please don`t tell me about 3rd party software. Can I do this from Vista or
2k3-server-SP1, or should I reconfigure the LILO (Linux Loader) and boot
from the Linux partition?
LEGEND:
/hda is primary master
/hdd is secondary slave
/hdd1 is first partition on hdd and so on. I use the unix naming because it
is short and precise.
I am asking Microsoft to fix these problems for the final release of Vista.
And if MS is to lazy to create a graphical interfase to formatting options
and choosing drive letters, at least make sure that the diskpart.exe
utility's settings and drive letter assignments) will take effect after
installation. Can`t you simply offer the Disk Management console?