Well alright then
Here's the new release candidate:
http://visopsys.org/files/visopsys/viso ... 11-iso.zip
It has changes to the IDE drive detection code, which should fix the problem seen in VirtualBox. It works in VmWare also, and a couple of real systems I've tested, but it would be helpful if people could attempt booting this version on one or two different systems.
I have a stack of old (and sometimes weird) laptops that I use to test things, and I've yet to try it on all of those. I want to try and make sure this new code doesn't break anything that worked before!
Andy
Visopsys 0.7 release candidate
- espectalll123
- Posts: 54
- Joined: Tue Jan 25, 2011 7:58 pm
- Location: Toledo, Spain
- Contact:
Re: Visopsys 0.7 release candidate
Testing again! Please 0 bugs...
espectalll123, making dreams work!
- espectalll123
- Posts: 54
- Joined: Tue Jan 25, 2011 7:58 pm
- Location: Toledo, Spain
- Contact:
Re: Visopsys 0.7 release candidate 2 (bugs are invading us!!
Why, God?
The bugs are invading us!!! They made an error on my VirtualBox's FAT32 HD boot!!! Help!!! Help!!!
So, Andy, this is so strange... (Well, Windows ME can fail more, but...) Your RC2 is not valid for FAT32 install! Fix it... again ( ).
The bugs are invading us!!! They made an error on my VirtualBox's FAT32 HD boot!!! Help!!! Help!!!
So, Andy, this is so strange... (Well, Windows ME can fail more, but...) Your RC2 is not valid for FAT32 install! Fix it... again ( ).
espectalll123, making dreams work!
- espectalll123
- Posts: 54
- Joined: Tue Jan 25, 2011 7:58 pm
- Location: Toledo, Spain
- Contact:
Re: Visopsys 0.7 release candidate
With FAT16, Visopsys 0.7 RC2 works correctly. So, the bug is in the FAT32 startup controllers. One IDE fix isn't important if there's another IDE bug!
espectalll123, making dreams work!
Re: Visopsys 0.7 release candidate
No no, that can't be a filesystem error. Those error messages are generated before any filesystem is mounted. Those are hardware detection errors. Actually, it sort of looks like a problem was generated during mouse detection. There is a known bug wherein moving the mouse during PS/2 mouse detection can cause cascading errors, related to interrupt servicing (as the first error suggests). Can you give it another go with the FAT32?
Also, which version of VirtualBox, and what's the IDE configuration (slaves and masters, which channel etc)?
Also, which version of VirtualBox, and what's the IDE configuration (slaves and masters, which channel etc)?
- espectalll123
- Posts: 54
- Joined: Tue Jan 25, 2011 7:58 pm
- Location: Toledo, Spain
- Contact:
Re: Visopsys 0.7 release candidate
Testing again with FAT32 and no mouse move...
espectalll123, making dreams work!
- espectalll123
- Posts: 54
- Joined: Tue Jan 25, 2011 7:58 pm
- Location: Toledo, Spain
- Contact:
Re: Visopsys 0.7 release candidate
OK, is the mouse bug that left every 0.7 version (yep, I founded it on versions Preview and RC1).
espectalll123, making dreams work!
Re: Visopsys 0.7 release candidate
That mouse bug is very tricky. Even though mice are very simple, initializing them can be a PITA. Interrupts need to be enabled for some of the initialization phase, so I need to find a way to make that work without allowing data reporting - i.e. mouse wiggling - to interphere with the startup stuff. I'm certain there's a way to do it, but I haven't found one yet that works with most/all mouses.
- espectalll123
- Posts: 54
- Joined: Tue Jan 25, 2011 7:58 pm
- Location: Toledo, Spain
- Contact:
Re: Visopsys 0.7 release candidate
Wow! 0.7 final released! Installing it!
espectalll123, making dreams work!
Re: Visopsys 0.7 release candidate
Yup, pulled the trigger late last night. Haven't been by the computer much today, not enough time to put together a proper announcement!espectalll123 wrote:Wow! 0.7 final released! Installing it!