09-28-2009 07:27 AM - edited 09-28-2009 07:28 AM
After reading OPs problem I downloaded the ISO. The download went smoothly (see my earlier post) and I burned the ISO to CD.
Then I booted using that CD. The boot went smoothly. My product key was auto-recognized and updates were downloaded. I didn't run a scan but I don't have any reason to think a problem would surface at that point.
It's very curious that different users are experiencing wildly different results. I'm glad you're communicating the problem to Symantec and I'm looking forward seeing the response.
09-28-2009 08:00 AM
Thanks for the input Brubaker!
I failed to mention that I have only tested on XP SP3. I'll try Vista SP2 later this evening.
What platform are you using?
Norton 360 • Norton Internet Security • Norton Zone | XP SP3 • Windows 7 Professional SP1 x64
• PLEASE, BACKUP or EXPORT your Identity Safe Data on a regular basis •
09-28-2009 08:18 AM
I've just downloaded the file and mine is 251MB ......
I don't have time now to burn this and try it but without knowing exactly what it would tell me I opened the ISO file with ISOBUSTER and looking down the tree it shows that under Norton the BOOT.WIM file is flagged with a red X as is the BCD file under Microsoft and it reports a large number of missing sectors.
As I say I've never used this tool before -- just happen to have it on board. This may be normal but someone might want to check a 291MB file with ISOBUSTER and see if it shows the same red flags.
09-28-2009 08:41 AM
I just tried again using the same CD on a laptop running Vista SP2. Everything went the same except that the updates did not download. I think that's because it's using a wireless connection. I could have tried an ethernet connection to my router, but that didn't seem necessary as everything else appears to be working normally and it was ready to scan.
09-28-2009 08:44 AM
I just tried again using the same CD on a laptop running Vista SP2. Everything went the same except that the updates did not download. I think that's because it's using a wireless connection.
Hi brubaker, You are right, only a hardwired connection works to get virus defs downloaded.
I could have tried an ethernet connection to my router, but that didn't seem necessary as everything else appears to be working normally and it was ready to scan.
We look forward to the time when the Power of Love will replace the Love of Power. Then will our world know the blessings of peace. ~William Ewart Gladstone
09-28-2009 09:34 AM
Plugged in my old computer - XPSP3 w/all updates - and it downloads just fine. Burned .iso - it boots and works perfectly.
Returned to VistaSP2 computer. Removed WRT610N router from equation - connected DIRECT to SB6120 cable modem - it downloaded just fine! ??hmmmm?? Reconnected WRT610N router and tried again. No dice.
Downloading this file behind my WRT610N router with XPSP3 works while VIstaSP2 does not.
09-28-2009 03:31 PM
09-28-2009 04:44 PM
Took me 3 downloads, 4 burn tries before I got a disk that worked. Part that bothers me is, it looks like it didnt download defs. When I scanned, it said using current defs: aug 29, 2009. My ver of 2009 will not dl defs either but maybe that's because my 2009 licence has expired. Frankly IMHO even if your licence for the installed program has expired, they should still allow your NRD to update. That said, I wasn't impressed. NRD scanned only a third of the files the installed ver does. Seemed worse than the 2009 ver but maybe I'm not recalling right.... mad cow ya' know.
From 2009 the applications stop working completely once your subscription expires; not just frozen in time. So that would be why your Recovery DIsk would not DL defs too.
If you had a vailid subscription 2010 would have updated the definitions for the scan when you ran the disk but 2010 would be fixed on the date it was put on the server I imagine, like the downloaded trial versions or even the downloaded ones for installation.
2010 is designed not to scan files that are OK'd by Insight which means not just that their reputation is OK but that they have not been altered in anyway since the were cleared. That could explain why it did not scan as many -- are you comparing installed 2010 with the 2010 Recovery Disk? -- but you may be right that the recovery disk should update. That would make sense but it might mean that even after your 4th attempt it was not right.
Hopefully someone from Symantec can comment about this -- they know about the downlod problem.