Hi mr-smartepants (huh, when I say that, it sounds like I want to insult you, which is not the case)

anyway, this line
2007-03-12 09:06:20 : <SEL>  Selected module: mod_slip_wxp_x86-32_disc_m1.
that is method 1

that line about the INI  is no error, when base is run from a freshly unpacked folder, the ini does not yet exist.
Hence,
2007-03-12 08:50:40 : <INIT> Could not find settings file"C:\My Stuff\Software\MS Windows XP\_WinXPSP2updates\DriverPacks\DPs_BASE.ini".

Hi
I think you would be better off using method 2, snce you have all packs in there.

@ bigbrit,
it got stickied, but even while it is regularly asked, it was not in FAQ..
http://forum.driverpacks.net/viewtopic.php?id=960

hmmm, if KTD takes five seconds, that"s wrong... it moves the files quick enough, but PNF and devpath will still have to run, and that can take five minutes.
When it fails, a finisher LOG would be handy, it may tell where it gets the CRIT error
We's always looking for regulars that want to be testers, I think.

hi
you are using a fixed cdrom drive letter?

I am glad there is a discussio with real info going on by now.
My first thoughts were to ask for the batch file content, and that there could be a problem because you use winnt.exe (DOSINITIATED=YES), and all base slipstreamed sources I saw so far do not use that.

anyway, the fixed letter, that could be a problem as well.
you may be able to solve this by using cd-find looking for tagfile

example

SET TAGFILE=\DSPdsblr.exe
FOR %%i IN (C D E F G H I J K L M N O P Q R S T U V W X Y) DO IF EXIST "%%i:%TAGFILE%" SET CDDRIVE=%%i:
 
%CDDRIVE%\I386\WINNT.EXE (options)

Hi
welcome to driverpacks net

a sound issue can be caused by missing modem driver
There is a modem driver pack in third party, but you did not use it.

the top stickied post in third party drivers forum (the forum Muiz showed you) has all the links to the 3rd party packs. (it is called all packs repacked.)
http://forum.driverpacks.net/viewtopic.php?id=587

I just looked wether the modem HWID is supported in the current pack, and found that its subsys information is NOT supported, so we will need the compaq driver, and a "formal" request topic with the driver in it is the way that makes it easy for us to keep track.

I would suggest you start a new topic in third party packs forum,
the opening post has good info, so you can reuse it
you should, however, also add the output from saveHWIDs

you can add the link to the driver you need.
that way, we do not have to search for the compaq softpaq

hi
I'm too lazy to look it up, can you tell me what chipset uses ICH8 ?
It could help if I knew what mobo this is on, just in case I come across something similar.

edit.. DUH, it is in first post.
:sleepy:

Hi

that is what I usually do while testing new releases or betas, and I use RW media..
wink

There is a clean copy of the CDs I have to test on on a hard drive, and I can copy one to working folder on other hard drive.
On that storage drive, there are also LEAN copies, where not much more than the essential stuff is kept in, which get used a lot more often for copy to working folder then takes less time.

I have no hardware using ICH8 at the moment, mine use ICH7.
I wish I could test this. When I get a machine in, I'll look..

2,133

(33 replies, posted in Other)

hi
you're welcome

done some txt cleanup, and added link to 7zip

to speed it up, give it some real memory, and disable its virtual memory.

Microsoft does this in the Internet Explorer readiness toolkit virtual machine
(they made available a virtual hard disk image, with XP and IE7 in a VHD image, free to download.)

the IE7 readiness toolkit image will expire march 30...

It is a testing platform of sorts, and I used the beta with satisfaction. And best of all: it's free!

http://www.microsoft.com/windows/produc … fault.mspx

hi
halfway throug the clicking through options and settings, you changed location of source.
maybe that this caused this

...just a guess...

but this is something I noticed here, after a first detection.
2007-02-28 17:13:38 : <GUI>  Changed Windows installation files OR export (depending on the installation platform) location to E:\.
2007-02-28 17:13:38 : <GUI>  Windows XP Professional -  OEM SP2 detected.

