Ah well - to reply to my own posts!
I asked
In article <[EMAIL PROTECTED]>, robert w hall
<[EMAIL PROTECTED]> writes
>Previous versions of win4lin have run fine on my DX4-100 laptop, and the
>current FAQ 'will win4lin work on a 486' reflects this position.
>
>Before I contemplate moving to v 3.0 on to this old but still useful box
>can I check that it should still work on a 486.
Well
The following restricted tests still seem OK
Elpack (a UK Election database with 80,000 entries) under dos
Word 7a (aka Word-95) under win95 original
both these tests on an IBM 755ce - DX4-100 with 24Mb RAM - running slack
4.0 with kernel 2.2.13
(Bet you'ld never manage _that_ with VmWare!)
>
>And can I request that we be given _explicit_ warning if the modules
>were to come _compiled_ for pentium cpu only.
>
>Bob
>
> I say this with feeling having just installed the latest version of
>MI/X (v3.0.1, which is X11R6 based at last) on my wife's DX4-75 only to
>have it lob out in 'invalid instruction', and be told by MicroImages
>it's now compiled for a pentium only - this seems a peculiarly silly
>decision - using a legacy box as a remote X-terminal must be pretty
>common, and the change in speed in moving to pentium-only code barely
>worthwhile.
This seems to have got through to MicroImages! - they tell me MI/X 3.0.2
_will_ again run on a 486. This is pleasing because MI/X 3.0.1 (run on a
686) will now remotely run win4lin without falling over (unlike MI/X 2),
although some of the graphics imaging is a little flaky.
--
robert w hall
ancient technology expert :-)
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users
