• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

A7V, Bios Update & Problem with ATA-100

K

KurtD

Member
I had been running with 1004 and decided to flash 1005. The flash went fine, I reset the bios and then changed settings as I had under 1004. The computer posts but won't boot (can't find the boot disk which is attached to the Promise controller). I was using the Promise controller under 1004 without problem and get the same sort of behavior as if the drivers were not loaded in windows correctly. I know I can disconnect the cable from the Promise controller and move it to the ATA-66 slot, but why is it doing this? Also, when using the Promise controller the Bios detects a boot virus (did this under 1004 as well). I know there isn't anything there (Norton does not detect anything), so why is that happening - I simply disabled boot virus detection in Bios (and it ran fine under 1004).

Do I need to go through the routine of switching the cables, loading the Promise drivers, etc.?

Any suggestions or explanations?
 
I had 100% of all the problems KurtD has had. Boot virus dected as well. I was like WTF???

THis A7V sucks........

I have BIOS 1005C and im in busness again 😉 befor that I was at the retail BIOS 1.0 I think

I dunno if that is helped but..


 
Question:
When I disable boot virus detection in the A7V/A7V133 BIOS, I cannot boot into the HDD connected to the Promise® ATA100 controller. It shows an error message, "DISK BOOT FAILURE, INSERT SYSTEM DISK AND PRESS ENTER".

Answer:
It was found to be a problem of Promise® BIOS build 31 and build 33. Promise® BIOS build 35 combined in A7V BIOS rev. 1005D and A7V133 BIOS rev. 1002A has fixed this problem.


dam this was not on the site 2 days AGO!!!!!!!!!!!!!!!!
 
update: Clearing the CMOS solved the boot problem with ATA100. Thanks hclarkjr.

However 1005C was very unstable on my system. When I set the system from optimal to normal it would revert back to optimal (as if it would not save this setting). Also, the CPU voltage was set to auto and was being reported by Probe around 1.79. I was having all kinds of windows problems and just said the heck with it and re-flashed back to 1004C. Maybe one day when I have some extra time and a few Buds in the 'fridge..... Just don't have the patience right now.:disgust:
 
i have had 2 a7vs, and now and a7v133, and never exprienced this. now i am using full raid on the a7v133,and not a glitch.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top