one aspect of the present invention is to implement a media boot loader which expedites the boot process by eliminating the need to have a master boot record ( mbr ) for bootable partitioned media , or in the case of bootable non - partitioned media , eliminates the need for a boot sector . in one embodiment , boot loader code is stored in bios rather than on the boot media itself . the boot media may be preloaded with information that identifies its file system type ( e . g ., fat12 , fat16 , fat32 , etc .). based on this information , the bios code may cause a corresponding processor to load and execute the corresponding boot loader code . in one embodiment , this boot loader code is loaded and executed from bios . in another embodiment , control is passed to the bios boot loader code which , in turn , may cause the processor to load a kernel loader that is present on the boot media . this kernel loader may then load an operating system ( os ) into memory . in one embodiment , execution control is passed to the operating system upon initialization . another aspect of the present invention is to use the aforementioned kernel loader to load the os into memory from the boot media itself . in one embodiment , this os is a lightweight os that may also be used to subsequently load one or more application programs from the boot media . yet another aspect of the present invention is to pre - format the boot media with a file allocation table ( fat ) file system , thereby enabling the boot media to be usable for non - boot related data storage . in this fashion , the boot media may be used to store data in the same manner as traditional storage media , as well as provide the functionality of a bootable media . the present invention will now be described with reference to fig1 - 5 . fig1 is a schematic block diagram of an exemplary electronic device 100 , for example , a tablet pc or other suitable device that is configured to implement one or more aspects of the present invention . although described with reference to a tablet pc , the electronic device 100 may include , but is not limited to , general purpose computer systems ( e . g ., server , laptop , desktop , palmtop , personal electronic devices , etc . ), personal computers ( pcs ), hard copy equipment ( e . g ., printer , plotter , fax machine , etc ), or any suitable circuitry capable of processing data and combinations thereof . the electronic device 100 includes a processor 104 , for example , a central processing unit ( cpu ). the cpu 104 may include an arithmetic logic unit ( alu ) for performing computations , a collection of registers for temporary storage of data and instructions , and a control unit for controlling operation for the electronic device 100 . in one embodiment , the cpu 104 includes any one of the x86 , pentium ™, pentium ii ™, and pentium pro ™, pentium celeron ™ pentium iii ™, pentium 4 ™, and centrino ™ microprocessors as marketed by intel ™ corporation , the k - 6 microprocessor as marketed by amd ™, or the 6x86mx microprocessor as marketed by cyrix ™ corp . further examples include the alpha ™ processor as marketed by digital equipment corporation ™, the 680x0 processor as marketed by motorola ™, or the power pc ™ processor as marketed by ibm ™. in addition , any of a variety of other processors , including those from sun microsystems , mips , ibm , motorola , nec , cyrix , amd , nexgen and others may be used for implementing cpu 104 . the cpu 104 is not limited to microprocessors but may take on other forms such as microcontrollers , digital signal processors , reduced instruction set computers ( risc ), application specific integrated circuits , state machines and the like . although shown with one cpu 104 , the electronic device 100 may alternatively include multiple processing units . the cpu 104 is coupled to a bus controller 112 by way of a cpu bus 108 . bus controller 112 provides an interface between the cpu 104 and memory 124 via memory bus 120 . moreover , bus controller 112 provides an interface between memory 124 , cpu 104 and other devices coupled to system bus 128 . it should be appreciated that memory 124 may be system memory , such as synchronous dynamic random access memory ( sdram ) or may be another form of volatile memory . it should further be appreciated that memory 124 may include non - volatile memory , such as rom or flash memory for maintaining bios code , for example , that includes the boot code for implementing the present invention . system bus 128 may be a peripheral component interconnect ( pci ) bus , industry standard architecture ( isa ) bus , etc . coupled to the system bus 128 are a video controller 132 , a mass storage device 152 , a communication interface device 156 , and one or more input / output ( i / o ) devices 168 1 - 168 n . the video controller 132 controls the processing and other manipulation of data 133 that is presented for display on a display screen 148 , for example , a flat panel display , a crt or any other suitable display device or combination thereof . in another embodiment , the video controller 132 is coupled to the cpu 104 through an advanced graphics port ( agp ) bus . the mass storage device 152 may include , but is not limited to , a hard disc , floppy disc , cd - rom , dvd - rom , tape , high density floppy , high capacity removable media , low capacity removable media , solid state memory device , or any other suitable volatile or non - volatile memory device and combinations thereof . the communication interface device 156 includes a network card , a modem interface , etc . for accessing network 164 via communications link 160 . the i / o devices 168 1 - 168 n may include a keyboard , mouse , audio / sound card , printer , and the like . the i / o devices 168 1 - 168 n may be disk drive , such as a compact disk drive , a digital disk drive , a tape drive , a zip drive , a jazz drive , a digital versatile disk ( dvd ) drive , a magneto - optical disk drive , a high density floppy drive , a high capacity removable media drive , a low capacity media device , and / or any combination thereof . in accordance with the practices of persons skilled in the art of computer programming , the present invention is described below with reference to symbolic representations of operations that are performed by the electronic device 100 , unless indicated otherwise . such operations are sometimes referred to as being computer - executed . it will be appreciated that operations that are symbolically represented include the manipulation by cpu 104 of electrical signals representing data bits and the maintenance of data bits at memory locations in memory 124 , execution of software instructions maintained , for example , in the memory 124 , as well as other processing of signals . the memory locations where data bits are maintained are physical locations that have particular electrical , magnetic , optical , or organic properties corresponding to the data bits . when implemented in software , the elements of the present invention are essentially the code segments to perform the necessary tasks . the program or code segments can be stored in a processor readable medium or transmitted by a computer data signal embodied in a carrier wave over a transmission medium or communication link . the “ processor readable medium ” or “ machine - readable medium ” may include any medium that can store or transfer information . examples of the processor readable medium include , but are not limited to , an electronic circuit , a semiconductor memory device , a rom , a flash memory , an erasable rom ( erom ), a floppy diskette , a cd - rom , a dvd - rom , an optical disk , a hard disk , a fiber optic medium , a radio frequency ( rf ) link or any other suitable medium or combination thereof . the computer data signal may include any signal that can propagate over a transmission medium such as electronic network channels , optical fibers , air , electromagnetic , rf links , etc . the code segments may be downloaded via computer networks such as the internet , intranet , etc . fig2 is a flow chart illustrating a conventional boot process . the boot process 200 begins at step 205 with the loading and execution of the bios boot block . in step 210 , the bios then performs the post operation and general hardware initialization . in step 215 , the bios code searches for and detects bootable media that may be connected to the associated device . the bios of fig2 has often been programmed to search for bootable media in a particular order ( e . g ., check floppy drive first , then cd - rom , then hard disk drive ). once the bios has detected the presence of bootable media , a determination is made , in step 220 , as to whether the detected bootable media is partitioned . when bootable media is partitioned ( such as is the case with a hard disk drive , removable disk drive , flash , memory , etc . ), the boot process proceeds to step 225 where the bios validates the first block of data on the bootable media ( known as the master boot record ( mbr )). once the mbr has been validated , in step 230 the bios loads and executes the mbr loader code ( which it assumes is in the mbr ). in step 235 , the mbr loader code loads and executes the code from the boot sector of the selected boot partition , where the boot sector is the first block of data in the selected boot partition . in step 240 , the executing boot sector code loads and executes operating system initialization files . if , on the other hand , the determination in step 220 indicates that the detected bootable media is not partitioned ( e . g ., such as in the case of a floppy drive ), the boot process proceeds to step 245 where the bios may validate the first block of data on the bootable media ( i . e ., boot sector ). in step 250 , the bios loads and executes code ( which it assumes exists ) from the boot sector . in step 255 , the boot sector code then loads and executes the operating system initialization files . while fig2 represents a conventional boot process , fig3 a - 3b illustrates an exemplary boot process 300 consistent with the principles of the present invention . while the electronic device 100 ( fig1 ) may employ or execute the illustrated boot process 300 , it should equally be appreciated that numerous other systems and devices , each with varying configurations may also be booted according to boot process 300 . the boot process starts at step 305 , where the bios boot block is loaded and executed . in step 310 , the bios code may cause the processor to perform post operations and system hardware initialization . in step 315 , the boot process then causes the processor to check if a quick boot mode has been selected . in one embodiment , the quick boot mode is determined by having bios poll a flag in system memory or a register of a peripheral component , for example , a switch , a hard key , soft key using a keyboard controller or other suitable i / o devices or combinations thereof . if , in step 320 , it is determined that quick boot mode has not been selected , then the bios code may cause the processor to perform normal boot operations in step 325 . if , on the other hand , the quick boot mode has been selected , then the boot process continues to step 330 where the bios code checks for bootable media . it should be appreciated that the bios code may cause the processor to check for bootable media in a particular order ( e . g ., flash memory , then floppy drive , cd - rom , then hard disk drive , etc . ), or may default to check for a particular type of bootable media . while in one embodiment the particular type of bootable media is a compactflash ® card , it should equally be appreciated that any type of non - volatile media may be used , such as secure digital ( sd ) cards , memory stick ™, floppy disk , cd - rom , hard disk drive , removable hard drive , usb drive , etc . regardless of the media type for the bootable media , in step 335 , the process determines whether bootable media was found . if no bootable media was found , then boot process exits the quick boot mode in step 340 . at this point , the bios code may cause the processor to perform the normal boot operations or may provide an error message . alternatively , if bootable media was found , then the process continues to step 345 of fig3 b where the bios code causes the processor to initialize any additional hardware needed to perform booting operations from the located bootable media ( e . g ., pcmcia controller , vga bios , etc .). thereafter , in step 350 , the bios code may cause the processor 104 to read data from a predetermined location ( e . g ., cylinder : 0 , head : 1 , sector : 1 ) of the bootable media . in one embodiment , the bios code causes the processor to read this data using bios interrupt int13h . in step 355 , the data read in step 350 may then be stored in a predetermined memory location . in one embodiment , this memory location is 0000 : 7c00h , although this predetermined location could equally be located elsewhere . in step 360 , the file system type for the bootable media is determined from the previously read data . while in one embodiment , the file system type for the bootable media may be file allocation table ( fat ) 12 , fat 16 or fat 32 , it should also be appreciated that the bootable media may also be formatted according to another file system ( e . g ., vfat , hpfs , ntfs , etc .). in one embodiment , the bios code determines the type of file system using a predetermined algorithm , such as the algorithm illustrated in fig4 . referring back to fig3 b , if the bootable media &# 39 ; s file system is found to be fat 12 , the boot process proceeds to step 365 where a fat 12 boot loader code is loaded from bios to a predetermined memory location ( e . g ., 0 : 7c40 memory location ). as will be described in more detail below , in one embodiment the fat 12 boot loader code may be stored in non - volatile memory along with the bios code ( e . g ., in rom bios ), rather than on the bootable media itself . if , on the other hand , it is determined that the bootable media &# 39 ; s file system type is fat 16 , then the boot process will continue to step 370 where a fat 16 boot loader code is loaded from bios to a predetermined memory location . similarly , if the data read from the boot sector of the bootable media in step 350 indicates that the file system type is of some other type ( e . g ., fat 32 , ntfs or other suitable file system type ), then the boot process proceeds to step 375 where a corresponding boot loader program code may then be loaded from bios . in one embodiment , if there is no corresponding boot loader program available , the boot process would exit and normal boot operations would continue . alternatively , the boot process may provide an error message , followed by the electronic device being rebooted . once the appropriate boot loader code has been loaded , the boot process may then proceed to step 380 where execution control is passed to the bios boot loader code . in one embodiment , the bios boot loader code may then proceed to boot the electronic device 100 in the traditional fashion , in which case boot process would end while the bios boot loader code would continue to execute from bios non - volatile memory . however , in another embodiment , after step 380 , the boot process may proceed to process 500 of fig5 . fig5 is a flow chart illustrating the steps of process 500 which continue from where boot process 300 left off . in step 505 , the bios boot loader code causes the processor to check for executable programs to load from the bootable media . in step 510 , if it is determined that there are no programs available on the bootable media to load , the process may then cause the processor to locate and load an operating system from some other available non - volatile media ( e . g ., hard drive , floppy drive , cd - rom , etc .) in step 515 . if , on the other hand , the bios boot loader code causes the processor to detect the presence of executable programs on the bootable media , the process may proceed to step 520 where a kernel loader of the bios boot loader actually loads and executes the program from the bootable media . while in one embodiment , this program may be an operating system for device 100 , it should equally be appreciated that the program may be a standalone application program . moreover , additional programs located on the bootable media may subsequently be loaded in steps 525 and 530 . in order to be able to perform the operations described above , the bios code of the electronic device 100 may be pre - configured at the factory level . for example , the bios code used to implement process 300 ( fig3 ) and process 500 ( fig5 ), as well as the individual bios boot loader programs that may be called , may all be programmed at the factory level prior to user - level delivery of the electronic device 100 . alternatively , a firmware upgrade of the bios code for an existing device or suitable system may be undertaken to provide the functionality described above . in one embodiment , this firmware upgrade may be accomplished by having users download and execute a utility program , for example , phoenix winphlash ™ and / or phoenix phlash16 ™, manufactured and distributed by the assignee of the present invention or any other suitable device or combination thereof that is designed to re - program flashable memory . it should be appreciated , however , that any means known in the art for updating non - volatile memory may be used . in a further embodiment , a single executable program may be downloaded and installed by a user where the single executable program includes both the application program ( s ) referred to above with reference to steps 520 - 530 of fig5 , as well as the flashable memory utility program . in this fashion , the single executable program may be used to cause the bios firmware upgrade to take place , as well as to install the one or more application programs onto the bootable media . it should of course be understood that more than one executable program may be similarly downloaded . thus , what is disclosed is a media boot loader that may be used to expedite the boot process by eliminating the need to have a master boot record ( mbr ) for bootable partitioned media , or in the case of bootable non - partitioned media , eliminate the need for a boot sector . with the boot loader code being stored in bios rather than on the bootable media itself , one aspect of the invention is to enable control to be passed to the bios boot loader code which , in turn , may load one or more programs into memory ( e . g ., an operating system ( os ), standalone application programs , etc .). in another embodiment , since the bootable media does not have the special formatting or the mbr of traditional partitioned bootable media , the bootable media described herein may be used to store data as any non - bootable media would , while also being able to provide the functionality of bootable media . while certain exemplary embodiments have been described and shown in the accompanying drawings , it is to be understood that such embodiments are merely illustrative of and not restrictive on the broad invention , and that this invention not be limited to the specific constructions and arrangements shown and described , since various other modifications may occur to those ordinarily skilled in the art .