Discussion in 'ESET NOD32 Antivirus v4 Beta Forum' started by Cosmo 203, Jan 18, 2009.
Thank you - for both: Answering and investigating.
The last sentence of Marcos makes clear, that AIK is not applicable for a number of ESET customers. A number which is great enough to consider this fact.
Who could argue this better than an ESET moderator?
Do you even have the slightest idea how hard it is (for a non-OS developer!!) to
include the most important drivers, the hard disk controller drivers, automatically into a recovery disk, and then every single one of them out there?
That's why the AIK is there for, to gather them for at least the current HW setup.
I've never came across a single software that does this automatically for every peace of HW that's been ever made.
The BartPE plugin might work for you because either
You know how to implement drivers
the latest SP for XP got all the drivers you need for your setup included
You realize that this is not a solution for everyone, do you?
I too would really like to see a BartPE plugin...
Too bad ESET damaged their relationship to the UBCD4WIN project leader by ignoring the fact that NOD32 was issuing FPs on the UBCD4WIN installer package a couple of years ago, otherwise, they could easily add the ability to auto-update the definition files when creating a new UBCD4WIN boot CD...
Regardless, I'd still like to see this plug in made available, and maybe an effort to patch things up with the UBCD4WIN project...
Because you asked:
If you would have read my posts in this thread carefully, than you would have read my basic description about that. So the answer is: Yes.
What "slightest idea" do you have? (Besides obviously not reading)
The question of needed drivers has in PE Builder for Bart PE nothing to do with the plugin. If the drivers would not be there, the whole disk would not work (at least there would be no access to the hard drives). So in fact the question is wrong.
The plugin simply provides the functionality of the program; even for updating the definitions there is nothing special needed, this is the part of Bart PE (regarding the driver question).
I do realize that. And I do realize, that the Bart PE solution would be a solution for the greater part of the users. Where did you read, that ESET shall remove the AIK solution?
Otherwise you can tell tommygun, what he shall do in 2 days, the download of the AIK takes on a modem connection (theroretically) and how much he has to pay for that. ... and that he cannot use Internet and E-Mail in those 2 days.
In fact, you're obviously not reading your own posts:
It's not as easy as that, got it?
WindowsPE / BartPE
They are not the same. Get your facts straight.
The Link is dead or has been removed.
But officially, using BartPE is definitely not support by Microsoft.
On the second part of this MS page (http://support.microsoft.com/kb/315341) you will find the link for KB 894950. The article does exists, the page is at this time not reachable. Never seen this?
Regarding Bart PE: What is not easy: To unzip the download file? Okay, than this is not for you. As you said it yourself: Not for everybody.
Take it easy buddy, I'm an It Professional and therefore, think in place of those that are not. What are you?
Oh and BTW: The above statement is so wrong it hurts. Additionally, you have to do a lot of things to make a BartPE running an a specific setup, as you mentioned by yourself. And as already mentioned from my part, it's not full-automatic so go figure.
It with a little T. If you claim to be a professional, I would not like to be called by the same title on te same place.
And I will not attempt to tell you more about Bart PE in this place, as you already showed, that you did not even read, what has already been written. If it hurts you because you did not understand and do not read, then as said this is not for you. Take the some thousand of Megabyte Download and get happy, but don't forget, that you have to install all the necessary parts, there is no beloved automatism. Repeating the same misunderstanding repeatedly dos not make it true.
BTW: An IT Professional would know, that one quotes the part, where the answer belongs to, not the whole post. So far about self-declared pro's (who most often use this title, if the arguements are running out).
It's not my fault if you're unable to match parts and answers. Oh and for the I't' part: Little nit-picky there right?
Maybe you didn't figure that English is not my native language but I guess it was my mistake to believe that somebody like you would find this out without actually knowing.
If this is the only way to defend yourself, so be it.
This threads done fore me. I have better things to do than discussing with amateurs what I earn my money for.
Enough flaming each other, this thread points to a real issue and you're drowning it in your bullshit. Hope a mod can clean this up.
Are you sure about it? I can not find link for KB 894950 on mentioned page. It looks to be removed.
Yes, I am sure.
See the screenshot, which I made today, see the mouse pointer.
There does exist a list of KB articles, where the momentary not availible kb 894950ist listed and here is a reproduction of the questioned MS page.
A bit off topic but perhaps someone can help me.
After successfully creating a rescue disk, it doesnt recognize my hard disk booting with it. Is there some way to add the hd drivers manually into the recue disk?
edit: Nevermind i found it:
Yes, there is.
1) You can use "Aut. Search." button and then Wizard searches for currently installed drivers for SCSI controllers and NIC cards in OS which you are running. This option is available only if you have 32-bit OS.
2) Another option is to download drivers from internet and to use "Add" button. You need to locate .inf file in the driver package. All other driver files (.sys, ...) must be in the same directory. Simply you extract driver package if it is packed, and locate inf file.
Thx trencan. Another quick question. Is it possible to do a clean SysRescue boot cd from an infected system. Are the files included in the SysRescue cd always clean although there are infected for example system files ? Thx
SysRescue Wizard uses as source WinPE files (so not files of your currently running OS) which are packed in "winpe.wim" file inside your WAIK installation (it is something like virtual HD file). If this "winpe.wim" file is clean, SysRescue CD should be clean too. But still I can image that if you have infected system while creating SysRescue CD, malware can infect files inside WinPE, but it must be malware which is really dedicated for this purpose, so hopefully very small probability.
Separate names with a comma.