Omega Drivers 2.6.42 and IGP 350M

Zok · Jun 28, 2005, 08:26 PM

I know the Omega 2.6.42s are supposed to suport all Radeons (Mobility M6 and up), but can someone tell me why it will not work with my IGP 350M no matter what? It has support for IGP 34xM, but not the 350. Is there some sort of work-around that I can get this working?

ChoGGi · Jun 28, 2005, 10:01 PM

what error message do you get?

Zok · Jun 29, 2005, 12:06 AM

Well... the driver installation recognizes it as an IGP 34xM and upon windows retart I get the dreaded blue screen. Had to go in and clean the driver out and put in the manufacturer's driver to get it back... which is recognized at Catalyst 4.4.

ChoGGi · Jun 29, 2005, 12:48 AM

could you post the information from the blue screen

not all of it just the parts here:
A problem has been detected and Windows has been shut down to prevent damage
to your computer.
PFN_LIST_CORRUPT

and here:
STOP: 0x0000004e (0x00000099, 0x00000000, 0x00000000, 0x00000000)

WhatsUpDoc · Jun 30, 2005, 11:39 AM

I get the blue screen too after i try installing the newest omegas, but after i install the CAT 5.6 using patje's tools too!!! see below for my specs. its the infamous ati2dvag error. i read in another thread that the ati2dvag.dll in the CAT 5.6 is older than the one in the previous version, could this be it? the 2.6.25a omegas work just fine for me on my IGP 345M. i even tryied installing the 2.6.42s and replacing the ati2dvag.dll with the one from the 2.6.25as in safe mode but it didnt work, my laptop switched from 32 bit to 8 bit and minimum resolution, but at least it booted... if anyone finds an answer to this please PM me! i hope the ati2dvag.dll will work on the next set of drivers...
cheers

Jun 28, 2005, 08:26 PM	#1
Zok DriverHeaven Newbie Join Date: Jun 2005 Posts: 2 Rep Power: 0	Omega Drivers 2.6.42 and IGP 350M I know the Omega 2.6.42s are supposed to suport all Radeons (Mobility M6 and up), but can someone tell me why it will not work with my IGP 350M no matter what? It has support for IGP 34xM, but not the 350. Is there some sort of work-around that I can get this working?

Jun 28, 2005, 10:01 PM	#2
ChoGGi DriverHeaven Senior Member Join Date: Jun 2002 Location: Toronto Posts: 1,209 Rep Power: 0	what error message do you get? __________________ specs Common Problems and Fixes for your Radeon

Jun 29, 2005, 12:48 AM	#4
ChoGGi DriverHeaven Senior Member Join Date: Jun 2002 Location: Toronto Posts: 1,209 Rep Power: 0	could you post the information from the blue screen not all of it just the parts here: A problem has been detected and Windows has been shut down to prevent damage to your computer. PFN_LIST_CORRUPT and here: STOP: 0x0000004e (0x00000099, 0x00000000, 0x00000000, 0x00000000) __________________ specs Common Problems and Fixes for your Radeon

Jun 30, 2005, 11:39 AM	#5
WhatsUpDoc DriverHeaven Junior Member Join Date: Oct 2004 Location: Germany Posts: 26 Rep Power: 0	BSOD after omega 2.6.42 installation I get the blue screen too after i try installing the newest omegas, but after i install the CAT 5.6 using patje's tools too!!! see below for my specs. its the infamous ati2dvag error. i read in another thread that the ati2dvag.dll in the CAT 5.6 is older than the one in the previous version, could this be it? the 2.6.25a omegas work just fine for me on my IGP 345M. i even tryied installing the 2.6.42s and replacing the ati2dvag.dll with the one from the 2.6.25as in safe mode but it didnt work, my laptop switched from 32 bit to 8 bit and minimum resolution, but at least it booted... if anyone finds an answer to this please PM me! i hope the ati2dvag.dll will work on the next set of drivers... cheers __________________ Compaq Pressario 2529EU P4 M 2,8 Ghz 512 MB RAM ATI Radeon IGP 345M 128MB 60GB HDD, DVD+RW

Jun 29, 2005, 12:06 AM	Thread Starter #3
Zok DriverHeaven Newbie Join Date: Jun 2005 Posts: 2 Rep Power: 0	Well... the driver installation recognizes it as an IGP 34xM and upon windows retart I get the dreaded blue screen. Had to go in and clean the driver out and put in the manufacturer's driver to get it back... which is recognized at Catalyst 4.4.