Search options (Page 63 of 99)

he he, you know, one of the testpacks of two months ago failed, it had changes like this.., But what I had done was use search and I replaced a lot more, so it probably got messed up..

feedback by people who know what makes it tick like a swiss clock, would be very welcome.

torerro?

it is your lucky day.
sorry, bad link.

I am tempted to ask "you wanna make them?"

one thing is clear, there WILL ALWAYS be overlap in the Packs, because there are drivers for 2003 / 2000 / XP which have THREE drivers for same hardware, and one can easily see they will have same HWIDs in them.

I mentioned we currently have an Excell file what we started to use to see the duplicates in the INI in.
With proper annotations in it, this is a good worksheet to see what is used for what.
You can thank Mr EchoPlatoon for the work done on that.
The Excell file may even be made accessible to the users of DriverPacks.
--------------

I think I see what you mean by the service display name
("friendly-name")
I had no idea that this could be a problem in sysprep.
One learns something new every day.

I'll look, and may upload an updated testversion soon.

thanks.

this may be why it sometimes did not work here.

at bottom of this http://forum.driverpacks.net/viewtopic.php?id=1637

Hi zookeeper.
you waited long enough, the files finally got looked at again.

I don't mind helping in other than DriverPacks forum on such questions.
but, we are not a general help forum.

Tiger, a DMI reseat, always good.
and Tiger, it is JAAK.

yep, Mr. Holmes, you are right.
Those INI sections do not exist in the release.

But, the files for i-3, i-4, i-5 and i-6 are in the pack. (I think a request was not finalised, but the files were in none the less)

Ruudboek, if you read this, have a look.
they are all SCSI miniport, and i-5 is SAS

Hi Randall,
welcome to DriverPacks.

I assume you used the driverpacks to install the machine.
Question 1,  DID you use the driverpacks to integrate drivers to your home SP2?

Q 2,  if you did, can you post HWIDs list (tool is in my signature) and the finisher log (found in 'windows' folder)

hi
when you try such an approach

if: 1; you change ALL references to filename in the INFs from iastor.sys to iastorXX.sys
Notes, there are references  to iastor.sys in iastor.inf AND in iahci.inf.
BOTH most be done.
(stick to 8.3 convention)

then:
A> you must change filename in IN\1 from iastor.sys to iastorXX.sys
B> you must change INI section where you change filename from iastor.sys to iastorXX.sys

if: 2; you did that for all three (iastor55, iastor62 and iastor75)
(The XX were used instead of the numbers)
then
pack it up, use it as mass storage pack to run base on a fresh copy of your windows CD.
And then TEST this non-sysprep CDR on a live test machine which uses one of the iastor files.

btw, this approach was almost in the pack.
It should work, and it can be in a future Pack.

what you are saying is,
all SiS drivers disabled during TXTmode, and then it gets picked up by #2110

Q; But why does it come up with BSOD when the same driver is used in graphical portion of installer?

the answer to that?
1, the drivers cannot co-exist on the CD.
2, the 2030 was the one that got updated to 2110

now IF you used the nightly. but DID YOU?
then answer 3 is> version 2110 wont do it in TXTmode.

Did you try that nightly?

hi

have you ever started completely fresh with the prepared winnt.sif IN PLACE before you ran Base?
(fresh as in, a new clean copy of the source, put winnt.sif in, then run base)

what I see happening here is this.
the backup in that source does not have the stuff you want.
when Base starts, it first restores the backup.