is E: your CDROM?

if E: is a CD, that will never work.

Hi
can you get the modifier script, and post it?

2,138

(22 replies, posted in DriverPack Graphics)

btw, thanks for that feedback, it was useful.

there was no real issue then, see?

edit, I wish you guys would say Jaak...

2,139

(22 replies, posted in DriverPack Graphics)

cool
watson is pleased smile

Hi Hari

maybe you'll have a go at customising driverpacks,
I noticed it uses ATIGART.EXE for the AGP bridge, and I do not find that file in the current packs.

I think this one should be added to grafics C
Too bad you no longer have the laptop this is used on, you could have tested your first addition.

oh
on the last trial, using 608.6
when I uncomment some of the driver files that my test-machine needs, (I also looked in all other relevant sections, in both dosnet.inf and txtsetup.sif), I could install 2000, but finisher gave me an array error .

hi muiz

did it with base 7.02 nightly and newest test versions
did it with the current released versions, and then also used base 608.6 with older packs that are compatible with 608.6
they all had these three file name without "locator" at bottom in the dosnet.inf after win2000 was streamed.

These three files are files that get updated, and found higher up in the inf.
But it surprised me the lines are there, at bottom, in that form.

2,143

(22 replies, posted in DriverPack Graphics)

I am still trying to figure out why you mentioned that it was greyed out.
I cannot reproduce that fenomenon.
we have no log, so I assume user error
when two versions are in folder, base goes for the latest.
(maybe C was not in folder... when a file is NOT in folder, it is greyed out. When a file does not use standardised driverpacks naming convention, it would be greyed out too, but greyed out files are not processed.. Therefore, I assume reporting or user error).

anyway, it worked for both of you, so this one can be implemented
(it is currently up on a driverpacks server for further review by testing team. >>  G\B 7.021 )

hi

I used base 7.01.6 on a english win2K_sp4, and there is indeed a long list of "commented out" entries in dosnet.inf.
I had notepad replace ;d1 with d1 to uncomment them.

while reading dosnet.inf, I noticed another weirdo at the very bottom

adpu160m.sys
ipsraidn.sys
dac960nt.sys

these had no d1 nor ;d1 in front of them.

Looking at txtmode.sif reveals sections where all entries are "commented out"
textmode mass storage files, and mass storage HWIDS too..
(I looked at an not-yet-streamed dosnet inf and want to closely compare those, but it does seem ALL that should be added are in, but inactivated by the "comment" .)

I'll be replacing the "comments" with nothing soon, and run a live trial.

smile you guys did not do it the wrong way. wink

hi
the tool should be run in a system that has this sigmatel soundchip, and the output (HWID-List) should be posted.
That is how we can find out wether this is supported.

you could do that too, if you have 7zip installed.
un7zip the sound packs
look for the HWID for this soundchip in the List
search the unzipped soundpack folder for TXT string, paste HWID in the dialog box, and it crawls all inf files...

let us know..
post hwid list

2,146

(22 replies, posted in DriverPack Graphics)

thanks for additional info on CPL.

it had crossed my mind to ask about it, but then I forgot to put that in a post..
hehe, I am getting old wink

I forgot to take pill against forgetfulness, I think... LOL

2,147

(22 replies, posted in DriverPack Graphics)

I am not 100 percent sure on the following assumption I make, but if you put it in 3rd party, it will indeed be in the OEM folder, but, I "assume" that exception filters will not process this graficks-in-3rd..

therefore, please put G-B-nightly in driverpacks folder and rerun.

future base releases will use driverpacks releases that will have an individual INI file, so that people can customise more easily if the need arises.

2,148

(22 replies, posted in DriverPack Graphics)

huh?
greyed out?
the nightly has to be put in driverpacks folder, not in third party folder (what I think u did)

2,149

(22 replies, posted in DriverPack Graphics)

hi
rerun base, and just ignore that update checker... hit slipstream

tool
http://www.driverpacks.net/Downloads/save_hwids.exe