🚀 go-pugleaf

Are you seeing any Error message ?
Does it start up all ?
or does the launcher not even appear ?
@@@Mouse@@@

DMP <D...@mungemaid.com> wrote in news:n9nc74$4s5$1...@dont-email.me:

> Downgraded to Win 10 Pro.

I'd say that's your main problem right there.

If you are able to, go back to your older (and, frankly, far better) 
version of Windows because this current 'version' is far from being user 
friendly.

(As if M$ didn't have *enough* to answer for) >_<

On Sat, 13 Feb 2016 08:51:12 -0500, DMP <D...@mungemaid.com> wrote:

>Upgraded to Win 10 Pro.
>
>Have not been able to get BGEE(from Beamdog) to run; tried compatibility 
>mode for both Win7 & Win8; disabled scaling; Open AL still on my PC 
>after the upgrade; can't get the launcher to budge. Can play BG II EE 
>however;went to forum; only a couple of suggestions that I already tried
>
>Has anyone gotten BGEE to run? Thanks.

Some folks have been able to run it without problems on Windows 10,
others seem to have had trouble with Open AL, possible solution at
this link.

https://steamcommunity.com/app/257350/discussions/0/541907675755948205/

I've upgraded no less than 8 systems to Windows 10 from Win7 and about
the only thing I've ever seen not go swimmingly is typically audio
driver related.  Creative drivers are notorious for this.  It usually
turns out to be something very simple, like reinstalling the driver,
telling Windows which version of the driver to use, etc.

Audio driver is almost certainly your culprit.

On 2/13/2016 12:02 PM, Trimble Bracegirdle wrote:
> Are you seeing any Error message ?
> Does it start up all ?
> or does the launcher not even appear ?
> @@@Mouse@@@

I'll reply to all here.....The game didn't start at all; couple of spins 
of the blue circle thingie and nothing. No error messages and no 
launcher appeared.

I tried all the compatibility settings in properties with scaling both 
on and off. Still no start. I don't have a Creative Labs sound card, but 
just use sound from the motherboard with Real-tek drivers.

Put it all back to original settings; did a few unrelated things with 
the PC and updates and stuff requiring a couple more reboots then I 
already had done trying to get it to work. Clicked on it a few minutes 
ago and its now working. Go figure. Thanks for your replies.

On Sat, 13 Feb 2016 17:05:04 -0500, DMP <D...@mungemaid.com> wrote:

>I tried all the compatibility settings in properties with scaling both 
>on and off. Still no start. I don't have a Creative Labs sound card, but 
>just use sound from the motherboard with Real-tek drivers.

Just as an FYI, I mentioned Creative because they took over the OpenAL
project from another developer as an open standards project.  It's a
cross platform driver, and you don't have to use a Creative brand card
to use OpenAL.

Also when I said Creative drivers are notorious for this, I wasn't
necessarily picking on them as a company.  The problem is that because
Windows is designed to work with a gazillion different audio interface
hardware possibilities, there are a lot of things that can go wrong
with regards to gaming.  If Microsoft went the way of Apple, and made
their software runnable only on their own hardware, this sort of audio
driver snafu would go largely away because it removes driver
configuration differences as a potential source of issue.

Sometimes Windows works itself out with regard to audio config issues
with a few reboots, installs, etc.  Sounds like this might be what
happened for you.  Glad its working now.

On 2/13/2016 3:03 PM, Rin Stowleigh wrote:
> On Sat, 13 Feb 2016 17:05:04 -0500, DMP <D...@mungemaid.com> wrote:
>
>> I tried all the compatibility settings in properties with scaling both
>> on and off. Still no start. I don't have a Creative Labs sound card, but
>> just use sound from the motherboard with Real-tek drivers.
>
> Just as an FYI, I mentioned Creative because they took over the OpenAL
> project from another developer as an open standards project.  It's a
> cross platform driver, and you don't have to use a Creative brand card
> to use OpenAL.
>
> Also when I said Creative drivers are notorious for this, I wasn't
> necessarily picking on them as a company.  The problem is that because
> Windows is designed to work with a gazillion different audio interface
> hardware possibilities, there are a lot of things that can go wrong
> with regards to gaming.  If Microsoft went the way of Apple, and made
> their software runnable only on their own hardware, this sort of audio
> driver snafu would go largely away because it removes driver
> configuration differences as a potential source of issue.
>
This is what Microsoft is doing with WX.  I don't have a URL for the 
press release but they have announced that WX will not be fully 
supported unless it is being running on certain hardware.

(Of course they waited until WX had been forcefully installed on 
millions of "non-compatible" machines....)

-- 
Now the Force-Ghost of DTravel since he was forced by shame to commit 
hara-kiri with a dull light-spork after liking the Abrams/Bad Robot Star 
Wars movie.

On Sat, 13 Feb 2016 17:58:25 GMT, Warewolf <warewol...@shaw.ca>
wrote:

>DMP <D...@mungemaid.com> wrote in news:n9nc74$4s5$1...@dont-email.me:
>
>> Downgraded to Win 10 Pro.
>
>I'd say that's your main problem right there.
>
Well, I'm glad somebody said it; I didn't want to be the first ;-)

