Why DOS? Well... I have a lot of small old DOS programs and it will keep me occupied until I get some laptop harddrives. It is also kinda ironic how DOS can also stand for "denial of service" - pun intended.
http://members.aol.com/powercntrl/iowebs.jpg <- I-Opener AND WebSurfer both running STOCK (no hardware mods) with their flashdrives loaded with DOS.
On the I-Opener, this was simply a matter of using qnxflash to reflash the BIOS - then I connected a laptop drive I borrowed from a friend (yea, I had to modify an IDE cable, my attempt to replace the flash via the "gzip image to flashdrive" hack didn't work out so well) and reformatted the I-Opener's sandisk with DOS.
The WebSurfer is a bit more of a pain in the ass. All I had to boot from was a SCSI card, so it made reflashing the Disk-On-Chip somewhat "interesting". It seems the Disk-On-Chip could override the SCSI card's authority to boot, no matter what boot device was set as first in the BIOS.
First I tried booting like normal, that was a no-go. After yanking out the Disk-On-Chip, it booted fine. I then put the Disk-On-Chip BACK IN (yep, hotflash) and used the utililites I got from www.m-sys.com to reformat the disk-on-chip. Then, I rebooted and was greeted with a nice "Insert System Disk" message - great, the Disk-On-Chip is still overriding the SCSI controller. I pulled the chip out again, and booted up.
This time I looked in one of the directories that the Disk-On-Chip tools came with and found there are loadable device drivers for it. I installed the drivers and rebooted, still with the Disk-On-Chip removed. NOW, as soon as I saw the detection sequence for the SCSI card show up, I plugged the Disk-On-Chip back in and the Websurfer booted up fine and the Disk-On-Chip was accessable. I systemized it following the instructions provided by the Disk-On-Chip utilities and copied some stuff to it.
Finally, I pulled out the SCSI controller (the websurfer was OFF first, heh) and rebooted... Volia! DOS!
If you were using an IDE controller, I'd imagine this process would be a lot easier. :)