Jump to content

rgreen83

Member
  • Posts

    52
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by rgreen83

  1. Dont just say "I fixed it on my own" share how you fixed it so that the next person to read this thread will find the answer you may already know.
  2. That shouldnt be it since x64 has its own driver package anyways doesnt it?
  3. Maybe unknown devices could help you? its here http://www.halfdone.com/Development/UnknownDevices/ Make sure you update the pcidevs.txt per instructions first.
  4. Maybe compressionbin from the unattended guide?
  5. rgreen83

    Nlite Noob Help

    maybe for a different post?
  6. rgreen83

    Nlite Noob Help

    As far as I know, it has yet to be determined how to get nlite to work with dell oem cds. heck even slipstreaming sp2 is nearly impossible on them! Honestly I would say that the benefits will not be worth the rewards for this endeavor. Sorry!
  7. rgreen83

    Nlite Noob Help

    can you edit that with paragraphs so i can read it? it hurts my eyes. love to help you out if i can!
  8. Maybe I am missing something, but where does it even say where on the cd to put the ATIRARSFX.exe? Also I just see setup.exe, *.dat, *.cab, *.dll, and an *.msi, in the ccc folder, no *.reg files to customize. Also the radclocker.msi (its actually named radlinker.msi) is in windows\installer directory. The guide is pretty old, and 5.3 just came out, maybe it could get an update?
  9. if you delete the windows drivers, it wont be able to use them right?
  10. Been awhile since any news, any updates on v3 progress?
  11. @prathapml: maybe my post was confusing, I didnt know that you made your own drivers, I was referring to omegas. @BTS changing the infs would be the same thing that omega does already, either way it will make the drivers non-whql.
  12. The omega drivers is only a modified INF I think? All DLLs are same?just asking... That's possible... I'll investigate that later this week... Yup, old CPL is good. The new CCC package based on .net seems not needed at the moment - plus, including the .net driver will not allow auto-detection based on INF (oempnpdriverspath) like we do currently. Well, the auto-detection wouldn't be the problem! There's no such thing as a '.Net driver' . It's just the CCC that's .Net... So I'd only have to edit the Graphics_Control_Panels.cmd file and add the installer... But that takes some MORE space, which I don't want No need to apologize here, just was giving a suggestion. I only thought maybe ppl would download the CP of their choice and it would be integrated during the batch process, just concerned for your bandwidth is all! prathapml is right about omega drivers only being modified .infs, this does mean they will not be whql though if that matters. I use his set myself and have never had an issue, they are even supported by ATI if only unofficially. Therefore I use the old control panel that is included, but new features in the future will be CCC only, such as the auto-overclocking tab similar to the coolbits tweak, so more ppl will eventually begin using it. I think it may be polite to discuss using omegas drivers in the pack with him, just as a gesture of good will if nothing else. I do also like the idea of the seperate drivers for ATI and Nvidia, this would probably reduce the strain on your bandwidth considerably seeing as these are probably two of the largest sets of drivers.
  13. I think since the ATI driver and CP is obtainable seperate, it might make sense not to include the CP. Also because ATI has two CPs now, the old one and the new CCC in .net. Many would have to uninstall the CP you included to install the CCC. Possibly just make a guide for ppl to get their CP installed silently after install is completed?
  14. How difficult is it to make it so this program will run on a machine with only .net 2.0? I dont run 1.1sp1 because it screws up the ATI CCC.
  15. if you mean the full pack of WLAN drivers, you cant, Bashrat hasnt finished it yet. he is going to very soon though!
  16. Maybe you missed this page? it says WLAN drivers down in the lower right http://www.easytel.fi/en/index.shtml
  17. I or anyone else could send you the newer drivers but that would seem to violate your "official website only" policy. I only have one wireless controller yet in C:\Program Files\Microsoft Broadband Networking\Drivers I find drivers for all models ever offered. I firmly believe installing the software directly from microsoft is the best method. I believe what the program checks your model for is to look for firmware updates, which the software is also capable of updating.
  18. How are you certain that the drivers on the CD are the latest and support all models?
  19. Bashrat, I have used a microsoft wireless g card for a long time now, and believe me there is no way to get the drivers except to download and install the MSBNSoftware.exe and then run the update file. you may then copy the drivers from C:\Program Files\Microsoft Broadband Networking\Drivers this is the only way that I have found anyways Edit: guess i should be more complete and add that the .inf and .cat files are located in C:\Program Files\Microsoft Broadband Networking
  20. I dont think you did anything wrong, it says extraction completed. I dont consider something an "error" unless it results in fire of some sort, that, or a portal opening to hell.
  21. Well, actually the size IS 1.91 MB... I'll change that in the first post And there isn't a 30 Sep update, I guess I changed some typo or something... EDIT: but there WILL be an update 6 October (Wednesday), 95% certain... whoops, im dumb, that was aug 30th It was the different file sizes that confused me! looking forward to wed, my new motherboard will be here thurs, so a nice new unattended cd with your new mass storage pack on it would save me a lot of time! Thanks a million!
  22. The driverpack on your webpage is still the old one @ 1.91mb, when will we be able to download the sep. 30th update @ 1.93mb?
×
×
  • Create New...