UNSOLVED

phoenix00

updated

22 years ago

Closed

P

phoenix00

20 Posts

0

6516

February 2nd, 2005 09:00

I600m IDE driver problems -- BIOS A16 may be culprit

Hi everyone! This post may appear to be in the wrong place for this, but please read on and hear me out:

I just updated my dad's 600m BIOS to A16, and a funny thing happened with WinXP: it suddenly had to redetect the primary and secondary IDE channels, then the Add New Hardware Wizard pops up a window saying the "Drivers are not suitable for this platform". The "IDE Channel" entries inside Device Manager also remain yellow-banged.

This cycle repeats every time the comp WinXP is rebooted.

I've also tried reinstalling the IDE drivers, both using the Intel Chipset install util and directly thru Device Manager -- no go.

Therefore I'm reasonably assured that the new BIOS is the culprit. My previous BIOS was A14 and that worked great -- does anyone still have their hands on that?

Thx lots everyone, and since it's Chinese New Year next week, Gung Hay Fat Choy!!
  • mich43L

    108 Posts

    422

    0

    Posted February 2nd, 2005 14:00



    @billw020104 wrote:

    Can you roll it back to A14? Remember with BIOS, "If it ain't broke..."

    BillInspiron

    600m
    Inspiron 8200
    Inspiron 8100






    There is the second battery fix in A16 althogh I haven't tried if it indeed works. When I flashed my system to a16 from a14, xp had to install some things. I let it do it's thing and everything is fine now. Try reinstallinig the intel mobile chipset drivers.
  • billw020104

    152 Posts

    422

    0

    Posted February 2nd, 2005 14:00

    Can you roll it back to A14? Remember with BIOS, "If it ain't broke..."

    BillInspiron

    600m
    Inspiron 8200
    Inspiron 8100

  • phoenix00

    20 Posts

    422

    0

    Posted February 3rd, 2005 07:00


    phoenix00 wrote:
    I've also tried reinstalling the IDE drivers, both using the Intel Chipset install util and directly thru Device Manager -- no go.

    My previous BIOS was A14 and that worked great -- does anyone still have their hands on that?



    I was asking b/c I cannot find A14 anywhere -- neither on Dell's website nor on Google

    Message Edited by phoenix00 on 02-03-2005 01:56 AM

  • mich43L

    108 Posts

    422

    0

    Posted February 3rd, 2005 13:00

    You can get A13 here: ftp://ftp.us.dell.com/bios/600m_A13.EXE

    Tech support might have A14.
  • phoenix00

    20 Posts

    422

    0

    Posted February 7th, 2005 23:00



    @mich43L wrote:
    You can get A13 here: ftp://ftp.us.dell.com/bios/600m_A13.EXE

    Tech support might have A14.



    no they do not have A14...... they did suggest removing & redetecting the IDE controllers in Safe Mode -- no go.

    I tried rolling back to A13 -- that works.

    sigh........ every previous BIOS has been rock-solid up to this point (for both the 600m and my 8600). Hope this isn't part of a trend.....
  • johnallg

    2 Intern

    •

    7280 Posts

    422

    0

    Posted February 8th, 2005 02:00



    @phoenix00 wrote:

    Hope this isn't part of a trend.....

    I don't know who is writing BIOS for Dell, or how much they are paid, but it is way too much for the quality of output....
  • mich43L

    108 Posts

    422

    0

    Posted February 8th, 2005 11:00

    This might not be an elegant solution but how about turning back your system using System Restore to before you installed a16?
  • johnallg

    2 Intern

    •

    7280 Posts

    428

    0

    Posted February 9th, 2005 02:00

    Wouldn't do a thing - the BIOS is independant of the OS.  The BIOS is board level code to help the cpu wake up and find the hardware.
  • phoenix00

    20 Posts

    428

    0

    Posted February 9th, 2005 08:00

    johnallg is right -- System Restore wouldn't do a thing. This is a BIOS problem, not a Windows or software problem.

    I've disabled System Restore anyways. Rather reinstall Windows than deal with that evil.
  • mich43L

    108 Posts

    366

    0

    Posted February 9th, 2005 13:00


    phoenix00 wrote:
    johnallg is right -- System Restore wouldn't do a thing. This is a BIOS problem, not a Windows or software problem.




    I misunderstood, I thought you flashed back to a13 and still was getting the error.

    In any case, with a16, I don't see how can you completely rule out windows as the problem. I repeat again, I flashed mine from a14 to a16 and windows had to redetect something (don't remember exactly what) but it finished successfuly. Did you try giving windows the latest chipset drivers?

    Message Edited by mich43L on 02-09-2005 09:46 AM