I have got mobo "AK31V3.1 (VIA KT 233).
How large hard drive can I use with that mobo..?
How to check it without connecting physical hdd..?
Best regards,
Tom.
AK31V3.1 - how large hdd to be supported?
-
Denniss
- BIOS Guru
- Posts: 3153
- Joined: Thu Mar 21, 2002 8:16 pm
- Location: Near Hannover (CEBIT) Germany
- Contact:
http://eu.shuttle.com/archive/en/ak31.htm
Should be your board - please compare images.
It should have native support for HDD up to 128 GiB and may support even bigger HDD. Otherwise any modern OS could be used to access space above a possible Bios limit
Should be your board - please compare images.
It should have native support for HDD up to 128 GiB and may support even bigger HDD. Otherwise any modern OS could be used to access space above a possible Bios limit
Last edited by Denniss on Wed May 20, 2009 5:53 pm, edited 1 time in total.
Denis - thanks for information!
But - is it possible to "break" BIOS file to patch it for 160GB hdd to be supported..?
I remember "Rainbow" did such favour for me with other BIOS file in the past.. B))
Tom.
But - is it possible to "break" BIOS file to patch it for 160GB hdd to be supported..?
I remember "Rainbow" did such favour for me with other BIOS file in the past.. B))
Tom.
native bios support for HDDs larger than 128GB would require 48bit LBA support in the bios. this is not possible with reasonable effort. but it isn't required at all if you're using a modern OS (Linux, Windows 2000 SP4, XP SP2, Vista) the only thing you have to take care of is that your boot partition (which holds the OS) is within the BIOS-detected space. the rest of the HDD can be used without any restrictions once the OS is loaded.
If you email me include [WIMSBIOS] in the subject.
GRUB still uses BIOS calls to access disks (LBA or CHS), so it can only boot partitions that are within a BIOS-known space. The problem accessing disks beyond 128GB dissolves when the OS (and its drivers) is loaded. This isn't a problem, at least from my point of view, because a custom Linux kernel requires 1-2MB (on a 20MB boot partition) and contains everything that is needed for 48bit LBA. An old 32MB CF-card on an ide-to-cf-adaptor should be more than enough :)
If you email me include [WIMSBIOS] in the subject.
Is it a good way to partition hdd:
1, 2, 3 partition up to the 128GB capacity (and not to across that limit), rest of the hdd - till the end of (--> 160GB)?
Or in general - is one of the partition end must be at 128GB capacity?
Tom.
1, 2, 3 partition up to the 128GB capacity (and not to across that limit), rest of the hdd - till the end of (--> 160GB)?
Or in general - is one of the partition end must be at 128GB capacity?
Tom.
depends on how many different OS are installed. if using Windows it's always a good idea to make a boot partition which holds the OS. its size should be around 4-8GB. the rest of the hdd should be a single extended partition which only holds one logical partition.
the boot partiton should only be used to install Windows and for the hibernation data file (which can not be saved anywhere else). all programs, my documents and all other data should be saved to the extended partition to keep the boot partition clean.
with linux you can create a 20MB boot partition which holds the kernel and do what you want with the rest of the harddisk. once the kernel is loaded 48-bit LBA is used anyway.
there's no need to align a partition to any boundary or cut it at any boundary.
the boot partiton should only be used to install Windows and for the hibernation data file (which can not be saved anywhere else). all programs, my documents and all other data should be saved to the extended partition to keep the boot partition clean.
with linux you can create a 20MB boot partition which holds the kernel and do what you want with the rest of the harddisk. once the kernel is loaded 48-bit LBA is used anyway.
there's no need to align a partition to any boundary or cut it at any boundary.
If you email me include [WIMSBIOS] in the subject.
