Hi Matt,
Thank you for looking into this. My word version is 2003 (11.8237.8221) SP3.
Now, I don't have a problem with Excel, Access and quite a few other programs that I use, only Word (not sure about Power point).
DaveF
Hi Matt,
Thank you for looking into this. My word version is 2003 (11.8237.8221) SP3.
Now, I don't have a problem with Excel, Access and quite a few other programs that I use, only Word (not sure about Power point).
DaveF
Dave --
FWIW I have WORD XP / 2002 on XP Pro SP3 and I just created a test file in WORD and saved it to a thumbdrive without any problem.
Double clicked on the file on the thumbdrive and it opened WORD and displayed it ....
NIS 2009 16.2.0.7 ....
It would seem you are not alone!
I googled on [can't save word file to thumb drive] and although yours was the first reference I spotted this further down the list:
Can't save .doc file in microsoft word through USB - Kaspersky Lab ...
2 posts - Last post: Jan 15I've just installed KIS 2009 and now I can't save my .doc files when I use microsoft Word 2007 from the USB thumbdrive. .docx files works ...
forum.kaspersky.com/index.php?showtopic=100096 - 30k -
Exactly!..it is only WORD with NAV. My other Office products work fine. What is worse…if you are unaware of what the error msg is you are seeing and hit OK…you loose the ENTIRE document from your file and are left with a worthless .tmp file. There is an issue here - and using Save As to another drive then copy back is not the solution. You are not alone.
<< Exactly!....it is only WORD with NAV. >>
According to Kaspersky users, they have it too so it's not only NAV.
As I pointed out previously in this thread, we've produced this problem in the past on a system with just Office installed. As huwyngr pointed out, the problem occurs with other anti-virus products as well. I haven't seen a solution yet, but all of these threads seem to pointing to a problem with Word:
http://social.microsoft.com/forums/en-US/onecaregeneral/thread/6ca30489-6ea4-4f37-8d50-802bf22a408e
Hi Reese,
I appreciate that this is related to Word. But, as the end user (or customer) I'm interested in getting the problem fixed. Not trying to wade into the middle of finger pointing between Symantec and Microsoft particulary on something as highly technical as this appears to be.
I see this as an opportunity for Symantec to differentiate its product from the others in the market place: if there is a similar one that doesn't have this problem I will go for it and I bet a number of others will too.
MS and Word are with us for a long time to come (for better or worse). The Antivirus software that works with Word the best will do better.
I look forward to the update to NAV that patches this problem. Please keep us posted on progress.
Regards, DaveF
The middle link that Reese posted is interesting since there it is OneCare under siege and a moderator identifies one cause the found -- an Acer driver:
<< Yes indeed - it is this one: Acer eRecovery service driver (int15.sys). >>
Just in case anyone has an Acer .....
And someone else reports this:
SOLUTION: Change the format of your portable USB / thumb drive to NTFS from either FAT or FAT32 which it may currently be.
Solved all my "file permission error" issues
Just as background to the problem of identifying the cause and so what to alter to fix it let me, once more <g>, recount my experience here in the Forums when N360 went from V1 to V2 and Microsoft issued XP SP3 / VISTA SP1 all about the same time. I upgraded and my PowerDesk file manager started crashing every time I right mouse clicked on a file.
Go back to V1 -- no problem; upgrade to V2 -- problem
Microsoft says Norton and Norton say Oh no it isn't ...
Norton talk with PowerDesk and it turns out that MS changed a protocol some time back and did not themselves change to observe it so others didn't either. Then MS started to observe their own protocol and things started going wrong in the applications that had not already changed.
PowerDesk wrote and issued a fix and all is well again.
So we really have to careful not to look for the fix to be in the obvious culprit which in my case was N360 V2 --- but it wasn't.
When Microsoft are aware of the problem when their own OneCare is used and say they can't pin down what it is in WORD that is triggering the problem .....