Win2k likes to default to the 4096 file allocation during installation and
the reason is Bill thinks that you are using humongous hard drives on servers.
The 512 allocation is much more efficient and to get Win2k "C" drive on that
allocation is quite difficult if the drive is already on 4096. The only way to
get it back is by booting from a Win98 boot disc to the "A" drive and use
FDISK to set the "C" drive partition. Then reboot with the same disc and set the
"C" drive to format. This will format the "C" drive to fat32 512 allocation.
Then using the win98 boot disc set the partitions only on remaining drives.
Install Win2k as normal but select "Convert to NTFS" when asked. This will
copy the 512 allocation on the "C" drive. All other drives can be formatted
after Win2K installation. If by chance your "C" drive is one allocation and your
other drives are something else you will have huge delay's in the operation
of VV-3 functions especially "deleting".
Win2k has a touch of "AI" in it and your hard drives must be clean from
previous installations or the new installation will "suck" information from
even a newly partitioned hard drive. Do not have any network cards installed
when installing Win2k as it will suck info from other sources. It is best to install cards one at a time as Win2k does not like multiple assimalations and will
"blue screen you" for trying. SP-3 fixes a problem of fast processors shutting
down Win2k too fast and loosing data so get this fix in pronto or install
the Win2k with the "internal cache" disabled in the CMOS. this will slow the
install down to a crawl to prevent loss of data. Then install the SP-3 update
and enable the internal cache. Old drivers and Win2k do not get along and will
blue screen you. During the Win2k install if you have new drivers "third party" for certain components press the F6 button when asked several times during install to get them in. Win2k will come back later to ask for the drivers.
Win2k has exceptional information gathering capabilities and can even
tap info from cleanly formatted hard drives.
James J. Kizak
the reason is Bill thinks that you are using humongous hard drives on servers.
The 512 allocation is much more efficient and to get Win2k "C" drive on that
allocation is quite difficult if the drive is already on 4096. The only way to
get it back is by booting from a Win98 boot disc to the "A" drive and use
FDISK to set the "C" drive partition. Then reboot with the same disc and set the
"C" drive to format. This will format the "C" drive to fat32 512 allocation.
Then using the win98 boot disc set the partitions only on remaining drives.
Install Win2k as normal but select "Convert to NTFS" when asked. This will
copy the 512 allocation on the "C" drive. All other drives can be formatted
after Win2K installation. If by chance your "C" drive is one allocation and your
other drives are something else you will have huge delay's in the operation
of VV-3 functions especially "deleting".
Win2k has a touch of "AI" in it and your hard drives must be clean from
previous installations or the new installation will "suck" information from
even a newly partitioned hard drive. Do not have any network cards installed
when installing Win2k as it will suck info from other sources. It is best to install cards one at a time as Win2k does not like multiple assimalations and will
"blue screen you" for trying. SP-3 fixes a problem of fast processors shutting
down Win2k too fast and loosing data so get this fix in pronto or install
the Win2k with the "internal cache" disabled in the CMOS. this will slow the
install down to a crawl to prevent loss of data. Then install the SP-3 update
and enable the internal cache. Old drivers and Win2k do not get along and will
blue screen you. During the Win2k install if you have new drivers "third party" for certain components press the F6 button when asked several times during install to get them in. Win2k will come back later to ask for the drivers.
Win2k has exceptional information gathering capabilities and can even
tap info from cleanly formatted hard drives.
James J. Kizak