UNSOLVED

bouncingbaby

updated

22 years ago

0

7692

September 22nd, 2004 12:00

Norton 2004 creating rescue disks

I am having a heck of a time. I can't even create rescue disks that work. One of the files it tries to copy to a disk is way too large. It warns me of  this fact before I even try. Norton Support just tells me to uninstall and do a bunch of other stuff (which I have done more than once) all to no avail.   The exact error that I get is "Some of the files needed for the rescue disk set cannot be copied. These files may not be essential, but if you continue, be sure to test the rescue disk set". I then click details and get this "The following files cannot be copied to the rescue disk. The file is VIRSCAN9.DAT It then goes on to say that the problem is insufficient rescue media space to copy this file". I really don't see how uninstalling and reinstalling Norton and running live update is going to fix the problem. Is anyone having the same problem?
  • mbernie1

    4 Posts

    163

    0

    Posted September 22nd, 2004 20:00

    I am getting the same exact error message since I installed NAV 2004 at the end of August. I replaced NAV 2002 because the subscription expired. Symantec is well aware of the problem and they have no solution at this time. They are working on it and will post a updated message when they come up with one. You can read their posting by going to their support site and searching for document# 2004082708430213. I am not sure if this will work but here is the link to the document
    http://service1.symantec.com/SUPPORT/sharedtech.nsf/d3c44a1678bd8f45852566aa005902cb/aecb27f3ff71e84088256efd00565656?OpenDocument�=Norton%20AntiVirus&ver=2004%20for%20Windows%202000/Me/98/XP&src=sg&pcode=nav&svy=&csm=no

    I am using W98SE. Symantec has had this problem with rescue disks on previous versions also and have fixed it by updating the rescue program.
  • 163

    0

    Posted September 22nd, 2004 22:00

    Thank you for the link. I have been in touch with their support by email on two different occasions. The latest being today.

    The latest email told me to modify my usage.dat file. I did this following the directions precisely. Still I get the same error. If

    they don't know how to resolve, why don't they just be honest about the situation?  The first told me to simply uninstall and reinstall

    Norton and then create rescue disks. Why are they putting out a product that for ME users at the very least is a problem?

    How are we to recover from an emergency if we can't even get our computer up and running? This makes me fume! Thanks for

    letting me vent. 

  • aevarga

    1 Message

    163

    0

    Posted October 4th, 2004 03:00

    I also have a problem creating a Rescue Disk set, but I have not called Symantec Support.  They were less than helpful when I had problems with NAV 2003.  I am now using NAV 2004, which does not have any bugs that have affected me yet.

    Perhaps the people at Symantec ought to take a look at their product rather than tell the users to look at it.  The latest version of VIRSCAN9.DAT, included in the definition folder 20040930.019, is 1,582 KB.  Last time I looked, a floppy only holds 1,440 KB.  Maybe this is a problem??  Maybe it's time to break VIRSCAN9.DAT into a couple of smaller files?

  • mbernie1

    4 Posts

    163

    0

    Posted October 4th, 2004 22:00

    aevarga

    You are correct.  The file is too large to fit on a floppy.  I found that out the hard way.  Since Symantec didn't seem to be doing any thing about the problem, I decided I might try making a zip disk rescue set.  I have an external SCSI zip drive and had done this with NAV 2000 a while back.  Well, NAV 2004 rescue screen showed the zip disk so I selected it and told it to create a set.  It took the zip about 1 minute to complete but it never made the required floppy boot disk.  After checking Symantec knowledge base, I discovered that they have removed the option to create a zip rescue disk since it only works for DOS based systems.  I looked at the zip disk to see what was on it and thats when I saw that the dat file was too large for a floppy. 

    So, what to do?  I decided to delete the zip disk and just update the floppy set I had made even though it wasn't complete.  Couldn't get it to make a floppy set now.  Kept telling me to insert the zip disk.  Finally just reset the rescue program and created a new rescue set.  Of course it still said it couldn't write the file only this time it asked for an additional floppy.  It wanted two floppy disks both numbered 6.  At this point a tried resetting the rescue program again this time using the full reset procedure they give. Didn't change anything.  Still asks for the additional blank floppy and still can't write the file.

    In past versions they have had both these problems.  I really don't see why they can't/don't figure out what to do about it.  The only fix for the additional blank disk it wants is to run Live Update and download the rescue update.  Well there is none.  Guess I will just sit here and wait for them to wake up and issue an update or replacement Rescue program.  I think that the defective set it does create might work for every thing except the actual virus scan so it might not actually be useless.  I have been making these rescue sets for years and have never had to use one so I will just hope my luck continues at least until they fix the problem.

    Message Edited by mbernie1 on 10-04-2004 07:08 PM