Posted: Thu Apr 10, 2008 10:11 am
Haos I do talk to greatlord a lot. I found about this one when trying to work out why 1 wine test case would work perfectly fine on windows 2000 but bring XP to a complete stop.
Issue with 2000 DX has safeguards that prevent a Direct X program with a minor error from blue screen the OS by passing invalid data.
XP removes these protections for the minor speed gains. Direct X in 2000 is also kernel mode to the same amount as XP.
Haos don't take me out of context. Wine direct X to opengl is not a unstable design. Due to syscalls missing MS Direct X cannot be completely used with wine. There are limitations from the wine design. Also wine design has a place with Reactos. When running inside a virtual machine with only opengl on the OS outside.
XP direct X design is unstable by design. XP is blindly trusting data sent threw to direct x kernel model.
Note the base design for React X is Windows 2000 direct x so the safe guards are there. Really Haos you need to talk to greatlord and kinda have the facts before telling me to go talk to him.
Unstable gpu drivers are not the issue I was referring to. There is nothing much you can do about that other than find better drivers. Its a equal problem to windows linux and mac that one.
The fault is where application does something stupid like sends a null pointer instead of a pointer to data. There is no reason for that to crash the OS.
Even Vista's direct X is not contained to usermode. But the usermode does a sane check on what is been sent to kernel mode. In side vista kernel there is protected path and other protections.
At long last you said the important thing Haos. performance issues. Wine Direct X does not match 1 to 1 with XP or Vista on performance. Its kinda part way between. Some parts are even faster than XP. There is room for improvement.
The important issue for me. Is if you are going to run windows drivers you might as well use windows driver direct X acceleration if it works. Since to to that requires kernel mode features. Time to add kernel features is when a kernel is in alpha before its in production use.
Issue with 2000 DX has safeguards that prevent a Direct X program with a minor error from blue screen the OS by passing invalid data.
XP removes these protections for the minor speed gains. Direct X in 2000 is also kernel mode to the same amount as XP.
Haos don't take me out of context. Wine direct X to opengl is not a unstable design. Due to syscalls missing MS Direct X cannot be completely used with wine. There are limitations from the wine design. Also wine design has a place with Reactos. When running inside a virtual machine with only opengl on the OS outside.
XP direct X design is unstable by design. XP is blindly trusting data sent threw to direct x kernel model.
Note the base design for React X is Windows 2000 direct x so the safe guards are there. Really Haos you need to talk to greatlord and kinda have the facts before telling me to go talk to him.
Unstable gpu drivers are not the issue I was referring to. There is nothing much you can do about that other than find better drivers. Its a equal problem to windows linux and mac that one.
The fault is where application does something stupid like sends a null pointer instead of a pointer to data. There is no reason for that to crash the OS.
Even Vista's direct X is not contained to usermode. But the usermode does a sane check on what is been sent to kernel mode. In side vista kernel there is protected path and other protections.
At long last you said the important thing Haos. performance issues. Wine Direct X does not match 1 to 1 with XP or Vista on performance. Its kinda part way between. Some parts are even faster than XP. There is room for improvement.
The important issue for me. Is if you are going to run windows drivers you might as well use windows driver direct X acceleration if it works. Since to to that requires kernel mode features. Time to add kernel features is when a kernel is in alpha before its in production use.