S10 floppy ain't drivin' - except w/WABI - and now WABI died!

S10 floppy ain't drivin' - except w/WABI - and now WABI died!

Post by Mark Morlan » Tue, 11 Feb 1997 04:00:00



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,

 
 
 

S10 floppy ain't drivin' - except w/WABI - and now WABI died!

Post by Robert S Campbe » Wed, 12 Feb 1997 04:00:00


|> 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

 
 
 

S10 floppy ain't drivin' - except w/WABI - and now WABI died!

Post by Adam Meltz » Fri, 14 Feb 1997 04:00:00


: 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.

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

                 ))       ._))       .    
                                     .  

 
 
 

1. WABI: Which win games do run under Wabi?

Now (1996) There are some games on the market, which are
"Windows Compatible", wouldnt it ba a good compatibility
test to run this games? I tried SimIsle ... after a while
it crashes with an exception error. Since Win 3.1 does not
have Memory protection (yes we do have 1996), but Solaris 2.4
has (SunOS3.x already had it 1985) -- this may the problem.

WinNT has memory protection. The game "Battle Isle2" has the words
on its box "ready to run on WinNT", can someone of you
-- Who has Battle Isle 2 and WABI -- Make this test?!?

                Tschau Thomas

--

/d{def}def/m{moveto}d/s{stroke}d/X{{52 sub 18 mul}forall}d/l{lineto}d/a{0 360


2. serial line / x86

3. questions about Wabi. WABI <---> WIN95 applications??

4. tar.gz

5. invoke WABI application from outside WABI?

6. Tutorial on Kernel patching

7. pls. give me information about 'WABI'

8. Adaptec 1520 hangs at boot.

9. Why can't I 'startx' except as 'root'?

10. Shouldn't 'netstat -ain' show my eth0?

11. my floppy.kdelnk ain't linking

12. cpio reading multivolume floppy archives - say it ain't so