Slow Microgaming

[vinylweatherman]

Every month, I update my Microgaming casinos, as we are all FORCED to do.

This month should have been painless, with only 4 new games. However, after all the games are installed my casinos run slow and splutter for a further TWO HOURS!.
I played at Mummys Gold earlier, having updated the 4 games beforehand. While I won in the end, the experience was so bad (software wise) that I had to take two co-codamol for a splitting headache after two hours of infinite delays in launching each and every game, slow and spluttery spins, jerks and display errors - you name it, it happened. After around two hours, the software suddenly freed up and ran smoothly again. At this point, I had pretty much completed the WR on the weekend offer, so out it came (glad that was over).

While I wait for the money, time for some science.

Case in point, Challenge Casino. All 4 games updated, and have left it logged in for a while, BUT it gives problems with some games just refusing to launch, and even simple games such as Double Magic spluttering and jerking.
I logged off, and retrieved an old friend from my archives, Dependency Walker, to see what was happening.

Well, it was most interesting, I am logging Challenge, supposedly idle having long since updated the new games, but idle it isn't - it's hitting CPU, file system, and internet with the following:-

----------------------------------------------------------------------
Thread 23 exited with code 0 (0x0).
Mup: Upgraded package "JackpotDeuces1"
MupQueue: Removed package "JackpotDeuces1"
Mup: Upgraded package "JackpotExpress1"
MupQueue: Removed package "JackpotExpress1"
Mup: Upgraded package "JacksOrBetter1"
MupQueue: Removed package "JacksOrBetter1"
Mup: Upgraded package "JacksOrBetter100Play1"
MupQueue: Removed package "JacksOrBetter100Play1"
Mup: Upgraded package "JacksOrBetter50Play1"
MupQueue: Removed package "JacksOrBetter50Play1"
Mup: Upgraded package "JacksorBetterPowerPoker1"
MupQueue: Removed package "JacksorBetterPowerPoker1"
Mup: Upgraded package "JacksOrBetterTenPlay1"
MupQueue: Removed package "JacksOrBetterTenPlay1"
Mup: Upgraded package "JewelThief2"
MupQueue: Removed package "JewelThief2"
Mup: Upgraded package "JokerPoker1"
MupQueue: Removed package "JokerPoker1"
Mup: Upgraded package "JokerPoker100Play1"
MupQueue: Removed package "JokerPoker100Play1"
Mup: Upgraded package "JokerPoker50Play1"
MupQueue: Removed package "JokerPoker50Play1"
Mup: Upgraded package "JokerPokerPowerPoker1"
MupQueue: Removed package "JokerPokerPowerPoker1"
Mup: Upgraded package "JokerPokerTenPlay1"
MupQueue: Removed package "JokerPokerTenPlay1"
Mup: Upgraded package "JungleJim1"
MupQueue: Removed package "JungleJim1"
Mup: Upgraded package "JurassicJackpot1"
MupQueue: Removed package "JurassicJackpot1"
Mup: Upgraded package "Kathmandu1"
MupQueue: Removed package "Kathmandu1"
Mup: Upgraded package "KingCashaLot1"
MupQueue: Removed package "KingCashaLot1"
Mup: Upgraded package "LadiesNite5"
MupQueue: Removed package "LadiesNite5"
Mup: Upgraded package "LionsShare1"
MupQueue: Removed package "LionsShare1"
Mup: Upgraded package "Loaded1"
MupQueue: Removed package "Loaded1"
Mup: Upgraded package "LotsaLoot1"
MupQueue: Removed package "LotsaLoot1"
Mup: Upgraded package "LotsaLoot5Reel1"
MupQueue: Removed package "LotsaLoot5Reel1"
Mup: Upgraded package "LuckyCharmer1"
MupQueue: Removed package "LuckyCharmer1"
Mup: Upgraded package "MajorMillions1"
MupQueue: Removed package "MajorMillions1"
Mup: Upgraded package "MajorMillions5Reel1"
MupQueue: Removed package "MajorMillions5Reel1"
Mup: Upgraded package "MardiGras3"
MupQueue: Removed package "MardiGras3"
Mup: Upgraded package "MermaidsMillions1"
MupQueue: Removed package "MermaidsMillions1"
---------------------------------------------------------------------

