Gå til innhold

555

Medlemmer
 Vis profil  Se deres aktivitet

  • Innlegg

    1 024

  • Ble med

  • Besøkte siden sist

 Innholdstype 

Innlegg skrevet av 555

  1. Grafikkortguiden.Kjøpe nytt kort?Se her før du lager ny post

    i Skjermkort

    Skrevet

    Radeon 8500

    Radeon 8500 LE

    Radeon 9100

     

    Ser du har forandret en god del etterhvert som det kommer komentarer og det er fint ,men og si at 9100 er etter 8500 er vell og ta i litt. Det finnes også endel forskjellige kort og noen kjører på 250 (LE) og 275(normal) og 300. Kanskje verdt og nevne dette.

     

    Hvor har du dette fra?

    Jeg finner ingen 9100 kort som kjører mer en 250/250MHz.

  6. R9800 PRO og CS! Drivere!

    i Skjermkort

    Skrevet

    Det kan ikke være at du har flere komponenter på samme interrupt request (IRQ) da?

    Jeg har samme problem, kjøpte nettopp Herkules 3D Prophet 9800 pro men jeg dropper fortsatt i cs. Så tok jeg en titt på device manager og fant ut at grafikk kortet delte samme IRQ som lyd kortet, nettverks kortet og USB portene. Nå har ikke jeg så veldig peil men når jeg deaktiverte lydkortet og nettverkskortet løp jeg rundt i lan game med 100fps=) noe som ikke funka etter deaktiveringen. Feks lage et lan game med map de_aztec, gå ut på b1 og se ned i vannet. Her fikk jeg 50fps, helt til jeg deaktiverte=) Flax at mitt hk har alle pci portene og agp porten på samme IRQ.

     

    Jeg byttet hk og innstalert win på nytt for noen dager siden og har etter det hatt fps dropp som F.. (i CS) men når jeg så posten din sjekket jeg irq'ene mine og fant ut at net.kort, lydkort og skjermkort var på samme!(irq12)

    Etter jeg hadde lett etter en måte å skifte irq fant jeg i BIOS'en et sted jeg kunne reservere irq for ISA.

    Jeg reserverte irq12 og så fikk kortene nye og jeg 100FPS :D

  13. Maskin som låser seg tråd

    i Hovedkort

    Skrevet

    Har aldri hør om dette før men...

     

    Western Digitals hårddiskar fungerar ej tillfredställande med moderkort som har nForce2-chipset. Detta fel yttrar sig på Western-diskar med varierande firmware-version, det går därför ej entydigt att peka på specifika modeller. Det kan alltså fungera i vissa fall, men risken att det inte gör det är för stor för att vi skall kunna rekommendera denna kombination. Ovanstående gäller även moderkort med VIA KT133A och 686B chipsets

  20. Mulig og redde hovedkort med feilflashing av bios?

    i Hovedkort

    Skrevet

    I'm posting this because I think everyone needs to be a bit more aware

    that a so called "bad flash" does no necessarily mean a trashed BIOS

    chip or a hosed motherboard. I'm sure the more experienced computer

    builders are aware of this....so this post is aimed at the less

    computer savvy or the people that just plain didn't know.

    YES, flashing your BIOS is risky....it can go bad for any number of

    reasons.

    NO, you shouldn't flash unless the new version includes something that

    is truly needed.

    But if you just have to have the newest software,drivers,BIOS as soon

    as its released, and I'm included, then you need to know that there is

    a good chance that an "OHH SHIT" situation can turn into a "WHEWWW"

    AWARD BIOS' are "bootblock" BIOS'...basically what this means is that

    there is a portion of the BIOS that is reserved and unwritten to (most

    of the time) that allows rudamentary hardware accessability(eg.floppy,

    ISA, Keyboard) in the event that the BIOS becomes corrupted in some

    way as to prevent the system from POSTing normally.

    First off, if you think the flash went bad, try clearing the CMOS. I

    know this sounds generic, but it is sometimes all that is needed as

    the flash may have wreaked havoc upon the settings as to not allow the

    system to POST...and not actually corrupted the BIOS itself.

    Sometimes, if your lucky, holdind down the INSERT key while powering

    up the system will get it to POST normally as it resets certain

    settings to default. I actually saw someone mention this in a

    thread...good job...not alot of people are aware of this ability to

    "force" the system to POST. If these fail, your looking at a true "bad

    flash" scenario.

    As I said before, the "bootblock" allows access to to floppy, ISA, and

    keyboard input. If your lucky enough to have a board with an ISA slot

    (doubtful) and an old ISA vid card laying around, the recovery process

    is easy, as you will be able to see what your doing on the screen. I

    don't think any of SOYO's current boards have an ISA slot so it is

    more of a challenge as everything has to be automated and done blind.

    Let me say this. If you get ANY beep codes at startup and the floppy

    light comes on and appears to initialize, your chances of recovering

    are VERY high, regardless of whether or not the system appears to do

    anything else. If you don't have a floppy...well...send the BIOS chip

    off to get reprogrammed, or buy a new one...because there is nothing

    you can do.

    OBVIOUSLY YOU NEED ACCESS TO ANOTHER COMPUTER FOR THESE NEXT STEPS

    BECAUSE YOURS IS OUT TO LUNCH RIGHT NOW

    1.) You need to make a bootable floppy. The best way to do this is to

    go to www.bootdisk.com and download DrDOS...but you want the one "for

    flashing" as it has no drivers or any unesessary files with it. It's

    just "pure" DOS. Just click on the downloaded file and it will prompt

    you to place a floppy in the drive and will create the boot floppy for

    you.

    2.) Place "awdflash.exe" and whatever BIOS your flashing (ex.

    123abc.bin) on the bootable floppy you created.

    3.) Now you need to create an autoexec.bat file. This is what

    automates the entire process since it's being done "blind". To do

    this, all you need is a text editor, notepad being the easiest. Just

    open notepad and type "awdflash 123abc.bin /py /sn /Sb /cd /cp /cc /R"

    without the quotes. Make sure you fill in the "123abc.bin" with the

    correct filename...this is just an example. It should look like this:

    awdflash 123abc.bin /py /sn /Sb /cd /cp /cc /R

    Make sure there is a space between awdflash and you BIOS file and

    after your BIOS file and between all switches. Now save what you

    created here in notepad on your floppy as autoexec.bat

    Basically what this does is it automatically loads awdflash, inserts

    the BIOS file, and....

    /py - program yes

    /sn - save no

    /Sb - skips rewriting the bootblock

    /cd /cp /cc - resets all configuration data and clears CMOS

    /R - restarts the system when complete

    4.) Once you have this floppy complete it's time to put it in the

    drive, power the system up, and cross your fingers. Just keep your

    eyes on the floppy and HDD light and keep an ear out. It only takes a

    minutes or so to complete so you have to be ready to remove the floppy

    when the system restarts (you should be able to tell when all

    lights and activity stop, pause for a few moments and then restarts).

    At this point, if all went well, your system should POST. You can now

    go into your setup, make your needed changes, and bingo...your back in

    business.

    WELL...thats pretty much it. I hope this helps some people. This isn't

    100% quaranteed to work. Some "bad flashes" just can't be recovered

    from, but it has worked for me in the past.

    Good Luck,

    Cappy

    JUST A FEW NOTES:

    NO...I don't work for SOYO, but I figured this info might save some

    people some headaches....and money. I think this info might be on

    their site, with less detail and minus some of "awdflash's" switches

    that really should be included.

    Also, even if you don't have to use this proceedure, If your going to

    flash your BIOS, it's good to make this floppy anyway...just in case.

    And finally, this is only for AWARD BIOS'. AMI BIOS' use a different

    recovery proceedure.....It's WAY easier.

×
×
  • Opprett ny...