You are not logged in. Please login or register.
Active topics Unanswered topics
Search options (Page 3 of 3)
DriverPacks.net Forum » Posts by symbios24
botus wrote:symbios24 wrote:I did everything correct from the beginning... before the tune up utlities internal addon as i do always
well there's one of your problems!
try a simple search... Description: TUProgSt.exe is not essential for Windows and will often cause problems
i did now have any problems before with this,do you know why its not running as before?
is this the reason that is not working in the log of dpbase? "Will not slipstream patches, Service Pack 3 was detected" ? or what that does it mean??
I did everything correct from the beginning integrating DriverPack MassStorage into the XP image along with other driverpacks with DriverPacks BASE following the guide and also integrate before the tune up utlities internal addon as i do always, and i noticed in the task manager through the shift+f10 option (writing taskmgr in the cmd) during the windows installation that the TUProgSt (TuneUp Program Statistics service) is not running at it should be,it was always running in the previous installations.anyone knows whats wrong here? ?
mr_smartepants wrote:No.
The whole point of integrating dpms into the XP image with DriverPacks BASE is so that the system can "see" the hard drive at the beginning of the install (known as "textmode"). If dpms wasn't installed properly, the blue install screen of XP would say something like "No hard drives found to install onto".
Simply replacing the dpms archive on the image with a newer one will only provide updated drivers to the system once the XP installer has already began the install process. Just because you haven't had any errors doesn't mean that it's a bug-free image, it just means that you were lucky.
SAD3 cannot replace DriverPacks BASE for what you need. SAD3 can only upgrade the drivers AFTER the install has taken place.
thanks again i was confused it has the same name "dp_install_tool" as sad3 has.so i though if i replace with the newer files it will work.i tried sad3 before for a windows 7 lite image(700mb) but it did not work.i followed any possible instructions that are in the start of this threat but no luck.
botus wrote:symbios24 wrote:Hello i have install it also in some newer machines without a problem anyway lets do it correct how do i add it with dpbase ?
Two points,
1) Overflow suggests you probably don't need to update mass storage... As you say your current image works on yours and other systems. So for the kit you are working on you don't need to do anything. The only need to update mass storage would be to work with much newer / current hardware.
2) To update mass storage anyway (and from mr_smartepants last post I think he adds clearer advice, and the way I'd do it) you can have a modified image (e.g. where you have added service packs / updates etc.) its just that you should always start from this point and then add driver packs last... and for your project, you will not have full success unless you add mass storage to a previously unmodified by driver packs image
thanks for your help,is it possible to replace the dpbase with sad3 to delete all the folder and add the sad3 folder etc. will this work without massstorage integration by dpinstall tool??
botus wrote:symbios24, I suspect the frustration from those trying to help you is because you are not getting the message on how complex the integration of the mass storage pack is and therefore what its doing to your install image.
Overflow is clearly saying do it one way only....
Overflow wrote: in order to upgrade / swap mass storage you must use DriverPacks BASE to slipstream the new version
your way is wrong
I'm guessing just because you updated it "your way" and seems OK for you doesn't mean your way "works". Its probably that you have been very lucky and working on really old hardware where its not needed anyway, so you haven't noticed you now have a dodgy image that will crash out if you ever use on other systems/hardware
Hello i have install it also in some newer machines without a problem anyway lets do it correct how do i add it with dpbase ?
mr_smartepants wrote:symbios24 wrote:my install finds always a harddrive achi or ide so i just replace the old masstorage pack with the new in this case??
NO!!!
This has already been explained to you several times now.
Don't touch dpms.
The ONLY way to update dpms in your XP install image is to rebuild the entire image from scratch and integrate the new dpms with DriverPacks BASE.
Did you build your own image or was it built by someone else?
it was built by someone else i have only update it. but it`s strange there was a previous masstorage pack v901 and i update it with DP_MassStorage_wnt5_x86-32_1209 and i got no errors problems/missing drivers.
OverFlow wrote:mass storage has to be integrated into the disc with DriverPacks BASE. It becomes a part of the installation file set. Otherwise your install would not be able to find a HDD to install onto.
in order to upgrade / swap mass storage you must use DriverPacks BASE to slipstream the new version. It is unlikely that you need a newer version. has your install failed on a machine?
where did you get your install disc?
this is starting to remind me of F*cnutFour...
my install finds always a harddrive achi or ide so i just replace the old masstorage pack with the new in this case?? its just the pack that is over 2 years old
DP_MassStorage_wnt5_x86-32_1405176.7z is not going to work??
i want to put a complete collection of updated driverpacks which ones should i put? and i must use sad3 or the old driverpacks program will do?
its difficult to find new drivers here since i have to search in every post,is it possible to make only one post for new drivers only for any device ?? instead of many different posts?
the link for all latest [Nightlies] its not working can you fix it?
OverFlow wrote:i tested two of the listed packs, and the new dll was not required. techdud left them as they should be packed for DriverPacks BASE XP slipstream. Try it just replacing the packs first. (except mass storage, mass storage must be slipstreamed with DriverPacks BASE)
yes if you want to be able to support any video card, even really really old ones then add the 3rd party DriverPack.
difficult to add it with the base program since i don`t want to create the iso or the driverpacks installation from the beginning but only to replace the old one`s with new
is there another older version(except the latest official in the download page) that is not require dpbase?
and is necessary to put both DP_Misc_wnt5_x86-32_1308272.7z and DP_SmartCard_wnt5_x86-32_1403281.7z ??
as they both have card readers drivers if not which one from the two is better to put ??
thanks
OverFlow wrote:Did you make any changes to your XP install disc after you added DriverPacks?
Did you fail to make a copy of the disc from immediately before you added DriverPacks?
if the answer to either of these questions is yes then it is unlikely that your mass storage drivers can be updated.
the other drivers may be updated simply by replacing them with newer versions 
(woo hoo)
it's that simple for all but mass storage
i did not test my xp disc yet i have put the driverpacks only (without sad3) i will test them with the old dpinstall tool
another question are this driverpacks enough to detect any vga card old or new
DP_Graphics_A_wnt5_x86-32_1401181.7z
DP_Graphics_B_wnt5_x86-32_1408051.7z
DP_Graphics_C_wnt5_x86-32_1403071.7z
or i also need third party`s driverpacks too like this one for example??
DP_Graphics_ATi-Legacy_wnt5_x86-32_1312081.7z
and last i only update the 7-zip32.dll file replacing the old one right ??
thanks
OverFlow wrote:IDK until you answer my question
IF a nt5x86 pack is SAD3 dependent. (This should NOT be the case.)
Please give details IE links to these packs and list of affected drivers.
Are you trying to update a DriverPacks slipstreamed XP install disc?
or are you trying to add SAD3 as an additional feature to an Install / repair disc?
Help me to help you
you mean you want the page that i get the driverpacks here?
if i give you the names will be easier
this are the new driverpacks
DP_Bluetooth_MS-Misc_wnt5_x86-32_1408061.7z
DP_Chipset_wnt5_x86-32_1308271.7z
DP_CPU_wnt5_x86-32_904.7z
DP_Graphics_A_wnt5_x86-32_1401181.7z
DP_Graphics_B_wnt5_x86-32_1408051.7z
DP_Graphics_C_wnt5_x86-32_1403071.7z
DP_Graphics_PhysX_wnt5_x86-32_1408051.7z
DP_LAN_wnt5_x86-32_1408061.7z
DP_MassStorage_wnt5_x86-32_1308271.7z
DP_Misc_wnt5_x86-32_1308272.7z
DP_Modem_wnt5_x86-32_1403111.7z
DP_Phone-Mobile_wnt5_x86-32_1406041.7z
DP_SmartCard_wnt5_x86-32_1403281.7z
DP_Sound_A_wnt5_x86-32_1406011.7z
DP_Sound_B_wnt5_x86-32_1406021.7z
DP_Sound_C_wnt5_x86-32_1406011.7z
DP_WebCam_wnt5_x86-32_1405281.7z
DP_WLAN_wnt5_x86-32_1408061.7z
DP_Graphics_ATi-TV_wnt5_x86-32_1310291.7z
DP_Graphics_ATi-Legacy_wnt5_x86-32_1312081.7z
and the old driverpacks i had before for xp are those that already available in the latest,in the driverpacks download page
OverFlow wrote:[GUIRunOnce]
%SystemDrive%\Dp_Install_Tool.cmd
is the short answer... BUT what NT5 packs "require" SAD3???
Related help: http://unattended.msfn.org/unattended.xp/view/web/18/
this is going to require some detailed / specific instructions from me to make work...
IF a nt5x86 pack is SAD3 dependent. (This should NOT be the case.)
Please give details IE links to these packs and list of affected drivers.
There will be issues with the GUIRunOnce listed above... related to timing
http://unattended.msfn.org/unattended.xp/view/web/31/
Guirunonce runs AFTER user logon as that user, RunOnceEx runs PRIOR to user logon. If AutoLogon is enabled they will seem to run at the same time 
.
you should not run commands after a command that forces a reboot, the rest won't run or will be ended while running 
.
Thank you for your help can i put the silent switch /S in the end also? and where i put the driverpacks?? inside the OEM\NT5\x86 folder or i leave them in the main folder of sad eg. "OEM"
i want to put a newer version of driverpacks program since the one included is too old and it`s not working with newer driverpacks as some of the require sad3,but i dont want to go from the beggining create the windows disc again so i`m asking how can i replace the driverpacks program in the windows disc(iso) with a newer one? just replace the folder or do something more?? In General words if i want to put winxp sad3 with the driverpacks in a winxp disc in the readme file of sad3 it says:
How to add ISO's:
%WinXP-Disc%\$oem$\$1\ (entire contents of SAD3 folder with all DriverPacks goes here %systemdrive%\)
%WinXP-Disc%\$oem$\$1\DP_Install_Tool.cmd
Call the Dp_Install_Tool.cmd from winnt.sif file which will go in %WinXP-Disc\I386\WINNT.SIF
what is the call thing i don't understand what i have to put in the winnt.sif file??
i searched in the disc that has the old driverpacks program in the winnt.sif file it has this:
[GUIRunOnce]
command9="%SystemDrive%\DPsFnshr.exe"
wucdcreator="wscript.exe %systemroot%\RunOnceEx.js"
so what i put for the sad3 in this file??
Hello i have a custom made winxp disc with the old driverpacks program how can i add the sad3?? i just replace the old DP_Install_Tool.cmd with the new one? and also after the setup of drivers finish it deletes the files used will if i replace the old tool with the new one it will do the same or i need to do something more that replacing files?
in final words how do a i add it to a winxp cd that already has it but it`s a very old version(2009)
and a last one which one should i use sad2 or sad3?
thanks
bigfoot wrote:Without seeing what is in your sysprep mass storage section, I/we can't help you much. It sounds like your ahci driver is not being loaded correctly.
Here is my custom xp pack for mass storage. Sysprep.inf with populated mass storage section us included. Make sure drivers are in c:\d\m folder if you wish to try it out.
http://www.mediafire.com/?kshl9q7ls4wapuk
Hello did it happen to update your custom xp pack for mass storage txtmode drivers?? it`s very difficult to find them one by one
thanks
mr_smartepants wrote:Your first line is using both forward & backslashes in the path. That's wrong. \o/
The environment variable %systemdrive% will point to the drive letter where Windows is installed. In most cases this is resolved to: C:
Please post the entire contents of your setupcomplete.cmd here. Copy/paste (don't free type). Use code tags.
Also copy/paste the entire path where your setupcomplete.cmd file & SAD3 folder is contained on your .iso
The instructions are in the first post.
Create the following folder structure to your Win7 disc:
{Win7-Disc source folder}\sources\$oem$\$1\D\SAD3 (entire SAD3 folder with all DriverPacks goes here)
{Win7-Disc source folder}\sources\$oem$\$$\Setup\scripts\setupcomplete.cmd
Add the following code to the setupcomplete.cmd file.
@echo off
START %systemdrive%\D\SAD3\DP_Install_Tool.cmd /s
my setupcomplete.cmd file path is "sources\$OEM$\$$\Setup\Scripts"
and my SAD3 path is "sources\$OEM$\$1\SAD3"
my contents of the setupcomplete.cmd is
@echo off
START %CDROM%\sources\$OEM$\$1\SAD3\DP_Install_Tool.cmd /s
DEL %0
i tried by adding the extra D folder
@echo off
START %systemdrive%\D\SAD3\DP_Install_Tool.cmd
its not working.
i saw this and i put exactly what i saw i did not think that the systemdrive needs to be changed sorry so i put in the script:
@echo off
START D:\sources/$oem$/$1/D/SAD3\DP_Install_Tool.cmd
OR
@echo off
START %CDROM%\D\SAD3\DP_Install_Tool.cmd
I tried both options in the iso but they did not work 
the last attempt i did was with :
@echo off
START %CDROM%\sources\$OEM$\$1\SAD3\DP_Install_Tool.cmd /s
DEL %0
But did not work also, but when i run the the setupcomplete.cmd manual from the disc it setup`s the drivers normal
Any Help ???
Hello thanks i did not saw it at all, what i put in the systemdrive?
Hello Great tool i`m using the one for xp for years now
I currently having problem trying to integrate driverpacks to a windows 7 sp1 32bit iso using this tool
what i do is create the following folders in sources: $oem$/$1/D/SAD3/ and $oem$/$$/Setup/Scripts/
after that i extract the tool in the folder sources/$oem$/$1/D/SAD3/
and put the compressed "7z" driverpacks into the sources/$oem$/$1/D/SAD3/NT6/x86 folder and the setupcomplete.cmd script in the sources/oem$/$$/Setup/Scripts/ folder
the script it self has the commands:
@echo off
START %systemdrive%\DP_Install_Tool.cmd /s
DEL %0
and save the iso
after the windows setup finish nothing happens no drivers installed
what do i do wrong???
Posts found [ 51 to 70 of 70 ]
DriverPacks.net Forum » Posts by symbios24
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.016 seconds, 5 queries executed ]