Number: 207

Date: 20-Mar-84 11':00':21

Submitter: le.pasa

Source: teknowledge (Reported by Bill van Melle).

Subject: SYSOUT to floppy doesn''t reset FLOPPY.MODE after

Assigned To: Roach.pa

Attn: LISPSUPPORT

Status: Fixed

In/By: 

Problem Type: Bug

Impact: Moderate

Difficulty: Moderate

Frequency: Everytime

Priority: Perhaps

System: Operating System

Subsystem: DLion Floppy

Machine: 1108

Disk: 

Lisp Version: Fugue.5

Source Files: 

Microcode Version: 

Memory Size: 

File Server: 

Server Software Version: 

Disposition: '
[Date': 13 APR 84 17':26 PST'
From': ROACH.PA'
207 Difficulty _ Easy (probably)]'
[DATE': 22 JUL 84 ROACH DIFFICULTY _ MODERATE]'
[KBR 22-AUG-84 This was fixed last month.  STATUS _ FIXED.]'
[KBR 26-AUG-84 ATTN _ LISPSUPPORT]'
["Roach" "26-Aug-84 12':24':07" Attn': Disposition':]

Description: '
Date': Thu, 15 Mar 84 18':32 PST'
From': Raim.pasa'
Subject': Bug report from teknowledge'
To': Le'
cc': 1100Support, Raim'
'
System': Fugue.5'
Machine': 1108'
'
Teknowledge claims that (SYSOUT ''{FLOPPY}) does FLOPPY.MODE(SYSOUT) and doesn''t set it back.  If you try to read a regular floppy when in this state, you get error ARG NOT LP NIL underneath some floppy code that is trying to open a huge file.'
'
(Reported by Bill van Melle)'
'
-----'
'
Date':  2 APR 84 12':06 PST'
From': ROACH.PA'
Subject': AR207 SYSOUT to floppy doesn''t reset FLOPPY.MODE'
To':   LISPSUPPORT'
cc':   ROACH'
'
     I did a sysout to floppies this morning and find FLOPPY.MODE'
being set back to PILOT as it should be after moving the sysout'
onto another machine.  Of course, if the user was in FLOPPY.MODE'
SYSOUT before doing the (SYSOUT ''{FLOPPY}), then FLOPPY.MODE will'
remain at SYSOUT.'
     Teknowledge told me on my last visit to them (early Feb) that'
they had this sort of problem after sysouting to a VAX.  Maybe it''s'
a bug that''s been fixed or maybe some code is doing something funny'
to aftersysoutforms or device eventfns somewhere.  I can''t reproduce'
the problem and I''ll need more information before I can do anything'
meaningful.'
     The ARG NOT LP NIL part of this message is a bug and is being'
handled under AR217.'
     Difficulty _ Impossible'
     Priority _ Unlikely'
     Status _ Incomplete'
				Kelly'
'
-----'
'
Date':  4 Apr 84 14':49 PST'
From': vanMelle.pa'
Subject': AR 207': SYSOUT to floppy doesn''t reset FLOPPY.MODE after'
To': LispSupport'
cc': vanMelle.pa, Roach'
'
Kelly''s reply does not completely address the bug.'
'
  "I did a sysout to floppies this morning and find FLOPPY.MODE being set back to PILOT as it should be after moving the sysout onto another machine."'
'
But was floppy.mode smashed on the machine that performed the sysout?  Was floppy.mode smashed even if the sysout wasn''t to floppy?  I.e., what does the sequence'
'
_SYSOUT({Phylum}<Roach>FOO.SYSOUT)'
'
_FLOPPY.MODE()'
'
return when run on a Dandelion?  My cursory reading of the floppy code is that it returns SYSOUT, clearly a bug.  Unless Kelly disagrees, I propose this AR be reopened.'
'
	Bill'
'
-----'
'
Date':  5 APR 84 09':53 PST'
From': ROACH.PA'
Subject': Re': AR 207': SYSOUT to floppy doesn''t reset FLOPPY.MODE after'
To':   vanMelle, LispSupport'
cc':   ROACH'
'
In response to the message sent   4 Apr 84 14':49 PST from vanMelle.pa'
'
     Kelly disagrees.'
'
-----'
'
Date':  6 Apr 84 12':13 PST'
From': vanMelle.pa'
Subject': Re': AR 207': SYSOUT to floppy doesn''t reset FLOPPY.MODE after'
In-reply-to': ROACH.PA''s message of 5 APR 84 09':53 PST'
To': ROACH.PA'
cc': vanMelle.PA, LispSupport.PA'
'
I would not say the impact is severe, but it clearly is a bug':'
'
13_MAKESYSDATE'
"29-Mar-84 17':34':40"'
14_FLOPPY.MODE]'
PILOT'
15_SYSOUT({INDIGO}<LISP>TEMP>FOO.SYSOUT]'
{INDIGO}<LISP>TEMP>FOO.SYSOUT;1'
16_FLOPPY.MODE]'
SYSOUT'
17_PL FLOPPY'
FILEDATES ': (("20-Mar-84 19':45':55" . {PHYLUM}<LISPCORE>SOURCES>FLOPPY.;3))'
'


Workaround: 

Test Case: 

Edit-By: Roach

Edit-Date: 26-Aug-84 12':24':08