There have been several bug fixes in SAD / SoFI platform... stay tuned for a link
i do not belive that teh amd bug was reported before so that one we will need to look at after you try the new base ver.
thanks for reporting and have a great day!
You are not logged in. Please login or register.
DriverPacks.net Forum » Posts by OverFlow
There have been several bug fixes in SAD / SoFI platform... stay tuned for a link
i do not belive that teh amd bug was reported before so that one we will need to look at after you try the new base ver.
thanks for reporting and have a great day!
tell me if it works like
[GuiRunOnce]
Command0=%systemroot%\install\install.exe
;
; Edited by DriverPacks BASE 8.11.27.rc
; http://www.driverpacks.net/
;
command9="%SystemDrive%\DPsFnshr.exe"
I will look for things that may result in this - the log would have helped
not many people report on KTD and SoFI (the feature previously known as SAD) is going to be making KTD obsolete in the very near future. If it hasn't already.
perhaps someone has time to try to reproduce this issue for me. I will be glad to fix it if it is reproducible
Welcome to DriverPacks...
with all the recent releases of graphics and intel drivers chipset has been on the back burner with graphics and mass storage being the on fire items.
Thanks for the link and good info it helps. IDK if you still have access to the machine fut if you do can you post the HWID of the device that matches that driver? tool in my signature...
have a great day
it does seem like %DPSROOT%\D\S\CR1\Audigy.exe was not found.
this file does exist in sounda 8.05 \D\S\CR1.
it is likely you ran out of disk space or have coruption of the pack or had a glitch during extraction.
if you are able to repeat this please let us know
have a great day!
PS Awsome details and Title for a first Post. You obviously read before you posted. Well done!
PSS i agree with your finding that a mess was left behind when the finisher did not ... um ... finish finishing.
path length (i think) is 9019 that does not seem like a "round" number (IE 4096 or 8192)
it may be a finisher related bug... i will look at it now...
thanks for your excellent details, as always.
the misc pack should not have text files in the root, unless it is a test pack.
if it is a release then this should be reported in the 3rd party DriverPack forum in the misc thread as a bug. TIA if so.
brb
Wait a minute that is just garbage... that is not valid at all...
let me see your DPsFnshr.ini & DPsFnshr.log , please
if you type set KTD at a CMD window, does it return %SystemRoot%\DriverPacks ?
read the older base tutorial in my signature as a basic guide.
check out our home page and look at the last release candidate copy of base
it includes a Stand Alone Driver updater (SAD) feature.
I will be renameing this feature SoFI (Software First Installer) because it is really not SAD at all
you could download that release candidate version and ALL 10 of the main packs
SAD is not specificaly mentiond in the tutorial but it will get you started.
SAD is documented somewhat in the FAQ forum here...
see how far you can get with those hints and report back.
Did you use the driverpacks to update or install your drivers?
grunger please don't act like a five year old in a toy store...
the guys do this in their free time...
remember to say please and thank you and at least attempt to respect their time
it is my belief that the dos flag will not interfere with f6 although i have not actualy tested this myself.
A floppy is 7 dollars. if you can't figure out how to scrape together 7 bucks...
1 i doubt you will figure this out. LOL
2 i fail to see how the info would be useful to you if you have no access AT ALL to a floppy anywhere.
3 why you would expect us to support you for free (since you don't even have 7 dollars to donate)
it is a lot more fun (for you) if you give some details as to what you are trying to do. and hopefully that is related to DriverPacks
you tell me...
i belive it is the OEM flag that disables the F6 funtionality, and kills several other features that are helpful for an unattended install.
if you wish to use f6 then you probably also wish to do an attended install.
If you use DriverPacks BASE to add textmode mass storage drivers you will never need an f6 floppy again
that is why we are here
posted in wrong forum Feedback and Support moved to OTHER
Feedback and Support is for users of the DriverPacks BASE program and DriverPacks ONLY
In that case, when you get back, can you also tell us how long the path was?
base version please?
which 3rd party DriverPack did you include?
was teh device path blank or just missing the inf entry?
NO trouble at all!
that is why we're here and we are so glad to have been able to help you.
It is important to us that DriverPacks BASE works as intended for all supported platforms.
by reporting any problems you encounter we can ensure that continues to be the case.
Please continue to post any problems that you have and we will gladly help!
Most of the time it is not DriverPacks BASE, but if it is we need to know imediately so we can fix it.
This time there is nothing for me to fix... i like that solution the best of all .
Have a Great DAY and welcome to DriverPacks.net
We're glad your here!
Jeff
PS since those files get edited Four or five hundred times during the slipstream of mass storage that would mean that your virus scanner would have scanned them each time . HINT: On some scanners you can indicate folders that are not to be 'on access' scanned.
if you can not follow simple directions (from my previous posts) don't expect any help.
DPs_BASE.log?
raid hwid's tool in my signature...
start a new post in mass storage or bartpe forum
this is not appropriate here (read above)
use read before you post in my signature to get you started with good details
please see the bartpe tutorial in my signature
follow the directions - problem solved...
2008-11-27 01:48:51 : <SLIP> Removed entries from \I386\dosnet.inf that will be updated.
2008-11-27 02:03:41 : <SLIP> Updated \I386\dosnet.inf and \I386\txtsetup.sif to support DP MassStorage text mode drivers.
15 min ??? wow... that is a long time to edit a couple of text files...
this should take seconds even though the files are opened and closed many times during this step.
the files are open/closed for each line edit made. (the alternate options to do what we need to do are no better)
virus scanner w/on access scanning....?
read/write cache disabled...?
severe disc fragmentation...?
the file 'Fedit.exe' is being stomped by a spyware, malware or virus scanner?
02:03:41
01:48:51
----------
00:15:50
18min - 15min = about 3 minutes which is what you (and I) might expect.
i belive this indicates corruption of the txtsetup.sif (and) or dosnet.inf file(s)
Especialy since the biggest task here should have been cab compressing the mass storage drivers.
That apparently took about one minute
2008-11-27 01:47:06 : <SLIP> Processing the files now. This may take a minute.
2008-11-27 01:48:14 : <SLIP> Created QuickStream Cache for DriverPack MassStorage text mode drivers.
Please try a clean source and report!
Thanks for posting and have a great day
KB950162 Is a hotfix...
this hotfix is intended to correct only the problem that is described in the article.
Apply this hotfix only to systems that are experiencing this specific problem.
PLEASE READ THE ABOVE LINES AGAIN
It must be supplied BY MS to you directly.
if this is not the case then you have again reinforced the 'You can't follow directions' assessment
Furthermore lets reference http://support.microsoft.com/kb/950162
When application repeats the driver load and unload operation many times on a computer that is running Windows XP or Windows Vista, the computer may become unresponsive.
If you use the Memory Pool Monitor (Poolmon.exe) utility to monitor the IoSe and Pp memory tags, the memory that these two tags consume increases as every successful driver load and unload operation occurs.
Restart requirement
You have to restart the computer after you apply this hotfix.
This Hotfix affects how drivers are loaded. DriverPacks loads drivers (DUH).
I don't see any way to apply this hotfix and then REBOOT before the DriverPacks are installed.
IT may be that this Hotfix will more often than not kill a windows setup when it starts installing drivers.
That is this hotfix's core function to alter driver installation (guess you didn't read the info provided)
this is definately an ID-10-T Error...
therefore you have a choice one or the other - not both
(I suggest you install the hotfix and not use DriverPacks... please.)
Slipstreaming this HotFix is CLEARLY YOUR MISTAKE.
I will bet that you don't even need KB950162...
I have cash for this bet - if there are any takers
AGAIN YOU CAN'T FOLLOW DIRECTIONS
(i was jsut going to close this but... in response to Email I just received... here we are)
you just can't fix stupid...
Hint
after your machine is loaded
and you have VERIFIED the issue exists
REPEAT and you have VERIFIED the issue DOES exist on a specific machine
then IF MS has provided you (personaly) this HotFix
THEN and ONLY THEN feel free to install this hot fix on that specific machine.
(Don't forget that instruction i mentioned... REBOOT required)
- It is designed to affect how drivers load
- It affects Driver installs adversely according to your reports.
DO NOT slipstream this hotfix! ... Simple
you should not install any hotfix unless it is absolutely necessary!
and you need to install the OS to the machine first in order to establish this need.
Clearly not the way you're approaching this...
- Updates are a different story - have at! -
DPs_BASE.log ?
Thanks for the Excellent info cdob... (again)...
added to 81125rc... in testing now
Thanks newsposter his post has been deleted...
We dont need rapid share with simple CDN on the job.
Now that we are not useing dreamhost as one of our mirrors anymore we won't be having issues.
thanks for playing and have a nice day...
Solved in base 8.11.25rc
Solved in base 8.11.25rc
DriverPacks.net Forum » Posts by OverFlow
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.128 seconds, 16 queries executed ]