Moved to appropriate forum

Just grabbed graphics b successfully - IDK what the answer is - but i will keep an eye on it...

the first line of your log should tell us which base version was used.
It is really really hard to help when the most basic of info is not included.

Please read the read before you post in my signature to see what i require at minimum TIA

here is the first 20 lines or so of a valid log...

2008-05-06 00:25:27 : <INIT> DriverPacks BASE (version) initialized.
2008-05-06 00:25:27 : <INIT> Host environment: WIN_XP Service Pack 2 on X86 CPU.
2008-05-06 00:25:27 : <INIT> Created temporary working directory.
2008-05-06 00:25:27 : <INIT> Imported proxy settings from Internet Explorer.
2008-05-06 00:25:27 : <INIT> Start scanning for DriverPacks for the wnt5_x86-32 platform.
2008-05-06 00:25:27 : <INIT> 	Detected DriverPack Chipset 7.10.1!
2008-05-06 00:25:27 : <INIT> 	Detected DriverPack Chipset 8.03!
2008-05-06 00:25:27 : <INIT> 	Detected DriverPack CPU 7.1220!
2008-05-06 00:25:27 : <INIT> 	Detected DriverPack CPU 8.04!
2008-05-06 00:25:27 : <INIT> 	Detected DriverPack Graphics A 8.01.1!
2008-05-06 00:25:27 : <INIT> 	Detected DriverPack Graphics A 8.02!
2008-05-06 00:25:27 : <INIT> 	Detected DriverPack Graphics A 8.04!
2008-05-06 00:25:27 : <INIT> 	Detected DriverPack Graphics B 7.12.1!
2008-05-06 00:25:27 : <INIT> 	Detected DriverPack Graphics B 8.01.2!
2008-05-06 00:25:27 : <INIT> 	Detected DriverPack Graphics C 8.01!
2008-05-06 00:25:27 : <INIT> 	Detected DriverPack LAN 8.01!
2008-05-06 00:25:27 : <INIT> 	Detected DriverPack LAN 8.02.1!
2008-05-06 00:25:27 : <INIT> 	Detected DriverPack MassStorage 8.02.1!
2008-05-06 00:25:27 : <INIT> 	Detected DriverPack MassStorage 8.03RC3!
2008-05-06 00:25:27 : <INIT> 	Detected DriverPack Sound A 7.12!
2008-05-06 00:25:27 : <INIT> 	Detected DriverPack Sound A 8.02.1!
2008-05-06 00:25:27 : <INIT> 	Detected DriverPack Sound B 7.12!
2008-05-06 00:25:27 : <INIT> 	Detected DriverPack Sound B 8.01!
2008-05-06 00:25:27 : <INIT> 	Detected DriverPack WLAN 7.12!
2008-05-06 00:25:27 : <INIT> 	Detected DriverPack WLAN 8.03!
2008-05-06 00:25:27 : <INIT> 	Detected 3rd party DriverPack(s).
2008-05-06 00:25:27 : <INIT> 	Finished scanning.
2008-05-06 00:25:27 : <INIT> Detected settings file "C:\dpbase\DPs_BASE.ini".

you seem to have major problems with your computer...

Is your host OS Vista... i bet yes... are you running base with the administrator account? (run as -> admin)

your log would also tell us this as well. (see above)

http://forum.driverpacks.net/viewtopic. … 074#p20074

follow the detard posts... it may help

Welcome to DriverPacks.net - have a great day

4,155

(14 replies, posted in DriverPack Chipset)

DPs_BASE.log

Well since you only included part of your log ther is not enough info to help...

but it seems that your mass storage pack is corrupt and so is your source...

I have to guess without sufficcient info being provided. please see read before you post

4,157

(61 replies, posted in News)

i would like that very much - Thank You so much!

However i would like to request at this point that we Please move this to a more appropriate Forum.

Universal Imaging

jeff

Darned fine Troubleshooting sir! well done...
That is what i would have done.
(except i have enough hardware laying around my office to not have to use my personal system)

You may not be wrong about the virus... some viruses can infect the BIOS.
this is not common but it is worth mentioning.

