Still alone... I'm not able to modify the script, I depend from you for everywhere...
1 2015-09-10 06:57:03
Re: Stand Alone Driverpack utility for all OS (XP, 2k3, 2k8, Vista, Win7) (525 replies, posted in Windows 7 tools)
2 2015-08-31 06:27:31
Re: Stand Alone Driverpack utility for all OS (XP, 2k3, 2k8, Vista, Win7) (525 replies, posted in Windows 7 tools)
No. Just got distracted.
DO NOT DO THIS ON OPTICAL MEDIA...
for thumb drive or better. All drivers extracted (M1 or M3)create folder on the root of your thumb drive called "OEM"
SET TAGFILE=\OEM 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 THUMBDRIVE=%%i:& GOTO DPsFound :DPsFound Start /wait /high /separate "" %THUMBDRIVE%\OEM\dp_install_tool.CMD EXIT
that should solve your issue.
= Since M1 (or M3) source is not deleted or extracted or copied it runs much faster (except on ODD devices) this solves two issues for you. The file copy / extraction and the removal of the D drive.
Hi OverFlow,
Thanks for your time, hope you'll have patience with me... I'm not sure to have clearly understood: I have to make a folder in my pen drive root directory, and put inside a new file called dp_install_tool.cmd containing instruction you wrote above. Is it correct? And what about the dp_install_tool.cmd existing in the sources\$OEM$\$1\D\SAD3 directory? Have I to delete it? And about setupcomplete.cmd file, in the sources\%OEM%\$$\Setup\scripts folder? What have I to do with these 2 files? I ask you that because I tried to keep everything original, just joining new dp_install_tool.cmd file in the root OEM folder, and install it from a pen drive on a virtual machine. But nothing happened... Hope you'll understand me, I know my english is very bad...
Thank you again for you kindness
3 2015-08-29 02:39:24
Re: Stand Alone Driverpack utility for all OS (XP, 2k3, 2k8, Vista, Win7) (525 replies, posted in Windows 7 tools)
Did you leave me alone?
4 2015-08-23 20:06:03
Re: Stand Alone Driverpack utility for all OS (XP, 2k3, 2k8, Vista, Win7) (525 replies, posted in Windows 7 tools)
Welcome to DriverPacks.net.
Thank you for the kind words. I think you may have missed something that most of us either think is obvious, or at least well known. the way the tool works is; it sets a RunOnce registry command to delete the folder when the computer is next rebooted. If you haven't rebooted the computer before checking for the "D" folder. There is a very high probability that it WILL still be there... Since it is not supposed to be deleted until the First Reboot AFTER the tool runs. Again this is often missed or not known. Sometimes users overwrite or erase the RunOnce command by accident. The reason is simple it gets around any issues of files that may or may not still be in use .
Please reboot the target machine before verifying whether or not that the cleanup is complete.
Report your results. Hope I guessed correctly.
PS please don't wait 6 months to ask, someone here prolly already knows the answer.
Hi OverFlow, thank you so much for your kind and quick reply. I follow your advice, I tried to make a fresh installation of win7 home premium x86 in a virtual machine on VMWare, but, after rebooting, that damn "D" folder was still there! I also noticed that, after finishing drivers installation, machine is very very slow, almost frozen, and replies to commands in a very slow way. When I reboot it, a message of "waiting to close program" appears, referrring to Windows host. After several seconds, system reboots, but "D" folder is still there at the logon.
Where's my mistake?
Thanks a lot, and, please, forgive my ignorance...
Edit:
I tried to download again a fresh version of SAD3, because I was not sure of my old DP_Install_Tool.cmd. I again tried the same installation above, but... Nothing happened. After reboot, the "D" folder was still at her own place. Pleeeeeeease, help me...
5 2015-08-23 04:38:50
Re: Stand Alone Driverpack utility for all OS (XP, 2k3, 2k8, Vista, Win7) (525 replies, posted in Windows 7 tools)
Hello guys,
First at all, thank you for this beautiful utility, it's great. But I'd like to ask something to developers, just an ultimate effort. At the end of win7 installation, the "D" folder remains at the %systemdrive%, and it's not deleted. It's 6 months, now, that I try to modify the DP_install_tool.cmd script to reach the target, but I'm not able to program, and I don't know commands and lines. I made billions of tries, but I can't find a way to automatically delete "D" folder at the end of installation, without receiving some error messages or having the cmd window open giving me error messages. I also tried to follow other user's suggestion, but I didn't reach any good result. Please, it's so frustrating for me to have that "D" folder, whitout being able to automatically delete it, without receiving any error message. Could you help me, please?
Thanks again for yor great job and your help