Bridge Commander Central
BC Forums => BC Technical Support => Previous "Black Screen of Death" Fixes => Topic started by: Dante Leonhart on May 28, 2007, 06:40:17 PM
-
Well, I installed Gfx and immediately got a BSOD. Unfortunately, there's no way for me to give a console dump because I can't get the console to come down. Hitting tilde doesn't do anything and the ds9fx console dump (shift+p) doesn't work either.
Now, the strange thing is, I used the gfx uninstaller to uninstall the mod, but it didn't do anything. All the files are still in place.
Stranger still, when I load up a completely different install of BC (untouched by gfx) I still get a BSOD. I don't understand how that can be possible.
Edit: I got a console dump
http://i52.photobucket.com/albums/g8/Dante_Leonhart0001/Untitled-1copy-1.jpg
-
Dante: try here page 1, very bottom (that explains)
http://bcscripters.com/forums/index.php/topic,624.0.html
-
There's already a folder there called 'logs' :(
-
I had the same problem, but my install didn't have the logs file or the .txt, so I fixed it, like in the thread and it worked, are you sure you've got everything?
-
I had the same problem, but my install didn't have the logs file or the .txt, so I fixed it, like in the thread and it worked, are you sure you've got everything?
I had same trouble, works fine now
I'm at a loss Dante
Go http://bcscripters.com/forums/index.php/topic,624.0.html and submit the console deport
-
lol, that's almost the same error I had when I installed gfx 1.0
I actually had to run TimeMeasurement.py with Python's IDLE. I used the Check Module function and it reported that there was some spaces where there should be tabs. Weird thing but ok. Once I created the folder Logs and put the file "GravityManagerLOG.txt" and edited the timemeasurement.py, that game worked after that.
Then again, I can always send the "TimeMeasurement.py" to your e-mail. I don't have a clue if it will work for you or not but can try it anyway. Just back up that file just in case anyway.
http://i155.photobucket.com/albums/s318/cordanilus/consolereport.jpg (http://i155.photobucket.com/albums/s318/cordanilus/consolereport.jpg)
-
sirneotheone@gmail.com
Go ahead and send it anyway, I'd appreciate it... I have no idea how to edit that in Python.
Tell me something... Gravityfx/logs ... what files are in there and is there an init.py in just the Gravityfx folder?
-
GravityFX/Logs...
I just made a blank txt file and called it "GravityManagerLOG.txt"
I don't have an init.py in the folder. as long as the folder is there with a the file mentioned above. The timemeasurement.py was just an extra thing I had.
k, sending the file.
-
I think it needs an __init__.py (note the underscores, they are important) if you want to create a file, so if the file is already there, then you are safe.
-
guys, if you just copy-paste MANUALLY the folders to the BC folder, it should work.
looks like the installer failed compiling one of the folders, so the scripts won't find it, giving a BSOD.
I have GFX installed manually and thus far, it works. once you install it, go to UMM and disable the logging options, just in case.
-
I think it needs an __init__.py (note the underscores, they are important) if you want to create a file, so if the file is already there, then you are safe.
Mine does Not have one!
-
But you do have a txt file in it (which is what I said).
-
The Logs folder isn't script related, but it's required. __init__.py isn't needed on it.
It is there just for GravityFX to dump logs into it, that's why when i packed GFX up i left it empty, why would i send you a log with the install? lol
But the .exe installer doesn't create the folder, probably because it is empty...
Also, creating .txt files in it isn't necessary, the Logger creates them if they aren't there, the only problem is if the folder is missing, because it doesn't create folders. And that is exactly what happened.
Now, what is REALLY strange is the TimeMeasurement *supposed* bug, supposed because i have it here, working, exactly like i put it in the pack, and all made using tabs, no spaces... Plus the console report DOESN'T tell what error happened in that line (you know, AttributeError, ImportError, etc...)
-
The Logs folder isn't script related, but it's required. __init__.py isn't needed on it.
It is there just for GravityFX to dump logs into it, that's why when i packed GFX up i left it empty, why would i send you a log with the install? lol
But the .exe installer doesn't create the folder, probably because it is empty...
Also, creating .txt files in it isn't necessary, the Logger creates them if they aren't there, the only problem is if the folder is missing, because it doesn't create folders. And that is exactly what happened.
Now, what is REALLY strange is the TimeMeasurement *supposed* bug, supposed because i have it here, working, exactly like i put it in the pack, and all made using tabs, no spaces... Plus the console report DOESN'T tell what error happened in that line (you know, AttributeError, ImportError, etc...)
I know that error. I've encounterd it many times before.
It only needs the __init__.py(c) to create the file, but for reading/writing to an existing file is fine.
-
Which one of those that i mentioned exactly?
-
I also had the BSOD problem immediately upon installing GravityFX, however for some strange reason and dont ask me why, I did nothing except Install it again straight away overwriteing its own already installed files and its worked ever since. Good mod too.
-
Which one of those that i mentioned exactly?
That would be the one without things like AttributeError or ImportError (the second one in this thread).
Sorry about that.
-
So... I don't need __init__.py in the logs folder or do I. Should I copy it from the Gravityfx folder? lol sorry guys, I'm getting confused on what I need to do to fix the problem.
-
did you try manually installing it? copy/pasting the data and scripts folder from GravityFX's "Manual Install" folder? that should fix it...
-
Yeah. I actually did that first and then tried the autoinstall when that didn't work. I think I'm going to just delete all of BC, copy over a back up and then try it all again to see if that works.
Edit:
Ok.... I just did a complete reinstall of BC.
Now it works. I have no idea why. I would guess maybe I dragged the manual install folders to the wrong directories in BC the first time, but that would probably have given different errors than what was already being reported. lol in any case, reinstalling everything seemed to work.
I really appreciate you guys helping me out!!