You are not logged in. Please login or register.
Strange, I'm not seeing that error.
When you start the batch, what path is being given on the screen that says "32-bit DriverPacks will be installed from..."
Uploaded v110502.
I'm taking this test in a virtual machine, see the problem:
(click in the image to enlarge)
The file structure of the SAD DVD:
http://img854.imageshack.us/f/filestructure.jpg/
Error screen part 1:
http://img839.imageshack.us/f/errorscreen1.jpg/
Error screen part 2:
http://img703.imageshack.us/f/errorscreen2.jpg/
Just after the first screen, it ends the batch file with the message "O sistema não pode encontrar o arquivo especificado." (The system can not find the file specified.)
Last edited by rafaelr (2011-05-03 01:52:46)
Ah, you're using method-1. OK, now I know where to look...
v11.05.03 uploaded.
Brother, it seems the problem is persisting...
On the first screen until it was ok, now recognizing as "D:\NT6\x86", but soon one second after I click to continue, no files are copied and the batch file ends prematurely...
See the screens:
ARrgggghhhh! OK, more testing....
*Edit
Aha! Got it. dpinst.exe wasn't being copied to your "%SYSTEMDRIVE%\D\" folder.
Fixed!
v110504 in first post.
OPS! The DPInst.exe is needed in a method 1??
I was deleting the DPInst.exe... left only a folder "D" in each subfolder "x86" or "x64"... is that the error was it then??
I'll try again here...
EDITED: Ah... Now I noticed that there is a "DPInst.exe" inside bin\DPsFnshr.7z, this must be what you are referring...
Last edited by rafaelr (2011-05-03 23:21:11)
Nothing yet ...
I tested two times, with and without the files "DPINST.exe" and "DPInst.xml" in subfoilder "x86"...
http://postimage.org/image/6e9uxu6c/
One question: should it must copy the driver files correct? Even though I already have all recognized devices in the system?
No, there are 3 versions of dpinst.exe, each goes in it's own folder. DO NOT REMOVE THEM!
You'll have to restore the files from the SAD2-110504.7z archive to the right folders. In fact, just extract the archive to a new folder, and copy your old \d\ folder to the new extracted SAD folder. That way I'll be sure you're not tampering with the contents of the \bin\ folder also.
I tested this using method 1 & 2, on all three OS (XP, Win7 32-bit and 64-bit) without ANY failures. I'm sure it's because of something you're doing to induce the failure.
*Edit
Nevermind. I know how I can code this to be failsafe! 
Do I delete the "DP_Chipset_wnt6-x86_1105.7z" file in "NT6\x86" before copy the "\D\" folder or not?
Man, I tried exactly this way you suggested:
Unzip the contents of "SAD2-110504.7z" to a folder, then just added the whole folder "\D\" with the drivers unzipped to "NT6\x86" and made an ISO to test the in the virtual machine ... did not work!
Then, just deleted the file "DP_Chipset_wnt6 x86_1105.7z-" from "NT6\x86" and also did not work! I do not understand what I'm doing wrong...
Funny thing is that the 110312 version seemed to work properly!
OPS!!!!!
Looks like it worked when I copied the entire contents of the ISO to a folder "C:\SAD", and run the "C:\SAD\DP_Install_Tool.cmd"... Seems to be some Windows 7 permission problem when I try to read directly from the DVD-ROM drive...
SCREEN 1:
http://postimage.org/image/k0hs1dc4/
SCREEN 2:
http://postimage.org/image/ms9jcco4/
SCREEN 3:
http://postimage.org/image/msmrn4mc/
SCREEN 4:
http://postimage.org/image/k1i5v078/
SCREEN 5:
http://postimage.org/image/mti6uq04/
SCREEN 6:
http://postimage.org/image/mts42sys/
Would it even then? Should I copy all SAD DVD content to a folder in "C:\"?
Last edited by rafaelr (2011-05-04 07:47:57)
Do I delete the "DP_Chipset_wnt6-x86_1105.7z" file in "NT6\x86" before copy the "\D\" folder or not?
From the readme.txt:
Method 1 will fail if the \NT6\x86\ folder contains any .7z DriverPacks.
OK, v110505 is linked in the first post. I fixed the bug where the script was trying to write the log file to the read-only disc (causing your failure). I also coded it to extract the needed dpinst* files from the \bin\ folder.
Yeah, I read this but was in doubt ... But my last test was without the .7z file !
I will test this new version now.
One minute boss...!
Last edited by rafaelr (2011-05-04 08:23:03)
Yeah!!! Now is working perfectly!
Congratulations for more this good job and sorry for any wrong procedure on my part! 
Regards!
Thanks for reporting the problems. Now the SAD utility is better because of it. 
Just done a VHP32 with the 110505 faultless!
I think your nickname suits Erik!
Glad to hear the good news. You know, these things only get better when folks try them in weird & wacky ways and report the bugs.
And because this is open source, I'm sure some enterprising soul with better code skills than me will take this, improve it, and give back to the community.
I love this place!
I've been having issues with the script. It keeps dropping the network share when it launches the VBS script.
I'm thinking it might be best to switch to an executable that elevates the script, such as http://code.kliu.org/misc/elevate/
Nice find. I like code65536's stuff.
hi, i'm a little confused when to use this and at what stage,
i have created a system (virtualbox) win7 and ready to sysprep it (ghost the image)
on my host (WAIK & supplement sp1 installed)
and put in MDT 2010 update 1
i'm now in deployworkbench (and there is out of bos drivers)
but this is where i'm lost.
where do i run the script,
can't i just put all the drivers in the deploymentworkbench, or am i completely in the wrong place?
this is the scenario that i'm aiming for.
create a universal image
Virtual Box (windows 7 starter installed)
sysprep this image,
deploy image on Desktop PC's/laptops
upgrade anytime to relevant level (if pc/laptop has key for pro, then upgrade to pro level, then use that key to activate)
of course i wish to insert drivers into the main image itself (i don't wish to utilize network shares for problems like connection issues, or network card not found problems (laptops sometimes use weird network systems))
i want the image to be self sufficient as possible and method 1 seems the best choice
i just don't know where driverpacks fits in, i tried to use winintergrator but my host is XP sp3 so it didn't work (strange as even WAIK and MDT 2010 is compatible with XP sp3 which i was amazed that MS went through that trouble kudos to MS for that)
appreciate any feedback,
thanks.
Hello mr_smartepants & rafaelr,
I need both your help to resolve or explain to me a way that I can integrate DriverPacks Drivers for Windows 7 using and during the initial R7Lite Build before the ISO Build and Burn step of RT7Lite.
One of my question is, Can I use the SAD2 utility to do this and if so how? What stage of R7Lite should I do this.
My next question is there a way the DriverPack .7z file can be detected by RT7Lite.
Please, response ASAP. I really need an answer for this. I have being googling and reading for a month now trying to find a utility that will allow me to Slimstream SP1 and integrate DriverPack Driver .7z for Windows 7 Utl but have not found it. I need your help and suggestion. I like to include the DriverPack Drivers , chipset, MassStorage, LAN, and WLan so that I can install Windows 7 an any machine.
I don't know. I've never used R7lite. I execute mine manually once the desktop loads.
Hello mr_smartepants,
Could you explain more in detail what you mean by once the desktop loads. Are you saying during the installation of Windows 7 and not part of the Build ISO.
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.022 seconds, 11 queries executed ]
