I finally tried what I was planning, and with a 910rc1 install, I uninstalled CCC, and then installed CCC from 804 and it worked.  tongue  I've been meaning to try it for a while and now I feel more the dummy for not having done so sooner.

So I'm fine with considering this to be my solution and moving on with life.

I also really appreciate the help I've received, and I'm more then happy to continue debugging if there is interest.  Just let me know what you'd like me to test.  I'd still welcome getting to the bottom of this issue and potentially help others avoid this problem.

If you think that specific combination will solve it, I'll give it a try.  However, I already did try something very safe and minimal as noted in post #11 of this thread, and I did determine in post #24 that the 8.04 Graphics Packs works perfectly in that configuration, leading me to believe that it is an issue with the driverpack changes between 8.04 and versions since then (I've tested almost every version since then without success), and not with my minimal OS install set.

Don't get me wrong, I'm happy to try it if you think it might work, I just wanted to remind you what I've already tried.  I know you're busy fixing everyone's problems, not just mine.  big_smile  And I do appreciate you giving some time to me! wink

I'm still looking for a solution to this.  I tried the latest RC's yesterday:

DP_Graphics_A_wnt5_x86-32_910rc1.7z
DP_Graphics_B_wnt5_x86-32_910rc1.7z
DP_Graphics_C_wnt5_x86-32_910rc1.7z

Same results as with 9.06.  I have not tried installing the 804 CCC with the 910 driver.  I guess I can try that if there aren't other recommendations.

Thanks

Thanks again for all the help. I finally was able to run the test today and success!  Using the 804 packs (A+B+C) I successfully have the CCC on my D600/Radeon 9000.

Now how to solve this using a current driver pack is the question.  Do you think I could install the 9.06 packs, and then simply install this older CCC after the fact?  What do the experts recommend?

Again, many thanks!!

DizzyDen wrote:

Try implementing everything except HID pack.... I believe the issues lie within that pack.

Skipping or including HID doesn't seem to make the difference for me.  It really does seem to track to the quantity of drivers, not any specific pack.

Thanks!  I won't be able to test it again until next week, so please don't misinterpret my temporary silence.  I definitely will try them and report back. Your help is very much appreciated.

OverFlow wrote:

I am beginning to belive we have exceeded the max size allowed for a registry entry in windows XP...

working on verifying this now... (I belive the max size for a single reg entry is one megabyte)

Is there anything more I can do to help confirm this is the issue?

I've now figured out what SAD is. tongue  I've been using DriverPacks for a long time, but I run it from the command line, so I've only ever noticed the options in the default comments of the DPs_BASE.ini.  Perhaps a future base release can update those comments for dumb people like me to include mention of SAD as an option?

So going on the suggestion of SAD for 3rd Party, is there any thoughts of including that automation as an option in the BASE so that running it once will both integrate the main packs and SAD the other packs (perhaps setting SAD to run automatically after the finisher)?

I'm just looking to see if I can work back to a release that doesn't have my problem, so I can figure out where the issue occurred.  If I'm not crazy (which is possible smile ) I had CCC working on this Dell D600 in the past via driverpacks...I just can't seem to remember which packs worked.

mr_smartepants seems to be trying something for me, so I'm happy to wait and try that before turning back the wheel of time smile.

You guys are just so darn helpful, I really want to do my part in contributing to the debug effort.

I can't say it enough, thanks!

OverFlow wrote:

Most all of our DriverPacks are available on the home page since the move to the new drupal based website... Click the "drivers" tab and select "Browse all releases" You may select any release you like... If you find one is missing let me know and i will see that it is made available big_smile.

I tried picking the 8.04 Graphics packs and got the following error on each:

404 File Not Found - SimpleCDN Upload Bucket

o5.76

Same with some other random attempts.

Thanks OverFlow and mr_smartepants!

I have some new testing results to report.  I found an older CD with A-8.10.2,B-8.10,C-8.10.1.  I tried this and now I get the ATI icon in the system tray.  I also get all of the ATI-specific tabs added to the advanced display settings.  Unfortunately, CCC is installed, but behaves just like before--it does nothing.

So I guess my success months ago was with something older.  I'll download something older and try that.

Thanks again.

Tried 9.06, no good.  I guess I'd been using something earlier then that in the past.  Is there an older version somewhere?  Do you hack CCC to work with different drivers?  (Meaning, could I grab the old driver package from Dell's website, and just install the CCC from that, keeping the newer driver that's in the current driverpacks?)

Thanks for your help!!

No ATI icon in the system tray.

I don't get any visible errors when I try to open CCC and don't see any errors in the event log.

Is there any repository of older CCC versions out there somewhere that I can use to attempt regressing CCC?

Other suggestions?  I feel like I last imaged this machine between 6 to 12 months ago and it worked fine.

