bought Black Shark today and only problems

[joey45]

Have you tried using DCSMAX which bypasses the Luancher????

[JG11Preusse]

Hm, still LUA crashes - IMHO LUA isnt involved with any graphic activities, still it's responsible for all system activities - asking Windows to do this & that.

So - the only other time I saw the LUA crash like this was when this other bloke had installed another LUA kit on his computer.

 

Ah, suddenly something else also occurs to me(!). Can you please do the following:

- Start a Command Promp (CMD) window

- Type the command: SET

- Righclick in the window, use "Mark text", rightclick to copy all the text you marked - then paste it in a post reply here.

I have a hope that I can see a specific problem with the text you post the next time we meet. :)

 

 

here it is:

 

Microsoft Windows [Version 6.1.7600]

Copyright © 2009 Microsoft Corporation. Alle Rechte vorbehalten.

C:\Users\AndiHH>set

ALLUSERSPROFILE=C:\ProgramData

APPDATA=C:\Users\AndiHH\AppData\Roaming

CommonProgramFiles=C:\Program Files\Common Files

CommonProgramFiles(x86)=C:\Program Files (x86)\Common Files

CommonProgramW6432=C:\Program Files\Common Files

COMPUTERNAME=ANDIHH-PC

ComSpec=C:\Windows\system32\cmd.exe

DFSTRACINGON=FALSE

FP_NO_HOST_CHECK=NO

HOMEDRIVE=C:

HOMEPATH=\Users\AndiHH

LOCALAPPDATA=C:\Users\AndiHH\AppData\Local

LOGONSERVER=\\ANDIHH-PC

NUMBER_OF_PROCESSORS=2

OS=Windows_NT

Path=C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Program Files (x

86)\ATI Technologies\ATI.ACE\Core-Static;C:\Windows\System32\WindowsPowerShell\v

1.0\;C:\Program Files (x86)\Common Files\Adobe\AGL

PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC

PROCESSOR_ARCHITECTURE=AMD64

PROCESSOR_IDENTIFIER=Intel64 Family 6 Model 23 Stepping 10, GenuineIntel

PROCESSOR_LEVEL=6

PROCESSOR_REVISION=170a

ProgramData=C:\ProgramData

ProgramFiles=C:\Program Files

ProgramFiles(x86)=C:\Program Files (x86)

ProgramW6432=C:\Program Files

PROMPT=$P$G

PSModulePath=C:\Windows\system32\WindowsPowerShell\v1.0\Modules\

PUBLIC=C:\Users\Public

SESSIONNAME=Console

SystemDrive=C:

SystemRoot=C:\Windows

TEMP=C:\Users\AndiHH\AppData\Local\Temp

TMP=C:\Users\AndiHH\AppData\Local\Temp

TRACE_FORMAT_SEARCH_PATH=\\NTREL202.ntdev.corp.microsoft.com\34FB5F65-FFEB-4B61-

BF0E-A6A76C450FAA\TraceFormat

USERDOMAIN=AndiHH-PC

USERNAME=AndiHH

USERPROFILE=C:\Users\AndiHH

windir=C:\Windows

C:\Users\AndiHH>

[JG11Preusse]

I've re-read this thread from page 1, and just so we don't lose focus of where the actual problem is occurring, you're still getting the c0000090 code in the app crash output, is that correct?

 

And this is happening more or less within the first few seconds of launching the single player icon (so the loading screen is the first and only screen you see before it crashes, you never see the main menu)?

 

absolute like you described. i see a picture in a window of the ka-50, also hear sound playing for 1-2 seconds and then it crashes.

 

never saw the main menue

[JG11Preusse]

Have you tried using DCSMAX which bypasses the Luancher????

 

no never tested it beacause i also never heard of it. dont know where to get it and dont know how to use it :)

[JG11Preusse]

Have you tried using DCSMAX which bypasses the Luancher????

 

 

tried it, game start with a selected mission, if i choose a mission.

 

but cant change to the main menue to setup options...

 

if i end the mission, im back on theskop with this utility

 

can i start with DCSMAX also to the mainmenue to steup keys and grafics and so on ?

 

now that i can start the game missions with this tool, we can sue no opengl issues are the probelm ?????

 

 

... if i start without choosing a mission, i have the same problem as befor "launcher .exe" .....

