- Joined
- Oct 24, 2005
I have an Asus A8V Deluxe which I recently upgraded the bios on from 1008 to the latest 1017. Normalyy I don't run a floppy drive but had attached one prior to flashing so as to save the original bios and have a diskette in case I needed to flash back.
I used the Asus Update program and it worked just fine. I was able to use the floppy directly after flashing and then I went ahead and removed the floppy as it was just hanging out the side and I don't have a spare external slot for it.
Well, while this bios recognises my chip properly and addressed a voltage issue I was having, I'm just not able to hit the overclocks I was getting prior to the update and I'd like to flash back to an earlier version. The problem is that now the floppy can't seem to properly detect the diskette media. I have tried a couple of cables and a couple of floppy drives and a load of disks and I'm at a loss as to what could be causing this.
The bios lists the legacy diskette as 1.44 and I don't see any other setting that might affect this. Windows reports that all is well. I've never seen anything like this. And of course a web search confirms my suspicion that I am the only one to ever report this sort of problem.
Hopefully someone here can shed a sliver of light on the situation. I don't want to have to create a bootable CD, etc.
I used the Asus Update program and it worked just fine. I was able to use the floppy directly after flashing and then I went ahead and removed the floppy as it was just hanging out the side and I don't have a spare external slot for it.
Well, while this bios recognises my chip properly and addressed a voltage issue I was having, I'm just not able to hit the overclocks I was getting prior to the update and I'd like to flash back to an earlier version. The problem is that now the floppy can't seem to properly detect the diskette media. I have tried a couple of cables and a couple of floppy drives and a load of disks and I'm at a loss as to what could be causing this.
The bios lists the legacy diskette as 1.44 and I don't see any other setting that might affect this. Windows reports that all is well. I've never seen anything like this. And of course a web search confirms my suspicion that I am the only one to ever report this sort of problem.
Hopefully someone here can shed a sliver of light on the situation. I don't want to have to create a bootable CD, etc.