@Benz93 first of, what is the pixel shader 3 error said? hmm, interesting, but u forget one single thing, the 4 series driver support sM2.0, 3.0 and 4.0 (dx10 capable) shaders...so, im juz guessing that u guys have managed to solve the SM2.0 mod, which shows with the 10fps boost in pixel shader test. saying that, i have to ask, did u guys have make SM3 and SM4 (by SM,im refering to shader model) compatible with the x3100? every codes that have been mod, change other dependent codes reaction. meaning, yes u have done a wonderful job modding SM2 for the X3100, but have u tried to manage connecting the SM2 codes with the rest of shader model?
yes, lol, it's trickier to explain rather than do it..every shader instruction connects each other in a series of dependencies..while it is easy to make 965 drivers compatible with 945, it's because of one single thing, 945 only support SM2 hardware wise in theory (with Vertex Processing done in software), so as for myself as a modder, i juz have to make the SM2.0 codes compatible without worrying about SM3.0 codes which the 945 cant support.. in the case, to make 4 series driver compatible with x3100, for starters, x3100 are capable both SM2 and SM3, and the 4 series driver capable of SM2, SM3 and SM4.. so u have to make SM2 and SM3 compatible with x3100...again this is not easy work, like TheFog said.. making 1 shader model to work is relatively easy as it doesnt concern of the shader connections with each other..2 shader model again dependent on each other..so if on have been mod, the other must be also mod.. also the newer CUI mentioned above, is theoretically possible...im not sure but it's some how possible... about the *.sys file....that file is a compiled code both in C++ and VC++...contains shader instructions...both vs and ps..(pixel and vertex shader instruction ) also contains some HAL codes...so modding it would be time consuming...decompiling it is another thing.. i am not a x3100 or 4 series expert, but SUGGESTION : - u can mod the inf which holds the driver setup instruction to make it 60% compatible with ur x3100 (yes , 60%), but also time consuming if u have to pin point what causing the SM3 error... driver modding is time consuming and can taking months... - search for linux driver source code of the card, X.org driver is ur best bet...and no u cant use the source code as windows base driver, but u can look at what features that intel 4 series driver support that x3100 cant..disabling the features that x3100 cant support can greatly improve compatibility.. again great work there bro, it interested me and i wish u guys the best ^^ also welcome to the revolution ^^ On Wed, Aug 4, 2010 at 7:08 PM, THEfog . <[email protected]> wrote: > It is built for a completely different gpu so you have to expect > issues, by sys I'm assuming you are referring to the *.sys file > sitting in the MD install? If so you are looking at the file which is > holding most of the drivers Variables and setting for operational use, > you will be looking for a Resource Hacking/ File Disassembler or the > likes of a hex decompiler to access and edit this, your mate should > know how to use one if he managed to get this far through a MD, > interestingly enough you can actually view the dependencies and File > Variables though the use of a run of the mill hex editor. if you need > any further help MAD_BEAST or AngelicTears should be along soon enough > to expand further upon what i just covered briefly, ask as many > questions as you want, we are here to help after all. > > THEfog > > -- > 9xx SOLDIERS SANS FRONTIERS > -- Laptop: Acer Aspire Core Duo T2300E @ 1.67GHz Intel GMA 950 IGP Intel 945 Chipset 1GB RAM (512MB*2) Dual Channel DDR2 80GB standard PATA HDD Win7 Ultimate 32bit / Ubuntu 10.04 -- 9xx SOLDIERS SANS FRONTIERS