since it seems you have quite properly narrowed the field (by a huge margin) - let's consider what is left.
AMD processors use a huge amount of power and run quite hot - verify the heatsink is clean and well seated.
they are also very sensitive to lack of proper voltage - is the PSU dust free and have a good fan?
(heat will cause your voltages to be off) Intel processors are more tolerant and less needy but it still could be the issue.   

MB - I have a POST card but you will have to come to my office wink
As a last resort  (unless it has a dual bios)  Flash the bios
is it under warranty ?

Jeff

we have gotten way outside the scope of our forum at this point
I must warn you of the fact quite strongly... mad

I am however curious how this turns out - cool
even though i am going to have to ban myself for misuse of the forum... sad

4,159

(61 replies, posted in News)

if we get past this hurdle i will have to step up to the plate... you worked hard on this.

by this i mean i will code mass storage integration for sysprep. big_smile

4,160

(61 replies, posted in News)

were you calling dpinst.exe /s /c ? 
(/S ilent /C onsole logging)
{ which is similar to if not the same as  <suppressWizard/> <quietInstall/> }


Does the amd driver in the pack work if installed localy? (or manually)

PS it sounds like we are close to getting this to work!

well i didn't do a search... that was just my memory...

and i thought i was starting to get forgetful in my old age... wait...

I forgot about 33% of the posts... Rats... my memory is failing (jeff is sad now)

wink

Well i have to have at least one bug or what are people going to report? ;P

German was not the only language i missed either...
It was the most current... Thanks Helmi, You are a DriverPacks Hero!

I will need to pay attention to that more closely in the future

Well I think it is important because it means it is not likely to  be changed anymore.

Fixed... more likely it has been raised... but still very good news.

I suppose that the dup file name prob still exists...

4,165

(61 replies, posted in News)

parameter for the finisher hmmm... Who said there wasn't...? Oh yeah that was me...

Silly me...  look in the finisher.ini at  DPsRoot    = "%SystemDrive%"

we dont pass parameters to the finisher but... it does read it's INI. and
%SystemDrive%\D is not hardcoded
just the \D is hardcoded

i think i am getting Sometimers... lol

Jaak spotted that and they should be fixed now... U tell us...

4,167

(61 replies, posted in News)

the finisher is hard coded to %systemdrive%\d no way to make that work with the network... sad
if you want the finisher you must copy the files to the local machine.
my script copies the files runs dpinst then the finisher - the finisher then cleans-up /deletes the files.
so if you want the finisher just call my script and let it do its thing...
yeah it copys the files over teh network but 7zipped it is only 300meg to copy them

99% of the drivers don't use /need the finisher so it is not a big deal (ati control panel is one example that does use it)

runonceex registry keys will only be called one time and then remove themselfs - that is their function in life wink
So... 

myscript.cmd

SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx
REG ADD %KEY%\996 /V 1 /D "cmd /c start /wait net use z: \\server\autoinst [pass /user:admin /Y]"
REG ADD %KEY%\996 /V 2 /D "cmd /c start /wait z:\DP_Install_Tool.cmd"

4,168

(61 replies, posted in News)

i edited my post and clarified my suggestion.

you can login from a script please revisit my last.... PS i deleted the dreaded QUAD post lol...

4,169

(61 replies, posted in News)

hint...
call dpinst from a runonceex script that runs before login

net use z: \\server\autoinst [pass /user:admin /Y]
z:\path to driverpacks here\dpinst.exe /s /c

the d\ folder that contains the cabbed or extracted drivers must be a subfolder of the one that you run dpinst from.

4,170

(3 replies, posted in DriverPack Graphics)

I am surprized that one is not natively supported by windows. Were you installing 2k or XP?
do you remove native windows drivers with nLite? (guessing)

Thanks so much for the report...

Welcome aboard and we are glad your here.

Thanks for your feedback. It makes DriverPacks better for everyone.

I just noticed that Helmi has already submitted an updated language file for German...

try this by overwriting the one in your lng folder... http://3rdpartydriverpacks.thesneaky.co … German.lng

Jeff

included in 8.05 select no packs on selection screen and hit the 'slipstream' button.