Not that I'd entirely blame Windows 10 there; many games are developed
for specific Operating Systems and have problems with later versions.
It's the nature of the beast and Microsoft has gone to amazing lengths
to maintain backwards compatibility. Unfortunately, games are often
the biggest loser in the process. I mean, just the changes to the
drivers can cause all sorts of problems.

Win7 is still the defacto platform for many developers. Using anything
else - especially for games developed in the last five years or so -
is just asking for extra headaches.

On 2/14/2016 9:39 AM, Spalls Hurgenson wrote:
> On Sat, 13 Feb 2016 17:58:25 GMT, Warewolf <warewol...@shaw.ca>
> wrote:
>
>> DMP <D...@mungemaid.com> wrote in news:n9nc74$4s5$1...@dont-email.me:
>>
>>> Downgraded to Win 10 Pro.
>>
>> I'd say that's your main problem right there.
>>
> Well, I'm glad somebody said it; I didn't want to be the first ;-)
>
> Not that I'd entirely blame Windows 10 there; many games are developed
> for specific Operating Systems and have problems with later versions.
> It's the nature of the beast and Microsoft has gone to amazing lengths
> to maintain backwards compatibility. Unfortunately, games are often
> the biggest loser in the process. I mean, just the changes to the
> drivers can cause all sorts of problems.
>
> Win7 is still the defacto platform for many developers. Using anything
> else - especially for games developed in the last five years or so -
> is just asking for extra headaches.
>
>
>
>
>


I played with it for months on my laptop; didn't mind it much and I 
don't mind it much now. The Win10 install went off w/o a hitch on two 
PC's;Turned off all the locator and phone home stuff and using a local 
account. I don't sync anything either.

Actually, the thing is pretty speedy booting up/shutting down and I've 
had no issues whatsoever with the games I have on my PC. They all run 
very well.

The only thing that gave me a real headache was my Saitek Cyborg 
keyboard that I was able to fix. Maybe I'm the party of one here, an OS 
is an OS is an OS. It runs when I turn it on, doesn't BSOD me and it's 
just Win7/8/8.1 in a little fancier dress.

Diane

PS I wish there was more chatter here

On Sat, 13 Feb 2016 20:29:27 -0800, Dimensional Traveler
<dtr...@sonic.net> wrote:

>On 2/13/2016 3:03 PM, Rin Stowleigh wrote:
>> On Sat, 13 Feb 2016 17:05:04 -0500, DMP <D...@mungemaid.com> wrote:
>>
>>> I tried all the compatibility settings in properties with scaling both
>>> on and off. Still no start. I don't have a Creative Labs sound card, but
>>> just use sound from the motherboard with Real-tek drivers.
>>
>> Just as an FYI, I mentioned Creative because they took over the OpenAL
>> project from another developer as an open standards project.  It's a
>> cross platform driver, and you don't have to use a Creative brand card
>> to use OpenAL.
>>
>> Also when I said Creative drivers are notorious for this, I wasn't
>> necessarily picking on them as a company.  The problem is that because
>> Windows is designed to work with a gazillion different audio interface
>> hardware possibilities, there are a lot of things that can go wrong
>> with regards to gaming.  If Microsoft went the way of Apple, and made
>> their software runnable only on their own hardware, this sort of audio
>> driver snafu would go largely away because it removes driver
>> configuration differences as a potential source of issue.
>>
>This is what Microsoft is doing with WX.  I don't have a URL for the 
>press release but they have announced that WX will not be fully 
>supported unless it is being running on certain hardware.
>
>(Of course they waited until WX had been forcefully installed on 
>millions of "non-compatible" machines....)

Umm..  There is a massive difference between saying "ok, here are the
tens of thousands or so of compatible devices" and saying "our OS will
only run on hardware we sell you".

On 2/14/2016 9:06 AM, Rin Stowleigh wrote:
> On Sat, 13 Feb 2016 20:29:27 -0800, Dimensional Traveler
> <dtr...@sonic.net> wrote:
>
>> On 2/13/2016 3:03 PM, Rin Stowleigh wrote:
>>> On Sat, 13 Feb 2016 17:05:04 -0500, DMP <D...@mungemaid.com> wrote:
>>>
>>>> I tried all the compatibility settings in properties with scaling both
>>>> on and off. Still no start. I don't have a Creative Labs sound card, but
>>>> just use sound from the motherboard with Real-tek drivers.
>>>
>>> Just as an FYI, I mentioned Creative because they took over the OpenAL
>>> project from another developer as an open standards project.  It's a
>>> cross platform driver, and you don't have to use a Creative brand card
>>> to use OpenAL.
>>>
>>> Also when I said Creative drivers are notorious for this, I wasn't
>>> necessarily picking on them as a company.  The problem is that because
>>> Windows is designed to work with a gazillion different audio interface
>>> hardware possibilities, there are a lot of things that can go wrong
>>> with regards to gaming.  If Microsoft went the way of Apple, and made
>>> their software runnable only on their own hardware, this sort of audio
>>> driver snafu would go largely away because it removes driver
>>> configuration differences as a potential source of issue.
>>>
>> This is what Microsoft is doing with WX.  I don't have a URL for the
>> press release but they have announced that WX will not be fully
>> supported unless it is being running on certain hardware.
>>
>> (Of course they waited until WX had been forcefully installed on
>> millions of "non-compatible" machines....)
>
> Umm..  There is a massive difference between saying "ok, here are the
> tens of thousands or so of compatible devices" and saying "our OS will
> only run on hardware we sell you".
>
Their press release says the list is not exhaustive and more may be 
added to it.  At the moment MS' list of compatible devices is:
Intel Skylake chips.
End of list.