Was any problem ever determined here, because I think I'm having the same issue?  I have a Dell Latitute D600 (yes, it's old).

PCI\VEN_1002&DEV_4C66&SUBSYS_011D1028&REV_02\4&1BFA44D4&0&0008: ATI MOBILITY RADEON 9000

The driver successfully installs, and the ATI CCC seems to install, but it doesn't work.  To clarify, if I right-click on the desktop, it is a menu option.  It's also in my start menu programs group, but no matter what I choose in that folder, nothing happens.  The CCC never opens.

At first I though it was a .NET issue, so I've spent a bunch of time and I think I've eliminated that.  I did the following:

Clean XP SP3 CD.
RVM with only user_hidden's update pack.
RogueSpear's Runtimes V3.5.1 for .NET 2.0 installed during SVCPACK
DriverPacks with all the main packs and without any 3rd party packs.

This is about the simplest scenario I can come up with: .NET installed in SVCPACK so a nice reboot before the DP Finisher runs.

I put my DP log,Finisher,HWids in a zip file here if that helps.

Any ideas?  Thanks!

64

(24 replies, posted in DriverPack Graphics)

Just reporting that the latest nightly seems to work fine for me without having the problem in this thread.  Thanks!

65

(24 replies, posted in DriverPack Graphics)

I was looking at the nightly and noticed that there isn't a nvhotkey.dll file anymore, so I guess the lastest driver can't have this specific problem.  wink

Two step process with the 3rd parties as a second step sounds good to me.  As I said in my initial post in this thread, running DP_Install_Tool.cmd after the failed install works great, so I think having all the main packs detected during install is better.

What is "SAD"?  I've been thinking I need to hack DP_Install_Tool.cmd to achieve this.  Is there a better way?

That makes sense, since from my testing it seems to be more of a quantity issues, than any correlation between packs.

So that leads to the obvious question, is there a way around that limit?

68

(24 replies, posted in DriverPack Graphics)

Has there been any further progress on this?  I too am trying to install on a Dell D630c and I'm having the exact same problem.  It seems that the file nvHotkey.dll just doesn't copy to the system32 directory.  I guess I'll just implement the fix above posted by mr_smartepants?  Any other comments or things I should try?

I'm still working on trying to find the conflict here.  Thanks to mr_smartepants my testing is going faster!  I'm also trying to test on different systems to see if the error is hardware dependant.

Where I'm at currently, the following works:

All BASE packages plus the following 3rd Party packs:
DP_LCD_wnt5_x86-32_810.7z
DP_Misc_wnt5_x86-32_90322.7z
DP_Modem_wnt5_x86-32_90805.7z
DP_SmartCardReader_wnt5_x86-32_80228.7z
DP_Graphics_A_PhysX_wnt5_x86-32_906.7z

Adding more 3rd Party packs then this seems to cause problems, but I'm still too early in my investigation to blame another pack.  I'll report back when I have more info.

Not sure I understand, but perhaps I wasn't clear about what I was doing.  I took a clean source (clean CD...no nLite/RVM), integrated all the non-3rd party packs, and created an WXPVOL_EN directory.  From there, I started with that WXPVOL_EN directory each time, and re-ran DPs_BASE on that directory simply adding or removing files from the 3rd party directory.

@mr_smartepants: are you saying I can add 3rd party driverpacks without re-running DPs_BASE?

Well, I found that I could re-run DPs_BASE having it add the 8 packs above 1 by 1 and everything kept working (I assume each time it uninstalled all the driverpacks and started over).  Then I went and added the HID and printer packs together...failure.  Then I tried each alone...failure.  Then I removed both...failure (which had succeeded before).  So either I was sloppy and didn't do what I thought I was doing, or this process has some error.

To eliminate (or reduce) human error, I'm starting the process over.  I have a new clean install with just the non-3rd party packs...success.  So now I'm going to keep a copy of the last working install, so I don't have to remove 3rd party packs.  I'll report how that goes.

Well, testing hasn't gone quite like I had hoped.  I did my testing by simply rerunning DPs_BASE on the same clean source until I had a problem.  I had the following 3rd party packs added without incident:

2009-08-24 14:11:20 : <INIT> 	Detected 3rd Party DriverPack Graphics A PhysX 906!
2009-08-24 14:11:20 : <INIT> 	Detected 3rd Party DriverPack JL-Blackberry 808!
2009-08-24 14:11:20 : <INIT> 	Detected 3rd Party DriverPack JL 809 Phone 80207!
2009-08-24 14:11:20 : <INIT> 	Detected 3rd Party DriverPack LCD 810!
2009-08-24 14:11:20 : <INIT> 	Detected 3rd Party DriverPack Misc 90322!
2009-08-24 14:11:20 : <INIT> 	Detected 3rd Party DriverPack Modem 90805!
2009-08-24 14:11:20 : <INIT> 	Detected 3rd Party DriverPack SmartCardReader 80228!
2009-08-24 14:11:20 : <INIT> 	Detected 3rd Party DriverPack WebCam 90513!

