1,501

(32 replies, posted in Other)

I'm pleasantly surprised, larciel smile

It's indeed the case that it seems easy in the end, but under the hood it's quite often very complex. For example DriverPack MassStorage, on which I'm working now. RogueSpear, the poor guy, had to hear a rant from me about my frustration with nVidia's crappy drivers, and Intel is turning to the same dark path... 3ware drivers aren't the best either. And not to speak about Promise.
Hey, that's another rant... sad Let's just say this project is often VERY frustrating while getting almost nothing in return.

Kind words are nice. Kind words are necessary when doing this kind of donationware project (not receiving many donations either, that might have been a stimulus). But so is some money. You can all scream money is not the most important thing. I agree. But without money you couldn't live either. Put yourself in my place. Would YOU undertake this kind of project, if you would only get kind words and enough money to buy something small every now and then?

To elaborate: my vacation has been spartan, I might say. I've had two weeks of summer job, during which I've been working on the new DriverPacks BASE every single night. I went out once or twice a week. Then there's been three weeks of 'vacation', i.e. enough time to work more than fulltime on the DriverPacks. I've been out several times, at nights, but have been working from 7-9 am to 22-23pm in general. For three weeks. That's exhausting, trust me. (A big thanks to my testing team is in its place here: they have made it alot easier and pleasant for me, and have definetely sped up things.)

If donations will go up short after the release, nothing will change. But if that does not happen, I will have to put ads online. Initially for everyone, but I'll work on removing them for those who have taken the effort of donating.

I do not plan on abandoning this project though. wink Definetely not.

P.S.: if someone who's into webvertising reads this, please contact me. I have to get a Google Adsense account but they seem to be denying my application...

@lieblingsbesuch: yes, I've made it so that 'B T S' (without the spaces), will be replaced by Bâshrat the Sneaky. Easier for me, easier for everyone who finds it. You're the first! Congratulations smile wink

1,502

(27 replies, posted in DriverPack Graphics)

mickmack wrote:

this is regtweak to fix it

[HKEY_LOCAL_MACHINE\SOFTWARE\NVIDIA Corporation\Global\NVTweak]
"NvCplEnableMultiGPUConfigurationPage"=dword:00000000

this to unfix

[HKEY_LOCAL_MACHINE\SOFTWARE\NVIDIA Corporation\Global\NVTweak]
"NvCplEnableMultiGPUConfigurationPage"=dword:00000001

This is a known nVidia driver problem, then?

ixian wrote:

I am getting the exact same error and no combination of config settings makes it go away.

is BASE .08 available in beta form to see if it's fixed?

I've made you a beta tester, as you asked wink

Welcome, ryanv smile wink

Please use code tags next time. And I know it's a bug, you can see that in the topic title and in my first reply. You can also see that it's fixed now wink

I estimate that 0.01% of everyone who uses a pc, uses MIDI software (which is what this hotfix fixes). Plus it can be unstable. That's enough for me to decide to NOT include this hotfix.

This hotfix is not critical/recommended either, so you won't get it through Windows Update, which again says how rarely this hotfix is needed! wink

lightsout wrote:

I've had a look at the supported hardware, and it drops support for some older RAID controllers it seems. Or I am being blind and missing these elsewhere?

; ICH5R - 82801ER
%PCI\VEN_8086&DEV_24DF&CC_0104.DeviceDesc% = iaStor_Inst_RAID, PCI\VEN_8086&DEV_24DF&CC_0104

; ESB - 6300ESB
%PCI\VEN_8086&DEV_25B0&CC_0104.DeviceDesc% = iaStor_Inst_RAID, PCI\VEN_8086&DEV_25B0&CC_0104

These will need to be updated, I suspect it'll support the 965 chipset Intel is releasing for the Core 2 Duo (Conroe) architecture.

You're very right. I will have to include THREE drivers now...

Then I guess there's a bug in the driver that causes it to write to a wrong memory address, which could cause this problem. My only suggestion is to use an older driver... I can't do anything to fix it.

RogueSpear wrote:

It's a request only hotfix so it would need a serious amount of testing.  The request only hotfixes with driver updates have given me a crapload of troubles.

Hmm... then I will not use it - unless Ryan can tell me it's safe.

1,509

(40 replies, posted in Other)

pyroman1 wrote:

So is the uAwiki officially abandoned?  I just updated it recently for the new GUI based 6.06.1.

It's not abandoned. I just think it's better to keep the OFFICIAL documentation/manual at driverpacks.net: that's less confusing.

coucou wrote:

In my both computers my graphic board is ATI, ill try later w/o DP_Graphic's, unless Bashrat could upload DriverPack_Graphics_A_V603

Regards
coucou

I told you you could use the current DriverPack Graphics wink It's compatible.