It's still going, having only got as far as "M" after over a quarter of an hour. I estimate it will take around two hours to go all the way to "Z".
This seems to happen EVERY MONTH at the upgrade - it isn't just the new games, it is pretty much the whole damn casino that updates,

but WHY!

As the casino grows in size, the strain of this "secret" upgrade hits ever harder, and makes for more and more problems, even on new XP machines now!!!!


Nearly an hour now, so went back to look at casino, and it seems MG programers have a sense of humour after all:-

-------------------------------------------------------------------------------------------
Mup: Upgraded package "WhataHoot3"
MupQueue: Removed package "WhataHoot3"
Mup: Upgraded package "WhatOnEarth1"
MupQueue: Removed package "WhatOnEarth1"
GetProcAddress(0x63000000 [c:\windows\system\WININET.DLL], "InternetQueryOptionA") called from "c:\windows\system\MSHTML.DLL" at address 0x636A54E8 and returned 0x6301AAD3 by thread 1.
Mup:MupLimitBackground - Starting Rate Limited.GetProcAddress(0x63000000 [c:\windows\system\WININET.DLL], "IsUrlCacheEntryExpiredW") called from "c:\windows\system\MSHTML.DLL" at address 0x636A54E8 and returned 0x6305612B by thread 1.
Thread 25 started in "c:\windows\system\MSHTML.DLL" at address 0x63780662.
DllMain(0x78000000, DLL_THREAD_ATTACH, 0x00000000) in "c:\windows\system\MSVCRT.DLL" called by thread 25.
DllMain(0x78000000, DLL_THREAD_ATTACH, 0x00000000) in "c:\windows\system\MSVCRT.DLL" returned 1 (0x1) by thread 25.
DllMain(0x66800000, DLL_THREAD_ATTACH, 0x00000000) in "c:\windows\system\SHELL32.DLL" called by thread 25.
DllMain(0x66800000, DLL_THREAD_ATTACH, 0x00000000) in "c:\windows\system\SHELL32.DLL" returned 1 (0x1) by thread 25.
DllMain(0x65F00000, DLL_THREAD_ATTACH, 0x00000000) in "c:\windows\system\OLE32.DLL" called by thread 25.
DllMain(0x65F00000, DLL_THREAD_ATTACH, 0x00000000) in "c:\windows\system\OLE32.DLL" returned 1 (0x1) by thread 25.
DllMain(0x79E00000, DLL_THREAD_ATTACH, 0x00000000) in "c:\windows\system\MSOSS.DLL" called by thread 25.
DllMain(0x79E00000, DLL_THREAD_ATTACH, 0x00000000) in "c:\windows\system\MSOSS.DLL" returned 1 (0x1) by thread 25.
DllMain(0x70100000, DLL_THREAD_ATTACH, 0x00000000) in "c:\windows\system\RPCRT4.DLL" called by thread 25.
DllMain(0x70100000, DLL_THREAD_ATTACH, 0x00000000) in "c:\windows\system\RPCRT4.DLL" returned 1 (0x1) by thread 25.
DllMain(0x5CF00000, DLL_THREAD_ATTACH, 0x00000000) in "c:\windows\system\CRYPT32.DLL" called by thread 25.
DllMain(0x5CF00000, DLL_THREAD_ATTACH, 0x00000000) in "c:\windows\system\CRYPT32.DLL" returned 1 (0x1) by thread 25.
DllMain(0x65340000, DLL_THREAD_ATTACH, 0x00000000) in "c:\windows\system\OLEAUT32.DLL" called by thread 25.
DllMain(0x65340000, DLL_THREAD_ATTACH, 0x00000000) in "c:\windows\system\OLEAUT32.DLL" returned 1 (0x1) by thread 25.
DllMain(0x63000000, DLL_THREAD_ATTACH, 0x00000000) in "c:\windows\system\WININET.DLL" called by thread 25.
DllMain(0x63000000, DLL_THREAD_ATTACH, 0x00000000) in "c:\windows\system\WININET.DLL" returned 1 (0x1) by thread 25.
DllMain(0x76000000, DLL_THREAD_ATTACH, 0x00000000) in "c:\windows\system\WS2_32.DLL" called by thread 25.
DllMain(0x76000000, DLL_THREAD_ATTACH, 0x00000000) in "c:\windows\system\WS2_32.DLL" returned 1 (0x1) by thread 25.
DllMain(0x794D0000, DLL_THREAD_ATTACH, 0x00000000) in "c:\windows\system\MSWSOCK.DLL" called by thread 25.
DllMain(0x794D0000, DLL_THREAD_ATTACH, 0x00000000) in "c:\windows\system\MSWSOCK.DLL" returned 1 (0x1) by thread 25.
DllMain(0x75FA0000, DLL_THREAD_ATTACH, 0x00000000) in "c:\windows\system\WSOCK32.DLL" called by thread 25.
DllMain(0x75FA0000, DLL_THREAD_ATTACH, 0x00000000) in "c:\windows\system\WSOCK32.DLL" returned 1 (0x1) by thread 25.
DllMain(0x10400000, DLL_THREAD_ATTACH, 0x00000000) in "c:\program files\casinos\challengev2\MGSCOMMS.DLL" called by thread 25.
DllMain(0x10400000, DLL_THREAD_ATTACH, 0x00000000) in "c:\program files\casinos\challengev2\MGSCOMMS.DLL" returned 1 (0x1) by thread 25.
DllMain(0x10000000, DLL_THREAD_ATTACH, 0x00000000) in "c:\program files\casinos\challengev2\FDI.DLL" called by thread 25.
DllMain(0x10000000, DLL_THREAD_ATTACH, 0x00000000) in "c:\program files\casinos\challengev2\FDI.DLL" returned 1 (0x1) by thread 25.
DllMain(0x68400000, DLL_THREAD_ATTACH, 0x00000000) in "c:\program files\casinos\challengev2\VCLIENT.DLL" called by thread 25.
DllMain(0x68400000, DLL_THREAD_ATTACH, 0x00000000) in "c:\program files\casinos\challengev2\VCLIENT.DLL" returned 1 (0x1) by thread 25.
DllMain(0x1A400000, DLL_THREAD_ATTACH, 0x00000000) in "c:\windows\system\URLMON.DLL" called by thread 25.
DllMain(0x1A400000, DLL_THREAD_ATTACH, 0x00000000) in "c:\windows\system\URLMON.DLL" returned 1 (0x1) by thread 25.
DllMain(0x783C0000, DLL_THREAD_ATTACH, 0x00000000) in "c:\windows\system\RNR20.DLL" called by thread 25.
DllMain(0x783C0000, DLL_THREAD_ATTACH, 0x00000000) in "c:\windows\system\RNR20.DLL" returned 1 (0x1) by thread 25.
DllMain(0x7B410000, DLL_THREAD_ATTACH, 0x00000000) in "c:\windows\system\MSAFD.DLL" called by thread 25.
DllMain(0x7B410000, DLL_THREAD_ATTACH, 0x00000000) in "c:\windows\system\MSAFD.DLL" returned 1 (0x1) by thread 25.
DllMain(0x02B20000, DLL_THREAD_ATTACH, 0x00000000) in "c:\windows\system\MSIMG32.DLL" called by thread 25.
DllMain(0x02B20000, DLL_THREAD_ATTACH, 0x00000000) in "c:\windows\system\MSIMG32.DLL" returned 1 (0x1) by thread 25.
DllMain(0x7FBF0000, DLL_THREAD_ATTACH, 0x00000000) in "c:\windows\system\MPR.DLL" called by thread 25.
DllMain(0x7FBF0000, DLL_THREAD_ATTACH, 0x00000000) in "c:\windows\system\MPR.DLL" returned 1 (0x1) by thread 25.
DllMain(0x5EF80000, DLL_THREAD_ATTACH, 0x00000000) in "c:\windows\system\KSUSER.DLL" called by thread 25.
DllMain(0x5EF80000, DLL_THREAD_ATTACH, 0x00000000) in "c:\windows\system\KSUSER.DLL" returned 1 (0x1) by thread 25.
DllMain(0x77950000, DLL_THREAD_ATTACH, 0x00000000) in "c:\windows\system\WLDAP32.DLL" called by thread 25.
DllMain(0x77950000, DLL_THREAD_ATTACH, 0x00000000) in "c:\windows\system\WLDAP32.DLL" returned 1 (0x1) by thread 25.
DllMain(0x7ED00000, DLL_THREAD_ATTACH, 0x00000000) in "c:\windows\system\CRYPTNET.DLL" called by thread 25.
DllMain(0x7ED00000, DLL_THREAD_ATTACH, 0x00000000) in "c:\windows\system\CRYPTNET.DLL" returned 1 (0x1) by thread 25.
DllMain(0x63580000, DLL_THREAD_ATTACH, 0x00000000) in "c:\windows\system\MSHTML.DLL" called by thread 25.
DllMain(0x63580000, DLL_THREAD_ATTACH, 0x00000000) in "c:\windows\system\MSHTML.DLL" returned 1 (0x1) by thread 25.
DllMain(0x76F90000, DLL_THREAD_ATTACH, 0x00000000) in "c:\windows\system\JSCRIPT.DLL" called by thread 25.
DllMain(0x76F90000, DLL_THREAD_ATTACH, 0x00000000) in "c:\windows\system\JSCRIPT.DLL" returned 1 (0x1) by thread 25.
GetProcAddress(0xBFF70000 [c:\windows\system\KERNEL32.DLL], "CreateFiber") called from "c:\windows\system\MSHTML.DLL" at address 0x637CF3D4 and returned 0x84E9F298 by thread 25.
GetProcAddress(0xBFF70000 [c:\windows\system\KERNEL32.DLL], "DeleteFiber") called from "c:\windows\system\MSHTML.DLL" at address 0x637CF3E5 and returned 0x84E9F2A8 by thread 25.
GetProcAddress(0xBFF70000 [c:\windows\system\KERNEL32.DLL], "ConvertThreadToFiber") called from "c:\windows\system\MSHTML.DLL" at address 0x637CF3F6 and returned 0x84E9F2B8 by thread 25.
GetProcAddress(0xBFF70000 [c:\windows\system\KERNEL32.DLL], "SwitchToFiber") called from "c:\windows\system\MSHTML.DLL" at address 0x637CF407 and returned 0x84E9F2C8 by thread 25.
Mup:MupLimitBackground - Rate Limiting Disabled. Full Speed Ahoy!
Mup:MupLimitBackground - Rate Limiting Disabled. Full Speed Ahoy!Mup: Upgraded package "WheelofWealthSE1"
MupQueue: Removed package "WheelofWealthSE1"
Mup: Upgraded package "WinningWizards1"
MupQueue: Removed package "WinningWizards1"
---------------------------------------------------------------------------------------------------