I then added both of the following:

2009-08-23 15:32:57 : <INIT> 	Detected 3rd Party DriverPack HID 90808!
2009-08-23 15:32:57 : <INIT> 	Detected 3rd Party DriverPack PrintersCanonInkjet 61105!
2009-08-23 15:32:57 : <INIT> 	Detected 3rd Party DriverPack PrintersCanonLaserjet 61020!
2009-08-23 15:32:57 : <INIT> 	Detected 3rd Party DriverPack PrintersHP 71126!

and nothing was detected (same as my original post).

Unfortunately, this is where I started getting confused.  First I removed the HID...failure; then I removed all the printers keeping the HID...failure.

So this is where I'm at.  Either I was sloppy, or not using a completely fresh source each time plays some role here.  I'm now trying to repeat my success from this post with a complete fresh source to see if I can repeat that.  I'll report back when I have results.

Testing update...

Without 3rd party, everything works:

2009-08-22 18:14:16 : <INIT> 	Detected DriverPack Chipset 902!
2009-08-22 18:14:16 : <INIT> 	Detected DriverPack CPU 804!
2009-08-22 18:14:16 : <INIT> 	Detected DriverPack Graphics A 906!
2009-08-22 18:14:16 : <INIT> 	Detected DriverPack Graphics B 906!
2009-08-22 18:14:16 : <INIT> 	Detected DriverPack Graphics C 8121!
2009-08-22 18:14:16 : <INIT> 	Detected DriverPack LAN 8121!
2009-08-22 18:14:16 : <INIT> 	Detected DriverPack MassStorage 901!
2009-08-22 18:14:16 : <INIT> 	Detected DriverPack Sound A 907rc1!
2009-08-22 18:14:16 : <INIT> 	Detected DriverPack Sound B 907rc1!
2009-08-22 18:14:16 : <INIT> 	Detected DriverPack WLAN 806!

Added the following 3rd party packs (to get my my remaining unsupported devices) with success:

2009-08-22 18:14:16 : <INIT> 	Detected 3rd Party DriverPack Modem 90805!
2009-08-22 18:14:16 : <INIT> 	Detected 3rd Party DriverPack SmartCardReader 80228!

I'll continue to add 3rd party packs until it breaks and report back.

OverFlow wrote:

Unfortunately we have several reports of similar issues by the testing team...

No one has been able to isolate the issue to a single pack...

The possablility exists it is a conflict between two third party packs...

the best advice we can offer is to try it with half the 3rd party DriverPack and then the other half. try to isolate it to a group first then narrow it to a pack or a limited combo of them...

the more info that is reported on this the faster we can get to the answer... if you have time we would love to hear more of your results.

It helps us to help you, and everybody else too wink

Binary search pattern...lots of fun sad

I'll give a few installs a try and see if I can find something.  I may try to be more strategic than simple binary though smile  I gotta hope I get lucky...binary searches take a while...

I am happy to do my part in fixing though, which is why I already tried it without the 3rd parties. smile

Thanks to everyone involved!!!

I did an install without any 3rd party driver packs, and that seemed to solve it (even the video was found).  So now my question is can anyone shed any light on how to find the offending pack(s) other then spending hours adding/removing packs to find the conflict?  Also, I thought 3rd party packs should only add more options to find drivers, not prevent any matches...does this failure mode make sense?

Should I post my logs from this success?

HWIDS post install without 3rd party.

PCI\VEN_104C&DEV_8038&SUBSYS_01871028&REV_00\4&2FA23535&0&0DF0: PCI Simple Communications Controller
PCI\VEN_10DE&DEV_00CC&SUBSYS_019B1028&REV_A2\4&27EA4097&0&0008: NVIDIA Quadro FX Go1400
PCI\VEN_14E4&DEV_1677&SUBSYS_01871028&REV_01\4&2959CBDC&0&00E0: Broadcom NetXtreme 57xx Gigabit Controller
PCI\VEN_8086&DEV_266D&SUBSYS_542314F1&REV_03\3&61AAA01&0&F3 : PCI Modem
PCI\VEN_8086&DEV_266E&SUBSYS_01871028&REV_03\3&61AAA01&0&F2 : SigmaTel C-Major Audio
PCI\VEN_8086&DEV_4220&SUBSYS_27218086&REV_05\4&2FA23535&0&18F0: Intel(R) PRO/Wireless 2200BG Network Connection

(Note it doesn't find the SmartCard or Modem since they are only in 3rd party packs)

I'll take another pass without 3rd party packs as suggested above and provide the results.  Thanks for the help.