Please post your DPsFnshr.log, Apollo.

You must download all DriverPacks and then place them in the "DriverPacks" directory... wink

Could you please post your DPsFnshr.log?

I've just increased the limit from 250 MB to 400 MB, you'll have some headroom again now.

730

(1 replies, posted in Other)

Toolman wrote:

It's a pitty we can't help you (Basrat) troubleshooting, because it now comes down to a single .exe file for the finisher and base setup program ... sad

That will change soon smile wink [/sneaky mode]

731

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

That's the changelog for the next release...

But I agree, it shouldn't be listed there. I'll report this to the dev team of Mantis.

732

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

I'm currently working on site improvements, and that's definitely on my todo list wink smile I can't promise you a date though.

rayw69 wrote:
Bâshrat the Sneaky wrote:
Bionicmaster wrote:

in this mobo that mention, I had trouble to install O.S in SATA2 disc with JMicron connector, simply Disc doesn't boot, with or without drivers, Black Screen before Blue Screen Loads.... a real trouble, I was thinking in change discs, my SATA for boot and my SATA2 for info (my SATA in the ALI controller was recognized right, without any driver in IDE mode), thinking that my SATA2 disc was not able to boot, but a few days later, I changed my PC for an AM2 based A64, with nforce 410/Geforce 6100 based Chipset, and all is right, my S.O. is in SATA2 disc and all is right....

Experience: Jmicron is too bad...

Couldn't agree more smile

I will make the appropriate changes in DriverPack MassStorage, to reflect that JMicron is absolute crap: its drivers will NOT be loaded by default, brave souls will be able to renable them manually.

I don't think it is fair to call jmicron crap just because the txtsetup.sif file is not created correctly when using driverpacks.

I would agree with you, if this were the first time we had a bad JMicron experience. But I will look into that supposed txtsetup.sif error. I'd be very glad if that would solve everything, and then I would draw my words back as well. But I'm afraid we're not the only ones having this issue... Just google for JMicron BSOD and you'll find plenty of hits.

Must be an identical HWID issue and my guess is that this problem is therefore irresolvable.

The device did not work properly either, I assume (since you mention "code 10" in the topic title, and I think you meant "error code 10")?

This driver is currently missing. It was on a friend's mobo. Will be added in the next update of DriverPack LAN.

That means their sound driver is missing. 95% chance it's a Soundmax/Sigmatel driver. Just create a small DriverPack with that driver if you want it fixed really quickly.

Will be added to the next update of DriverPacks-b.

737

(4 replies, posted in Other)

You must not extract the DriverPacks, but simply copy them to the "DriverPacks" directory!

738

(32 replies, posted in Feature Requests)

Yes I used AutoIt, and that was also the reason why it failed to work.

Bionicmaster wrote:

in this mobo that mention, I had trouble to install O.S in SATA2 disc with JMicron connector, simply Disc doesn't boot, with or without drivers, Black Screen before Blue Screen Loads.... a real trouble, I was thinking in change discs, my SATA for boot and my SATA2 for info (my SATA in the ALI controller was recognized right, without any driver in IDE mode), thinking that my SATA2 disc was not able to boot, but a few days later, I changed my PC for an AM2 based A64, with nforce 410/Geforce 6100 based Chipset, and all is right, my S.O. is in SATA2 disc and all is right....

Experience: Jmicron is too bad...

Couldn't agree more smile

I will make the appropriate changes in DriverPack MassStorage, to reflect that JMicron is absolute crap: its drivers will NOT be loaded by default, brave souls will be able to renable them manually.

740

(32 replies, posted in Feature Requests)

I have actually made that a couple of weeks ago. It worked in Windows. It did however NOT work (it would simply not execute) during the presetup stage, because some things had not yet loaded. I kept on trying finding work-arounds, without success. But that's because I'm using AutoIt and I cannot tell AutoIt not to load certain dependencies.

Yesterday I had to install a pc with an ICH8R and a JMicron 363. It took me hours. It was the JMicron controller's driver: it was somehow resulting on BSODs. As soon as I removed the driver, and ONLY used the Intel driver (2 SATA drives were connected to the ICH8R in RAID0), it worked fine.

If you have the choice, DO NOT USE THE JMICRON CONTROLLER. But you do not have the choice... Good luck!

742

(1 replies, posted in 3rd Party DriverPacks)

Check the 3rd party Monitor dp! wink

Will be added in the next update.

It's only used when you choose RunOnceEx as your Finisher method. It adds an entry to the registry to make sure the Finisher is executed by DPsFnshr.exe, the number behind it allows you to manipulate the order in which possible other RunOnceEx commands will be executed.

Helmi wrote:
Bâshrat the Sneaky wrote:

Any progress with this issue, Helmi?

Unfortunately, I can't test it anymore right now since I gave my laptop to my sister and my new one hasn't arrived yet, so I am left without any machine that features a HDA sound chip.

(unless there's another way to fake it somehow, maybe in a virtual machine or something...)

Nope, that's not possible. I'll label this topic as inactive, then.

Yes, the D\D bug is known and is already solved internally, though I just want to do a few more tests to verify that.

I'm glad it's solved for you. Correct me if I'm wrong, but doesn't this prove that this was NOT caused by DriverPack Sound B 6.10?

747

(19 replies, posted in DriverPack Sound)

Sereby wrote:

i could tell you 2 mainboards maybe.. but the first one could be damaged now because its not starting only beeping (seems to be the gfx card or the port.. dont know) and the other one could be soundmax and i can send you the hw-ids if you need

Do not send me the HWIDs, I can't do anything with that, I need the brand + product name of the motherboard, nothing more, nothing less. (I need that to download the missing driver from the website.)

Then please post your DPs_BASE.ini.

I'm afraid I did not succeed in reproducing this issue, did you see my note?

I think this topic can be closed now: the issue is no more since a very long time smile