[Marcie Mac]

Thanks for posting this - am glad to know it isn't my slow computer. I find myself logging in when I have no intentions to even play just to get the new games downloaded to keep my frustration level down when I have money to play and two hours later games are still sputtering along.

I did notice though that when the process is all said and done, I seem to hit a little more and am able to play a little longer with my money

Marcie

[Mousey]

Like Vinylweatherman, what I want to know is: What's up with updating all or most of the existing games every damn month??

Thanks for posting about the full casino updates, VWM, because at first, I thought I was seeing things when I caught Mermaids doing one of those sly background updates -- yet again. And I wish it was 'full speed ahoy' when the games download.... I'm on 1.5 mb DSL and it fairly flies along until I hit the MG updates, then everything bogs down, my system processor spikes up to 100% off and on -- so even leaving the casino DL'ing in the background bogs down my entire system.

Yes, yes, I'll get a new comp eventually, but I'm not sure that's the solution.

[vinylweatherman]

Thanks for posting this - am glad to know it isn't my slow computer. I find myself logging in when I have no intentions to even play just to get the new games downloaded to keep my frustration level down when I have money to play and two hours later games are still sputtering along.

I did notice though that when the process is all said and done, I seem to hit a little more and am able to play a little longer with my money

Marcie

It DID take 2 hours. After reaching "Z", it went aroud the alphabet again for some of the newer games, such as the "gold" series, and the new slots and multihand variants. In the end, the "mupQueue" stopped issuing logs, so I tried the casino, lo and behold, Double Magic loaded and ran pretty smoothly - no co-codamol needed