This could be a lot of things. It seems that the CD/DVD Rom is not accessable
after the textmode reboot and we are begining the PE stage of setup.
If he has a SATA ROM then it may be a driver issue - unlikely but possable

Since it worked on another computer lets figure your disk is OK (but maybe it got scratched)
That leaves us with his machine as the problem.
Did you try it a second time and get the exact same result?

Is his CD on the same controler as the HDD? (is it a standard IDE cd or dvd rom)
Is it a new machine or are you reloading?

could be his CD rom
could be his HDD
could be his RAM, MB, CPU fan, PowerSupply (check the PS fan too),
If a video card is failing VERY strange things can happen.

Can you tell us a little more...

4,174

(47 replies, posted in Hardware)

the fact you found us reinforces that...

As of Base 8.05 dpinst.exe is included and copied during the slipstream
this makes any DriverPacks slipstreamed disk a drivers only disk, in addition to its normal function.

Bâshrat the Sneaky called this feature a 'SAD disc' or Stand Alone Drivers disc.
we are exploreing other options for this tool as well, stay tuned...

Since DPInst is a Microsoft redistributable file lets start with their description...

http://msdn2.microsoft.com/en-us/library/ms790308.aspx
http://msdn2.microsoft.com/en-us/library/ms790806.aspx

text below is copied from the above links

Windows Driver Kit: Device Installation
Driver Package Installer (DPInst)
Driver Package Installer (DPInst) version 2.1 is a component of Driver Install Frameworks (DIFx) version 2.1 that simplifies and customizes the installation of driver packages for devices that are not yet installed in a computer (commonly known as a software-first installation). DPInst also automatically updates the drivers for any installed devices that are supported by the newly installed driver packages.

By using DPInst, you can:

Enhance the user experience of a driver package by eliminating most of the manual steps that would otherwise be required to install driver packages. When a user runs DPInst, a wizard notifies the user of the installation progress and provides an optional end-user license agreement (EULA) page that gives the user the option to cancel installation. For more information about the wizard pages, see DPInst User Experience and Installing and Uninstalling Driver Packages.

Avoid writing a custom installation program to install driver packages and update the installed drivers for supported devices. You do not have to change your driver packages to use DPInst. You only need to create an installation package that includes DPInst and one or more driver packages. For more information about creating this type of installation package, see Creating a DPInst Installation Package.

Very Microsoft-eze,  In simple terms;

It updates Windows drivers at any time - not just during an install - It could be post install...
and this is how we use DPinst.exe - we add it to the OEM folder. (or $OEM$\$1\ for M1)
We also add a small script file in the same folder.
The script prepares the DriverPacks in the same way as it would for the method used to create the disk
(Method One or Method Two is "staged" the same as DriverPacks would do it.)
then DPinst is called from the script.

DPinst is the missing link we have been searching for to add drivers to an existing installation of windows, or update them:
It checks the current machines device manager, and compares its drivers to what is in the DriverPacks
If newer drivers are found in the DriverPacks than exist in the target machine then it's drivers are updated
- on the fly - Unattendedly.

Now, if that is not pretty darned slick all by itself... let me just toss this in for a bonus;

Since we have prestaged the drivers in exactly the same way as DriverPacks would the DP_Finisher will run exactly as it would if you had just done an unnatended install (except we didn't, we just dropped our disk in any computer)
The finisher calls keep the driver (KTD) and cleans up the packs and removes all traces of the driverpacks. (just like normal)
note: It applies whatever KTD settings exist in the source OEM folder. 


So what we have after all the smoke and mirrors is a way to install DriverPacks on any system (BlackBox) at any time.


THE SCRIPT IS \OEM\DP_Install_Tool.cmd (or \$OEM$\$1\DP_Install_Tool.cmd for M1)

--------------------------------------------------------------------------------------------
It's a one click solution to update ANY win2k winxp or win2k3 box with the DriverPacks!
--------------------------------------------------------------------------------------------

can you say...    Have a nice day! cool


PS normal installation of DriverPacks does not need or use DPInst.
PSS you could use AUTORUN.INF to call DP_Install_Tool.cmd big_smile
(might want to add a pause at the beginning of the script if you do wink )