Edited April 17, 2010 by JG11Preusse

[topdog]

In case Panzertard's review of your SET / path results comes up blank, please could you try the following:

 

1. Download and run Procmon ( http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx )

 

2. Once it's launched press Ctrl+L (or go to menu Filter > Filter ...) and select the following:

 

Process Name

is

launcher.exe

include

 

3. Click Add (important else it doesn't get used) and then OK.

 

4. The main window for procman should now be blank, this is OK.

 

5. Run the single-player Blackshark from its normal icon, wait for it to crash. There should be a lot more output in the procman window now all related to launcher.exe (probably thousands of lines, hundreds at least, depending on how far it gets before crashing of course)

 

6. In Procman do File > Save and pick these options:

 

Events to save: Events displayed using current filter

Format: Native Process Monitor Format (PML)

 

7. Zip up this .pml file you created and upload it here.

 

This should help to identify all of the different file and registry accesses that the launcher.exe is trying to do, and at least be comparable against the same output on my machine (or your wife's) so that you can see where it stumbles to see the difference and what it's trying to do next.

[Panzertard]

I notice you got these installed,

Adobe AGL: - unicode font / substitution helper http://en.wikipedia.org/wiki/Adobe_Glyph_List

See which Adobe suite that installed this, uninstall those and try again.

 

Do you have Adobe Lightroom too? Because it contains it's own LUA intepretor. If so, uninstall and test again.

 

"TRACE_FORMAT_SEARCH_PATH" seems to be part of a Windows Driver SDK or Tracefmt

This may be a good candidate for causing unknown issues too. Try to uninstall whatever Windows SDK / driver developer tools you got installed.

 

DFSTRACINGON seems to be mentioned regarding php / scripting tools / developer environment.

Searching for both DFSTRACINGON and LUA gives a fair share of people discussing errors.

See if you can figure out which one that added this - it may also be one of the things that interferes with LUA and BS.

Edited April 17, 2010 by Panzertard

[JG11Preusse]

I notice you got these installed,

Adobe AGL: - unicode font / substitution helper http://en.wikipedia.org/wiki/Adobe_Glyph_List

See which Adobe suite that installed this, uninstall those and try again.

 

Do you have Adobe Lightroom too? Because it contains it's own LUA intepretor. If so, uninstall and test again.

 

"TRACE_FORMAT_SEARCH_PATH" seems to be part of a Windows Driver SDK or Tracefmt

This may be a good candidate for causing unknown issues too. Try to uninstall whatever Windows SDK / driver developer tools you got installed.

 

DFSTRACINGON seems to be mentioned regarding php / scripting tools / developer environment.

Searching for both DFSTRACINGON and LUA gives a fair share of people discussing errors.

See if you can figure out which one that added this - it may also be one of the things that interferes with LUA and BS.

 

hi panzertard,

 

tried to follow you suggestions, but if im serious, i have to tell you that i dont understand anything :)

 

no idea what and how to uninstall, what you meant :)

 

greetings

andi

[JG11Preusse]

In case Panzertard's review of your SET / path results comes up blank, please could you try the following:

 

1. Download and run Procmon ( http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx )

 

2. Once it's launched press Ctrl+L (or go to menu Filter > Filter ...) and select the following:

 

Process Name

is

launcher.exe

include

 

