I've tested it using a converter utility website. I don't know if I will be able to find a suitable debugger for Windows which will work with Bochs, so I'm going to code up some functions to dump registry values.įound a good LBA-to-CHS translation routine and incorporated it in the code. Wrote some calls to help me debug FAT12 operations. Started reading about reading from a floppy disk, since the plan is to read FAT12 and locate a file with a specific name which will contain the kernel. The build script now injects a few test files into the floppy image. I don't know if this is a DOS-specific thing, or not, but the generated floppy image now boots in Bochs and VMWare, and is recognized as a valid floppy disk in both Windows XP and DOS. Instead, I changed the 0 to a nop (0x90) instruction, and it started working. With a 0 there, DOS 6.22 doesn't recognize the floppy as valid. While the FAT12 specification says that the first 3 bytes of the boot sector are ignored, this is not true. ![]() I refused to give up and took a look at an online example of a bootloader which specifies the PBP in order to make a "proper" floppy image. Of course, it boots in both Bochs and VMWare. I reached a compromise where DOS no longer can read the floppy, but Windows XP can. Of course, as soon as I try to copy even one file to the floppy image, it stops working (can't be read by DOS or Windows XP). It also became readable in both DOS and Windows XP. Once I added it, my floppy disk image booted in both Bochs and VMWare. It turns out I was missing one byte from the beginning of my BPB (BIOS Parameter Block). However, in VMWare, I can read the FS, but of course, doesn't boot. I added it, and it boots in Bochs, but I can't read the FS from a DOS 6.22 VM. The problem could be that I'm missing the BPB boilerplate. dd'ing the image to insert my own bootloader simply corrupts things.įor now, I can either create a floppy image with files on it, or a bootable, empty floppy image.Ībout five different tools later, I can boot, as well as have valid files on the floppy image. The floppy imaging tool tries to be extra smart and injects its own bootloader. Put together toolchain - it assembles and creates boot loader floppy image from one script. Installed Bochs, a virtual machine provider which I hope to use as my development environment. Start thinking about where applications will be loaded, and how they'll return to the OS. Start thinking about organization of segments (stack, etc.). ![]() Re-familiarized myself with boot loaders and BIOS booting process. Outside of this, I often spent time thinking about what to do next and how to do it. It was developed primarily during evenings, some longer and some shorter. I already installed the latest version of WINPCAP and configured Bochs with the Novell 2000 compatible adapter settings that niclister.exe showed me, but it turns out that NE2000 is not properly initalised.This is the development log of Snowdrop OS. Is there any way to get networking working properly under Bochs? Here's the current configuration of what the Windows 95 Bochs VM looks like: The full version of the logs can be found here:Ġ0000252000e device not ready to receive dataĠ0006048000e device not ready to receive dataĠ0078624000e device not ready to receive dataĠ0091476000e device not ready to receive dataĠ0100044000e device not ready to receive dataĠ0105840000e device not ready to receive dataĠ0125748000e device not ready to receive dataĠ0137844000e device not ready to receive dataĠ0152208000e device not ready to receive dataĠ0172872000e device not ready to receive dataĠ0208908000e device not ready to receive dataĠ0230580000e device not ready to receive dataĠ0235620174e DCR write, loopback mode selectedĠ0235620174i DCR write - AR set ?Ġ0235620201i RCR write, monitor bit set!Ġ0235774446i TCR write, loop mode 1 not supportedĠ0238339581i TCR write, loop mode 1 not supportedĠ0238339724i Physical address set to b0:c4:20:00:00:01Ġ1387833607i TCR write, loop mode 1 not supported I enabled the logs to see what could be the problem here and this is what I found and the logs have to do with the NE2K device. I can't even browse the internet using Internet Explorer at all.all I get is a "This page cannot be displayed".
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |