A7V333 - Max bootable drive size?

  • Thread starter Thread starter KWW
  • Start date Start date
K

KWW

I tried porting my OS/boot disk to a new 120 Gb drive (from my 15 Gb drive)
and when I tried to startup from it I got a Windows 2000 error... don't know
why it should cause problems. I would think if it were a BIOS problem that
it wouldn't have gotten to the OS splash screen, right? Is is a Western
Digital drive instead of a Maxtor, but I am not running any sort of overlay
program or anything, so it is weird. Anybody experience this sort of thing?
Is there a limit to the boot disk size on the A7V222 BIOS vsn 1005?

TIA!
 
KWW said:
I tried porting my OS/boot disk to a new 120 Gb drive (from my 15 Gb drive)
and when I tried to startup from it I got a Windows 2000 error... don't know
why it should cause problems. I would think if it were a BIOS problem that
it wouldn't have gotten to the OS splash screen, right? Is is a Western
Digital drive instead of a Maxtor, but I am not running any sort of overlay
program or anything, so it is weird. Anybody experience this sort of thing?
Is there a limit to the boot disk size on the A7V222 BIOS vsn 1005?

TIA!
Click to expand...
I use 12oGb drives, partitioned, and they boot up OK.

What error does W2K give you ? and I think the BIOS revisions are p up to
something like 1017, so you may need to upgrade, but first, the Windows
error please.

the_gnome
 
When I formatted the new 114GB Western Digital drive (120,000,000 bytes).
I did use the
installation tools (from WD) to let them transfer the OS stuff from my 15 Gb
drive to the replacement drive. It all says that it works fine, it doesn't
show any signs of that "EZBIOS" stuff, but when I swap out the new one to be
the master, I get the following black screen error on startup:

Windows 2000 could not start because of a computer disk hardware
configuration problem. Could not read from selected boot disk. Check boot
path and disk hardwared. Please check the Windows 2000 (TM) documentation
about hardware disk configuration and your hardware manuals for additional
information.

MS Knowledge base notes that such a thing can happen if WD EZ Bios is
present. Otherwise there were some things about how a ghosted or mirrored
drive won't boot if the physical characteristics of the replacement drive
are different (or it has a different firmware revision, etc...) I don't
know if this is the problem.

System:
ASUS A7V333 mobo (not using RAID at present) 1005 BIOS (I guess I could
flash up to 1017, but I sort of would like to get this going first... and
the board has not given me problems... and I didn't see anything in the
(available) descriptions on the ASUS website for 1014 - 1017 dealing with
any of these issues. (they don't have anything before 1014).

256 MB RAM
AMD Athlon XP+ 2100 CPU
W 2K Pro SP4 & all security patches
IE 6 and all patches
USB: Scanner/Zip 100
2 CD R/Ws on Secondary IDE
New WD 120 Gb Primary Master Boot disk (some day) NTFS
(Currently WD 15GB Primary Master Boot disk, NTFS
Maxtor 80 Gb Primary Slave disk, NTFS
3Com Ethernet 10/100 PCI
G Force4 MX440 (NIVIDA) video (MSI MS-StoarForce)
Floppy drive
SOME WEIRD device attempting to be registered (but I don't allow it because
it makes no sense) "B ER H"

Any help is appreciated.
 
Back
Top