3. Click Add (important else it doesn't get used) and then OK.

 

 

 

sorry .. cant follow what you told me ...........

 

4. The main window for procman should now be blank, this is OK.

 

5. Run the single-player Blackshark from its normal icon, wait for it to crash. There should be a lot more output in the procman window now all related to launcher.exe (probably thousands of lines, hundreds at least, depending on how far it gets before crashing of course)

 

6. In Procman do File > Save and pick these options:

 

Events to save: Events displayed using current filter

Format: Native Process Monitor Format (PML)

 

7. Zip up this .pml file you created and upload it here.

 

This should help to identify all of the different file and registry accesses that the launcher.exe is trying to do, and at least be comparable against the same output on my machine (or your wife's) so that you can see where it stumbles to see the difference and what it's trying to do next.

 

tried to follow your suggestion.

dowloaded this program and arrived this step

Process Name

is

 

 

didnt found "launcher.exe" in the list and thats why i had to stop to go forward with you suggestions :)

Edited April 17, 2010 by JG11Preusse

[JG11Preusse]

In case Panzertard's review of your SET / path results comes up blank, please could you try the following:

 

1. Download and run Procmon ( http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx )

 

2. Once it's launched press Ctrl+L (or go to menu Filter > Filter ...) and select the following:

 

Process Name

is

launcher.exe

include

 

3. Click Add (important else it doesn't get used) and then OK.

 

4. The main window for procman should now be blank, this is OK.

 

5. Run the single-player Blackshark from its normal icon, wait for it to crash. There should be a lot more output in the procman window now all related to launcher.exe (probably thousands of lines, hundreds at least, depending on how far it gets before crashing of course)

 

6. In Procman do File > Save and pick these options:

 

Events to save: Events displayed using current filter

Format: Native Process Monitor Format (PML)

 

7. Zip up this .pml file you created and upload it here.

 

This should help to identify all of the different file and registry accesses that the launcher.exe is trying to do, and at least be comparable against the same output on my machine (or your wife's) so that you can see where it stumbles to see the difference and what it's trying to do next.

 

 

maybe to much wine yesterday :)

 

did it now an here it is

Logfile.rar

[JG11Preusse]

I notice you got these installed,

Adobe AGL: - unicode font / substitution helper http://en.wikipedia.org/wiki/Adobe_Glyph_List

See which Adobe suite that installed this, uninstall those and try again.

 

Do you have Adobe Lightroom too? Because it contains it's own LUA intepretor. If so, uninstall and test again.

 

"TRACE_FORMAT_SEARCH_PATH" seems to be part of a Windows Driver SDK or Tracefmt

This may be a good candidate for causing unknown issues too. Try to uninstall whatever Windows SDK / driver developer tools you got installed.

 

DFSTRACINGON seems to be mentioned regarding php / scripting tools / developer environment.

Searching for both DFSTRACINGON and LUA gives a fair share of people discussing errors.

See if you can figure out which one that added this - it may also be one of the things that interferes with LUA and BS.

 

all i have installed releated to adobe is adobe flashplayer 10, adobe photoshop cs2 and adobe reader 9.3.2.

 

Windows SDK / driver developer tools : no idea what this is and where to find it

 

 

DFSTRACINGON : same here... no idea what this program is and where to find it or uninstall it.

[Panzertard]

all i have installed releated to adobe is adobe flashplayer 10, adobe photoshop cs2 and adobe reader 9.3.2.

 

Windows SDK / driver developer tools : no idea what this is and where to find it

 

 

DFSTRACINGON : same here... no idea what this program is and where to find it or uninstall it.

It's just that I noticed those things (the data you posted from the SET command) because they are extra on your system. There are a few software things that can conflict with DCS and FC2.

 

But that said, FC2 is a bit newer - and you could run that - so there might be a chance your DCS problem can be solved when the new patch for DCS is out.

I have no estimate on the patch, we just have to wait and see.

 

I'm looking through the processmonitor log you sent as well, takes a bit of time.

Edited April 18, 2010 by Panzertard

[JG11Preusse]

It's just that I noticed those things (the data you posted from the SET command) because they are extra on your system. There are a few software things that can conflict with DCS and FC2.

 

But that said, FC2 is a bit newer - and you could run that - so there might be a chance your DCS problem can be solved when the new patch for DCS is out.

I have no estimate on the patch, we just have to wait and see.

 

I'm looking through the processmonitor log you sent as well, takes a bit of time.

 

uninstalled photoshop cs2 ..... still dont works.

[JG11Preusse]

uninstalled photoshop cs2 ..... still dont works.

 

 

what time the patch will be released ?

 

dont want to wait many weeks to be able to use, what i allready bought and payed :)

[Panzertard]

I dont know when it's released, sorry.

I really hope it's near - because we all want to fly DCS online together with FC2. :)

[JG11Preusse]

to said that i cant reach the menue .....if i could, i would setup everything (videooption, flightcontrol system x52 and so on) and then i could fly missions with DcsMax

 

 

 

 

in wich file are the keysettings ????????

Edited April 18, 2010 by JG11Preusse

[JG11Preusse]

ok foun d the file for the joystick.

 

can i change the direction of the pitch ?

 

now thrust slider forward is "pull the pitch"..... for planes ok, for heli a bad feeling, need it otherway round ....

Edited April 18, 2010 by JG11Preusse

[topdog]

I'll aim to check your procman log tomorrow; seems it required a 64-bit OS to read the file generated by the same, and I just don't have one near me today, sorry.

[topdog]

There wasn't anything being reported in the procmon logs relating to path/file issues.

 

It got as far as reading the AboutGeneral.txt file from the Blackshark\data\text directory, the next file it wanted to read in the main app thread was AboutCredits.txt, but it didn't even attempt to open this file/location before it bombed (so whether the file exists or not is actually moot, the crash happened before).

 

Around the same time although this could be coincidental, it was about to play the beginning chunks of the Sounds\EditorMusic\Babylon.ogg file, but never got to read more than 128k into the file before the app crashed - unknown from the procmon log if it was the sound itself contributing to the crash, or the game simply didn't last long enough to need to stream in any more than this because it crashed so fast. Either way, the file was there, and buffer reads were successful from it, no premature end of file or the like.

 

Everything else in the file was pretty clean, and could (relatively speaking) be mapped across to my own procmon log even though there are some differences in hardware and codecs/libraries, nothing that stood out as being undoubtedly wrong.

 

So unless the testers/moderators here have access to an internal list of error codes that the games are mapping to (unlikely for an app to remap core codes), then I think it more likely this is a genuine C0000090 error instead which is a floating point exception (like trying to do things like divide a number by NaN (the special indicator in FP math for 'not a number') or some other incompatible conversion/calculation).

 

(EtherealN - may I ask what made you think this was search/path related, just to be sure?)

 

ERROR_CODE: (NTSTATUS) 0xc0000090 - {EXCEPTION} Floating-point invalid operation.

 

Non-games can hit this error too, like SQL Server: http://support.microsoft.com/kb/318053

 

Here it blew up in a 'float to long' conversion function (aka ftol()), which could certainly happen if you tried to convert a 'NaN' to a long integer value. This isn't always called explicitly, the compiler can sneak them in whenever a typecast is done to a long/int from a (potentially) floating point value.

 

And other games/apps have had this exception too, but normally the cause has not been clear, however the general consensus is that this is an error code thrown back by the FPU because it couldn't comply with what it was asked to do.

 

Unfortunately little in the way of clues beyond this; typically these problems would be reviewed by the developers themselves using crashdump / minidump analysis and the source code they're in possession of.

 

Else I would have to hope that the BS/FC2 compatibility patch contains an updated launcher for BS that uses the codeline from FC2.

 

...

 

Only closing comments I have, are that functions like ftol() reside in the msvcr71.dll within the bin\stable directory, and at the point of the crash, this was the first library queried by the appcrash dialog that pops up.

 

In case you're experiencing a form of "dll hell", there are two solutions you may try:

 

1. Putting a new (empty) file named launcher.exe.local in your bin\stable directory

 

or

 

2. Rename the msvc*.dll files in the bin\stable directory

 

The first option tries to advise the game to use only local DLLs if it finds multiple, the latter is forcing it to try and look elsewhere for them (in case there are conflicts with the Windows SDK / DDK stuff that your machine seems it may contain, even if these are just leftovers from some wonky driver development and installation).

 

Both options are easily reversible (delete the .local file, rename the .dlls to their original names).

 

This isn't entirely clutching at straws, just an outside chance at trying to resolve any incompatibilities you may have with these files since there are many versions of each and "dll hell" is a long term compatibility problem.

[ShadowVonChadwick]

Is this thread still running,,,Unless your willing to reload a fresh install of Win7 with current drivers your not going any where, sorry. Been there done that. Its a laptop, proprietary drivers some stuff works yes!! I do this all the time, try to get some old/new game to run again on an existing config, some times you have to start from scratch.

 

I use a multi OS boot manger that can past in a fresh OS when needed. And then its which Anti Virus is installed, how many versions of C++ are installed (I know should not make a difference ??) what game do I install first. Some times it just doesn't work.

And uninstalling stuff dosent always take you back.

 

Sorry man I feel your frustration.

Edited April 19, 2010 by ShadowVonChadwick

[JG11Preusse]

Is this thread still running,,,Unless your willing to reload a fresh install of Win7 with current drivers your not going any where, sorry. Been there done that. Its a laptop, proprietary drivers some stuff works yes!! I do this all the time, try to get some old/new game to run again on an existing config, some times you have to start from scratch.

 

I use a multi OS boot manger that can past in a fresh OS when needed. And then its which Anti Virus is installed, how many versions of C++ are installed (I know should not make a difference ??) what game do I install first. Some times it just doesn't work.

And uninstalling stuff dosent always take you back.

 

Sorry man I feel your frustration.

 

 

talked to our IT today.

 

they told me that noone will be like this stupid, to setup the whole system new, only because one single game dont works.

 

as you allready know, the bs simulation itsel works, but the launcher dont works and so i cant reach the main menue.

 

they checked my systems and told me that it is absolute ok, without any problems.

also dont installed much software, which dont belongs to windows7.

again ..... all games i listed before are working properly and at a super performance, including lock on original and lock on fc2.

 

there is absolutely no reason to destroy everything only for a try to get this one game bs working.

the chance that it also wont work, after new installation is also present.

 

the notebook is not very old an i never changed drivers, beacause all of them are the latest availible. all i did is a bios update, because toshiba released a newer one. thats all.

 

greetings

andi

[JG11Preusse]

There wasn't anything being reported in the procmon logs relating to path/file issues.

 

It got as far as reading the AboutGeneral.txt file from the Blackshark\data\text directory, the next file it wanted to read in the main app thread was AboutCredits.txt, but it didn't even attempt to open this file/location before it bombed (so whether the file exists or not is actually moot, the crash happened before).

 

Around the same time although this could be coincidental, it was about to play the beginning chunks of the Sounds\EditorMusic\Babylon.ogg file, but never got to read more than 128k into the file before the app crashed - unknown from the procmon log if it was the sound itself contributing to the crash, or the game simply didn't last long enough to need to stream in any more than this because it crashed so fast. Either way, the file was there, and buffer reads were successful from it, no premature end of file or the like.

 

Everything else in the file was pretty clean, and could (relatively speaking) be mapped across to my own procmon log even though there are some differences in hardware and codecs/libraries, nothing that stood out as being undoubtedly wrong.

 

So unless the testers/moderators here have access to an internal list of error codes that the games are mapping to (unlikely for an app to remap core codes), then I think it more likely this is a genuine C0000090 error instead which is a floating point exception (like trying to do things like divide a number by NaN (the special indicator in FP math for 'not a number') or some other incompatible conversion/calculation).

 

(EtherealN - may I ask what made you think this was search/path related, just to be sure?)

 

ERROR_CODE: (NTSTATUS) 0xc0000090 - {EXCEPTION} Floating-point invalid operation.

 

Non-games can hit this error too, like SQL Server: http://support.microsoft.com/kb/318053

 

Here it blew up in a 'float to long' conversion function (aka ftol()), which could certainly happen if you tried to convert a 'NaN' to a long integer value. This isn't always called explicitly, the compiler can sneak them in whenever a typecast is done to a long/int from a (potentially) floating point value.

 

And other games/apps have had this exception too, but normally the cause has not been clear, however the general consensus is that this is an error code thrown back by the FPU because it couldn't comply with what it was asked to do.

 

Unfortunately little in the way of clues beyond this; typically these problems would be reviewed by the developers themselves using crashdump / minidump analysis and the source code they're in possession of.

 

Else I would have to hope that the BS/FC2 compatibility patch contains an updated launcher for BS that uses the codeline from FC2.

 

...

 

Only closing comments I have, are that functions like ftol() reside in the msvcr71.dll within the bin\stable directory, and at the point of the crash, this was the first library queried by the appcrash dialog that pops up.

 

In case you're experiencing a form of "dll hell", there are two solutions you may try:

 

1. Putting a new (empty) file named launcher.exe.local in your bin\stable directory

or

2. Rename the msvc*.dll files in the bin\stable directory

 

The first option tries to advise the game to use only local DLLs if it finds multiple, the latter is forcing it to try and look elsewhere for them (in case there are conflicts with the Windows SDK / DDK stuff that your machine seems it may contain, even if these are just leftovers from some wonky driver development and installation).

 

Both options are easily reversible (delete the .local file, rename the .dlls to their original names).

 

This isn't entirely clutching at straws, just an outside chance at trying to resolve any incompatibilities you may have with these files since there are many versions of each and "dll hell" is a long term compatibility problem.

 

 

wilco ... will try it today evening

[JG11Preusse]

There wasn't anything being reported in the procmon logs relating to path/file issues.

 

It got as far as reading the AboutGeneral.txt file from the Blackshark\data\text directory, the next file it wanted to read in the main app thread was AboutCredits.txt, but it didn't even attempt to open this file/location before it bombed (so whether the file exists or not is actually moot, the crash happened before).

 

Around the same time although this could be coincidental, it was about to play the beginning chunks of the Sounds\EditorMusic\Babylon.ogg file, but never got to read more than 128k into the file before the app crashed - unknown from the procmon log if it was the sound itself contributing to the crash, or the game simply didn't last long enough to need to stream in any more than this because it crashed so fast. Either way, the file was there, and buffer reads were successful from it, no premature end of file or the like.

 

Everything else in the file was pretty clean, and could (relatively speaking) be mapped across to my own procmon log even though there are some differences in hardware and codecs/libraries, nothing that stood out as being undoubtedly wrong.

 

So unless the testers/moderators here have access to an internal list of error codes that the games are mapping to (unlikely for an app to remap core codes), then I think it more likely this is a genuine C0000090 error instead which is a floating point exception (like trying to do things like divide a number by NaN (the special indicator in FP math for 'not a number') or some other incompatible conversion/calculation).

 

(EtherealN - may I ask what made you think this was search/path related, just to be sure?)

 

ERROR_CODE: (NTSTATUS) 0xc0000090 - {EXCEPTION} Floating-point invalid operation.

 

Non-games can hit this error too, like SQL Server: http://support.microsoft.com/kb/318053

 

Here it blew up in a 'float to long' conversion function (aka ftol()), which could certainly happen if you tried to convert a 'NaN' to a long integer value. This isn't always called explicitly, the compiler can sneak them in whenever a typecast is done to a long/int from a (potentially) floating point value.

 

And other games/apps have had this exception too, but normally the cause has not been clear, however the general consensus is that this is an error code thrown back by the FPU because it couldn't comply with what it was asked to do.

 

Unfortunately little in the way of clues beyond this; typically these problems would be reviewed by the developers themselves using crashdump / minidump analysis and the source code they're in possession of.

 

Else I would have to hope that the BS/FC2 compatibility patch contains an updated launcher for BS that uses the codeline from FC2.

 

...

 

Only closing comments I have, are that functions like ftol() reside in the msvcr71.dll within the bin\stable directory, and at the point of the crash, this was the first library queried by the appcrash dialog that pops up.

 

In case you're experiencing a form of "dll hell", there are two solutions you may try:

 

1. Putting a new (empty) file named launcher.exe.local in your bin\stable directory

 

or

 

2. Rename the msvc*.dll files in the bin\stable directory

 

The first option tries to advise the game to use only local DLLs if it finds multiple, the latter is forcing it to try and look elsewhere for them (in case there are conflicts with the Windows SDK / DDK stuff that your machine seems it may contain, even if these are just leftovers from some wonky driver development and installation).

 

Both options are easily reversible (delete the .local file, rename the .dlls to their original names).

 

This isn't entirely clutching at straws, just an outside chance at trying to resolve any incompatibilities you may have with these files since there are many versions of each and "dll hell" is a long term compatibility problem.

 

 

1. Putting a new (empty) file named launcher.exe.local in your bin\stable directory

dont works, same problem

 

2. Rename the msvc*.dll files in the bin\stable directory

dont works ....... program dont starts, because a msvc file is missing .. reinstall the program says the error message

[Distiler]

Hey buddy, 23 pages!!! :joystick:

 

Time to try OS reinstallation , or wait for patch with fingers crossed.

 

1-2 hours for OS, drivers and other software at max? way less than what you spent in this thread (days). I really think it's worth a try.

 

The worse that can happen is...having a fresh and ready installation so it never hurts! :)

Edited April 20, 2010 by Distiler

[ShadowVonChadwick]

talked to our IT today.

 

they told me that noone will be like this stupid, to setup the whole system new, only because one single game dont works.

 

greetings

andi

 

Sorry if I sounded rough, what I ment to say was that you have tried hard to get BS to run without complete success, many people have given good advice & it still wont run. The only logical step now is a clean OS +BS.

Its a radical action only if you have the desire. Im not saying you should.

 

But BS is a nice piece of work.

 

Best of luck...Shad