It looks like the casinos each need to be logged on for two to three hours each time there is an update. Unfortunately, MG have been updating two to three times per month recently.

Now that this has been exposed, MG will have to consider "coming clean" about this mass update that takes so long. Each time I have queried it, they have tried to dodge the question, resorting instead to blaming my PC, Internet connection, corrupt installation of casino (please reinstall the casino - as if that would make a difference).

I have more science to do later, I have to investigate why one casino stopped installing because my PC ran out of hard drive space, yet under "my computer" it shows 11Gigabytes remaining. Seriously, does the casino grab 11 Gigabytes of virtual memory - it looks that way, because on my XP machine I got a "virtual memory too low" error, despite the fact it has 2Gigabytes of RAM and a 200Gigabyte C: drive.
I suspect that the error involves the installer storing stuff in the Windows paging file, and then just leaving it there rather than deleting it when it moves on. Most new MG installations produce this error, characterised by the hard drive churning for ages as soon as the casino software is exited.

I hope some MG reps see this thread, these issues need looking at, and I am getting hard evidence that it is NOT my PC or the internet, but is the MG Viper client AGAIN that is responsible for all the problems.

[lojo]

Here's w-a-g... notice the difference in what is client and server in the files from before. I noticed this because I was hypothetically trying to 'replace' some graphics in fun mode. I think there is a vulnerability issue that they are working on. It could also be a malware security fix, but I don't think so.

