7.01.2 RC1 is in the Testing Team forum, which has this new feature and in which this problem doesn't exist at all. It should only take a couple of days before this new version is available.

Done!

@Debugger: can't we live WITHOUT this hack? I think if you just add the CC_0104 and CC_0106 suffixes, that would work as well.

Protonus wrote:

So, since I'm a total noob to the driverpacks.. I'm assuming what you're saying is the next version of the driverpack now will "solve" the BSOD with a 3112r ?  Do you know if it also solves the two different drives in a RAID 1 mirror setup, showing up as seperate partitions in the first stage of setup?   This was the other problem this distrib caused that others have seen including myself.

Also, if if this is fixed in the newest driverpack... how do I update my "eXPirence" DVD windows distrib to include this new pack?  See my previous post on page 3 for details on my distrib...

The only way we can assure you this problem is now fixed, is by you testing it. Nothing is sure in the world of drivers, I can tell you that much by now wink

ricktendo64 wrote:
Helmi wrote:

Heh, it was merely a small translation so I guess that's why most of us where so fast (plus the fact that you initially told us it was very little work so one one was scared wink).
Still, great to see most folks are still around regularly so they can respond on even such minor issues ASAP!

But I still do mine over by grabbing Bâshrat the Sneaky English.lng file and re-doing it all over again, just to be sure there is no incompatibilities in my Spanish.lng

Off Topic: How about in the future something like E-Mail Notifications to all team members that theres a Update Commimg soon?

I'm working on a revamped website which will make all of that and much more possible wink

EDIT: powered by drupal, by the way wink

@Pedro80: thank you very much for the detailed report! After scanning through all previous posts, the general rule seems to be that you're all using RunOnceEx as the Finisher method. Now this itself shouldn't be the cause of this problem. I think the problem would lie in some of the other programs you're running. Are you running ANY program that COULD possibly perform a clean-up before the Finisher gets executed? Such as WPI or XPlode for example, or a self-written batch file?

If that's NOT the cause, then it must be the system variable that cannot be imported or something. Would you like to do another test run with a custom DriverPacks Finisher that logs the values of the system variables (%SystemDrive% in particular of course)?

EDIT: is now implemented by default in the next update of the DriverPacks Finisher!

Cause was tracked by muiz & ruudboek!

Topic closed.

It's solved now, thanks to muiz and ruudboek their great effort.

Thanks, all fixed now.

The pnp949r was a typo, but it didn't break anything though wink

++++++ wrote:

dooes the two methods take the same effect?

See the FAQ

jtdoom wrote:

so, if i remove these 3ware, Repack, and test on the Gigabyte royal wich has that sil 3132, I could be of help?
(this did a BSOD too... see)

note, the royal also has a Jmicron chip.. did that no have issues of its own? I sorta forgot.

Don't forget to remove the txtsetup references or it won't have any effect...!

muiz3 wrote:

YES.YES YES YES.......!!!!.. Ruud and I solved the Siliconimage BSOD mistery , after  LOTS of tests , we finaly know wich diver causes the BSOD....

Its the "3ware78k" driver...... or the "3waregsm" will do final test  today....

Time to test this on more machines....Bashrat?? big_smile

Maybe it caused more problems ,Jmicron , Nforce ...??


Ruud...thx again m8 !!! nice teamwork wink

WOW

Nice work!!!!!!!!!!!!!!!


Talk to the both of you ASAP on MSN.

Helmi wrote:

Heh, it was merely a small translation so I guess that's why most of us where so fast (plus the fact that you initially told us it was very little work so one one was scared wink).
Still, great to see most folks are still around regularly so they can respond on even such minor issues ASAP!

That's indeed very great smile

564

(13 replies, posted in News)

@midiboy: this has been reported already, but I haven't got the slightest clue on what could cause this. Check this new feature in the next development version of the DriverPacks BASE however: http://bugtracker.driverpacks.net/view.php?id=308. This is already working and muiz & ruudboek are working very hard on getting the Silicon Image problem (with the 3112r and apparently also the 3132) solved, so a new MassStorage DriverPack will be there very soon, which will immediately solve this weird bug as well.

