> I was wondering if Analog could output the "trouble" lines as it reads a > file? That is, it would output the log file name it is working on, and the > line it barfed on. DEBUG CF seems to display a wealth of information... F: Opening log1 as logfile C: ohcrapit'sabadlogfileline C: ahsjkdhaksjhhnn F: Closing logfile log1 F: Opening log1 as logfile C: bl;ah bkaskd ahksjkha F: Closing logfile log1 See if that'll fix you up. -=Jim=- -------------------------------------------------------------------- This is the analog-help mailing list. To unsubscribe from this mailing list, send mail to [EMAIL PROTECTED] with "unsubscribe analog-help" in the main BODY OF THE MESSAGE. --------------------------------------------------------------------
- RE: [analog-help] corrupt browser type in log file Jeff Lloyd
- RE: [analog-help] corrupt browser type in log file Stephen Turner
- RE: [analog-help] corrupt browser type in log file jfoley
- RE: [analog-help] corrupt browser type in log file Stephen Turner
- RE: [analog-help] corrupt browser type in log ... jfoley
- RE: [analog-help] corrupt browser type in ... Stephen Turner
- RE: [analog-help] corrupt browser typ... jfoley
- RE: [analog-help] corrupt browser... Stephen Turner
- Re: [analog-help] corrupt browser... Jeremy Wadsack
- RE: [analog-help] corrupt browser type in log file bgahl
- [analog-help] Netscape log problems Jim Sander
- [analog-help] Netscape log problems Keith Purtell
- Re: [analog-help] corrupt browser type in log file Aengus Lawlor
- Re: [analog-help] corrupt browser type in log file Aengus Lawlor
- Re: [analog-help] corrupt browser type in log file Stephen Turner
