Hmmm... All may well be lost, but just maybe not. Dissection of 382v152m.exe which is the 1.52 S3 BIOS file for the MSI 6382 from Medion shows the Award flasher, so your mobo must have an Award bios. For 2 beeps try reseating the memory before anything else.
Your PC SHOULD have a boot-block BIOS which means that there is a small section that isn't normally overwritten and which supports a floppy ONLY (If you have a PCI video card you won't see anything on the screen because the boot-block BIOS only supports an ISA videocard), so this means that you may be running blind, but never mind, you can get round that. But check your mobo documentation to see if there is a BootBlock Protection jumper (usually not).
Make a bootable floppy and check that it boots properly on another PC. Then unpack 382v152m.exe onto the floppy - you should see 4 files, an AUTOEXEC.BAT, AWFL789.EXE, LIESMICH[readme].TXT AND W6382VM7.MED
Their autoexec.bat is:
@echo off
cls
echo. start flashing BIOS ?
pause
awfl789 W6382vm7.med /Py /Sn /Cd /Cp /Cc /E /R
strip it down to the last line only, i.e.
awfl789 W6382vm7.med /Py /Sn /Cd /Cp /Cc /E /R
Insert and boot from cold, pray the bootblock catches the floppy (you have Scandisk'ed it carefully on Surface Scan haven't you?). Pray very hard.
Read
http://www.wimsbios.com/HTML1/faq.html and see
http://www.plasma-online.de/index.ht...ios_flash.html to see what AWDFLASH command line arguments are to get more tips. Since your old BIOS has been saved you may be able to restore it (renaming as you did may not work), substitute whatever name it was given for W6382vm7.med in the above autoexec.
For AMI and Award BIOSes you MAY be able to clear a corrupt BIOS by creating a bootable floppy as before, copying DEBUG.EXE to it and executing the following script from the DOS prompt if you have one.
A
DEBUG
-O 70 17
-O 71 17
Q
or, if you're "blind" as you seem to be, copy the following lines to a text file (use the DOS Editor if you can, rather than Notepad)
-O 70 17
-O 71 17
Q
and name the file debug.scr (doesn't matter what you name it so long as you have an autoexec.bat that calls it, to whit:
debug < debug.scr > debug.out
That SHOULD wipe your BIOS and you can start afresh as above (debug.out is just a text file that contains everything that DEBUG would have displayed on your screen).
Once the BIOS is up, you'll probably have to tinker with all the settings to get your kit to work, try "set to BIOS defaults", reboot and work from there.
Good luck and let us know.