visopsys.org

Looks like everything was successful, and you created the ISO correctly. Unzip the *-iso.zip file, then go into your VM settings, edit the settings for devices, and choose CD, boot from ISO image, connect at power on, and browse to your unzipped image. You may have to edit the boot settings in the V...

Great, thanks. Here are 2 floppy images. I'm assuming floppies are better for you, than burning a bunch of CDs. Don't unzip both of these at the same time, in the same folder, as the unzipped file name is the same for each. First one. This one just loads the kernel and stops: http://visopsys.org/fil...

Hi Paul, sorry you're having trouble with it. It doesn't sound promising -- almost as if there's a problem with the processor being too old. If you have time, I can post links to a couple of 'debug' floppy disk images that will help me to understand the problem a bit better. If it turns out to be pr...

That's almost right. Assuming that directory contains the Visopsys source code, do:

# cd /root/Desktop/visopsys
# make

Andy

Hi again Mac, Unfortunately I wasn't able to reproduce that crash on any of my systems -- it's a head-scratcher. Anyway, I've created this image that has the ACPI power management code disabled, so this should allow you to test USB connectivity on your system: http://visopsys.org/files/misc/partlogi...

Hello, Did you install Visopsys using the built-in installer (like from the live CD?) Normally it will ask you to set the password for the account 'admin', but it seems like there's a little bug in the program which causes it to skip past that dialog box :doh:. If that happens, then the 'admin' acco...

Hello, It's recommended to get a Linux such as RedHat/CentOS 5.x, as that's what's currently used for development. Some newer Linuxes such as RedHat/CentOS 6 or Ubuntu > 10, create executables that can't be used by the OS kernel, yet. Make sure that GCC and NASM are installed. Then just change to th...

I don't see any obvious problems with the ACPI code, so I'm working my way through my collection of test hardware trying to reproduce that crash. :think: If I can't, I'll post a version with that disabled so we can (hopefully!) find out whether I've solved the USB issues with your mouse and keyboard...

Yes indeed, thanks for pointing this out. I sometimes use VirtualBox for development, though I mostly use VmWare.

Ah, bummer, looks as if the new power management code has an oopsie in it :doh: That USB error may or may not be from the keyboard or mouse, so I guess I can't tell from this whether your original problem has been solved. Thanks again for the help. If I can find that ACPI bug and have confidence tha...