Jump to content

XP running on a 486 cpu


Dietmar

Recommended Posts

Posted (edited)

@roytam1

Please describe more exact this Bsod.

I test all my modded files a lot and now no kind of such a Bsod happens to me.

Does it happen during Setup of XP, my modded setupldr.exe and setupldr.bin together with my modded ntdll.dll

Dietmar

Edited by Dietmar
Link to comment
Share on other sites


6 hours ago, Dietmar said:

@roytam1

Please describe more exact this Bsod.

I test all my modded files a lot and now no kind of such a Bsod happens to me.

Does it happen during Setup of XP, my modded setupldr.exe and setupldr.bin together with my modded ntdll.dll

Dietmar

your setupldr.bin patch doesn't help and I still have to patch 75 to EB in 0x23513, and replacing NTKRNLMP.EX_ with our hacked NTOSKRNL.EXE.

because you didn't replace system32\ntdll.dll, it tries to use cmpxchg8b in NTDLL.DLL and BSODs:

image.png?ex=66318117&is=66302f97&hm=be0

 

Link to comment
Share on other sites

Posted (edited)

@roytam1

The ntdll.dll is patched.

So I dont know, where this Bsod happens

Dietmar

EDIT: Ah, I see, there is a second ntdll.dll on the xp.iso, crazy;))..

Edited by Dietmar
Link to comment
Share on other sites

Oh I think I find my problem: I can't replace resources with resource hacker in patched NTDLL.DLL.

so maybe every language of NTDLL.DLL has to be done separately.

Edited by roytam1
Link to comment
Share on other sites

@roytam1

I replace the second ntdll.dll with my modded one but get the same reboot just at the end of the Setup process, before you have to hit F8.

Please, can you tell me, what simulator you use for the AMD 486 cpu.

And is there a possibility, even in this very first Setup of XP to let Windbg watch it, may be via a crash debug log

Dietmar

Link to comment
Share on other sites

find the root of problem when changing NTDLL.DLL size.

@Dietmar you forgot to kill .rsrc section before adding your new section. (and add back .rsrc after filling new section, by using resource hacker)

had a hard time when relocating all related calls to new section. please keep in mind that variable size sections (for example, .rsrc) should be in last in the section list.

finally fixed NTDLL.DLL for localizations. fixed ger NTDLL: https://rthost.win/tmp/NTDLL-xpsp3-486hack-ger.7z

I can upgrade from 2000 to XP directly on 486 now:

image.png?ex=66326813&is=66311693&hm=a89

Edited by roytam1
Link to comment
Share on other sites

Posted (edited)

@roytam1

I am just testing on Shuttle Hot 433 board with AMD 133 MHZ486 cpu

AMD AM5x86-P75

Dietmar

EDIT: On real 486 compi, the same reboot happens before the F8 appears.

Is there something other, that you change on my "Source" CD for setup of german XP SP3 with all those modded files?

Edited by Dietmar
Link to comment
Share on other sites

Posted (edited)

Yessssaaa, it installs XP SP3 on my AMD 486 133MHZ cpu:cheerleader::cheerleader::cheerleader:  !!!!!!!!!!!!!!!!!!!!!!!!!

Even I do not get any Bsod before, I did exact the same extras as you:

Extra setupldr.bin patch 75 to EB in 0x23513 (strange, because it has CPUID), and replacing NTKRNLMP.EXE with our hacked NTOSKRNL.EXE,

niccccccccccccccccccccceee.. And I also delete logagent.exe and wmnetmgr.dll from the XP SP3 install CD,

because those 2 are the only files left, with CMPXCHG8b opcode in it

Dietmar

Edited by Tripredacus
removed warez link
Link to comment
Share on other sites

5 hours ago, Dietmar said:

@roytam1

I am just testing on Shuttle Hot 433 board with AMD 133 MHZ486 cpu

AMD AM5x86-P75

Dietmar

EDIT: On real 486 compi, the same reboot happens before the F8 appears.

Is there something other, that you change on my "Source" CD for setup of german XP SP3 with all those modded files?

Replacing resources with English one and repack it with cabarc.exe and replace same files in English CD.

WINNT32A.DLL and WINNT32U.DLL has CPU check cracked to allow 486 to run.

and English SETUPLDR.BIN has different offsets and I have to patch it manually (just patched the condition branch ops).

after 1st copying it reboots and got BSOD:

image.png?ex=66328080&is=66312f00&hm=ee5

Edited by roytam1
Link to comment
Share on other sites

@roytam1

With my XP TXTSETUP runs ok.

But then, after first reboot, compi hangs after about 4 min.

Sometimes hanging after about 4 min and sometimes during detect of devices (37min to wait is shown).

Are WINNT32A.DLL and WINNT32U.DLL on the german CD the same as on English ones?

Please tell me the crack or send me the already modded files

Dietmar

Link to comment
Share on other sites

12 hours ago, Dietmar said:

Are WINNT32A.DLL and WINNT32U.DLL on the german CD the same as on English ones?

Please tell me the crack or send me the already modded files

patch 2 JNZ and replace 2 JZ with nops:

 7:44 D:\OS\xp-486-hack\eng-orig>fc /b WINNT32A.DLL ..\eng-hack\WINNT32A.DLL
Comparing files WINNT32A.DLL and ..\ENG-HACK\WINNT32A.DLL
000250C7: 75 EB
0002986D: 0F 90
0002986E: 84 90
0002986F: 87 90
00029870: 04 90
00029871: 00 90
00029872: 00 90
0002987D: 0F 90
0002987E: 84 90
0002987F: 77 90
00029880: 04 90
00029881: 00 90
00029882: 00 90

 7:44 D:\OS\xp-486-hack\eng-orig>fc /b WINNT32U.DLL ..\eng-hack\WINNT32U.DLL
Comparing files WINNT32U.DLL and ..\ENG-HACK\WINNT32U.DLL
000323CC: 75 EB
0003739E: 0F 90
0003739F: 84 90
000373A0: 43 90
000373A1: 07 90
000373A2: 00 90
000373A3: 00 90
000373AE: 0F 90
000373AF: 84 90
000373B0: 33 90
000373B1: 07 90
000373B2: 00 90
000373B3: 00 90

 

Edited by roytam1
Link to comment
Share on other sites

@roytam1

Have you tested with the modded WINNT32A.DLL and WINNT32U.DLL,

if the hack in ntoskrnl.exe against Bug Check 0x5D UNSUPPORTED_PROCESSOR

is not necessary any longer

Dietmar

Link to comment
Share on other sites

33 minutes ago, Dietmar said:

@roytam1

Have you tested with the modded WINNT32A.DLL and WINNT32U.DLL,

if the hack in ntoskrnl.exe against Bug Check 0x5D UNSUPPORTED_PROCESSOR

is not necessary any longer

Dietmar

yeah, tried upgrading from Win2000 to XP. Without patch it will pops out a message box of requiring Pentium processor and exit.

as it runs cpuid by its own, patching kernel doesn't help.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...