Author Topic: G PLan (358) initial load errors in log  (Read 2257 times)

Offline Emile

  • Navigator
  • ****
  • Posts: 136
  • Country: be
    • View Profile
G PLan (358) initial load errors in log
« on: September 01, 2009, 07:51:28 AM »
Hello,
Running initial load (version 358) I see some errors in the log. See attached screenshot for an example


any recommendations?

Thanks for this tool.
Emile EBBR Asus P7P67 Pro v3, Intel 1155 3.4 GH, Cordair DDR3 8Gb,PCX Nvidia 560 ti,PCX Nvidia 550 ti,
SSD 120Gb, 2 x 1 Tera SATA6, Dual Boot .

Offline tim arnot

  • Administrator
  • Master Navigator
  • *****
  • Posts: 5919
  • Country: england
    • View Profile
Re: G PLan (358) initial load errors in log
« Reply #1 on: September 01, 2009, 09:29:06 AM »
Hi Emile

Any chance you could zip up those two files (AFX_LERL.bgl and AFX_LEVC.bgl) and send them to me? Then I can sort out the problem.

Thanks

Tim. @TimArnot

Offline falcon409

  • Tracker
  • **
  • Posts: 23
    • View Profile
Re: G PLan (358) initial load errors in log
« Reply #2 on: September 01, 2009, 12:17:51 PM »
There's a new build out (358)?

Offline tim arnot

  • Administrator
  • Master Navigator
  • *****
  • Posts: 5919
  • Country: england
    • View Profile
Re: G PLan (358) initial load errors in log
« Reply #3 on: September 01, 2009, 01:06:13 PM »
True, but it doesn't address Emile's problem  ;)

Tim. @TimArnot

Offline Emile

  • Navigator
  • ****
  • Posts: 136
  • Country: be
    • View Profile
Re: G PLan (358) initial load errors in log
« Reply #4 on: September 01, 2009, 03:24:27 PM »
Hello,
I have added all the error .bgl found on my PC.
Hope it helps.
Thanks
Emile EBBR Asus P7P67 Pro v3, Intel 1155 3.4 GH, Cordair DDR3 8Gb,PCX Nvidia 560 ti,PCX Nvidia 550 ti,
SSD 120Gb, 2 x 1 Tera SATA6, Dual Boot .

Offline tim arnot

  • Administrator
  • Master Navigator
  • *****
  • Posts: 5919
  • Country: england
    • View Profile
Re: G PLan (358) initial load errors in log
« Reply #5 on: September 01, 2009, 03:59:05 PM »
Thanks, I'll take a look.

Tim. @TimArnot