You may get a VIA C3 then. ;)
Nah, there are three reasons why I would prefer a Crusoe over a C3:
1) Crusoes are faster
2) Code Morphing(tm) makes the CPU upgradable by software
3) Linus Torvalds works for Transmeta :grin:
I have the C1VN with 128MB memory upgrade.
Error
SMSW eax: 0F01E0 eax = 80000019
SMSW ax: 660F01E0 eax = 00000019
OK
Winblows ME, 128mb ram, athlon 900Mhz processor (might be T-bird, but i doubt it)
SMSW eax: 0F01E0 eax = 80000019
SMSW ax: 660F01E0 eax = 00000019
OK
Winblows ME, 128mb ram, athlon 900Mhz processor (might be T-bird, but i doubt it)
Pentium IV 2.0GHz / Windows 2000
mov eax,cr0=8001003B
smsw eax = 8001003B
I've also got a Pentium Pro 200 and a few PIII's laying around if you want info from those too (i'm not sure my 486 would handle NT/2000 though :tongue: )
-----
Domain
mov eax,cr0=8001003B
smsw eax = 8001003B
I've also got a Pentium Pro 200 and a few PIII's laying around if you want info from those too (i'm not sure my 486 would handle NT/2000 though :tongue: )
-----
Domain
P6 200 result would be interesting.
Thanks.
Thanks.
You may get a VIA C3 then. ;)
hahah, VIA C3's LOL! Those things are at the bottom of the heap, I had a Cyrix chip and man its FPU performance was next to crap, Quake lagged too much >=|
and I had a damn Matrox Millenium, since when does Quake, lag on such a kick @$$ 2D card with frieken fast LFB access times ? >=|
The answer of course, can be done only with driver written or some debugger that shows cr0.
I don't know one.
perhaps... http://www.anticracking.sk/EliCZ/export/DumpXDT.zip ?
I've already written driver and upload it here
I'm again asking a favour:
I'm trying to use OEM pseudo gfx
inside GUI application. It looks OK
in my machine, but I'm not sure that
OEM gfx would work in GUI in any machine.
Could you please run it and say,
if table under label "Alternative way to decode"
looks OK.
I mean table aligned and no funny characters
instead of pseudo gfx lines.
I'm trying to use OEM pseudo gfx
inside GUI application. It looks OK
in my machine, but I'm not sure that
OEM gfx would work in GUI in any machine.
Could you please run it and say,
if table under label "Alternative way to decode"
looks OK.
I mean table aligned and no funny characters
instead of pseudo gfx lines.
Svin - Your latest test app works perfectly on WinXP SP1 :alright:
Works fine on win 2k sp3