[Oberon] Plug and Play OS BIOS Setting

[Stauber Sven Philipp]

Hi!
 
Rene K.>The Plug-n-Play-Setting did the trick for me, thanks.
Rene K.>So, does this have any draw-backs for using this computer under WinXP?
The Microsoft Windows XP Support Center provides the articles Q321779 (Info about PNP OS Setting) and Q222973 (Use PNP OS=No to solve a specific boot problem). According Q321779, setting PNP OS to "No" can result in a less optimal H/W configuration. This shouldn't be a problem, though.

Peter E.>Aos could read the setting in the CMOS and, if
>appropriate, make a warning in the System.Log. 
>Example.
>Warning: "PnP OS Installed" in the CMOS system
>parameters is set to "YES".  Aos is not a PnP OS.'
This would be nice.  I don't know, however,  whether this CMOS setting is standardized. The systems I use at work (Pentium4) don't even provide a PNP OS setting in BIOS setup (At least, it's not accessible. Per default, the BIOS initializes all devices).

Peter E.>An even better (simpler) solution is to correct
>the setting, put an explanation on the screen,
>wait for an acknowledgement from the user and
>reboot.  Problem solved, for everyone, permanently!
>If BootMan does this, the parameter can also be
>set "YES" for other systems.
At the time the bootman gets control, the BIOS did already initialize the devices depending on the PNP OS setting. To change this later will have not effect (and I, personally, don't like to reboot the computer too often). Since other OS's shouldn't have problems with PNP OS = No, for me, the preferred way would be to set it permanently to "No".
 
The nicest solution would be to make AOS becoming a PNP OS and therefore avoiding workarounds. Aos.PCI.Mod seems to provide some functionality for IRQ routing. Unfortunately, the lack of time is as always the devil.... 
For now, I've just noted "Put PNP OS thing into FAQ"  (but I'm on holidays for the next three weeks, so that will take some time).

Cheers,
Sven Stauber