From: David Mosberger <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Re: kernel update (relative to 2.4.10)
Date: Thu, 27 Sep 2001 08:31:24 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805267@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205855@msgid-missing>
>>>>> On Wed, 26 Sep 2001 17:59:11 -0400, Bill Nottingham <notting@redhat.com> said:
Bill> David Mosberger (davidm@hpl.hp.com) said:
>> with these fixes in place, I'm able to successfully run the ia32
>> versions of realplay, OpenOffice, mozilla, netscape, acrobat,
>> strace, Intel compilers, etc. But as usual, your mileage may
>> vary.
Bill> Did you try wine? :)
I hadn't.
Bill> Seriously, I tried this previously, and it didn't really work
Bill> at all. At the time, I wasn't even sure if it could be *made*
Bill> to work, and I haven't looked since.
I wasn't sure either. I looked at the docs a bit and there doesn't
seem to be anything that would stop it from working in principle.
16-bit apps might be harder, as those require vm86() which I know
nothing about (I'm sure it could be implemented by someone more
knowledge of x86).
Encouraged by this, I tried the wine RPM from Red Hat. After fixing
the ia32 sendmsg()/recvmsg() implementations, I am now able to run
"wordpad.exe" and "mspaint.exe". I had never seen wine in a working
state, so I was quite amazed to see a windows-looking application pop
up! As far as I can tell, these two apps work perfectly fine.
However, I didn't get much else to work (e.g., acrobat and the HP
printing software both died after the splash screen...). Even with
"wordpad.exe" I get some worrisome warning messages:
err:win32:fixup_imports No implementation for shlwapi.dll.0(StrRetToBufA) imported from shell32.dll, setting to 0xdeadbeef
err:win32:fixup_imports No implementation for shlwapi.dll.0(StrRetToBufW) imported from shell32.dll, setting to 0xdeadbeef
FIXME:pthread_rwlock_rdlock
FIXME:pthread_rwlock_unlock
I think the first two errors are real problems. Not sure about the
pthread-related messages. I suppose if someone is serious about this,
all of these could be fixed.
Oh, to get this to work, I had to switch to 4KB page size.
--david
next prev parent reply other threads:[~2001-09-27 8:31 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-15 17:54 [Linux-ia64] Re: kernel update (relative to 2.4.0-test12) Bill Nottingham
2001-05-09 17:04 ` [Linux-ia64] Re: kernel update (relative to 2.4.4) Bill Nottingham
2001-07-24 2:28 ` [Linux-ia64] Re: kernel update (relative to 2.4.7) Bill Nottingham
2001-07-24 16:42 ` Bill Nottingham
2001-07-24 16:49 ` Andreas Schwab
2001-09-27 8:31 ` David Mosberger [this message]
2001-09-28 15:32 ` [Linux-ia64] Re: kernel update (relative to 2.4.10) Bill Nottingham
2001-09-28 15:58 ` Bill Nottingham
2001-09-28 16:13 ` David Mosberger
2001-09-28 19:01 ` Bill Nottingham
2001-09-29 1:45 ` Chris Ahna
2001-10-01 18:14 ` Bill Nottingham
2001-10-02 3:37 ` David Mosberger
2002-06-26 17:30 ` [Linux-ia64] Re: kernel update (relative to 2.4.18) Xavier Bru
2002-06-26 17:46 ` David Mosberger
2002-06-28 19:42 ` David Mosberger
2002-06-29 20:02 ` Chen, Kenneth W
2002-07-03 13:28 ` Xavier Bru
2002-07-03 16:33 ` [Linux-ia64] " Chen, Kenneth W
2002-07-03 16:38 ` David Mosberger
2002-07-04 13:42 ` Xavier Bru
2002-07-10 18:39 ` Chen, Kenneth W
2002-07-11 16:29 ` Xavier Bru
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-linux-ia64-105590698805267@msgid-missing \
--to=davidm@hpl.hp.com \
--cc=linux-ia64@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox