PowerPacker will soon support the new DriverPacks BASE. Until then, support is partially broken.

Doesn't Siginet mention this somewhere? :s neutral

1,777

(8 replies, posted in DriverPack Sound)

But it DOES seem to solve at least one other MAJOR issue: http://forum.driverpacks.net/viewtopic.php?id=79.

Nope. The problem is completely at my side.

The .log file SHOULD stay by the way wink

haha big_smile

So the beta driver did fix it?

Try downloading the latest beta X-Fi driver, I believe it's the 2.009 or something.

OK... you're right, this shouldn't happen.

But as it seems you're the only one having this issue (googling didn't get me any related hits), I guess the issue is located elsewhere. And according to the drivers page, I've got all drivers covered and up-to-date, with the exception of the ethernet driver.

EDIT:

Didn't see that last post... now THAT is strange! I really have to update DriverPack Sound A soon!

Checking their website...

1,784

(5 replies, posted in Other)

DevPath just scans for driver directories and then updates the DevicePath registry key.

So... just extract all DriverPacks onto a CD, run DevPath like this:

devpath.exe X:\

where X:\ is your CD drive and the DriverPacks are extracted into any of the subdirs inside X:\. Then just pop in that CD and it'll be very easy to install new hardware! wink

EDIT:

forgot to say: this 'mode' will be added after my exams.

Ehm... that's virtually impossible, but then again... this is Windows... Possibly an internally connected device? Does it happen to be an MSI motherboard? Since some of their models have a Bluetooth stick on their mobo by default and they are connected through USB.

Well... what USB devices do you have connected to your system?

1,787

(8 replies, posted in DriverPack Sound)

I'll check for updates to this driver.

Problems 1+2 were fixed in 6.05.2

Problem 3 is not related to the HDA fix (KB888111). I don't know what device that is though. Will look it up later.

Problem 4: what are you talking about? neutral Please clarify!

Problem 5: thank you very much. This has indeed not yet been solved (lost track of it, no complaints about it so I just forgot about it). It will be soon now! wink

Problem 6: thanks, was not aware of this. Solved in next version.

Problem 7: is already fixed.

@laura: thanks, solved in next version.

1,789

(11 replies, posted in Site & Forum Issues And Feedback)

hehe big_smile

Yes indeed... haven't been updating the user groups lately. I've added you wink

1,790

(9 replies, posted in DriverPack WLAN)

Toblerone wrote:

ty, i haven't tryed yet with the 6.05 but with the previous isn't supported wink

Well, then it won't be supported in 6.05 either. Will be in the next update! wink

1,791

(1 replies, posted in DriverPack LAN)

Changelog
updated
-Realtek 8139(A/B/C/D/8130)/810X/8169/8169S(B)/8110S(B) driver from 01/18/2006,5.639.0118.2006 [6.39] to 05/19/2006,5.641.0209.2006 [6.41]


Known issues
-none

Remarks
-none

Download

1,792

(2 replies, posted in DriverPack CPU)

Eh? You're 11 seconds too late tongue

http://forum.driverpacks.net/viewtopic.php?id=72 wink

1,793

(0 replies, posted in DriverPack CPU)

Changelog
-updated: AMD K8 processors driver from 1.2.2.2 to 04/28/2006, 1.3.1.0.

Known issues
-none

Remarks
-none

Download

- Update BartPE code to support pack updates from config in PEbuilder
- Add MD5 checksum support for BartPE down-loader

- Method 3 Install (Fragbert) http://forum.driverpacks.net/viewtopic.php?id=3323

- SAD
  - Beta Install By HWIDs tool, addon for SAD (llewxam)- in testing
      opens the possibility for creating per machine packs...
      I believe that per machine packs was originally RogueSpears idea.
  - Add GUI for Driver selection menu
  - Replace dp install tool.
      Combine install by HWIDs tool and dp_inst_tool into
      a single classier and proper EXE with an optional pack selection GUI for attended install.

- Add menu to GUI for selecting individual 3rd party DriverPack.

- Add menu to GUI for selecting individual mass storage drivers.

- Add "Reset defaults" and "copy DPs_BASE.log to Source" features (BigBrit)

- fix known PnP errors related to missing reg entries RE: Debugger, Galapo and cdob

- Option to create an ISO at the end of the slipstream



These are probably not getting added
- Vista Support x86  &  x64 (new app for this is planned)
- Win7 Support - for testing team  (new app for this is planned)
- QuickStream Cache Manager
- 64 Bit Driver support 2k3
- support for new platform: RIS (Currently supported by RogueSpears AutoImage.)


- [partialy done] Add new platform 'Attended' installation
  - attended install support is currently provided by SAD, see above

- [partialy done] Update KTD function and add SAD functionality

- [ALPHA] Support for new platform: SysPrep
     - Back to the drawing board...
     OffLine syprep (Galapo) is the prefered method
     of implementing DriverPacks for sysprep currently.



- [Nightly] - Add MD5 checksum support

- [DONE] Update the website with proper guidelines
- [DONE] BartPE Graphics, LAN and WLAN Support.  BASE ver 8.12.1 or newer.
- [DONE] BartPE Mass storage support for platform. BASE ver 7.52 or newer
- [DONE] Download buttons on UpdateChecker page 8.12.1rc
- [DONE] GUI Option to create a SAD disk (or network share). - 809rc1
- [DONE] Backup DPs_BASE.log files by adding date stamp - 809rc1
- [DONE] PreSetup.cmd - add on success/exit to drive letter search loop- 809rc1
- [DONE] nVidia Driver Control Panel options for BASE - 809rc1
- [DONE] Faster Un7Zip
- [DONE] support for new platform: multibootDisc
- [DONE] 'SAD disc' (Stand Alone Drivers disc)
- [DONE] multilingual GUI
- [DONE] create a proper 'installation finisher', instead of the crappy batch files now
- [DONE] choose custom KTD location\
- [DONE] abstracted and deeply modularized GUI framework, to easily add new platforms
- [DONE] reorder source files to easily add new platforms
- [DONE] set custom KTD cache location
- [DONE] better Driver Signing Policy Disabler
- [DONE] improve dummy setup

(Note that this list is incomplete and is constantly being updated!)

Implemented in DriverPacks BASE 6.05.3.

Make sure your script is named (or called by)

%SystemDrive%\3pscript.cmd

This file must be available during the execution of DPs_fnsh.cmd (which is called by fnsh_log.cmd). It will be executed just before the cleanup.

During installation.

I submitted this bug at the AutoIt forums and am awaiting response: http://www.autoitscript.com/forum/index … opic=26939.

I will rewrite DPs_fnsh.cmd to a real executable (no more batch file). Currently this simple logging system is used to find problems. The new finishing executable will be written after my exams.

1,799

(12 replies, posted in DriverPack LAN)

Us2002 wrote:

Sorry, for example: Realtek in pack DriverVer = 01/18/2006,5.639.0118.2006 but last released 05/19/2006,5.641.0209.2006 and 05/15/2006,5.646.0515.2006
1 ftp://152.104.238.194/cn/nic/rtl8139abc … (0519).zip
2 ftp://152.104.238.194/cn/nic/rtl8111brt … (0515).zip

q: why?
q: how many "examples" in new driverpacks?

I knew that. Check the second reply in this topic. wink

And what do you mean by "examples"?

@jr:

1. Just use the 'custom' finishing option wink

2. Will implement this.


@razormoon:
Yes, but jr is asking if I could add support for calling an external script as well. And so I will.