🚀 go-pugleaf

That conflict is a known bug in Windows 95 with AGP cards. It doesn't
actually cause any problems, it's just that Windows 95's Device Manager
doesn't know how to interpret the AGP resources properly. The fix for this
cosmetic problem is to upgrade to Windows 98.

--
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamhome.com
Home Page: http://members.home.net/hancockr


"Simon Leyland" <the_red_roman@yahoo.com> wrote in message
news:3869DED9.F5FF1405@yahoo.com...
> I have just discovered a problem with DirectX 7 and Matrox Millennium
II's.
> I have been having problems editing JPEG's in Paint Shop Pro 6 and in
Photo
> Impact 4.0.  The same photo's are freezing Paint Shop and Photo Impact
when
> I try to crop them.  I looked in the Device Manager for problems, but
> everything seems to be working properly, expect that in the resource list
> for the Millenium II I get the following conflicts:
>
> Memory Range FC000000 - FCFFFFFF used by:
>     Intel 82443LX Pentium(r)II Processor to AGP controller
> Memory Range F4800000 - F4803FFF used by:
>     Intel 82443LX Pentium(r)II Processor to AGP controller
> Memory Range F4000000 - F47FFFFF used by:
>     Intel 82443LX Pentium(r)II Processor to AGP controller
>
> I have manually changed these settings(so they have no conflicts) and
> restarted my PC, but Windows 95 doesn't load, so I reboot in safe mode,
then
> disable the video card, reboot Windows 95 and then use the automatic
> settings which conflict(but Windows 95 loads ok!!!).
>
> The files that I am trying to edit are only 1/2 a meg and I have edited
> larger files before.  The only thing I can think that is wrong is that
> DirectX 7.0(which I installed a month ago) may not be compatable with my
> video card drivers(and I have the lastest drivers from the Matrox
website).
>
> My system specs are:
> Dell Pentium II, 300 MHz, 64meg RAM, 8mb Matrox Millenium II AGP graphics
> card, 12mb Diamond Monster II 3D card and I'm running Windows 95 OSR 2 and
> DirectX 7.
>
> I reckon my problems will be solved if I can somehow go back to DirectX
6!!!
>
> Simon.
>
>