vinylkid Posted June 22, 2004 Posted June 22, 2004 "Bios details To solve the occasionally auto reboot issue. To solve the cold-boot bug after removing and re-plugging power cord. To solve the Bug of S3 Resuming. To also Support "Boot Menu" feature. To also include the micro codes of mobile CPUs. To improve the BIOS writing-back process to minimize the possibility in getting BIOS crashed." Ok, one small request for the DFI people. When a beta BIOS like the 6/19 beta is released can we get more details then just 1 line of description per problem? I mean if we are supposed to be helping test the BIOSes we should really know what we are trying to fix. At the very least it might help reduce the number of people flashing the beta for the wrong reasons. Case in point: I think I may suffer from the "auto reboot issue" but how do I know? What are the symptoms? I KNOW I suffer from not being able to resume from S3. Does this BIOS solve my problem? Is it the same problem? Heck, I don't even know what the "Boot Menu" is, and I've owned my motherboard for months now. Is this asking for too much? Quote Share this post Link to post Share on other sites More sharing options...
Angry_Games Posted June 22, 2004 Posted June 22, 2004 auto-reboot = when the comp reboots out of the blue at a random time To solve the Bug of S3 Resuming = fixed S3 resume To also Support "Boot Menu" feature = allowing choice of boot devices (same as any mobo that has this) i dont mean to sound trite, but this is actually normal on any bios release, and its pretty explanatory on what hte BIOS covers. I can read those simple lines and know what they mean as can most others im pretty sure. Quote Share this post Link to post Share on other sites More sharing options...
Sachs Posted June 22, 2004 Posted June 22, 2004 Originally posted by Angry_Games auto-reboot = when the comp reboots out of the blue at a random time To solve the Bug of S3 Resuming = fixed S3 resume What bug? what is S3 ? Quote Share this post Link to post Share on other sites More sharing options...
Angry_Games Posted June 22, 2004 Posted June 22, 2004 S0 - Working State In this state, your PC is awake and working S1- CPU Stopped In this state, your PC is technically in standby and this is the default standby state if S3 is not supported. Power consumption is Five Watts to Thirty Watts of Power. S3 - Suspend to RAM (context saved to RAM) In this state, your PC in standby and all fans, hard drivers and other devices are powered down into a sleep state. Power consumption is less than Five Watts. S4 - Suspend to Disk(Context saved to HDD) Otherwise known as Hibernate, your PC has saved the contents of RAM to the hard disk and is pretty much tuned off. Power consumption is less than Five Watts. This isn’t very useful for desktop PCees and is mostly used in Laptops where battery drainage is far better than if you are in S3. Now, as I mentioned there are some requirements before you can use S3. Motherboard must support S3 S3 support must be enabled in the BIOS (many motherboards do not do this and default to S1) OS must support S3 (Windows XP does) To wake your PC from S3 your USB peripherals (like keyboard and mouse) must be enabled to arm your PC to wake. From the device manager, you must select they keyboard, go to properties and select Allow this device to bring this computer out of standby. http://www.phoenix.com/resources/acpi-bios.pdf Quote Share this post Link to post Share on other sites More sharing options...
vinylkid Posted June 22, 2004 Posted June 22, 2004 Well to be honest, this is not about being able to read lines and deciphering what they mean. One can guess what is being fixed. However the steps to reproducibility of any given problem are not. You know what the first rule about QA and bug-fixing is? Knowing the steps and conditions on how to reproduce the problem/bug. Are these beta BIOSes there to solve the problems or to allow users to help DFI *verify* that they solve the problems? There's a difference. You can continue to throw beta BIOSes against the wall and guess as to what sticks, or you can manage the process and let us (the users) help you by giving you accurate results. You can be just like any other motherboard company, or you can go that extra step to possibly improve the process. Your call, guys. (BTW, second rule of QA is: Never underestimate the stupidity of the user ) Quote Share this post Link to post Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.