Search options (Page 36 of 77)

I was interpreted the wrong way. nuhi did contact me to get DriverPacks support in nLite. But he did want want me to export them in an nLite-compatible format (much like RyanVM's UpdatePack). But as you all know, there's more to configure in the DriverPacks than in the UpdatePacks... Plus the UpdatePacks don't have to be transformed into an nLite compatible format, their nature lends them very well to be nLite-compatible. This unfortunately doesn't apply to the DriverPacks. That's why it's not for soon.

@McStarfighter: Perhaps, but it's too difficult I've only had German one year, one hour a week, so my knowledge is very limited. Aber ich glaube dich (If even that short sentence is correct...)
The reason that I want everything in English is that it makes everything accessible for everybody. You cannot deny that English is the defacto internet language... so let's just stick to that

Thanks a lot! You're now a member of the Donator user group!

I'm frustrated too. The Finisher has been in use for a while now, and now there are a few of people getting this error. A few, not all, not many, just a few. I will be testing it myself in detail today, though I have not yet been able to reproduce it.

Because it's such an unobvious, rather odd error, it's not easy to find the exact cause. Plus, as I've mentioned earlier, most people don't get this error, which makes it harder to find.

All I can tell you is that I'm working on it. This issue has currently my highest priority and I'm working very hard to get it fixed by today/tomorrow.

1) What motherboard are you using? I think it will be some exotic additional monitoring/overclocking chip again, so I just need to add that driver and it'll be fixed.

2) If you did not use KTD, then the easiest method would be to do this:

a) insert DVD
b) start > run
c)

cmd
cd /d X:\
X:\OEM\bin\7z.exe X:\OEM\DP*.7z %systemDrive%
X:\OEM\bin\DevPath.exe %systemDrive%\D

(where X: is the drive letter of your DVD drive)
d) install the drivers
e) if you closed the previous command prompt, start a new one and type

X:\OEM\bin\DevPath.exe

(this will reset the DevicePath to the original: %systemRoot%\Inf)

I was not aware of that! Thanks alot! Will try it out when I've got the time.

I will also see if it's possible to support OPK WinPE. If it is, then I will definitely add support for it.

@all: debug mode should be working, I've used it before to debug the exceptions and KTD functionality. There must be one tiny typo or something that prevents the debug statements that I've added from working.

@RogueSpear: no, THAT is the error: that an element could not be deleted from an array. Probably because an incorrect index is specified, but that's the reason for adding all those debug statements, but unfortunately they're simply not working...

@[dk]: I'm now confident that it has absolutely nothing to do with the system's locale. Don't waste your time on that. But as you can see, it only happens on a very small amount of systems. So it's got to be something tiny...

In that case, I can refer you to this topic.

Topic closed.

Support continued in your other topic, with basically the same problem. But because that test is with Windows XP, the tracking of the cause is easier.

Topic closed.

I've added your specific HWID to DriverPack Sound B 6.09. But your device already was supported.

I've added:

PCI\VEN_105A&DEV_3373&SUBSYS_80F51043

, but

PCI\VEN_105A&DEV_3373

was already supported, which also supports your device!

Could you please post the relevant part of your setupapi.log (in the %systemroot% directory, which is most of the time C:\WINDOWS) (search for the string "PCI\VEN_105A&DEV_3373&SUBSYS_80F51043"), it could help determining why the correct driver did not get loaded.

You can manually test the workaround by searching your \I386\txtsetup.sif file for a line in which the string "PCI\VEN_105A&DEV_3373" exists, duplicating that line and then editing the duplicated line so the "PCI\VEN_105A&DEV_3373" gets changed to "PCI\VEN_105A&DEV_3373&SUBSYS_80F51043".

EDIT:

Could you please post your DPs_BASE.ini? Just to make sure that you did slipstream DriverPack MassStorage text mode (which is of course necessary).

1. Copy your current winnt.sif file to your desktop.
2. Delete the winnt.sif file.
3. Copy the winnt.sif file back from your desktop to its original location.

It must be inaccessible due to filelocks, which is the only reason I can imagine why this kind of error could be thrown.

Did you format it? Are you using the automatical formatting functionality of setup?

That makes your installation attended, i.e. the opposite of what we're trying to achieve, even though the countdown would allow to proceed the unattended installation. My suggestion is that you make a multibootdisc (use Windows XP PowerPacker to create it without the hassles of doing everything by hand) and include one installation with and one without the DriverPacks.

Plus, this would only work for method 2. Plus, the DriverPacks would already have been extracted, so no time is saved.