Catalyst conflicts with slipstreamed W2K

[d6xkr]

On my slipstreamed w2k installation, when i installed the catalyst center the AGP bus is disabled by default. I tried the smartgart to enable it, but no sign of change. The smartgart refuses to activate or change the speed of the AGP. Any one konws why this happens or a solution or someone esle with the same problem.


thanks all.

 

[blade85]

have you tried not using CCC??

uninstall everything to do with ati and try again, this time just use the drivers, and then use ati tray tool instead of the catalyst centre.

Alternatively you can also give the omega drivers a go as they also use ati tray tools.

 

[d6xkr]

I can't believe you just said that, cause i already done it... smart!

 

[blade85]

lol, so is it working or this issue after you tested it?

 

[d6xkr]

there is only a single question that I find important at the moment, was your 1st post to offend me?

cause i was offended by your avatar and signature, which made me answer in that way.

 

[Valtiel]

This is the problem with there not being tone over the internet, messages can be misconstrued as insults. I believe that blade85 was only trying to help, not to offend.

 

[Zorg]

there is only a single question that I find important at the moment, was your 1st post to offend me?

cause i was offended by your avatar and signature, which made me answer in that way.

You have got to be kidding me. His recommendation was spot on, and since he has had that avatar for a while, there is no way that it could be directed at you. You need to get a little thicker skin or you are going to have a really hard life.

 

[blade85]

there is only a single question that I find important at the moment, was your 1st post to offend me?

cause i was offended by your avatar and signature, which made me answer in that way.

LOL sorry mate, no offence intended. I find the avatar and my sig comical, and they are both quotes and not my personal saying.

Apu says what my avatar has on, and my sig is from an old old game.

 

[d6xkr]

Hmmmmmmmmm..., So ......I'm gonna be the fool of the scene! Ok....., that can go with me now, until I get my self familiar with how things go on.


My appologies to all,
And specially to blade85, please accept my appologies to your humorous self

--------------------------

Valtiel.....I totally agree with you, and what adds to complication of the problem is the global nature of the internet, which involve multicultures into direct interface the thing can lead into serious conflects not just simple misunderstandigs. No one can realy make sure what could be an insult or what could be a joke!

hay....nice hardware you' ve got
--------------------------


zorg.............this is gonna be a tough job



________________________________________________


Now down to the real business.


Allow me to answer your last question blade85, yes i checked and rechecked the software you mentioned. The omega drivers proved themselves as good as the original ccc in being useless. Also the ati tray tools, showed only reports about the system, and didn't accept to change any settings.


what's realy keeping me wondering, is I tested the card ..........on the same machine.....on the same system, every thing worked fine, what was new to the scene; slipstreamming w2k sp4. I slipstreamed the sp into an fresh distribution share, made the iso, burned the whole thing to a disk then done the insatllation and to my surprise, the AGP wasn't there.


I searched forums, articles, stuff , read alot. But no sign of such a problem nor a solution, that's why I'm asking. I have two ideas in my mind about that; one the slipstreaming of the sp in w2k affects something in the w2k drivers, another is I have a PCI raid card which have bean there all the time but i guess it might be showing some bug or something, i didn't try installation without it. Also I might install some other system.


Oh... I forgot to introduce my graphics board,it's an abit 9550-cdt 256m AGP 4X/8X.....................................on a solano 2 chipset(could this have any thing to do with the problem?)


I guess that's all you're gonna need for now.

thanks again.

 

[TheGreatGrapeApe]

Is the issue about stability or is it just cause it says 4X and you want it to say 8X? If it's 4X or 8X on an R9550 it won't matter really if it's 4X. If it's a stability issue that's another story. For that first thing I'd recommend is blow out the old Drivers with DriverCleaner/DCPro

And when you have AGP/GART issues with the CCC the next thing I usually mention is to update your MoBo BIOS and chipset drivers. Most people don't do this, and most of the time this is the offending issue because the updated drivers have been updated to play with the new MoBo settings and if it can't recognize them it sticks in a stability default mode (likely 4X) which some times is annoying, and some times new changes conflict with older MoBo settings. This is something most people miss but fixed the issue twice for me (R9600P) and a friend (X1600P), as well as a few people I recommended it to online.

I always disable FastWrites but if you can't change anything in the SmartGart panel that won't help.

PS, did you slipstream drivers into your build or leave them out? You should always leave the graphics drivers out of a slipstream, but it's likely not the biggest issue. I'd just be sure to start with a fresh driver slate and use DriverCleanerPro to remove all old graphics drivers, and then update to the last one you knew was stable/good.

 

[d6xkr]

My mobo is a fujitsu seimens, and they stopped releasing updates cause it's old......a bit!. The last update to chipset was released in 2004 and I already applied it, do you think that the problem is with it and I should change it? if that's it, I predownloaded all the prereleased bioses (about 11 or some). And changing it is a matter of copying a floppy disk, nothing more. That's for the mobo.

For the w2k slipstreaming microsoft updates is something and patching the build with thierd party software is another story. The great differences are in that, microsoft updates disasseble themselves inside the folders of the distribution share replacing the older files then rgister thier components into text files read by the insataller. But patching third party stuff is to put the whole files inside a folder, then register it in a text file called GuiRunOnce which will tell the system to install your software after the installation completes. I might consider disassimbling the drivers file and maybe try to merge it(it won't be realy slipstreaming, more like injection).

I'll see also about the mobo drivers, I'll try all what I've got.

 

[TheGreatGrapeApe]

I wouldn't bother if there's no newer MoBo bioses/drivers, rolling back helps rarely compared to moving forward. It's usually that the GPU Maker uses the latest version for their latest drivers.

If anything I'd try rolling back the graphics drivers (remove the old with driverclear then install your last known stable version). I wouldn't waste time, re-slipstreaming unless all else fails.

So is it that your system is unstable or just not allowing 8X?

 

[d6xkr]

Not allowing AGP at all, but leaving PCI fastwrites. The slider of the AGP accelelration serve more like an accessory rather than an advanced settings button.

 

[d6xkr]

Hello ppl,


I solved the problem , it turned out to be with the AGP Bus itself rather with the AGP graphics board. I tried windows xp, also windows 2008 server longhorn. They both worked fine, with full acceleration and aero in longhorn like vista. which made me wonder more what is the problem if every thing is working.

Suddendly I discovered that I had to install some driver from intel called "Intel INF drivers" so as windows 2000 could detect and operate AGP bus. I downloaded it and installed it, now i have full graphics acceleration on my w2k workstation and the ccc is working just fine. Nevertheless, I want to say that I posted a ticket to ATI support and they werent helpfull at all, no body even tried to ask what is the problem?


I also found a post on msfn on how to integrate the drivers in the installation disk so as to make the w2k by it self detect and install AGP bus without the need for updates, here is the URL

http://www.msfn.org/board/slipstream_Intel_INF_updates_t13854.html


I wish that somebody can make use of this!

Thanks again!

And TheGreatGr apeApe IT REALY WAS because my board was intel's solano, also I don't know if the same prob/sol works for chipsets from other vendors or not.

Now I guess I'll work on injecting the graphics drivers into the installation.

 

[TheGreatGrapeApe]

Ah yes the silly intel-AGP issue, yeah pretty much every AMD mobo had that note when installing Windows. Not something you would think about immediately, especially for an intel board.

Weird, but good to know, thanks for sharing the solution, filed it away along with the MoBo into my memory of the various issues for it.