OldUnreal (Engine)

Is there ANY WAY to get this to stop showing up? I have Unreal.log and Running.ini readonly'd and completely blank, and 227 keeps thinking Unreal "crashed" when all I'm trying to avoid is log write\read accessing, which severely bogs down my system.

I never had this issue in UT436, is there a bool or a commandline param I can use to get this screen to stop showing?

And please don't say that the answer is to remove Running.ini as that's going to piss me off... I don't want Unreal to access the log to read or write to it, period...

you have much bigger problems if read/write accessing is slowing down your system. your IDE controller drivers are probably bad or the HDD is dying, or windows needs to be reinstalled.

I'm unsure of what unreal actually checks for when it crashes, but it's probably running.ini.

When unreal decides to log messages 1000 times a second it tends to slow down, I alleviated the problem by readonly'ing the Unreal.log and Running.ini, this also cut's loadtimes in half when precacheing is also turned off.

IS there really no way to tell Unreal to not attempt a safemode thing...? Seriously I've done this in < 227 and in UT436 for a long time now.

it should be exactly the same as UT and any other version, we only added an audio change button in 227f, and i'm pretty sure thats it

Sometimes my PC runs utterly slow, sometimes it's normal, I'm blaming the idiots at AVG Technologies... 8.5 made my computer run slow as hell but atleast it let's me add exceptions so it can stop thinking something's a virus even though it isn't...

I've defragged my computer and did a full disk check on my HD, still 0kb in bad sectors and no file system errors supposedly, I've been defragging even at the slightest .5% of file fragmentation because for some reason it seriously makes a difference...

Running.ini causes Unreal to open Safe Mode. Delete it and run Unreal from a script that constantly deletes any new generated Running.ini files, if you don't want to see the safe mode again. But, simply put, delete Running.ini. It exists for the sole purpose of telling Unreal to open that dialog. And it's always empty.

Emerald, you can't delete a file that's in use by something else.

Unreal creates a Running.ini file on launch, and deletes it when you close it normally. When it crashes, it doesn't delete it, and thus it's a sign that it should open the safe mode menu. So make sure Unreal can delete the file when it closes, and that should fix the problem.

Hard for anything to touch a file without rejection\confirmation when it's write protected...

1. http://lmgtfy.com/?q=Unlocker+download
2. http://free-av.com/

Are those capable of running under my screwed over OS?

Seriously I just wish that safemode BS could be turned off through a commandline param.. Would be so much easier.

Un-writeprotect it then. You don't need that on Running.ini.

Yes I do, it completely forbids Unreal from writing ANYTHING to the log, regardless if I opened it or not... Thus the write times on my harddisk aren't so huge and Unreal doesn't take a field day logging everything that happens... So load times are dramatically faster than they were with the log in use...

I don't see how Running.ini is related to the log. Just writeprotect the log, and that's it.

Then you don't understand what goes on as Running.ini is accessed.... Try it yourself.. But you use Linux, not windows. So I don't know how you're able to have a log window and Unreal running at the same time, I guess through a terminal? (Forgive me if I sound like a idiot..)

I use both Windows and Linux. Try what? Opening the log when you have Unreal running?