565

(5 replies, posted in DriverPack Graphics)

You can update the drivers on your current system. Do this:

1) Extract DriverPack Graphics A.
2) Go to Control Panel > System > Hardware, now right-click your device and click "update driver".
3) A new window will pop up, "No I don't want to.... this time", then choose advanced and then navigate to <directory where you extracted>\D\G\A\1, hit ok and hit ok again. Now it should be installing the driver for you...

566

(5 replies, posted in Feedback and Support - DriverPacks Base)

theuni wrote:

i'm using powerpacker to make the cd, but i integrate using integrator, then use driverpacks base to insert the drivers... I dont actually use powerpacker to insert the drivers (haven't had good luck with it)

How can i use dpbase to slip drivers into an existing powerpacker-created dirstructure?

Thanks
TheUni

That would still work as I described earlier.

567

(5 replies, posted in Feedback and Support - DriverPacks Base)

Aha you are using PowerPacker.... well in that case you don't have to set up anything manually in the DriverPacks BASE I think. You really should ask in Siginet's forums if it's a PowerPacker question wink

568

(5 replies, posted in Feedback and Support - DriverPacks Base)

In short:
1) Create settings files for each multibootdisc platform you want to slipstream the drivers into. JUST CREATE THE SETTINGS FILES, DON'T DO THE SLIPSTREAM. Use the "Disc" platform to create these settings files.
2) Then select the root directory of your multibootdisc as the location, add all settings files you've created in the previous step and hit slipstream.

That's it!

@ricktendo64 & mickmack: great! Almost half of the translations have been submitted within 24 hours... which is great IMO.

BigBrit wrote:

p.s. Great work, how about giving me a January birthday present - MassStoreage ????
       All the rest was a wonderful Christmas present

We're working very hard on that, with 3 people simultaneously wink (To get the Silicon Image problems solved.)

And Romanian as well!

I found a bug (see issue #304) and therefore a version 7.01.1 will be put online now already, and your translation updates will be included wink

Thanks to all of you for updating so fast, that's really motivating wink

Relix wrote:

My system is just re-installed about 2-3 days ago, maybe some software cause this problem? if it is can you give it the list?

I have tried uninstalling some programs but no luck, If I'm not mistaken at the very beginning (pure) system (without any software installed, just windows) I can integrate it just find. Or is it because nlite?

I'm sorry, I cannot think of a single reason that my running my program could result in a reboot... I won't be able to fix this 'bug' I'm afraid... wink

kSaMi wrote:

french language updated & sent in the bugtracker smile

That's fast! smile

That is something I have never heard of... And I haven't got the slightest clue what could cause this.

The only thing I can ask is this: how long ago did you install Windows on this system? Because it's definitely unstable if a non-CPU-intensive program like the DriverPacks BASE can make your pc reboot...

575

(13 replies, posted in News)

A small list of new bugs has been reported for DriverPacks BASE 6.12 and they've all been fixed in this update, as you can see in the changelog at the bugtracker.

If you are using a different GUI language than English or Dutch, you'll get an error thrown at you because the translation isn't updated yet. Don't worry, it's just to WARN you for this. You can still use the DriverPacks BASE without any further problems or warnings.
The reason for not waiting for updates from the translators is simple: this update fixes some critical bugs that prevented the Finisher from working properly. Functionality fixes have a higher priority than translation updates.

Still some bad news though: apparently I didn't replace the flawed DriverPacks BASE 6.12 with its patched brother, in which the auto-updating issue was solved. Which means you still can't use that functionality to update from 6.12 to 7.01. It however really is fixed in version 7.01. I'll eat my hat if it isn't.

UPDATE:
Version 7.01 has already been replaced by 7.01.1 due to a small typo (see issue #304) that caused the DriverPacks BASE to crash. If you already have 7.01, the auto-updating to 7.01.1 should work without a problem.

Download the new version!