Dex wrote:I disagree, i have never used a emulator in my OS Dev cycle, i have done all my Dev work on real PC's, i must turn my main test PC on/off about a 100 times aday (at least ) and i have never had any of my PC's break in anyway.
It's not just about breaking, it's that transferring your OS to a floppy, move the floppy to the test machine, reboot the test machine, wait until the OS boots, etc. etc. takes a pretty long time. So unless you're truely multi tasking and can do something else in the meanwhile, you are wasting time. Emulators are far faster, and there's not the physical floppy moving etc. you need. I'm not critiquing you're preferred method of OS development (you seem to have done pretty well this way), but in general it's not a wise thing to do this.
This is all you need to debug code
Code:
Code: Select all
mov byte [fs:0xB809E], "1"
; Some code
mov byte [fs:0xB809E], "2"
; Some code
mov byte [fs:0xB809E], "3"
; Some code
mov byte [fs:0xB809E], "4"
; Some code
mov byte [fs:0xB809E], "5"
; Some code
That won't help you when tripple faulting and/or when using paging, unless you manage to reboot into some special monitor that can still analyze that address (provided it knows the physical address in case of paging).
I think that most here agree that for a newbee, using an emulator like Bochs is the wisest thing to do. Noone says one cannot do without, just that it is very cumbersome and (even more) time consuming.
JAL