gonna put AVG on (first uninstall avast, of course)
I want to see wether avg free still complains/blocks.

if it does; we users, we can write them a friendly word?

(I am Flemish, and have used "tinker" as description for aaages. So here is a puzzler, "what is a tinker?".

Is it a guy like Tinker Dill... or a smithweld? Or both?
(TIPS, Ask Lovejoy; or your local Great-granny.)

Grinz.
Hey, real knowledge can come from a googlebunny. Even a Blonde googlebunny.

Cheers
MC.

Avast warned, so I chose "no action", and it let me run driverbase.

I tried that with AVG Free, i hit ignore and it still wouldnt let me use it, a complete uninstall is the only thing that worked.

I think its cuz its the free version.

Symantec antivirus also reported that it is a virus
I uninstalled the SAV then reinstall it after finishing every thing
Thanks

There's no need to since you can simply exclude the file from being scanned.
This setting is saved so even on any consecutive slipstream processes it will never bother you again!

Avast warned, so I chose "no action", and it let me run driverbase.

this must be because of a recent update, because it did not do that a week or so ago (when I was building a couple RAID enabled booters.).

will see wether Avast  sees it as a danger in my other machine.
(where I did not yet use BASE it for that one is a x64 driven system).

Thanks for the driverpacks effort.
Before I found this site, I was trying to slip the drivers I needed into my anwerfiles all by myself,  to build me my own, so I know it took considerable time and effort to do this for us.

another note, I wanted it to boot with RAID support (my machines have two raid chips in them, and one of them is actually running two striped/mirrored raid arrays. The other has just a stripe)
More important to me, I had to able to get to the repair console after booting off the CD and see the drives.

With your tool and driverpacks, I managed to do that.
Then I posted how I did that...
http://www.cybertechhelp.com/forums/sho … stcount=39

Kind regards, Jaak

Problem is, although this is a completely harmless operation it is being abused by some malware/trojans/keyloggers so it got
blacklisted.

Yep, that's the cause. It's not a virus though... just a tool to hide windows...

I agree

In DriverPacks BASE 6.07, this tool won't be used anymore: the finishing script is completely rewritten. No more worthless, yet annoying virus warnings!

because if you go that way, one had to blacklist Windows as well, as it enables these malware to execute ;P

LMAO

Probably the cmdow.exe is triggering the false positive. NAV and SACE both classify (wrongly) that cmdow.exe is a hacktool.hidewindow threat.

Well, the both riight about it in so far that it does indeed make use of the hidewindow feature (that's what it's being used for in the DriverPacks).

Problem is, although this is a completely harmless operation it is being abused by some malware/trojans/keyloggers so it got blacklisted.

A shame really, because if you go that way, one had to blacklist Windows as well, as it enables these malware to execute ;P

Anyway, last I heared is that NOD32 is supposed to be a good scanner.
Still using NAV and haven't checked out yet, but maybe you should

maybe AVG says all *.exe are suspicious

But yea Rogue it sucks