Jump to content

Ad Nelson

Members
  • Content count

    25
  • Joined

  • Last visited

About Ad Nelson

  • Rank
    New Member
  1. Ad Nelson

    Lost MAC address

    e_d, are you using the mac# from the AGP slot? Let me know if you get something to work...it always bugged me that I had to give up. Ad
  2. Ad Nelson

    Lost MAC address

    Thought that I'd update this just in case some one finds it w/ a search. I gave up on that chip and installed one of my shiney elts_drac chips. Flashed to 6/19 using the awdflash that came zipped w/ it (v8.30) w/o the /f switch and it worked fine. The funny thing is that durring the flash it displayed a mac address of 7003F6F000E73900 which doesn't even resemble what is on my AGP slot. Maybe some day I'll put the fubar one back in and try flashing that address. Ad
  3. Ad Nelson

    Lost MAC address

    For some reason f6 (load failsafe defaults) doesn't do anything. F5 (restore previous) and f7 (optimised defaults) both work. And "enter mac address" in the Genie section gives me a blank with no cursor, hitting enter just locks up the bios. Ad
  4. Ad Nelson

    Lost MAC address

    Thanks for the link RGone. I've been reading a lot of threads like that lately. I'll check for the bold number, but my prob is like the last post in that thread except when I enter the address and hit the bios just freezes solid. Popcicle replied in the pcper forum that the new bios reads the address from the existing bios when you flash. That makes me wonder,tho, that if you hotflashed a bios on a different machine you would end up w/ the wrong address and it doesn't seem like I've ever heard anyone have that happen. Of course it IS your fault that I used the /f switch in the first place . It's funny, when I post about BIOS/CMOS and what is stored where and how, I don't get a lot of replies. I guess I'm not the only one scratching my head. Still striving, Ad
  5. elts_drac, 6/19 is promising to give me my first oportunity to use one of my trusty spares. Ad
  6. I flashed 6/19 w/ the /f switch and lost my MAC address. So far I've tried various versions of awdflash and various combinations of switches with both the 6/19 and 12/31. I've tried entering it in Genie bios and it just looks up. I've tried /nvmac:xxx /wb with both of the numbers on my AGP slot. I've got a bios savior so I have booted from a working 1/21 and then switch over and flash. I've got a couple of spare chips (thanks elts_drac) so I could just lay this one aside and install a working 12/31 and try flashing 6/19 again (w/o the /f). But I hate to give up, I'd like to learn what's going on here. Always striving towards compentence.:cool: Ad
  7. Ad Nelson

    NF2 - Poll - your 6/19 BIOS Results

    I used then earlier set of suggested switches, so I flashed w/ v8.24F and the /f switch. I lost my MAC address. Ad (p.s. if anyone can help me get it back, I'd sure like to hear in a different thread )
  8. gcs3, if you don't have cpuz, do a search and pick it up. It will tell you what bios is running. I know how you feel, I've got a bios savior and am forever forgetting which one is running. As for my computer: I guess 6/19 just isn't gonna work on my computer. When I tried to enter my MAC address in genie bios it locked up. When I used awdflash xx.bin /nvmac:xxx it didn't help...still no LAN. When I just enabled "Nvidia lan MAC address" in genie I got no post. So I'm giving up on 6/19. I tried different versions of awdflash & w/ or w/o the /f switch. No go, so now I'm gonna try flashing back to a former bios and hope that it will pick up the MAC address from this 6/19. If not...I bought 3 new chips from elts_drac and have no worries! AD
  9. RGone, yeah I read Popcicle's post, and you & he are probably right. But it's not speed. When I first noticed it I was only running 180x10. I'm not that interested in FSB, w/ 1/21 I usually run 205x12.5. With what I do (CAD) that's as fast as 240x10.5 w/ much lower volts & temps. No biggie, I was just trying 6/19 for the heck of it and will play around w/ it in my spare time. I'll post back if I think that I've learned anything of interest. Ad
  10. I flashed using RGone's procedure (awdflash 8.24F with the "/f" switch). Everything went fine but I lost my network. When I switched my bios savior back to 1/21 it was back. Right now I'm assuming that it's as DFI warned ...using the /f switch. I'll try some other flashing schemes. Ad
  11. Ad Nelson

    Slightest Hardware Change Kills System?

    Thanks Popcicle, real info for my little mind to ponder. Does this mean that the various modded BIOS' w/ all the added setting choices are actually exacerbating the problem? I long ago got in the habit of f10...a couple of beats...manually enter "y"...a couple of beats for luck and then enter. All these years I just thought I was just being superstitious. Ad
  12. Ad Nelson

    Slightest Hardware Change Kills System?

    So RGone, have you ever had a case of "bios corruption" where you could not clear the CMOS and replaced the BIOS chip w/ a fresh one and had it then post? I bought and flashed some of elts_drac's chips and wonder just how legitimate my sense of security really is. My bios savior has let me down a couple of times. Respectfully, Ad
  13. Ad Nelson

    Slightest Hardware Change Kills System?

    Discussions of whether this MB is great or not can be entertaining (if non-productive), but I'd like to get back to the subject of the original post...why the board will refuse to post after a simple hardware adjustment. I've had mine at "stock" speed of 166x11 (my 2500M seems to think that its stock speed is 133x6), changed the master/slave cables & configuration of my drives and had it fail to post. And fail to clear the CMOS...which is what really interests me. Has anyone ever had another MB that was difficult to clear? And need it so often? With every other MB that I've had, clearing the CMOS was a routine and trivial exercise. Move the jumper or take the battery out for more than a few seconds and you got the checksum msg. You then reentered the BIOS settings and were good to go. Even if you switched CPUs and forgot to clear the CMOS, all that happened was an error msg and you had to reenter your BIOS settings. Who ever heard of taking the battery out, moving the jumper and waiting overnight hoping that the CMOS will clear? Maybe I've got it all wrong, but my understanding is that the CMOS is a chip (eprom?) with a small amount of volatile memory which requires the juice from a battery to retain its data. Shorting the jumper OR removing the battery should cause it to lose this data and require the user to restore it before the computer will post. So what's different about this board? This is also the first board that I've owned that has CMOS Reloaded...where are those settings saved, because they are non-volatile. Can that be related to the fact that CMOS data itself seems to be so persistent? Does anyone have any information, opinions or even wild speculations which would set me more firmly on the path to understanding some of these issues? Respectfully, Ad
  14. Ad Nelson

    Slightest Hardware Change Kills System?

    Hey, bring it on! I've been told that I'm trainable. (tho I, too, am a bit of an "old dog") Ad
  15. Ad Nelson

    Slightest Hardware Change Kills System?

    RGone says,"Anybody know what DMI is? Anybody know what it is designed to do as a computer boots? Is it some sort of polling procedure during the boot up process? I have often wondered ..." --------------------------- Yes, this is the conversation that I'd like to see. The heart of the cold boot problem seems to me to have to do w/ the reading of the CMOS saved settings. If the initial voltages are too low to support the clock settings, then a "reset" working makes sense. But why only some times? Insert+reset also makes sense, but not always. And why does shorting the "clear RTC" jumper some times (often?) fail? I've never seen this on any other MB I've owned. And if cold boot (or the 4LOD) is due to failure to initialize the CMOS settings, then why would physically replacing the BIOS chip w/ a fresh one make any difference? And why, after a cold boot failure and several hours of babying, begging and bitching a successful boot reveals that the BIOS wasn't corrupted after all? OK, so I sound like a little kid..."why, daddy, huh? why?" I feel like this MB is trying to force me to learn something about computers and I'd like to comply. And I know of no better place to go. Ad
×