Yeah I read the agreement, but once it's on my computer it is mine as long as I don't publish it.

If that doesn't get MG on the thread, nothing will

[vinylweatherman]

Here's w-a-g... notice the difference in what is client and server in the files from before. I noticed this because I was hypothetically trying to 'replace' some graphics in fun mode. I think there is a vulnerability issue that they are working on. It could also be a malware security fix, but I don't think so.

Yeah I read the agreement, but once it's on my computer it is mine as long as I don't publish it.

If that doesn't get MG on the thread, nothing will

Interesting theory about vulnerability or malware. Although every game generates this update log, other than the new games, the actual amount of information going through my cable modem is nothing like what it would be were the entire game being downloaded and installed from scratch. However, the time taken, and resources used, see to be the same as when the entire game downloads. It seems that attempting to use the PC causes this MUP Limiter to act, and letting the PC rest earns "full speed ahoy". Sadly, the limiter does not seem to work, surely it would ensure that the games did NOT spurt and splutter while being played. I have further noticed something. Old games that have NOT been "secretly updated" are blocked from being launched, even though they are shown as playable. The launch screen freezes, and will not load the game from the hard drive. I am forced to cancel the process, at which point control returns to the lobby, which briefly freezes, the graphic to the right for the game is replaced by the default holding image, the game then flashed red and updates again - with the progress bar quickly moving to completion. At this point, the game will launch properly.

Perhaps there really WAS a vulnerability, all this started in November, just after the debacle over at Mini Vegas over "illegitimate play", being neither bonus abuse, player fraud, or a scam.
I always thought that the client served only to display the results of a game, and handle requests for a spin or deal. Perhaps there were vulnerable files stored locally that could somehow influence the outcome of what is supposed to be RANDOM, and resolved on the server.

Altering the graphics locally COULD be used, however, to generate a fake screenshot of a supposed big win that would stand up to scrutiny against "photoshopping". Terms usually state that records held on the server will determine the argument in such cases, but perhaps this might be where one of the vulnerabilities may lie.

With this in mind, it could be that the old game updates are files containing checksum data, which the CPU then laboriously checks against the local files, with a discrepancy causing the whole game to be reinstalled. This would explain a small download yet massive CPU loading for two or three hours on some machines.

My new PC is more able to cope, it has TWO Athlon64 cores, one can handle a McAfee virus scan while the other will still spin 5-Reel Drive at 3800 spins per hour!
I set it to simultaneously install FOUR new MG casinos from scratch. It almost made it too!! It issued a virtual memory error, and ditched one of the four casinos, which will not launch. The other three are fine. It was all done in a couple of hours too! Conversly, on this old PC, it took over TWELVE hours to fully install Bella Vegas from scratch, and still missed of "Glory of Rome".

