View Full Version : New insntall of VortexBox 1.7 won't boot
01-01-2011, 06:50 AM
MD5sum matched download, K3b burned CD, NF325-A7 SOCKET 754 Mother Board, 2GB DDR400RAM, GECUBE GC-R7000-B3 Radeon 7000 64MB 64-bit DDR AGP 2X/4X Video Card, WDG 80GB hdd, system previously used for WinXP x32 SP3. VB1.7 installation went well according to the on screen prompts , on reboot no prompt to halt and remove CD, which was removed by opening the drive but system hangs soon after BIOS.
What is going on? How to boot to get the IP number screen expected to be displayed on boot after fresh installation? Please help
01-01-2011, 08:37 AM
Try leaving the CD in when the system auto reboots on a new install.
01-05-2011, 10:13 AM
Thank you for your response and my apology for the belated reply post. I tried letting the VortexBox1.7 installation CD in the drive and this time it booted to the New Installation Menu options.
Next, after a repeat Installation I shut down the PC and then during the cold boot entered the BIOS Setup and made sure my HDD [ Seagate ] ST 380011A is still displayed there as the IDE channel 0 Master ( no device in the IDE 0, Slave position] and my DVD RW drive [Lite-ON DVDRW-SH] as Master in IDE channel 1 (no device in IDE 1, Slave slot) and HDD Priority in the Phoenix-Award BIOS advanced Menu showing 1. Cho M .... ST380A11 and Changed the Boot sequence to HDD as #1 making CDROM as 2nd and USB FDD as 3rd and saved and rebooted.
This time the screen hung showing: Verifying DMI Pool Data....
I suspected corrupted MBR on that HDD and therefore without bothering to do any more troubleshoot on that disk , installed a new 80GB WDG HDD and installed VORTEXBOX 1.7 on that and this time it booted to the expected screen with the host name and IP number. Once successful , I changed the HDD to a 500GB Seagate which has worked flawlessly.
Conclusion of Boot failure after POST: damaged HDD possibly corrupt MBR. I will be running a low level format and see if the HDD can be used again.
01-05-2011, 08:07 PM
Glad you got things working. Hope the low-level format recovers the faulty drive.
Powered by vBulletin® Version 4.1.12 Copyright © 2013 vBulletin Solutions, Inc. All rights reserved.