Very Computer

After update from Solaris 2.4 to 2.5 on my S10, my floppy has been
inop, except that it would work with WABI.  vold is running.

volcheck seems to do nothing.  

Wabi has come up with some fatal error of its own (Error loading file:
c:\windows\commdlg, file read error) upon start
of ANY applications (file manager).  This began one week ago, and
has forced the issue of fixing the floppy access from the shell.

Reinstall of Windows 3.1 did not fix, reinstall of WABI 2.1 has not
been tried.

Thanks for any and all help.

Mark Morland,

|> After update from Solaris 2.4 to 2.5 on my S10, my floppy has been
|> inop, except that it would work with WABI.  vold is running.
|>
|> volcheck seems to do nothing.  

We've had this problem with many Sparc 5's that were upgraded to 2.4.
Our solution has been to do a reconfiguration reboot (reboot -- -r or
boot -r at the eprom prompt).  That ought to clear up your problems.
Before doing that, also check your /etc/vold.conf to make sure the
floppy drive isn't commented out.

Bob Campbell

: After update from Solaris 2.4 to 2.5 on my S10, my floppy has been
: inop, except that it would work with WABI.  vold is running.
:
: volcheck seems to do nothing.  
:
: Wabi has come up with some fatal error of its own (Error loading file:
: c:\windows\commdlg, file read error) upon start
: of ANY applications (file manager).  This began one week ago, and
: has forced the issue of fixing the floppy access from the shell.

Wabi messes with your vold.conf and comments out the floppy drive entries.

Remove the comments, restart vold, and it'll work.

--
 ___                                  
 ))_) ___  _  _  __  ___  ___  __    :  

                 ))       ._))       .    
                                     .