Forget official minimum requirements, heed this:-

Vinyl Minimum spec for running MG casinos.

Intel or Athlon dual core processor 2 Ghz per core and above.
At least 2 Gig RAM, preferably 4Gig
3 Gigabytes of hard drive per MG casino you intend to use (leaves room for everything else and future proofing at 6 new games per month).
Separate Graphics card, NOT "on board chipset"
32 10-500 CoCodamol (if not running dual core processor, or more than 10 casinos)
19" Widescreen Monitor (up to two MG casinos simultaneously, or 24" 1900x1200 for 4+ simultaneous MG casinos).

Optional - second monitor for scoreboard if playing in casino tournaments. Second PC if wanting to do anything else during the 1 week spent updating all the casinos.



As for replacing the graphics and sound - it can still be done, the files have moved.
Sounds are usually MP3 or WAV files, and graphics are bitmaps stored in DAT files.

A new vulnerability has been introduced that did not exist before*, but it is only useful for the sport of "bonus abuse", or for taking part in tournaments based on "who can wager the most".

"Tweaks" are also possible to increase slightly the spin rates on the newer slots such as "Munchkins". It is also possible to "tweak" these to allow the "stop on..." variants available in the older "Thunderstruck" slots, such as "Stop on .. balance increase/reduce by", a responsible gambling feature curiously absent from newer slots, which will play till either the feature hits, or you bust out.






* - Our old friend "Classic Blackjack" - full of damn display bugs as widely reported here, such as 10 Foot high stack of chips, Aces that are NOT "Aces" etc.
Vulnerability involves the game getting jammed into "Expert Mode", with no means of switching back to "Regular Mode". In this state, it plays to the incorrect strategy of "European Blackjack", but at least knows when the "Ace of Spades" is something else

Cause? (theory follows) The game is equipped for "Autoplay", however by local implemetation it is normally excluded, and no strategy table is supplied. European is the default strategy table for all Blackjack games that lack their own strategy table, of which there is currently only the one - Classic Blackjack. Since all Blackjack games use the same "engine", Expert Mode is possible in them all.

[lojo]

Boggle! I'm hungover, I need a brain IV to ingest all that

Wow, I like your system, I thought I had it going on with projectors and surround sound... multi/systems-monitors, yeah.

Altering the graphics locally COULD be used, however, to generate a fake screenshot of a supposed big win that would stand up to scrutiny against "photoshopping". Terms usually state that records held on the server will determine the argument in such cases, but perhaps this might be where one of the vulnerabilities may lie.

Of course a screenshot means nothing to the data. I had a dispute on mermaids millions once and the playcheck didn't match my memory, but that was once, and probably my state of mind. I'm guessing they generate the images to match the datum. But I still kind of think that the game image and data were off kilter as a glitch, but i won't beleagure the point. Probably a brainfart.

With this in mind, it could be that the old game updates are files containing checksum data, which the CPU then laboriously checks against the local files, with a discrepancy causing the whole game to be reinstalled. This would explain a small download yet massive CPU loading for two or three hours on some machines

Makes the most sense to me so far.

[Simmo!]

I did my first fresh install of an MG casino for a while last week (Intertops). Slots are pretty much unplayable for a good 2/3 hours after install while it downloads all the games. That's on a 2.8Gig Athlon/512Mb Ram PC and on a SCSI drive. I just wonder how many players start to play and think "this is crap" not realising why the reels are stalling, uninstall and move on.

Not looking forward to doing that again. By contrast, I re-installed Club On The Park (Playtech) and it was a breeze.

[Nifty29]

This kind of thing really grates my gears

Its time for MG to allow the user to decide what they want to download - or at least allow you to choose which games you want to install with the original package (like crypto).

In the end, the "mupQueue" stopped issuing logs

Hmmm....interesting Vinyl....does that have something to do with Simmo and his toilet habits...??

[tennis_balls]

all my MG casinos continue to run smoothly on my Commodore 64.