I was wondering if someone can post some FASM code to show a BMP image in dos.. and if possible make it bootable from a disk...thanks!

Here is some asm code for dos BMP, it is not as easy as you think, 24 bit is easier then 8 bit , but then you have the size to think about. 24bit needs pmode and vesa, and then you need to load it, you can not use bios from pmode for floppy loading, very easierly, there are ways, but the code will not be small, or simple .

I would code you a demo, but i am busy with v3os, you should have a go and post back if you need help.
\\\\||////
(@@)
ASHLEY4.

Batteries not included, Some assembly required.

I tried compiling it using FASM and it didnt work. Is it using FASM or Tasm? if its Tasm, where would i go to get an actual working version of it, I tried Tasm before, to compile a few of your other examples, and Tasm wouldnt even start..i dont know whats wrong...anyway, thaks for the help.

Its most likely masm, it will need converting for fasm, maybe someone else has a dos bmp display code, with fasm code ?.

\\\\||////
(@@)
ASHLEY4.

Batteries not included, Some assembly required.

This is very simple 320x200x256 BMP viewer for bootsector

Nice code ATV, you should of entered it, in the 512b compo .

\\\\||////
(@@)
ASHLEY4.

Batteries not included, Some assembly required.

ASHLEY4, it's not really OS, but there is some extra lines that can load real kernel. Maybe BootBMP should load DebugOS?

But the compo was started, so we would get nippits of of code, to help people with OS dev.
And since the linux penguin, a lot of beginners like a boot up image, and your was a good example.
Now if you could of put the two (DebugOS that is) together you would of been onto a winner!.

\\\\||////
(@@)
ASHLEY4.

Batteries not included, Some assembly required.

since that uses a floppy loading, to make it show that image in 32bit mode, what all would you have to do?

That demo is run in realmode 16bit, it loads a 64k bmp, but you wanted higher-res and thats a bmp file of about 900k , not only will it take a long time to load, but you would need to use unreal mode, or make a pmode floppy driver.

which one would be better, and faster? using real mode or a floppy driver?

Its unrealmode and they are the same speed as they both use the floppy , but unrealmode you can use int 13h for floppy, but in pmode you need to make a pmode floppy driver or set up v86.

Read up on unrealmode its a sort of cross between real and pmode.
Heres a start: http://www.mega-tokyo.com/osfaq2/index.php/UnrealMode

Little update, I have looked my old files and found pcxloader written few months back, but I have forget to send it (my near memory is very bad, because lack of vitamin B1/B12)

New bootloader can display pcx file and load over 64k kernel, but only in FAT12 and 320*200*256 pcx picture :-(no room for more code)
Also updated bootbmp for bmp pictures included

How can you fit a 640x480x16 bitmap (Mode 0x13)?

If you mean when the image is NOT exactly 640x480, then you should divide your original width,height with that 640,480 and pick the BIGGER constant. Then you can plot individual pixels from the source picture "constant" amount apart. The same you would act on the height. This means that when the picture is not of the same aspect - you will have some screen blank.

The other way is to have separate constants on the H,W parts so the image fits perfectly, but it might be stretched either way.

Adam, biggest problem is to show picture, because it can be 1bit*4color_planes or 4bits*1color_plane.
That depend what program saves that pcx picture.
Main unpacking is same, but if there is 4 color planes (640/8=80 bytes*4planes).
You need combine color planes. Something like:
screen[0]=(buf[0] and 1)*8+(buf[80] and 1)*4+(buf[160] and 1)*2+(buf[240] and 1)
Or you can use screen mode 12h (640*480*16) and write it in right color plane (it's not so easy as it sounds).
If picture is 4 bit in 1 plane, it need to handle high/low nibble.
And if that is not too complex already, some programs use packing over color planes.
So it's more easy to use some graphic tools to convert picture 640*480*16 -> 320*200*256

If you are looking for challenge try unpacking GIF

I've tryed PNG, but the packing lacks documentation I need some clearer documentation than the RFCs laconic one.

And if looking for a bigger challenge, try JPEG .

All image formats should be nonone OS dependent, other than than the load of file and memory aloting, so should only need writing once in asm (any offers )
PS: There a pnglib here:
http://www.madwizard.org/view.php?page=downloads
coded with masm.
PPS: I think he just wants to display a 640x480 16 image at bootup, but put the wrong mode.

Don't worry about packing! Any 640x480x16 BMP will fit on a 1.2MB floppy disk with a little over 1MB left!

Why bother with packing and unpacking image files, when you can leave the image in Raw or BMP format?

Remember to KISS (Keep It Simple, Stupid)

The problem here is that the image is exactly 640x480. It is a 16-color BMP.
I can convert it to a variety of other file formats, but I like to work on the KISS (Keep It Simple, Stupid) principal.
Unpacking code wastes a bit of time.
Besides, the BMP only takes up 150KB