Page 1 of 1

L3DT Crashing upon bootup

PostPosted: Thu Apr 15, 2010 10:58 pm
by dlstorminc
Hey all:

Didn't find any info on the forums about this so here goes... hope I'm posting in the right zone... ok, L3DT 2.8 crashes when I boot her up. I ran it in Admin mode as well as without it and even did what was suggested for Windows 7 but I'm running Vista. The program has run fine for the last year until now, even the older 2.7 version does the same thing now... what I'm getting is:

"An error occurred when reading from the system registry"

and then when you hit ok, it gives you the code box but you can't hit OK on it so when you hit cancel, it says its exiting... I tried the keyreset program as well as even went to extremes to buy registry mechanic and still, not working. Any ideas on what I can do to get up and running? I'm downloading the .18 build and see if that will help but I doubt it.

Any ideas very much welcomed at this point... my email is dlstorminc@yahoo.com or yahoo msgr magic_man4_life Thanks much in advance for any help anyone can offer me on this. Looking forward to getting this back up and running.

Will

Dev Version Std .18

PostPosted: Thu Apr 15, 2010 11:14 pm
by dlstorminc
Ok, the dev version STDX version 2.8.18 seems to load without a hitch. I can get it up and running without a prob. now comes the question: When will the pro version get this update? I own the pro release and i hope to get it up and running, still, it works thou, I dont know if that makes any headway thou... Thoughts or ideas? Thanks much, looking forward to getting up and going again on making terrains.

Will

PostPosted: Fri Apr 16, 2010 12:35 pm
by Aaron
Hi dlstorminc,

I apologise for this inconvenience. Can you please send me the debugging logfile from Pro v2.8? You can get the log file by opening the Windows Start menu, and selecting the 'All programs->Bundysoft->L3DT Professional v2.8->L3DT logs' shortcut. This will open a folder containing a file called 'debug.dat'. Please send this file to aaron@bundysoft.com. With this file, I should be able to work out what is going wrong.

Best regards,
Aaron.

PostPosted: Wed Apr 28, 2010 11:02 pm
by Aaron
Hi everyone,

This was a timeout problem, which has now been fixed. If you experience the same issue, I recommend you update to the latest developmental build.

Best regards,
Aaron.