6.1.0.1002 is released, but the download link does not work... (at Intel's site)

EDIT: never mind, managed to get the file from intel.com

1,512

(76 replies, posted in DriverPack Mass Storage)

larciel wrote:

hey, it's just one stroke of a key wink

anyways, hope this mess gets cleaned by nVidia soon

Don't hope for that wink

They promised unified drivers for their chipsets... there are now TWELVE chipset packages... how unified roll mad

1,513

(76 replies, posted in DriverPack Mass Storage)

larciel wrote:

about nVidia mess, I just came up with this idea. I don't know how hard it'd be to implement it, so forgive me if this sounds like waste of time.

basically most problem lies with same HWID being shared by nf3 and nf4 solutions. (nf2 is fine right?)

then how about create two separate packs for nf3 and nf4, and integrate it to xp cd.

During install, if any one of those trouble HWID comes up, Setup prompts (like cmd window) for user input.   "Press 1 if you have nf3, press 2 if you have nf4.. etc)

User will input what setup they have, and the setup will call appropriate drivers.

Just my thoughts smile

That would completely void the concept of an unattended installation, and would be simply unacceptable for professional deployment. But I'm working on another idea that I got while I was typing the post above...

1,514

(76 replies, posted in DriverPack Mass Storage)

1. DriverPack Chipset
-ALL Chipset drivers are put together, to support ALL hwids. The theory behind this is easy: although there may be newer versions of drivers for specific Chipsets, old hwids are STILL supported in the newer .inf files. That implies that the newer drivers do support the older devices, which may seem to NOT be supported officially through this drivers.
I've been using this approach for a very long time (at least more than a year) and so far it has always proved to be working.
-Note that the nVidia Ethernet and nVidia Audio drivers are included in DriverPack LAN and Sound, respectively.

2. DriverPack LAN
There are only problems with nForce 3 drivers, that share some hwids with nForce 4 ethernet devices and therefore get the wrong drivers installed, resulting in an unusable networking device, that cannot even be disabled anymore...

3. DriverPack MassStorage
-nVidia's mass storage device drivers have been bad since the nForce 2 days: the well-known IDE filter driver that caused so many problems. That got fixed. Then nForce 3 got released, and the drivers were good. nForce 4 showed up, bye bye unified drivers, hello problems. That would not have been a problem, if nVidia wouldn't have decided to MAKE it a problem. They're reusing the same hwids for incompatible devices. Pure misery.
-My policy is to always have the latest drivers. But above that, there is stability. If I can make everything work in an out-of-the-box way and thereby not be completely up-to-date, then I'll choose that path. But that hasn't been the case for the nVidia mass storage devices for a long time (it HAS been that way though).
-As many will agree, I've invested a LOT of time in trying to find THE best solution. But there isn't. I don't remember who found it, but there is someone who found that you could use the mass storage drivers for nForce 1/2/3 for nForce 4 too. Ever since, most installations do succeed, but SpaceCommanderTravis' installation did not, unfortunately.
-I have contacted nVidia several times, but of course I've never got a reply.

General conclusion
If someone can come up with a very reliable solution, I'll implement it. But I have already spent so much time on the nVidia issues that I can assure you that the problem does not lie in our methods, but in nVidia's. The very least they could do, is at least provide a guide how you could make ONE install disc for ALL nVidia platforms, in such a way that all drivers would be up-to-date. Since it's their fault they've made this mess. As far as my experience goes, this problem is not to be solved in a good, clean way. It can only be solved by applying hacks.

P.S.: kudos for hmaster10. If that method seems to be working, that'd be great. But can you imagine that ALL sysadmins would be prepared to do such an awful lot of efforts to get JUST ONE system installed? In that same time, you'd get many other systems installed, if they weren't using an nForce 3 or higher chipset.

Could you please post your HWIDs? That might be helpful. Check my sig for a tool to find them.

No. The 'DriverPacks Method' page is the page where you can choose the method that should be used so Windows can find the drivers from the DriverPacks. Some interesting links regarding that:

[uawiki.org] Plug 'n Play drivers: Common Method/Via winnt.sif (method 1)
[uawiki.org] Plug 'n Play Drivers: Drivers From CD/DVD (method 2)

The Finishing method however (which will be renamed to 'Finisher Method' as of version 6.08, since there will be a new stand-alone program to handle it, called 'DriverPacks Finisher'), sets the method that will be used to execute the DriverPacks Finisher: this program handles all exceptions (mainly control panels, but it also fixes some drivers that would always get installed incorrectly), KTD and the cleanup.
GUIRunOnce executes just after the first logon, and so does RunOnceEx. The only difference is that RunOnceEx shows an installation progress. The option 'custom' allows you to set the execution of the DriverPacks Finisher manually. Here are some links with detailed explanations:

[uawiki.org] GUIRunOnce
[uawiki.org] RunOnceEx

And no, your own GUIRunOnce entries will NOT be overwritten. Nor will your RunOnceEx entries be overwritten.

1,517

(2 replies, posted in DriverPack WLAN)

Of course smile

Since you're obviously using the DriverPacks to save time, for professional goals, please consider making a donation! Although there are many professional users, only very few seem to do the effort of doing that... It would be very much appreciated! wink Of course only after you made sure it IS indeed a working product wink

1,518

(3 replies, posted in DriverPack CPU)

I had NEVER heard of it! yikes Will be added in the next update of DriverPack CPU (not Chipset...)

Topic moved to DriverPack CPU.

Ah... tongue I'll add them in the next update, probably! wink

McStarfighter wrote:

@Bashrat: Check my first post again. It isn't a DP, it is only the installer package from Apple which contains the Mac Drivers for XP.

Well, I have already received the drivers themselves from djbe. So I could make a DriverPack out of it wink

muiz3 wrote:

"due to a lack of donations" i did my best m8 sad

You're probably the best donator wink You definetely did your best! Thanks again smile

muiz3 wrote:

you just updated graphics A and CPU ,and CHIPSET didnt you? well those are not from the old system.
Now read my post again wink

I have read it well wink

muiz3 wrote:

just put some old driverpacks in the driverpacks folder , and start  base

Old DriverPacks, that use the old naming system, are not supported. You know that wink

McStarfighter wrote:

I'm uploading the Macintosh Driver Pack for XP at the moment to Rapidshare. I someone wants to create a DP, so do it.

I'll post the link, when uploading is ready.

Check the sticky in the 3rd Party DriverPack forum wink

I've moved this topic to there, too.

Should have been posted in the Betas forum. Topic closed.