Search options (Page 80 of 213)

Then you don't have a valid license... I don't EVER install software without proof of a valid license...

If you lost it sorry about your luck... Not my Problem. Next time you will know the value of taking care of it.

When i worked in a PC shop this was our policy.
If you cant provide the original install disc with Key or at least Proof of purchase - end of discussion.

You could extract the files and reg entries from the image with no problem. But, I won't do this if they can't produce the install disc / Key... They call that piracy.

It is strange... it cabs all the mass storage drivers NP. It is just setup.exe that is at issue. I can think of no logical reason for this.

hmmm...

Unfortunately we have several reports of similar issues by the testing team...

No one has been able to isolate the issue to a single pack...

The possablility exists it is a conflict between two third party packs...

the best advice we can offer is to try it with half the 3rd party DriverPack and then the other half. try to isolate it to a group first then narrow it to a pack or a limited combo of them...

the more info that is reported on this the faster we can get to the answer... if you have time we would love to hear more of your results.

It helps us to help you, and everybody else too

I asked specificaly about setup.ex_ ? is it read only (yes / no)

most AV programs will alert you, so that is probably not it... but checking the Log / quarantine is still a good idea just in case.

since DriverPacks BASE has millions of users and you are the only one with this issue we know that it is something quite specific that you alone are doing that several million other users are not... you have provided no info so far that helps isolate what that may be... but together we will continue to try to narrow it down...

I am really convinced that some AV or SpyWare program is interfering... just a guess

YAQW!

Have a great day!

LoL that link won't work unless they are on the testing team

and if they are they can and will see your post already (it is the one at the top )

IDK why you are having an issue... seems like it should do what you want...

Perhaps you needed to specify "ROE.exe 001" not "ROE.exe 1"

However since you are customizing all this anyway you are just trying to do it the hard way.... Don't do it the hard way silly...

Just select 'custom' when you run DriverPacks BASE in the future Then use this or similar Runonce.cmd

 cmdow @ /HID
@echo off

FOR %%i IN (D E F G H I J K L M N O P Q R S T U V W X Y Z) DO IF EXIST %%i:\CD.txt SET CDROM=%%i:

SET KEY=HKLM\Software\Microsoft\Windows\CurrentVersion\RunOnceEx

REG ADD %KEY% /V TITLE /D "Installing Applications" /f

REG ADD %KEY%\001 /V 1 /D "%SystemDrive%\DPsFnshr.exe"

REG ADD %KEY%\002 /VE /D "Adobe Flash Player" /f
REG ADD %KEY%\002 /V 1 /D "%CDROM%\Software\Adobe\Flash\install_flash_player_10_active_x.msi /qn" /f

REG ADD %KEY%\003 /VE /D "Adobe Shockwave" /f
REG ADD %KEY%\003 /V 1 /D "%CDROM%\Software\Adobe\Shockwave\sw_lic_full_installer.msi /qn" /f

REG ADD %KEY%\004 /VE /D "System Settings" /f
REG ADD %KEY%\004 /V 1 /D "%CDROM%\Software\System\Oemlogo.cmd" /f

Exit

and skip the ROE.exe 001 in your cmdlines.txt

that will be cleaner, and easier to read / maintain

Welcome to DriverPacks

PS I added "code tags" to your post please take a moment to 'edit' it to see how that is done

PSS what does cleanup do?

LOL the one it is currently in (he moved it already) Hee hee he...

the source path looks a little wild... it contains a "." and a " - " it may be a nested quote issue with DriverPacks BASE...

could you try useing a plain path like C:\DPsBASE\ and report if the issue still exists, or not?.

I agree! (Why didn't I think of that )

Welcome to the testing team!

Please find that the Testing Team forum is now available to you
and you can select a cool testing team banner "UserBar" if you like too
link -> http://forum.driverpacks.net/viewtopic.php?id=3522
Edit... (added one for you )

Jeff

@mr_s. Good thinking... as always!

To be clear... As if there were any grey area left after somone had read the above thread...

The ENTIRE [unattended] section must be removed

This is stated in at least three posts above .
It doesn't matter how many lines that there are there... They must ALL be removed including the [UnAttended] line itself.

Optionaly you can just delete the entire WinNT.sif file
If you are not doing an unattended Install (like when doing a repair) then you don't need an unattended response file do you

If you like I can see if we can get that translated into your language.

DriverPacks Uses devpath as part of our process

Look at presetup.cmd

Better yet, try it  run devpath on a D\ folder and look at that key afterwards