|
So altogther 30mb*30 + say 29mb*10 = 1190mb so around 1.2 gb of folders are definition folders.
If you want to save space or you are running out of space turn automatic update off on norton antivirus. This will mean though, that norton antivirus won't download the latest antivirus updates and you will have to manually download these from (Or manually run liveupdate in norton antivirus).
Link:
http://www.symantec.com/downloads/index.jsp[^]
Although this may prove time consuming if you have alot of computers.
Note: The files sizes you have specified are usual for definition files. If you are unhappy with these files sizes change to another antivirus solution such as:
Nod32 [^] or
Avg [^]
Or another one of your choice.
|
|
|
|
|
Most of what you say is obvious or at least I already know.
The one thing that would help is an answer to my question. Are your virus definitions that large? More specifically, how large is your VirusDefs folder?
|
|
|
|
|
Sam Hobbs wrote: Are your virus definitions that large
My definitions files are around 30 mb (some are nearly 32mb), this seems to be the usual amount for Norton antivirus definitions.
Sam Hobbs wrote: how large is your VirusDefs folder?
Currently my virusdefs folder is around 610mb.
I manually download mine every week, But as well as symantec i use spybot search and destroy for adware/spyware and lavasoft Ad_aware SE for adware and spyware.
I find that these together protect me from things that one can't detect, one of the others does.
|
|
|
|
|
the .tmp folders are almost certainly temporary files that your POS AV program isn't bothering to automatically delete. Move them to another location and if it doesn't start spitting out errors delete them after a week or so.
--
Rules of thumb should not be taken for the whole hand.
|
|
|
|
|
Of course that is a guess and I am capable of guessing like that too. If you have specific knowledge and/or experience that they can safely be deleted or moved then that would help.
I would expect Symantec to tell me I can delete them. I asked them and I have not received a response. I will likely try asking them a second time but if I don't hear from them I will likely move the files to another drive where I have plenty of space. I figured that out all by myself.
|
|
|
|
|
And their scanner is very much memory hogging too.
I prefer AVG.
|
|
|
|
|
how different is device driver development for XP compared to Windows NT?
thanks!
-- modified at 7:46 Wednesday 14th March, 2007
I am a SysAdmin, I battle my own daemons.
|
|
|
|
|
Given the ability of writing a driver under NT, it is much simpler under XP with the advent of the KMDF, Microsoft's Kernel Mode Driver Framework. KMDF includes default handling of most of the new stuff like power management and PnP notification. Granted the names of the functions are long (WdfIoQueueRetrieveRequestByFileObject), but they are descriptive  and the framework handle so much of the tedious stuff that was always error-prone like IRP cancellation. You still need to know the OS stuff like IRQLs and calling context, but it's no longer painful. Prior to KMDF, IMHO moving to XP was a pita becasue of power management.
Judy
|
|
|
|
|
Thanks!
So are my old books on Windows Driver Dev rendered obsolete? For example, I have Windows NT Device Drivers by Dekker and Newcomer which I think is one of the better books on the topic those days.
Can you recommend any good books?
I am a SysAdmin, I battle my own daemons.
|
|
|
|
|
No, they're all still good but now incomplete, not obsolete. As I said, you still need to know the underlying principles and the older NT books are a great way to get the "basics" before picking up the new stuff.
This is the "usual" list that gets given when folks ask about books on other forums.
"Programming the Windows Driver Model" 2nd ed by Walter Oney - make sure it is the 2nd edition
"Microsoft Windows Internals, Fourth Edition: Microsoft Windows
Server(TM) 2003, Windows XP, and Windows 2000" by Mark Russinovich and David Solomon
"Windows NT Device Driver Development" by Peter Viscarola and Tony Mason - dated but the stuff they discuss hasn't changed and it's a good foundation. This one serves the same purpose as your current Dekker book.
And finally, the book everyone is waiting for (and waiting and waiting, OSR says soon) - I've got my pre-order in already
"Introduction to the Windows Driver Foundation Kernel Mode Driver Framework " by Peter Viscarola, Tony Mason, Mark Cariddi, Brenda Ryan, Scott Noone, and OSR
Judy
|
|
|
|
|
how to create a customized file system for usb drive.which file syetem have read/write permission.
|
|
|
|
|
Start reading here[^]. I hope you're comfortable writing and debugging device drivers.
Dave Kreskowiak
Microsoft MVP - Visual Basic
|
|
|
|
|
Does anyone know of a good forum for asking questions about Symantec Antivirus?
This site, https://live-symantec.custhelp.com[^], has been suggested but I've been through the queue twice without connecting to a support rep.
Thanx...
>>>-----> MikeO
|
|
|
|
|
I am interested in the answer, too. I will post my question in a new thread in this forum but I am interested in knowing a better palce to put it. I have used the Symantec email support but after two weeks I still have no resolution.
|
|
|
|
|
This forum (
Mike Osbahr wrote: Operating Systems / SysAdmin
) should help you out.
|
|
|
|
|
I'm afraid the link you posted was neither clickable or readable. If you would, please post it again.
>>>-----> MikeO
|
|
|
|
|
Hi All,
I use a laptop with window XP operating system.
Last day I face a error with Blue Screen,
Error Message is Start the Dumping of Physical memory..
I want to know the main reason of this error.
Thanks for all.
nilesh
|
|
|
|
|
Look in the System Event Log for an entry with a Source of Save Dump. Could you post the entry's log message text? I'm afraid that without those details, it's very hard to say what the problem was.
Typically the primary cause of blue screens is bugs in third-party device driver software.
|
|
|
|
|
Or faulty RAM/other hardware.
|
|
|
|
|
hi,
i want to know if i can watch file and/or folder creation and/or copying into external devices (USB flash,external HD) to secure my company data from thieves.
iam working with C# and VB.NET
i had searched for this and i found that its related to WMI and system.managment class if there isnt another solution can u give me a useful links for WMI tutorials ?
thanks in advance for your help
|
|
|
|
|
Well any antivirus can perform monitering your externel devices, you could also use the debug namespace in System.Diagnostics to abn any thing from interfering with your device!
To follow the path, Walk with the MASTER, See through the MASTER, Be the MASTER!
|
|
|
|
|
Hai..
I want to send data through USB port as we can do for a serial port.
Can any one help me in doing so.
Sample codes will be more useful.
I want some stuff regarding the usb host controller driver in a PC and how can we communicate with it as any usb device driver does.
Thanks in advance
Regards
vijay
|
|
|
|
|
There is no generic solution to your problem. Try contacting the device manufacturer and see if they offer an SDK.
There also are USB-to-Serial devices which bring their own drivers.
If you want to build your own device, look into the USBWarrior-IC-series, they offer some great deals and include an SDK and example code with their delivery. There are even pre-manufactured PCBs that you can use to control common "modding"-items like LCD-displays.
You NEED the driver for the device AND access to some kind of source that enables you to compile driver access into your program.
But then, you know that. You have asked the same (slightly reworded) question for several days now, about a zillion times!
Cheers,
Sebastian
--
Contra vim mortem non est medicamen in hortem.
|
|
|
|
|
Thanks...Sebastian
Previously i went in a wrong direction so only i asked in different way.
Now i want to develop my own device driver to write data to the pendrive.
So could you help me how to develop the driver..
Thanks
Regards
vijay
|
|
|
|
|
Device drivers are way more complicated to write than user mode code. CP doesn't have a forum for that. You'll need the WDK (Windows Driver Kit) from Microsoft. You may be able to use the new UMDF (User Mode Driver Framework) - it supports some USB stuff but I don't know what specifically since I've never done USB.
Good beginner documentation and tutorials on driver development are just about impossible to find. It's a common question and the answer is always "sorry, doesn't exist." Get the WDK, read through the introductory sections and pour through the samples.
It isn't easy, it takes much much longer than user-mode code to develop and test, and it takes a lot of work trying different things until you understand the "why" of working code.
What are you trying to accomplish that using an existing file system does not work on your pen drive? You've never given anyone a good answer to this question. We might be able to suggest an easier way than writing your own driver / file system.
Judy
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
