Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Pastimes : Computer Learning -- Ignore unavailable to you. Want to Upgrade?

To: mr.mark who wrote (11721)	9/5/2000 8:40:39 PM
From: shadowman	Respond to of 110583

Kinda off topic: Peter Norton......a nice gesture. JD Salinger, the writer of Catcher in the Rye...a person noted for his reclusive ways, has been blessed (not) with an ex-lover who sold off a bunch of his private letters at auction last year and an opportunistic daughter who has just published a book detailing things about him that must make him wish that Roe Vs Wade had been handed down at a much earlier date. Anyway, Peter Norton: From a review (critical)of JD's daughter's book...in the NYTimes. Ms. Salinger has written a book that reveals not only her own life but previously unknown and deeply intimate aspects of her father's life. Her motivation in breaching his zealously guarded privacy is likely to be questioned by many who criticized Joyce Maynard's 1998 memoir, which included details of her romance with Mr. Salinger when she was 18 and he was 53. Last year's auction of letters that Mr. Salinger wrote to Ms. Maynard in the early 1970's also prompted criticism. The letters were bought by the California software entrepreneur and philanthropist Peter Norton, who returned them to Mr. Salinger.

To: mr.mark who wrote (11721)	9/6/2000 1:28:51 PM
From: mitch-c	Read Replies (2) \| Respond to of 110583

"but when I have a legit support issue (like this one)" forgive me, but if you are referring to the right-click menu selection addition of 'scan with norton antivirus' as a legit support issue, i would personally take exception. "The customer is always right" defines legitimacy for me. Especially when I'm the customer <g>. Although, most of the incidents I refer to involve investigating "why does it crash?" problems. Example - our NAV corporate deployment required a client to run IPX/SPX - even in a totally TCP/IP network. Otherwise, it died with illegal operations on RTVSCN32.DLL, VPEXRT.EXE, and LU32????.EXE, the executable that drives the live update. Is this documented? No. After much effort, we finally dug out a just-written article that said that using IPX/SPX might fix it in certain situations. So, the "hands off" deployment and update feature (essential for a 2-man IT staff) wound up requiring hands-on fixes on each of our 100 PC's - because Symantec compiled PROTOCOL DEPENDENCY into its code and didn't notice. I was not happy. IMO, when Norton-branded software works, it does well. When it doesn't, the complexity of troubleshooting rises exponentially - usually because it's so damned obscure about what it does, how it does it, and where it plants impenetrable cute little tweaks like that right-click option. Forget cute - gimme KISS. It's easier to fix that way. - Mitch