MS has a history of deliberately writing code that is not 100% 
compatible with the standards agreed upon by everyone else so that their 
in-house products run better on Windows than anything anyone else can 
make.  This is just an extension of that policy.

-- 
Now the Force-Ghost of DTravel since he was forced by shame to commit 
hara-kiri with a dull light-spork after liking the Abrams/Bad Robot Star 
Wars movie.

On Sun, 14 Feb 2016 13:46:58 -0800, Dimensional Traveler
<dtr...@sonic.net> wrote:

>On 2/14/2016 9:06 AM, Rin Stowleigh wrote:
>> On Sat, 13 Feb 2016 20:29:27 -0800, Dimensional Traveler
>> <dtr...@sonic.net> wrote:
>>
>>> On 2/13/2016 3:03 PM, Rin Stowleigh wrote:
>>>> On Sat, 13 Feb 2016 17:05:04 -0500, DMP <D...@mungemaid.com> wrote:
>>>>
>>>>> I tried all the compatibility settings in properties with scaling both
>>>>> on and off. Still no start. I don't have a Creative Labs sound card, but
>>>>> just use sound from the motherboard with Real-tek drivers.
>>>>
>>>> Just as an FYI, I mentioned Creative because they took over the OpenAL
>>>> project from another developer as an open standards project.  It's a
>>>> cross platform driver, and you don't have to use a Creative brand card
>>>> to use OpenAL.
>>>>
>>>> Also when I said Creative drivers are notorious for this, I wasn't
>>>> necessarily picking on them as a company.  The problem is that because
>>>> Windows is designed to work with a gazillion different audio interface
>>>> hardware possibilities, there are a lot of things that can go wrong
>>>> with regards to gaming.  If Microsoft went the way of Apple, and made
>>>> their software runnable only on their own hardware, this sort of audio
>>>> driver snafu would go largely away because it removes driver
>>>> configuration differences as a potential source of issue.
>>>>
>>> This is what Microsoft is doing with WX.  I don't have a URL for the
>>> press release but they have announced that WX will not be fully
>>> supported unless it is being running on certain hardware.
>>>
>>> (Of course they waited until WX had been forcefully installed on
>>> millions of "non-compatible" machines....)
>>
>> Umm..  There is a massive difference between saying "ok, here are the
>> tens of thousands or so of compatible devices" and saying "our OS will
>> only run on hardware we sell you".
>>
>Their press release says the list is not exhaustive and more may be 
>added to it.  At the moment MS' list of compatible devices is:
>Intel Skylake chips.
>End of list.
>
>MS has a history of deliberately writing code that is not 100% 
>compatible with the standards agreed upon by everyone else so that their 
>in-house products run better on Windows than anything anyone else can 
>make.  This is just an extension of that policy.

Every for-profit manufacturer of any sort of integrated product,
whether software, or anything else, deliberately takes steps to make
sure their products work better together than with competitors
products.  It's called the pursuit of competitive advantage.  We do
not live in a communist society where everyone has an obligation to
code to the lowest common denominator.  

Anyone who has been involved in the creation of this type of product
knows that there is another reason for this.  It is not cost-feasible
to test every possible third-party vendors stuff with your own stuff.
It is up to the third party vendor to make sure they are compliant
with the marketshare leader.  

If a group of hippies wants to march off and create their own
standards committee, they are free to do so, but it means fuck all if
they end up falling flat on their asses when they try to get their
shitty products to take off and fail to get market share.

Now, that said, Microsoft for years has pumped millions upon millions
into the WHQL initiative to wipe the asses of these third parties,
making it easier for them to ensure compliance.  The only thing they
haven't done thus far is twist people's arm.  The result of not arm
twisting is that people bitch about how Apple doesn't have driver
problems, yada yada.  Hell, Apple re-invents their cablilng technology
every couple of years to make sure you buy a new device. So Microsoft
is doing what they need to do in order to achieve Apple-like
reliability.

Microsoft made Office documents an open-standard, but people still
don't use the shitty rip off apps, because they aren't as good. They
go to great pains to make sure Office works just as well on Mac OS X,
because otherwise the operating system that has the second best
marketshare would not have to settle for shitty Open Office and such.

A lot of people don't realize that in the big scheme of things,
notwithstanding OEM licenses that PC vendors pay for, Microsoft does
not make much of their total revenue off individual Windows copies.

Therefore this notion of forcing Windows 10 on people as a money
making ploy is about as foolish as the individuals that propagate the
idea.

http://www.zdnet.com/article/windows-10-subscriptions-arent-happening-heres-why/