1,026 Reply by Wim Leers

(23 replies, posted in DriverPack Mass Storage)

Rogier wrote:

Hmm, it got me further than before, the new slipstreamed XP Setup properly recognized my hdd and formatted it and everything, but further in the process it asks for a file "usbehci.sys" which it seems to expect in D\C\I\2k but isn't there..?

I cancelled it now and Setup seems to continue, am I missing something important now or..? (the filename sounds like something USB-related, but my USB mouse is working fine in setup)

This problem has been reported months ago and then I fixed it by manually adding the file. The file is NOT included in the Intel Chipset drivers releases for some reason.
Now you mention it, I think I've forgotten to copy the file when I made separate directories for each winnt 5 OS (2k, xp and 2k3). I will fix this in the next update. Do you want me to send the file to you so you can fix your problem immediately?

Go to forum: DriverPack Mass Storage

1,027 Reply by Wim Leers

(13 replies, posted in Other)

It's NOT necessary. It's just better (it's like Windows does it) and faster (precompiled .infs) in theory.

Go to forum: Other

1,028 Reply by Wim Leers

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

Boegie59 wrote:

OKE, I finally integrated the drivers, I just have to point were the map WINXP was, You can close the topic

Yep, that was all you had to do smile Glad you got it working.

Topic closed!

Go to forum: Feedback and Support - DriverPacks Base

1,029 Reply by Wim Leers

(13 replies, posted in Feature Requests)

Helmi wrote:
twig123 wrote:

...can't it just be scripted to use IE settings for the proxy?

Yeah, that should be the preferred method (for any program actually) IMO.

Indeed. That was the way I was going to implement it, actually.

Go to forum: Feature Requests

1,030 Reply by Wim Leers

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

Sorry for the late reply.

This part of your log:

2006-09-05 14:34:13 : <INIT> Logging of HWIDs complete.
2006-09-05 14:34:13 : <CRIT> Could not delete element from array!
2006-09-05 14:34:20 : <CLNP> Deleted the DriverPacks, which were located in 'C:\D'.

Shows that there was a critical error and therefore the Finisher was ended before it got to the stage where it applies KTD.

Which means something went wrong with processing your settings in the DPsFnshr.ini. Could you please post your entire DPsFnshr.ini?

Go to forum: Feedback and Support - DriverPacks Base

1,031 Reply by Wim Leers

(7 replies, posted in DriverPack Mass Storage)

Sounds like either a corrupt image or a faulty CD/DVD. Please recreate the ISO and then burn it to a different CD/DVD. That should do the trick.

Go to forum: DriverPack Mass Storage

1,032 Reply by Wim Leers

(23 replies, posted in DriverPack Mass Storage)

Without 'DriverPack MassStorage text mode' enabled, the appropriate changes aren't made, so then it's quite normal that it was not detected! It'll work after you've reslipstreamed the DriverPacks with that option enabled. So I won't need your HWIDs.

I'd recommend method 2 over method 1 whenever method 1 is not absolutely necessary (if you're using very specific deployment methods).

Go to forum: DriverPack Mass Storage

1,033 Reply by Wim Leers

(13 replies, posted in Feature Requests)

If you don't want to do everything manually, then check out RogueSpear's AutoImage - it's developped especially for managing RIS images AND it uses the DriverPack Sound B API, so you can easily slipstream the DriverPacks without further worries.

Go to forum: Feature Requests

1,034 Reply by Wim Leers

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

tarquel wrote:

I unchecked DriverPacks Mass Storage text mode.

It will slipstream them into text mode regardless I believe - RogueSpear has started a BugTracker on here.... just so you know, although I am unaware whether this is just with the API mode [i.e. using AutoImage with Bâshrat the Sneaky DP] or not.

Regards
Nath.

This was due to an incorrect setting in RogueSpear's dynamically generated .ini file (he set it to "all" instead of "select"). He's already solved it I believe.

Through this a bug on my side has been uncovered though: if DriverPack MassStorage is NOT present, the DriverPack Sound B tries to slipstream it as text mode drivers neverthesless.

Go to forum: Feedback and Support - DriverPacks Base

1,035 Reply by Wim Leers

(13 replies, posted in Feature Requests)

tarquel wrote:

In line with the above [and i didnt think it needed its own thread lol sorry if I'm wrong]...

Can I ask whether you can add a way of putting in a http proxy in the settings, as my setup here at work is behind a proxy [no - i cannot bypass it] so I get a enjoyable long pause if i accidentally go to the UpdateChecker section of the program.

Sorry if this already exists, but i cant find it hehe wink

Cheers
Nath

Somebody already requested it, it's planned to be added in one of the next versions wink

Go to forum: Feature Requests

1,036 Reply by Wim Leers

(13 replies, posted in Other)

Trax wrote:

The slipstreamed version also runs into a lack of space to but i can do an overburn and take care of that. But the question is since it can be compressed into the slipstream can i just pull it out after its been placed in cabs and put just those cabs on a CD?

Yep, that's what I was explaining: I was telling you each step you should take to achieve that without having to do everything manually.

Note that each file is CABbed separately. This is necessary for Windows to detect the drivers.

Go to forum: Other

1,037 Reply by Wim Leers

(13 replies, posted in Other)

The easiest method is to slipstream the DriverPacks using method 1 and then copy the \$OEM$\D directory to a CD. Once you've done that, insert this CD into the system you'd like to install the drivers onto. Then execute the following command:

DevPath.exe X:\D

where X is the drive letter of your CD/DVD drive. This way you should be prompted to insert your CD the next time you have to install a driver (haven't tested this approach yet though).

From this basic way of working, you can create a method for your specific needs. If you explain me your installation method in detail, I can help you further.

Go to forum: Other

1,038 Reply by Wim Leers

(13 replies, posted in Feature Requests)

AFAIK, it's better to use method 2 and thus include the full DriverPacks. That way you have to transfer LESS files and LESS data too (method 1: >600 MB, method 2: <300 MB).

Go to forum: Feature Requests

1,039 Reply by Wim Leers

(13 replies, posted in Feature Requests)

homolka wrote:

No - shall change $OEM$ to a share?

Well, if you are not using the $OEM$ directory yet AND if you want to use method 1, then that's the best solution. If you want the DriverPacks to be used from a share, method 2 cannot be used so... that'd indeed be the best solution.

Go to forum: Feature Requests

1,040 Reply by Wim Leers

(13 replies, posted in Feature Requests)

And is your $OEM$ distribution directory also on that network share?

Go to forum: Feature Requests

1,041 Reply by Wim Leers

(2 replies, posted in Other)

I'm not asking for complete code... I was asking how you were exactly hex editing setupdlr.bin etc. I guess by just reading the raw file stream? That's all I need to know smile wink

And thanks for the kind words smile

Go to forum: Other

1,042 Reply by Wim Leers

(39 replies, posted in DriverPack CPU)

maxximum wrote:

I'll revert back to 'old CPU 6.08 smile wink

Bâshrat the Sneaky wrote:

Why didn't this problem occur with the previous DriverPack CPU? The CPU driver itself has not been touched whatsoever... I don't see any possible solution to this very odd issue...

wink

Go to forum: DriverPack CPU

1,043 Reply by Wim Leers

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

jtdoom, all of that is most definitely NOT necessary. During the initial beta testing it was a good thing to do, but now it's definitely useless.

@mikelm: What you describe (not remembering the settings for DriverPack MassStorage text mode and QuickStream Cache), is impossible - UNLESS you've opened the DPs_BASE.ini with a text editor that's using a write lock. You can ask any one on the forum, but you're definitely the only one with that problem. You must be doing something wrong, probably without realizing it - and that's something that happens to every one once every while.
You could try Unlocker to find processes that have locked the DPs_BASE.ini.

Go to forum: Feedback and Support - DriverPacks Base

1,044 Reply by Wim Leers

(39 replies, posted in DriverPack CPU)

Why didn't this problem occur with the previous DriverPack CPU? The CPU driver itself has not been touched whatsoever... I don't see any possible solution to this very odd issue...

Go to forum: DriverPack CPU

1,045 Reply by Wim Leers

(3 replies, posted in DriverPack LAN)

DigeratiPrime wrote:

can confirm it is working on nforce3 big_smile

Grrrrreat! That was the device I was afraid of it would not work.

Go to forum: DriverPack LAN

1,046 Reply by Wim Leers

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

The last configuration is automatically remembered... I don't see how that could not work.

And then please DELETE the directory I mentioned. Then slipstream again. The QuickStream Cache will now have been rebuilt and it should be a valid one this time.

Go to forum: Feedback and Support - DriverPacks Base

1,047 Reply by Wim Leers

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

Hmmm.... I think you have once cancelled the slipstreaming process while it was creating a QuickStream Cache for DriverPack MassStorage text mode. That would explain the missing files. Could you please exist if there are ANY files in the directory 

QSC\wnt5_x86-32_uni_DP_MassStorage_608_textmode

?

Go to forum: Feedback and Support - DriverPacks Base

1,048 Reply by Wim Leers

(14 replies, posted in DriverPack Graphics)

S3pHiroTh wrote:

My laptop (Compaq nc610c) hasn't any option for enable or disable agp. The strange thing is that I will install Omegadrivers in xp, all works well. But if I slipstream Omegadrivers in winxp installation cd, I have the same problem, no Direct3d, Directdraw and agp acceleration. I don't know why... yikes

Well then it's definitely NOT due to the driver I've included...

I'll try to find the changes that have to be made to the system to enable Direct3d, DirectDraw and AGP acceleration, so I can make an exception for your GPU...

Please post the HWID of your GPU already! (The entire DPsFnshr.log is fine too.)

Go to forum: DriverPack Graphics

1,049 Reply by Wim Leers

(39 replies, posted in DriverPack CPU)

Please post the relevant chunk of your setupapi.log file. (It's in the %systemroot% directory.)

Go to forum: DriverPack CPU

1,050 Reply by Wim Leers

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

ironside wrote:

When i had this issue the atiide.sy_ was in lower case in the i386 folder.

Converting the files in the i386 to UPPERCASE will fix it but having said that the latest DP base should do that for you automatically i dunno why it did;nt for you.

That could indeed be the cause. But it should be UPPER case automatically now... Could you please verify that, mikelm?

Go to forum: Feedback and Support - DriverPacks Base