Details
-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
None
Description
On some Gfx-Cards videoprt.sys fails to init because it detects too many access ranges due to legacy shadowed mem areas.
It can be avoided by using the videoprt.sys from XP. This will list one range less!
Confirmed cases and differences using XP's videoprt.sys instead of ReactOS's:
Sis630 on Uniwill 340s8:
I/O 3c0 - 3df
|
I/O 3b0 - 3bb
|
I/O ac80 - acff
|
Mem a0000 - bffff <- XP's videoprt.sys on ROS & XP does not list
|
Mem c0000 - cffff
|
Mem dfee0000 - dfefffff
|
Mem d0000000 - d7ffffff
|
Sis760 (Mirage 2) on Uniwill 255KI
I/O 3c0 - 3df
|
I/O 3b0 - 3bb
|
I/O cc00 - cc7f
|
Mem a0000 - bffff
|
Mem c0000 - cffff <- XP's videoprt.sys on ROS & XP does not list
|
Mem dfee0000 - dfefffff
|
Mem d0000000 - d7ffffff
|
Trident Video Accelerator Cyberblade i7 on PCG-9415
I/O 3c0 - 3df
|
I/O 3b0 - 3bb
|
I/O cc00 - cc7f <- XP's videoprt.sys on ROS does not list
|
Mem a0000 - bffff
|
Mem fb800000 - fbffffff
|
Mem fb100000 - fb11ffff
|
Mem fc000000 - fc7fffff
|
More will be added as soon as confirmed with working gfx-driver...