Changes regarding wnaspi32 layer ?

[David Elliott]

On 2002.01.10 14:06 Martin Hoffmann wrote:
> Mhhh,
> 
> must have been an issue with a not properly installed Wine on my machine
> !
> 
> As you told me i ran some tests: First with the working 20010731 build !
> Then i decided to switch to cvs from 20011226 and did ./tools/wineinstall
> !
> 
> Guess what, it was not reproducable :-/ With the fresh compiled cvs from
> 20011226 it works, too ...
> 
> So, i can only imagine that last time i installed a newer version i must
> have
> mixed up anything (or had a bad rpm - this time i compiled my own !)
> 
> Thank you anyway ! For me it's solved... (being happy)
> 
> Martin
> 

Speaking of which, I highly recommend you use CVS and configure with 
--prefix=/opt/wine-cvs (or something similar).  Then add YOUR_PREFIX/bin 
to your path and YOUR_PREFIX/lib to your /etc/ld.so.conf.

Then if you ever need to be sure you have a fresh copy of wine:
rm -rf /opt/wine-cvs
make install

Thanks to Jeremy for this suggestion (in fact, I think the CodeWeavers 
RPMs do this, or at least did IIRC).

It's a hell of a lot better than having wine strewn over /usr/local along 
with the rest of your programs compiled from source.

Glad to hear that you got ASPI working.  Especially because I could see no 
reasonable explanation for why it wouldn't work between the wine releases 
you gave given that no major updates have been made to ASPI since Andreas 
Mohr fixed some bugs with the /proc/scsi/scsi parsing in my code among 
other things.  Hehe.. actually, had people not had broken SCSI devices 
with a space as their first character this would not have been an issue.

-Dave