ProgramHacker

Guys, I just found out the secret of logagent.exe and its use I just read through the assembly codes of "logagent.exe" and... logagent.exe, also known for Windows Media Player Log Agent. The application that logs errors with Windows Media Player. Maybe, just maybe, windows media player is also leading the trails to this logagent.exe, maybe fixing Windows Media Player would fix logagent.exe problem

BTW, how much space does logagent.exe has left. It might be possible.

I think, to fix this logagent.exe space problem may requires us to code another one in C++ However, why is logagent.exe so strict when it just write logs?

@Dietmar why don't you take the windows 2000 files and overlap it with windows xp install. That way it might help to solve some problems

There is a way to make it work, you JUST need a single ssd with 32gb of storage, like this First step, you use the "IDE TO USB" adapter and connect your very old HDD to the new pc Make sure that the very old HDD had only ONE partition, or it won't work Then, type these commands; diskpart (if permissions, press yes) lis dis lis vol (look at your HDD <DRIVELETTER> and type: sel vol <DRIVENUMBER> at diskpart) then sel ur volume active exit After that, you copy ALL of your windows XP CD-ROM files to the very old HDD that you plug in, then eject the drive. For some reason this method works for windows vista and later DVD-ROMS when trying to copy all files over to the harddrive to make hdd boot. After that, plug it back into your old 486 PC and pray that it works. If problems, please tag me in the description.

There's a cheaper way

I tried it on an emulated 486, and it is laggy as hell even though it sort of support 486. Also I tried it on Pentium OverDrive 486 83mhz and it's not a fun experience. (86box)