Search options (Page 75 of 213)

most of the high end creative cards (and others too) require that their Setup.exe is run after the basic driver is installed.

If the setup is not run the card will not function or will function in a diminished capacity.

therefore the Full installer must be included in the pack...
These are huge since it is not simply the driver files, but all the control panels and related applications as well.

There is no way around this... It has always been so...
The size of these installers continues to grow with age only making it worse.

there have been several revisions of nightlies since this post... were not quite done yet... stay tuned!

was this a new install? did you use DriverPacks with your new install? what OS are you installing? SP level?

can you check out read before you post in my signature? DPs_BASE.log is helpful and will answer many of our questions.

did you folow our tutorial? (link in my signature)

Um we are THE guys who install drivers from pack.
(The original and The best)

thus our name DriverPacks

Welcome to DriverPacks 

tutorial in my signature

those other guys don't have as good an archive as us... and they charge.

I don't really care how good you think it is... or even how good they think it is...

If it is reporting false positives... then it is junk
How much of your time has been wasted, just on this issue?
What about our wasted time?
If someone wastes a few hours of IT time it will definately cost them more than what they thought that they had saved on the AV program. (even worse if they paid a premium price)   False positives cost time, lots of time, and time is money. 

Can you confirm the virus using another scanner of your choice?

Have you submitted the file to Quick Heal for evaluation?
did you check the hash on the file before and after your process to see if it actually is being changed?
were you able to reproduce the exact same result each time (IE more than once)
Are you runing any service packs as part of your setup that might update this file?

I assume you are doing on access scanning...
your source shows no virus,
DriverPacks shows no virus,
DriverPacks has to be the last step in your process before ISO creation..
So where does it come from?
(It is a magic teleporting virus that can add itself to WORM media )

(( You never answered my question:

Was the network card plugged in during the install?
(link light on, and conncted to a network... and possibly the internet
- I am going to bet the answer to that question is YES. Since it went unanswered)

that would explain different results each time... you are just getting a different virus from the net each time you install lol. if you give a machine internet access during an install you will have a virus before you get to the desktop. even local network access is risky

[are you installing from disc?]
If so just pull the network cable until you have your AV / Firewall in place .
Does the issue still exist?

))

We don't use Zip... and don't fool with ANY windows dll files.
txtsetup dosnet and setup... that is it, just those three.
we include our own un7zip app...

None of the team has heard of this AV...
collectively we service tens of thousands of machines. (daily)
DriverPacks is downlaoded at the rate of at least a million times a week.
this is the only report out of our tens of millons of users of this issue.
No one at all out of all those people also sees this issue... think about it...

the reviews you point to are all on their site... and not one of them is noteworthy...
Who cares if the  Mahratta Chamber of Commerce gave them an award???
(It is a small town with a specialty every one of the businesses is chocked full with MVPs CCIE's and other who saids)

I don't see a single reputable source, like Consumer Reports or PC magazine, in the list...

Google top AV programs / reviews
Check ANY independent list of top AV programs and topheal is not on their list.

So if they can't make a single top ten list, ever not once in 15 years... I think we can all agree it's junk.
And if you really paid as much as you would for Norton then you got taken to the cleaners.
I am sure they have no resources that even come close to compare to SARC.
Although I must admit i have been very disapointed with where Norton has gone since Peter left. I have stopped recomending all of their products for years now.

Either
1 resolve the issue with your process
2 resolve false positive with your prefered AV,  or get one that works...

Issue marked solved...

What file is infected?

Where did you obtain your XP source disc? is it a MS hologramed unit?

was the machine connected to the network during the install?

compare your version to the existing version(s) IE (date stamp, Provider and version from inf, also the date and size of .SYS file)

best of luck and thanks for helping us!

PS have you tried or are you useing the latest nightly mass storage pack?

We support the installation of the driverpacks with DriverPacks BASE

other methods may work... but they are not supported

try installing them as designed... Then you won't have any problems

Well i couldn't find that in the native drivers or in the Graphics C pack...

do you have a link to a 'tested and known to be good' driver (perhaps from Nvida) that works? We will slip it in!

PS... We do apprecieate that you tried to search for a related topic (Yea! He used serarch - Woo Hoo!).

       However the main Topic of this thread is in regards to the UNI to ANSI issue i fixed a couple of years ago

       Let's Do a new thread in Graphics Forum with a title that begins with [REQ] Nvidia RIVA.
       A link to here and a link to find the tested known good driver would be considered most polite.

Thanks for the feedback, it makes DriverPacks better for everyone

you are useing an older version of the hwids tool...

raid devices and compatable hwid info is not included... can we see the ouput of the current HWIDs tool>?

now by searchin the mass ini for those ids i can see which driver matches for textmode and by searching the pack i can find any compatable drivers I can then match those to a driver you link me to that we know works... (do you have a link to a working driver)
perhaps we jsut need to add that HWID to an existing driver (probably the case)

and what were the hwids in IDE / compatability mode?