This one simple example shows you the difference between using
a base frame and not using one. This is why you can't really rebuild
the quake models from the data you have (you don't have the base frame).
Read the .med files to see what is being done.

Instructions: 
Move example1.med to you MedDLe directory. Type
'mdl example1.med'. 2 models will be generated and the base
skin extracted. In the first model 'mod1.mdl' the first frame was used as
a base. Look at the skin. In the other 'mod2.mdl' a base frame was used.
You can see how much better that one is. Just change you progspath in the
MedDLe config file to view these models. If you want, try to modify the 2 skins
and see if you can make the first one useful. (ha, yea right).
LESSON: Use a base frame which makes a good skin! That is all a base frame
is used for. You overwrite it after you generate the new model. ( and NO
you can not get the base frame from the quake mdl files... it aint there.)  

The second example is used the same way. After running the first example,
run example2.med and it will stick a texture on the mod2.mdl and rename
the frame. This shows how MedDLe will try to match any 8-bit color palette. 
Not a very usefull example... but now you have a complete (mostly) model. Just 
write a quake c prog for it!

Added note:
 I added 2 commands : get_2dmap <file> and 2dmap <file>
 get_2dmap makes a txt file for the skin mapping points
 2dmap applies that txt file (skin mapping) to a model.
 Since you don't have id's base frames (or whoevers) you can
 use this to rebuild the model with basically the same info the
 base would give you.