[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference noted::ibmpc-95

Title:IBM PCs, clones, DOS, etc.
Notice:Intro in 1-11, Windows stuff in NOTED::MSWINDOWS please
Moderator:TARKIN::LINND
Created:Tue Jan 03 1995
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:3023
Total number of notes:28404

2892.0. "Windows crashes when reading B:" by WRKSYS::INGRAHAM (Andy) Sun Jan 26 1997 21:17

A friend's system recently started having problems when some Windows
3.1 programs try to read the B: (3.5") drive.

His three main programs are Lotus Organizer, 1-2-3, and Word for
Windows.  All three are in his Startup group.  If he takes one of
them, and goes to Open a file, and selects the B: drive (with a good
floppy in it), the machine may either:

   - lock up then and there, must do a hardware reset, or
   - dump back to DOS (abnormal Windows exit, no error message), or
   - clear screen (like dumping back to DOS) but hung there.

Yet sometimes it works normally.  Once it works, it keeps working in
that Windows session.  Booting up with a floppy in the drive seems to
help.  Changing floppies after it works sometimes makes it not work
again (I think).

File Manager never has a problem reading B:.  If he uses File Manager
first, then the other programs seem to read the floppy just fine.

He probably hasn't tried A: (5.25") lately.

I am not aware of any hardware or software changes that preceded this
problem, and I don't know what to check.  We don't believe a virus is
involved.

Any suggestions?
T.RTitleUserPersonal
Name
DateLines
2892.1re-install WindowsPERFOM::MATTHESMon Jan 27 1997 13:579
    I had a similar problem.
    
    The 3.5 drive A in my case, would work fine under Dos but not under
    windows.  I don't recall the exact symptoms, let's just say it was
    broke.  I reinstalled windows and it worked fine.
    
    Who says software doesn't spoil.
    
    I can only surmise the floppy driver got creamed somehow.
2892.2WRKSYS::INGRAHAMAndyWed Jan 29 1997 15:012
Short of a re-install, anyone know settings in system.ini (for
example) that might be more easily changed?
2892.3Try SET TEMP=C:\TEMPKETZEL::CHAFINThu Jan 30 1997 13:3719
    The university that I attend has the same problem in a lab
    of 486 machines running Windows 3.1  
    
    If I remember correctly, the problem was mainly with MS-Word.
    Word uses a lot of temp files, and when you open from a floppy
    drive, for some odd reason it tries to create a temp file
    on the floppy.  Something bad happens (I don't know what)
    and then it crashes.  The university fix was to add 
    		
    		SET TEMP=C:\TEMP 
    
    in the autoexec.bat.  I think this tells windows as well 
    as word to use drive c: always for temp files.
    
    However, I think I still had problems, so I always copy files 
    to the hard drive.  Try the SET TEMP=C:\TEMP (be sure the
    directory exists) and see if that helps.
    
    Craig
2892.4That's not itWRKSYS::INGRAHAMAndyThu Jan 30 1997 15:194
He's already got the "SET TEMP=C:\TEMP" in there.  Some time ago it was set
to C:\DOS (perhaps the Windows default installation does that?), and we had
a fun time last year clearing out hundreds of .tmp files in his DOS
directory.
2892.5University consultant says...KETZEL::CHAFINTue Feb 04 1997 16:3525
    This is the reply that I got from a PC consultant
    at the university...
    
    -------------------------------------------------
    The only similar situation that I know about is Word (all the way
    back to version 1.1) and floppies.  It seems that if you open a 
    file in Word directly from a floppy, bad things generally happen.
    It seems that Word needs to make temporary files on the current
    drive, and the current drive seems to be selected based upon where 
    you opened the last file from.
    
    This is why I argue against letting Word deal with floppies or 
    files on them and instead first move/copy files with File Manager 
    to a hard disk.
    
    -Paul
    
         Paul Probst,  Associate Systems Engineer  
         E-mail: Paul.Probst@UC.EDU
    -------------------------------------------------------------
    
    So, apparently if you want to get around this problem, you have
    to tell MS-Word where to ALWAYS put the temporary files.
    I don't know if this is possible in a WORD.INI file.