links to external mortgage solution companies deleted from OP's first post.
I would have just banned imediately thinking it's a BOT.
if it smells like an elephant
Your call.
PS If its a real person they will / can create a new account
You are not logged in. Please login or register.
DriverPacks.net Forum » Posts by OverFlow
links to external mortgage solution companies deleted from OP's first post.
I would have just banned imediately thinking it's a BOT.
if it smells like an elephant
Your call.
PS If its a real person they will / can create a new account
http://forum.driverpacks.net/help.php#bbcode
Image tags
[img]link[/img]
IE
produces:
[img]http://punbb.informer.com/img/small_logo.png[/img]
produces:
We will keep an eye on this issue... if it becomes important we can get Wim to open a ticket .
I just did a quick check here List of servers
IDK which one you may have been routed too... (it may not even be the server it might be a router.)
tracert may tell you IE "tracert downloads.driverpacks.net"
you may compare with your buddie and see if you share a common destination or route.
If you do share a common route the common part of the routing would be nice to have .
What is the dest IP? (Probably the most helpful info) IE "Ping downloads.driverpacks.net"
ATM i am at e1c.simplecdn.net [206.55.108.97] (Working fine)
Reply from 206.55.108.97: bytes=32 time=31ms TTL=52
@all
If you are seeing this issue then please report!
the more feedback we get the more likely we can isolate the issue!
it is probably possable to add teh old installer too and set an exception to run that instaed of teh newer one when needed...
I am sure mr_smartepants is almost done as i write this LOL.
still nothing even without the 3rd party DriverPack?
May i see your DPs_BASE.log please...
Sorry we have not gotten any further on this except,
we belive that it is definately related to exceeding the length of the devpath entry in the registry.
If you are only useing the main DriverPacks and no 3rd party DriverPack and then nothing is detected
I wonder if something else is or could be adding to or erasing your devpath entry?
{applause}
I was waiting to see if anyone else posted
since the DriverPacks are worked on and then tested by a large team and then released to a large audience Many different virus scanners get a crack at the packs at every stage of development and release... if only one AV program is reporting a result then there is a 99.99 percent likelyhood that it is a false positive.
On the other hand there are hundreds of new viruses and trojans each month...
There is the .01 percent chance that your AV / defs is the first one to be able to detect it...
I would submit to them for review... why take our word for it?... go straight to the source and get the poop.
it would be even better if you could reply here that they responded to you taht they thought it was a false positive.
then you have saved not only yourself, but others in your situation. (they update the definitions for everyone)
"Help us to help you" is the spirit of DriverPacks, a spirit you obviously share with us.
I would have seemed a little daft if I had simply dissmissed you without considering the .01 probablity and anounced there was no virus... and then got bitten by that .01 LOL
Well Done! Excellent report!
Welcome to DriverPacks and we are glad you're here!
PS you never told us which LAN pack version?
Good thinking... hmmm
requires some post DriverPacks BASE editing... not normaly recomended, but is what you need if you are committed to going that way
replace PRESETUP.CMD with one similar to this untested example...
Rem 'Dest' is your desired alternate extraction drive... D: has been set for you as an example
Set Dest=D:
If exist "%systemroot%\system32\setupold.exe" DEL /F "%systemroot%\system32\setupold.exe"
REM +==========================================================================+
REM | Finding CD/DVD driveletter. |
REM |--------------------------------------------------------------------------|
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 CDDRIVE=%%i:& GOTO DPsFound
:DPsFound
REM +==========================================================================+
REM | Decompressing the DriverPacks to the harddisk - using un7zip.exe. |
REM |--------------------------------------------------------------------------|
Start /wait /realtime /separate "" %CDDRIVE%\OEM\bin\un7zip.exe %CDDRIVE%\OEM\DP*.7z %Dest%\
REM +==========================================================================+
REM | Copying/decompressing the files to finish the installation. |
REM |--------------------------------------------------------------------------|
%CDDRIVE%\OEM\bin\un7zip.exe %CDDRIVE%\OEM\bin\*.7z %SystemDrive%\
COPY /Y %CDDRIVE%\OEM\bin\DPsFnshr.ini %SystemDrive%\
IF EXIST %CDDRIVE%\OEM\*.ins COPY /Y %CDDRIVE%\OEM\*.ins %SystemDrive%\
REM +==========================================================================+
REM | Scanning for driverdirectories. |
REM |--------------------------------------------------------------------------|
%CDDRIVE%\OEM\bin\DevPath.exe %Dest%\D
REM +==========================================================================+
REM | Disable Driver Signing Policy and keep it disabled. |
REM |--------------------------------------------------------------------------|
START %SystemDrive%\DSPdsblr.exe
EXIT
it will also require an edit of the \OEM\bin\DPsFnshr.ini
[Settings]
; DO NOT SET THIS MANUALLY, LET THE DriverPacks BASE DO IT FOR YOU! (may NOT contain any spaced, if it does, all exceptions must be adapted to be compatible!)
REM DPsRoot = "%SystemDrive%"
DPsRoot = "D:"
; DO NOT SET THIS MANUALLY, LET THE DriverPacks BASE DO IT FOR YOU!
KTD = "false"
; system variables supported (see remarks for a list) one location cannot be used as
; KTDlocation: the root directory specified in[Settings]\DPsRoot
KTDlocation = "%SystemRoot%\DriverPacks"
; system variables supported (see remarks for a list)
logLocation = "%SystemRoot%"
; enables/disables debug mode (enabled by default)
debug = "true"
I think the finisher will handle it fairly well, however, certain exceptions will fail. (any that are hard-coded for 'C:\D\...')
Again this is not tested...
I think you could do fairly well this way - but is not the way that I would go....
---- alternate and probably a better solution ----
since you want a Disc that is specific to your machine, and only has to support your single unit...
I would just grab the handful of drivers you need and add them with nLite.
That is the quickest and easiest way to solve your space problems - and speeds up your install by ten minutes or more!
I like the way you think though, well done!
Welcome back! Glad to see you again.
did you try the Sound-Packs Release Candidates on the home page?
(did not mention which packs you used )
CDN will absolutely stuff your pipe... Speeds of 3MB are no problem for sure.
Everyone I have ever talked to says it maxes their connection...
they are rolling out fiber here right now... I am trying to get mine ASAP
Not that 7Mb down and 1Mb up are bad but 30Mb down and 10Mb up is better
perhaps your modem is just tired buffer 'OverFlow'
well it's obvious then that we (you and I) are neighbors, in a regional sense.
<---- you probably picked up on that
If it works for me it should work for you too... we are both probably hitting a server in chicago. (guessing)
do you have on access virus/trogan scanner? firewall? Proxy? unfriendly ISP?
http://forum.driverpacks.net/viewtopic. … 557#p34557
looking back at that issue i had an idea about what may have happened / caused the issue...
I think i just figured this one out...
dosnet and txtsetup are restored from backup if DriverPacks BASE detects it was previously run.
It is possable that you relipstreamed into a source that was previously "BASEd"...
On the subsequent run txtsetup.org and dosnet.org are restored to txtsetup.sif and dosnet.inf...
the .org files may have been created before you mad your "additions"... what do you think?
Just a thought...
do you know anyone else in your region to test for us? (where are you [country])
Perhaps you should use a proxy to fool cdn into thinking you're closer to another server / location. LOL
you can put SAD and integrated DriverPacks on one fully unattended disc
HINT call SAD from RunOnceEx
first pass OS installed with integrated main DriverPacks.
Launch SAD from desktop (automate if desired like from Startup, or whatever)
use search LOL - ROFL
Um... a good place to start IS to use windows search.
Extract WLAN then windows search the "D" folder...
Put *.inf in for the file name box
Put the PCI/VEN part of the related HWID in the
"A word or phrase in the file" box
That will list all the existing drivers that support that HWID. A good place to start.
Compare your version to the existing (there is almost always an existing, sometimes more than one.)
Then you compare each INFs supported HWIDs list. Is it a replacement or a supplement?
That should get you started
More info on how to mess with the packs is in the testing team forum...
Since it now seems it would be helpful to everyone...
WELCOME to the testing team!
PS no INI in teh wlan pack because we don't have any issues with it .
an entry in the INI file is like a black mark on that drivers name. It means it has an exception. it is a problem child. a non conformist. a black sheep. ( you get the idea )
Thanks for contributing, we like that alot!
stupid question...
The nvgts.inf goes in I386? "100"?
My memeory is failing and im too tired to look it up ATM
the driverpacks are deleted after the install so no space is wasted...
the driver packs are designed to support any machine (even laptops). That is the whole idea .
No you can't remove anything... and then still support everything.
...Think about the conundrum you are considering...
Laptops require all the drivers a desktop does... plus many more oddballs (fingerprint reader for example). If you want to cut down on the size... then you should not support laptops .
Can't have your cake and eat it too .
Wow that is a cooooool way to do it!
I learned something new!!!
Please test and report!
a simple solution would be a two step process
integrate the main packs and use SAD for the 3rd party DriverPack
Simple CDN supplys our downloads...
As far as we know... they just rock! our downloads have peaked out at around 1.5 million a day. We haven't had any new releases in a while so its closer to a million a week now... These guys have the ultimate setup for a Content Delivery Network (CDN) mutliple backbones geographicaly dispersed clustering... etc... It's possable you hooked up with a local server that was having an issue. (local to you) if that is the case your issue should not reappear. And explains why so few people might see it. (Rather than it affecting everyone.) We will leave this thread open and see if anyone else is haveing similar issues.
Again, Welcome and thanks for reporting, it makes you a valued member of our team.
Jeff
you have "patched" your install to be compatable with nvidia controllers that do not support legacy mode operation.
if either the drivers or the hardware are not found these registry entrys will be ignored...
Your "patched" hive will be valid until nvidia changes thier driver file names .
It is known now ...
Thanks for reporting!
Welcome to DriverPacks and have a great day.
PS which definition version gave the false positive... (date/ver)
SAD...
KTD is never needed... Why do you think you need it???
And KTD ALL is just ridiculous... this would never ever ever be needed. (And wouldn't work)
if you do really need KTD functionality then KTD is not the solution, it never was. It's a good theory and will work @ some hardware... however it is depreciated.
SAD is what KTD was intended to be...
Tell me what you are trying to do... I'll tell you the quick way to get there...
PS there are two programs that should mute the sound and close the popups... however there will be thousands of popups. one for every driver x 2
since your source has not yet been installed there is no registry... (yet)
The target machines initial registry is created during the install from hive files like setupreg.hiv.
to create or delete a registry entry, before windows is installed, the Hive must be modified...
this is done with regedit... Load the hive file, mod the hive file, save the hive file.
this does not affect anything except the setupreg.hiv file loaded from your source.
Please note the first command is making a backup "copy" of this file...
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.134 seconds, 5 queries executed ]