451

(17 replies, posted in Universal Imaging)

The Intel issue was fixed by the new masstorage pack, Jaak splited the driver in three distinct folder so it support all Intel SATA controllers. Make sure you update your mass storage section in sysprep.inf when you update the Mass Storage drivers. If the sysprep dont shutdown your PC or runs forever it is because you have HWID or non existing INF pointing in your syspep.inf file.

I am not sure where you got the drivers you are using in the newer packs, the newest I could find on Creative site is the one I am utilizing.

The driver in CR\1 folder is for Creative X-Fi series. I noticed along with Jaak that this driver support the same devices has the one previously in CR\2. So the X-Fi driver can support the soundblaster audigy, audigy 2 and audigy 4. The only non-supported device would be the x-fi fatality because its use it's own driver, since just a few use it its not critical. It might be supported, but we need to double-check.

Muiz reported issue with the creative drivers with the test pack so I really appreciate your help. VIA has new driver so I will wait for your changes for the next update.

Here's the changelog so far.

7.09.3 (20 Sept 2007)
Updated
- R\2 Realtek HD Audio from to 09/05/2007, 5.10.0.5477 [1.76] to 09/11/2007, 5.10.0.5480 (1.77)(Muiz)

7.09.2 (17 Sept 2007)
Fixed
- INI updated to prevent mismatched exception executions. (mr_smartepants)

7.09.1 (11 Sept 2007)
Updated
- R\2 Realtek HD Audio 08/28/2007, 5.10.0.5473 (1.75) from to 09/05/2007, 5.10.0.5477 [1.76] (JakeLD)
- V\1 VIA Envy from 01/12/2006,5.12.01.3650 to 03/15/2007,5.12.01.3652 [5.20b] (JakeLD)
- V\2 VIA AC'97/Vinyl from 10/03/2006,6.14.01.4180 to 06/27/2007,6.14.01.4200 [7.00b] (JakeLD)
- V\3 VIA HD Audio from 09/18/2006,5.10.01.1080 to 06/06/2007,6.0.01.1240 [3.40d] (JakeLD)

Fixed
- CR\2 Removed folder, already covered by CR\1 (JakeLD)
- Moved CR\3 to CR\2 (JakeLD)
- INI updated (JakeLD)

That's good news. big_smile

454

(9 replies, posted in Universal Imaging)

Bigfoot, i use sysprep drievr scanner instead of devpath.exe and it runs before the whole sysprep process so my drivers have to stay in the same location (C:\D) If they get moved, it's over.

You can change the OEM info (my computer>properties)with sysprep driver scanner, that's the only reason why I use it.

455

(17 replies, posted in Universal Imaging)

I have a question, why you don't use all entries provided by the -bmsd switch in your [SysprepMassStorage]. Are the ones shown above enought to support all IDE controllers ?

For your HAL issue, you could use mysysprep.exe its much more simple. You could also use the driverpack "method" to install your drivers at 1st boot, refer to this post: http://forum.driverpacks.net/viewtopic.php?pid=11958

mysysprep.exe: http://jimtsay.googlepages.com/mysysprep

Another question, have you experienced any problems when sysprep is running and installing the Network Components ? Sometimes this part of mini-setup can take up to 5 min on certains PCs. I will try this and let you know.

[Networking]
    InstallDefaultComponents=No

[NetClients]
    MS_MSClient=params.MS_MSClient


0x00000007E issue fix
http://www.runpcrun.com/0x0000007E?page=1

I already sent that driver to Jaak big_smile

457

(9 replies, posted in Universal Imaging)

Plus yours entries for your drivers location in regedit wont be the same anymore.

No idea, jaak could help mebbe. Can you sent me your changes I will integrate it into the Input pack.
email: jakeld@gmail.com

Good job and thank you.

Yes, i'm pretty sure it's the issue. The thing is almost all drivers use that specific HWID so many INF needs to be edited. Plus I think windows drivers can handle ACPI\PNP0303 & ACPI\PNP0F13 without added drivers. Work in porgress.....

To post your HWIDs use the save_hwids.exe located in my sig.

Download is broken, 404 error. Is this part of the new forceware drivers ?

Can you provide the HWID of your device? Use the save_hwids.exe tool located in my sig.

I did integrate the driver in the test pack and did the necessary changes.

Test it and let me know, great suggestion btw thx again.

464

(3 replies, posted in DriverPack Sound)

Your device will probably be supported by the test pack. give a shot and let us know.

465

(2 replies, posted in DriverPack Sound)

I looked into hp website, there is no audio driver for XP. I downloaded the vista one and its only for vista, so unless you find me an XP driver or they make one, there is nothing i can do to help you. Sorry. maybe you could search for "open source drivers" or third party drivers, if you find any provide the link here here.

I sent you an email.

Sound Pack B:
http://dev.driverpacks.thesneaky.com/dr … 32_7104.7z

Since there is so many requests and issues with the soundpacks, me and the rest of the team made quite progress on the sound packs. So anyone who had issue/request in the past please try the new "Test Packs" and leave feedbacks here. We needed a fresh post to centralize all issues/requests because right now I'm getting lost. Please be specific and provide the HWIDs of your non-working devices.

test pack:

http://dev.driverpacks.thesneaky.com/dr … 32_7091.7z

469

(3 replies, posted in DriverPack Sound)

This manufacturer use sound chip by creative and c-media. They are maybe already supported. My suggestion is, test it and if use any issue post your HWIDs list (using save_hwdis.exe in my sig) and your exact sound card model.

Not yet, its a good thing you reminds me. Jaak just gave me the documentation in order to make your panels works. I'll give a shot and see what happens.

This one will be included in the next release.

I think I found the issue. In the Sound Pack A, the CR\1 and CR\2 folder cover the same hardware device (HWID), including your sound card. So the duplicated HWIDs in wdma_emu.inf is probably causing the issue. I will release a fixed update pack probably tonight or in the next days. Since there is like 100 requests i'll try to do as much as I can tonight. If you are rush, you can remove manually the CR\2 folder. Try that for now, I'll post the link when the updated pack is ready. And plz give feedback if it works!

Can you tell the specific creative sound-blaster x-fi model you have ? There is more than one. A link to a working driver would be appreciate too.

474

(8 replies, posted in DriverPack WLAN)

So should I integrate the driver into the pack or no ??

475

(8 replies, posted in DriverPack WLAN)

Never minds, I found the driver but it's for bluetooth 2.0 so I don't know if we should integerate it to WLAN, Input or Misc pack ? What's your opinion jaak ?