The Dreaded G'reloc error

[tarheelB&B]

After chatting with Gguruusa last night, i thought it might be a good i dea to centralize a disscusion on the error that it seems a few people on the forum are getting when they try to cook/compile a ROM, so we can find a common denominator between us that are having this problem. The error that is in question occurs in the 3rd step of the cook when G'reloc trys to open a file usually "can't open C:\Documents and Setting.....\S000" . In my experience the "file" is never there to be opened.
I would like for people that are having this error to post their machine specs and environments so that maybe we can figure out whats going on.


Mine are
AMD 5400+ BE 3.2 ghz
Win XP Pro x64 sp2
Login with Administrator Privaleges
Net Framework 2.0
No antivirus, no firewall

[edieppc]

Have same problem here which cannot be solved with disabling antivirus, firewall etc, or extracting rars.
"But now my problem was solved ( I'm using windows XP )."

I noticed that files cannot be opened ( OpenError ) in status log, some strange appeared here when I clicked on "Do It" button then status displays file open error with path location contain double slashes ( // ).
So I consider that this is due file system disadvantage that I used that time ( I use FAT32 file system ). So I managed to convert my file system to NTFS,
and the result is no more G'Reloc error anymore

Yes it's has been solved at last.

This is how I convert my system partition ( partition that contain "Documents and Settings" folder if you're not understand what I'm mean )

Notes:
Only do this if your system partition does not contain any potential data!! ( as default "My Documents" folder located at "documents and settings" folder ), so backup or move your data into safe partition first.
Alternatively you can install new OS with NTFS partition rather than FAT32.

- click "start" - "run" type "cmd" then enter
- type "convert C: /FS:NTFS /X" then enter
you will be prompted that the partition will be converted after
system restart ( this is due that partition cannot be unmounted )
so just answer "Yes" here, then restart!
The Process will take some time depends on your system performance
and amount of data contains on that partition.
- System will automaticaly restart, build your ROM

I Will post this post on another threads