set_thread_buffer error

lawson_whitney at lawson_whitney at
Mon Sep 17 15:16:30 CDT 2001

On 17 Sep 2001, Peter C wrote:

> No, it's standard Zipslack (the site doesn't give version numbers).
> I've looked all over Slackware's site and there's nothing mentioning
> bugs with 64-bit support or a patch for it. I've got glibc 2.2.3 at
> the moment, do you think upgrading to the latest version of glibc
> (2.2.4) will help?

I don't think so.  That is starting to look to me like a umsdos or msdos
bug, but to be sure I will have to compile a kernel with umsdos support,
and I may as well patch to 2.4.9 while I am at it.

If you have any ext2 partitions lying around, try pointig WINEPREFIX
there, or you can make a little one in a file, mount it on a loop
device, and try that for WINEPREFIX.  In truth I have never tried
using a loop device with umsdos, but it is easy enough...oops, mke2fs
wants a device, it doesn't have an option to use a regular file.
Make a file of an appropriate size with dd, use losetup to connect it to
a loop device, make an ext2 filesystem on that loop device, mount it,
and point WINEPREFIX there.  I'm guessing WINEPREFIX is where the
problem file is, but I think it is a pretty fair guess.


Juno offers FREE or PREMIUM Internet access for less!
Join Juno today!  For your FREE software, visit:

More information about the wine-users mailing list