Anti-Spam Bios PC-Professionalist wanted !BIOS Beep tonesBIOS Boot-CD IBIOS Boot-CD IIBIOS Boot-DisketteBIOS Boot-LogoBIOS Boot-USB-StickBIOS EPA-LogosBIOS IDBIOS PasswordsBIOS SoftwareBIOS Update instructionBIOS-Chips SaleMainboard manufacturer Captchas Lifelong! Links Online-Tools Programs SecurityAbout flazh Poll
Feedback
21.07.2010
Nicered wrote:
Ein ganz tolles Tool für Webdesigner und Webmaster. Erspart viel Arbeit. Vielen Dank...
more...
©1996-2010
Michael Rosenbaum Ratzeburg - Germany
Advert
Most wanted
Atomic Clock Bios BIOS Beep tones BIOS Boot CD I BIOS Boot CD II BIOS Boot Diskette BIOS Boot Logo BIOS Boot USB Stick BIOS EPA Logos BIOS ID BIOS Passwords BIOS Software BIOS Update instruction Blog Bios Boot Logo Feedback PC Professionalist wanted ! Mainboard manufacturer Programs Security
Domains
Domains for sale!
Short and catchy domains are very rare.
2cent.eu
9b9.de
pik7.net
wixxer.org
0xygen.de
0xygen.net
crocodil.net
rapidlinks.de
rapidlinks.net
rapidlinks.eu
Show available domains...
BIOS-Bootlogos
A short instruction, how to create EPA BIOS-Boot-Logos and Fullscreen BIOS-Boot-Logos under Bios-versions from AMI, AWARD and PHOENIX, with Bios-Tools like: AMIbcp, AMIFlash, AWDFlash, WinFlash, WinPhlash, CBROM, and my Freewaretool BMPtoEPA.
Extract Boot-Logo out of BIOS Update file
Insert Boot-Logo into BIOS Update file
Boot-Logo collection
Edit Boot-Logo (EPA-Format) with BMPtoEPA
Create Boot-Logo with Paint Shop Pro
Boot-Logo Software (CBROM, Flash tools)
Write BIOS Update file onto BIOS-Chip
Extract Boot-Logo out of BIOS Update file
Bios-Tool: CBROM v2.15
CBROM, a small software from AWARD (PHOENIX), has functions to read, edit and insert each segments inside a Bios Update file. CBROM works under DOS and the Windows command line. To show all parameters, go to the command line (DOS-Prompt) and insert: "cbrom215.exe".
First of all we need a Bios Update file to edit the current logo, and the parameter /D to show all ROM segments. In our example we use the BIOS Update file "N24LD505.BIN" from the DFI mainboard "LanParty NFII Ultra B". The input of "cbrom215.exe n24ld505.bin /D" shows:
The picture above shows the small EPA-Logo (EPALogo.bmp) on Pos.10, and the Fullscreen logo (LanParty.bmp) on Pos.11, and also the original and compressed size in kilobytes.
EPA-Logo extraction:
Extract the small EPA-Logo with "cbrom215.exe n24ld505.bin /epa extract".
Fullscreen-Logo extraction:
Extract the Fullscreen with "cbrom215.exe n24ld505.bin /logo extract".
Insert Boot-Logo into BIOS Update file
Bios-Tool: CBROM v2.15
Now we use CBROM to insert our self created (normal) Bitmaps. Because CBROM is able to translate normal BMPs into the special AWBM format. All we have to do is to create (see below) a Bitmap file in a specified size and format.
EPA-Logo insertion:
"cbrom215.exe n24ld505.bin /epa filename.bmp"
Fullscreen-Logo insertion:
"cbrom215.exe n24ld505.bin /logo filename.bmp"
If you get an error message like "not enough space!", you have to edit your Bitmap a second time with a graphics program either to reduce the Bitmap size, or to use less colors as a result to get a better data compression.
A collection of various EPA-Logos: bios-epa-logos.htm.
Edit Boot-Logo (EPA-Format) with BMPtoEPA
BMPtoEPA - download and howto
Create Boot-Logo with Paint Shop Pro
Now we create/edit a Bios-Boot-Logo. In this example i use the graphics program PaintShopPro from Corel, but you can use your favorite program as well.
The different formats for Fullscreen and EPA-Boot-Logos:
| Color depth | Res. (width x height) | Size (KB) |
| Fullscreen-Boot-Logos: | ||
| 16 colors | 640 x 400 pixel | 117 |
| 640 x 480 | 140 | |
| 800 x 600 | 234 | |
| 256 colors | 640 x 400 pixel | 251 |
| 640 x 480 | 301 | |
| 800 x 600 | 469 | |
| EPA-Boot-Logos: | ||
| 2 colors | 136 x 84 pixel | 1,7 |
| 136 x 126 | 2,5 | |
| 16 colors | 136 x 84 pixel | 5,7 |
| 136 x 126 | 8,5 | |
Start PaintShopPro, create a new file and choose one of the above formats with the right resolution and color depth.
During your first tries: use black as background and white as foreground color. After you have created your logo, save the Bitmap file (BMP) without RLE-Compression.
Fullscreen-Logo: start CBROM to insert the Bitmap into your Bios-Update file.
EPA-Logo: start the Windows tool BMPtoEPA, convert the Bitmap into the EPA-format, save it and use CBROM to insert the Bitmap into your Bios-Update file.
Finally write the Bios-Update file onto the Bios-Chip.
Boot-Logo Software (CBROM, Flash tools)
CBROM Download: www.award.com or Google
Version info:
CBROM-Version: 1.x for Award v4.x (old)
CBROM-Version: 2.x für Award v4.51+v4.6x (old)
CBROM-Version: 6.x für Award v6.x (new)
Use the flash tool from your mainboard manufacturer to program your Bios-Chip!
Write BIOS Update file onto BIOS-Chip
Please read my Bios-Update-Instruction or use the instructions from your mainboard manufacturer.
i am so glad to find this a great site thanks for all informations
ladjeroud 29.Apr.2010 01:55
Hi, yes, that's possible. But what'll happen when the user installs a new bios update? Your app will not work. It should be better to do it in the same manner like e.g. Microsoft XP: your app-installer checks the current hardware and generates a special ID. Maybe something like the following byte sequences:"37-60-01-98-12-78-43-55" where "37" => Mainboard:ASUS M2N-E, "6001" => sum of the digits of MAC-Address, "98" => AMD CPU xxx, and so on. Then let the user send this ID to you and you generate a special serial for this ID/user. At least: your app checks on every startup the hardware and your serial, and when more than 1-2 hardware components are changed, then let the app stop and inform the user to re-activate the app.
flazh 29.Mar.2009 07:27
Hi, your instruction is good. I would like to consult how to embed some codes into the BIOS to protect developers from software piracy? eg, can we write a simple OEM.bin file with our serial no such that our application software will check on this codes in OEM.bin If someone were to copy my application and use in other hardware, it will give an error message for hardware incompatibility.
E K Goh 29.Mar.2009 04:41