The Place to Start for Operating System Developers
http://forum.osdev.org./
go dive into the qemu source and implement it then.. there is a reason its not implemented.. cause windows is dumb and doesn't treat block devices the same way as files...Creature wrote:The mount -> copy -> unmount way does work, but it's still pretty lame that QEMU can't just recognize any boot floppy from virtual floppy drive (and I have no idea why, as it worked perfectly before and why else would there be support for an -fda \\.\A: option?) which would save the time of unmounting all the time.
Well if Bochs can use a floppy drive (a physical one), there is no reason Qemu couldn't use one...earlz wrote:go dive into the qemu source and implement it then.. there is a reason its not implemented.. cause windows is dumb and doesn't treat block devices the same way as files...
That's what I thought, and the documentation says it can, by using something like 'fda \\.\A:' but QEMU just doesn't recognize it as a boot device then for some reason. It could also be a new bug occurring in the new version.ru2aqare wrote:Well if Bochs can use a floppy drive (a physical one), there is no reason Qemu couldn't use one...earlz wrote:go dive into the qemu source and implement it then.. there is a reason its not implemented.. cause windows is dumb and doesn't treat block devices the same way as files...
I've just compiled mtools with Cygwin, though I'm not really sure how to use it, it keeps giving me a list of commands (I'll search for some documentation soon).Hi,
Use mtools and you don't need to mount the disk at all.
Cheers,
Adam
Um, really? What about implementing serial port support and doing remote GDB debugging? Or using debugging printfs/printks? Stack tracing isn't too hard to implement either. You could throw all your debug statements out a serial port (and have that serial port be attached to another computer, or just an old line printer). The only problem here is the need for some extra equipment, but you should really have that anyway. How many people that are developing their own OS don't have a second PC to test on?yemista wrote:You cannot debug by testing on a PC.
Sure it's time consuming and perhaps even a bit harder, but that's not the point I was arguing.JohnnyTheDon wrote:Yes, but debugging like that every time you change the littlest thing is quite annoying and time consumming, especially early on when you make plenty of mistakes that cause triple-faults and such (which will not be caught by in-kernel debugging). It is possible to develop an OS without an emulator, but having one does make it a lot easier.
It was said that it's not possible, and it certainly is. In fact, it's even needed. Neither qemu nor bochs correctly emulate all aspects of an x86 CPU. It's completely possible to write code that will work in an emulator, but not on real hardware. When that happens, you'll need to be able to debug your code on a real PC. Time consuming or not, it's best to take the extra time and steps to test your code often on a real PC, even at the low levels.For copying a file to an image:I've just compiled mtools with Cygwin, though I'm not really sure how to use it, it keeps giving me a list of commands (I'll search for some documentation soon).
Code: Select all
mcopy -i <image> <path_to_file_to_copy> ::/<path_to_destination>
Code: Select all
mmd -i <image> <folder name> ::/
Code: Select all
mcopy <file> A:/<path-to-file>
.