visopsys.org

Hello, welcome! I think there will be a version 0.84 soon, but it's only lots of small things and bug fixes so far. I'm spending most of my time working on 0.9. I was hoping to release it by the end of 2018, but I still have several things I want to add. It will be a few more months, I assume (I'm a...

Isoprofit wrote: ↑

Tue Jan 08, 2019 7:29 pm

Congratulations on releasing yet another amazing version of your Partition Logic. its gonna be great

Only 7 years late, I just have to assume you're a spambot.

Good instructions, thanks for queueing everything up for me :-) I'm deep into debugging something else at the moment, but I will give this a go soon. In the past I've been asked on here about some multiboot stuff, and PXE, and I wonder whether these changes would help to enable all of that - booting...

I guess what that Fiwix guy did is to create the ramdisk in the bootloader. So the loader would have to pick a memory address, load the entire emulated floppy into it using the usual int13 calls, then pass that address. But we wouldn't want it to do that under normal circumstances, so there has to b...

I'm not much familiar with this world of firmware flashing boot images and whatnot. Is there any way you could post some instructions about how to set this up in an emulator, such as Qemu or VMware or VirtualBox? How would the bootloader find out this memory address, of the virtual floppy image it's...

Hi Ron! I thought about posting up a dev version of 0.9 for you to try - and I can do so if you're keen! - but so far, from a user perspective, there's not much obvious added functionality. Most of it is still under-the-covers, or command-line, stuff. I still need to add the polish and the UI stuff ...

I should add that I've never been attracted to the initial ramdisk idea that Linux uses (and Visopsys was never intended to be a Linux/UNIX lookalike) and there's no "kernel command line" to pass text arguments via Grub and friends. I get that the initrd concept does allow for a lot of flexibility i...

Hi qmastery You've correctly described what the kernel does when it boots - the loader passes a media signature of the boot device, and once the kernel has initialized its disk drivers, it looks around for that thing. The Visopsys kernel does have a ramdisk driver. Normally you request the creation ...

qmastery wrote: ↑

Thu Dec 20, 2018 1:48 pm

It seems that PorkChops had a similar problem:

PorkChops wrote: ↑

Tue Jul 10, 2018 1:26 am

https://visopsys.org/forums/viewtopic.php?f=4&p=1433

It's the same symptom/error message, but I suspect that it was a different cause in that case.

It seems to me that this Error:kernel process:kernelDisk.c:identifyBootDisk(2081): The boot device could not be identified is the main problem that causes to fail kernelInitialize(351) and kernelMain(90). Please could we just print a warning message for the identification of BootDisk and just conti...