F
F Murtz
Charlie said:"The secret word is 'mindless'." Thank you, Groucho.
Wow - flamed by both of his personalities in the same day.
I've made it (whatever "it" is).
Blimey this subject has generated a lot of verbiage.
Charlie said:"The secret word is 'mindless'." Thank you, Groucho.
Wow - flamed by both of his personalities in the same day.
I've made it (whatever "it" is).
F Murtz said:Blimey this subject has generated a lot of verbiage.
Indeed. And I remember thinking when W95 came out (late!) how much
Microsoft had "borrowed" from MacOS, AmigaOS, Next and the *nix window
managers.
No they werent. Particularly when they installed device drivers for
all the hardware and even rescanned for drives visible, and didnt
use the bios or dos functionality at all, even for the keyboard etc.
Actually in modern PC's there is an increase in BIOS use. Windows and othergreenaum wrote
Win stopped using the bios LONG ago. Its basically just used in the boot
phase now.
Scott Lurndal wrote
Because few bother to cater for those of you that prefer a different OS.
You might as well whine about having to pay for heated seats when
you want to use a car in a place like Hawaii that never needs them.
Or child restraint anchor points in your new car when
you dont have any kids and never have kids in your car.
Sigh! Proprietary meant that the formats were not published. To
translate that sentence for you, it meant that nobody knew what the
formats were and, thus, could not write code to read those formats
unless they were ble$$ed by MS.
But it didn't have a mouse ball.
95 and 98 were still DOS underneath,
you could close 95 and get back to the dos prompt,
with a little tweaking you could do the same in 98
So did DOOM, that doesn't make it an operating system.
Actually in modern PC's there is an increase in BIOS use.
Windows and other 32bit protected mode operating systems stopped using
the BIOS as the BIOS vendors never wrote protected mode friendly code.
A modern PC with an ACPI BIOS provides a bytecode that can be executed
in the OS kernel to do chipset specific operations in an OS neutral way.
ATI also do a similar thing in their video card
ROMS for certain setup operations as well.
Suspending and resuming a modern laptop is done this way as
are a lot of the motherboard device discovery/power managment.
This bytecode approach gives the OS vendor a way of controlling the
processor mode and leaves it up to the OS to make sure the bytecode
interpreter is suitable for the OS environment. These BIOSs are not
without their bugs but the situation is getting better especially since
newer versions of Windows don't tolerate bugs in these bits of code.
Makes you wish they had done it this way in the first place although
I'd imagine the performance penalty on even a 486 would be shocking.
Jim Brown wrote
Sigh!
Proprietary meant that the formats were not published.
To translate that sentence for you, it meant that nobody knew what the formats were
and, thus, could not write code to read those formats unless they were ble$$ed by MS.
But I can certainly order a car that doesn't have them,
I may just have to wait longer
(it will often be cheaper as well unless the dealer
really wants the one with heated seats off the lot
and is willing to eat the cost of them to do it).
I actually have heard several childless people complain
about safety features aimed at children driving up the cost.
Morten Reistad said:There have been ages since I couldn't read a document. It still
happens all the time that it formats strangely. But that happens
on other MS installations as well; where the setup for the
details is different from what the original author intended.
Actually, probably even more so.
Sometime you should try to broaden your horizens and spend some time looking into SMM.
The SMM handler which is part of the BIOS executes _very_ frequently
(and invisibly) while Windows, Linux, Solaris, OS/2, et. al. are executing,
particularly when the power saving features of the system are in use.
And most operating system interactions with the hardware platform
are handled by the ACPI bytecode as others have noted.
Roland Hutchinson said:Are you sure?
I remember the "Works" and "Orifice" incompatability. Strange both were M$.How odd that plenty managed to work them out anyway. It aint rocket
science, stupid.
Jim Brown said:jmfbahciv wrote
Heavy breathing aint gunna save your bacon.
Duh. NTFS support etc is perfectly possible anyway.
How odd that plenty managed to work them out anyway. It aint rocket science, stupid.
How odd that so many did anyway.
Try again.
Joe Pfeiffer said:How much odder that even Microsoft software fails to correctly interpret
Word documents across versions.
I remember the "Works" and "Orifice" incompatability. Strange both
were M$.