X-Ray SDK compiler fatal error

[ket]

Title says most of it... heres the log;

* Detected CPU: GenuineIntel P3 family, F6/M15/S6, 2397.00 mhz, 63-clk 'rdtsc'
* CPU Features: RDTSC, MMX, SSE, SSE2

Initializing File System...
FS: 137 files cached, 86Kb memory used.
Init FileSystem 0.014066 sec
'xrCore' build 0, (null)

CRT heap 0x01330000
Process heap 0x00140000

I'm using the fixed xrlc. Anyone have any ideas? I haven't even changed that much in the level I edited... just added some objects so the level looked and felt a lot more finished. This SDK is really trying my patience its done nothing but bitch and moan over the simplest of things

[Nightwatch]

I'm not experienced in X-Ray SDK and haven't used it for a long time, but as far as I can collect from the error report that you posted, there appears to be a memory access violation/management problem going on there. That sort of errors are commonly seen in Java applications, but not limited with, of course.

A "heap" in programming language is an area of (pre)reserved memory in which a process stores its data, amounts of which will be realized once that certain program starts running. Obtaining a certain amount of heap storage beforehand from the OS enables the process to manage the storage (memory) faster and more effectively other than requesting memory allocation(s) from the OS each and single time it needs.

The process "manages" its own "pre-allocated heap" by asking a "chunk" of that heap (heap block ) as and when it needs. And then returns the no-longer-needed blocks.

It may be X-ray SDK problem in this management of affairs which may have been accentuated in your version of OS and in conflict with some drivers and/or programs (we know that SDK is quite sensitive, mildly put) or it can also be due to some erroneous code imported into the SDK which might've caused it act in this way. You may also wish to check your memory as an additional step. Though it may not be a great help in this respect -and you may have probably done that already, but I'm mentioning it for the sake of just mentioning it- you may want to use the IncreaseUserVa 3072 command for extended virtual memory usage, too.

[cOldSnake]

Or perhaps compiler is not installed correctly.Try using default one,"fixxed_xrlc" is only to skip fatal error for invalid faces,nothing else

[ket]

Thanks guys, I did start thinking the problem may be because I'm trying to use the compiler on W7 and not XP. I'll try increasing my pagefile but its already allowed to grow up to 4GB so the compiler shouldn't be complaining about that... but you never know. Oddly, the SoC SDK even asks for thm files, I've had to take them out of the CoP and CS files :/