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]

Ages

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]

Theory

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.

 

[vinylweatherman]

Another problem

Science exercise 2.

My second experiment was allowing the remainder of "Roadhouse Reels" to install.

I observed disk usage in this case. During the near two hour process, the Windows Paging file grew steadily from 57 Megabytes to a whopping 323 Megabytes. Closing the casino software resulted in a brief churning of the hard drive, and the contraction of the paging file back to the starting point of 57 Megabytes.

Given the long period of drive churning after some installs, this looks like another mystery busted, the one about the "virtual memory is low" message that appears on XP machines. The installer DOES seem to fill the paging file (Windows virtual memory) as it goes along, but fails to clean up after itself until the application is closed, or the PC crashes under the sheer strain.

It is likely that the hard drive error is due to an install making the paging file so big it takes up all the remaining space on the hard drive, causing the PC to crash, yet on reboot it resets the paging file, removing the "evidence" of the cause of the problem. This is back to our old friend, the Microgaming "memory leak". Naturally, if all the system RAM has been used up, and the paging file expanding, other parts of the OS, and other applications being used will slow down or seize, since no RAM is available any longer and all memory requests have to be satisfied through the paging file on the drive, which is a lot less efficient (read SLOWER) for an application to do.

 

[Nifty29]

Well Im looking at loading up another MG today - I'd better send for some more vacuum tubes.....

 

[EasyRhino]

I once had three different MG casinos (fairly newly installed), running lengthy autoplay sessions at the same time.

I ran out of RAM and virtual memory, and my computer crashed.

Now I know why!

I think someone at Microgaming needs to take a class in memory management. Or maybe they should stop programming in COBOL.

 

[Simmo!]

I ran out of RAM and virtual memory, and my computer crashed.

That happened to me too last week on my install now you come to mention it. Trying to play and install at the same time I think was the issue.

 

[dealer wins]

Note to self. Only play MG casinos using the no-download flash version.

On second thoughts vote with my feet and go somewhere that doesnt take the p$ss with slow and huge bloatware.

2 hours to update an online casino is quite frankly laughable, I have re-installed XP quicker than that!!!

 

[vinylweatherman]

All Slots

My attention has turned to All Slots.

This is the only MG casino to use the next generation Viper Lobby, and every time I used it, my OS crashed after exiting the casino, even though the casino worked fine. Worse, Windows cannot shut down and the display is f****d!!!!

I have been able to grab the exit process from All Slots, before the system crashed, and here is the bug!!

--------------------------------------------------------------------
00:38:53.226: Mup: Upgraded package "TheHighLife1" (en)
00:38:53.237: MupQueue: Removed package "TheHighLife1" (en)
00:56:42.328: Thread 7 exited with code 0 (0x0).
00:56:42.356: DllMain(0x69000000, DLL_PROCESS_DETACH, 0x00000000) in "c:\windows\system\macromed\common\SWSUPPORT.DLL" called by thread 1.
00:56:42.362: DllMain(0x69000000, DLL_PROCESS_DETACH, 0x00000000) in "c:\windows\system\macromed\common\SWSUPPORT.DLL" returned 1 (0x1) by thread 1.
00:56:42.367: Unloaded "c:\windows\system\macromed\common\SWSUPPORT.DLL" at address 0x69000000 by thread 1.
00:56:42.504: DllMain(0x66600000, DLL_PROCESS_DETACH, 0x00000000) in "c:\program files\casinos\allslots\global\menu\MENUCORE.DLL" called by thread 1.
00:56:42.516: DllMain(0x66600000, DLL_PROCESS_DETACH, 0x00000000) in "c:\program files\casinos\allslots\global\menu\MENUCORE.DLL" returned 1 (0x1) by thread 1.
00:56:42.521: Second chance exception 0xC0000005 (Access Violation) occurred in "c:\program files\casinos\allslots\MSS32.DLL" at address 0x211014E0 by thread 5.00:56:42.529: Unloaded "c:\program files\casinos\allslots\global\menu\MENUCORE.DLL" at address 0x66600000 by thread 1.
00:56:42.534: Thread 5 exited with code -1 (0xFFFFFFFF).
00:56:42.540: Thread 6 exited with code -1 (0xFFFFFFFF).
00:56:42.545: Thread 13 exited with code -1 (0xFFFFFFFF).
00:56:42.550: Thread 8 exited with code -1 (0xFFFFFFFF).
00:56:42.556: Thread 9 exited with code -1 (0xFFFFFFFF).
00:56:42.562: Thread 14 exited with code -1 (0xFFFFFFFF).
00:56:42.630: Unloaded "c:\program files\logitech\mouseware\system\LGWNDHK.DLL" at address 0x017D0000 by thread 1.
00:56:42.969: Thread 1 exited with code -1 (0xFFFFFFFF).
00:56:43.020: Exited "c:\program files\casinos\allslots\CASINOGAME.EXE" (process 0xFFE32887) with code -1 (0xFFFFFFFF) by thread 3.
-----------------------------------------------------------------------

I have highlighted it. It happens as the lobby menu core is unloaded, and is what is known as a "second chance exception", which means the software has not trapped the initial error appropriately, and the program has effectively failed. Worse, it is an access violation, a technical term for the program having performed an operation (probably a write) into an area of RAM that was not allocated to it. Whatever this WAS allocated to has been corrupted as the casino unloaded, and was most likely part of the OS dealing with the display/desktop and/or the windows shutdown process.

It could be a compatability problem with some other part of the PC. I have noticed that the casino has used one of the library files for my mouse, which is a corded USB optical mouse from Logitech.


UPDATE

MSS32.DLL contains the library for the "Miles Sound System". It is version 6.5a, which is the same as All Jackpots, which does not have the same problem. This looks like the Miles Sound System has an issue with the new lobby upgrade at All Slots. I presume this is the sound system that renders all the game sounds. I have found on other occasions that the casino launches with the sound not working, so perhaps the incompatability has always been around, but is more serious with the upgrade.

 

[lojo]

I wonder if they are presenting different versions to different countries? My home computer has allslots, and it was a quick and seemless download 1.5mm.
I run alljackpots on my system at work (two T1's so download was negligable)

It seems some systems handle the program and some don't? I followed you when the new lobby came out. My system hung on the initial (uninvited) download, but I uninstalled, cleaned my registry, downloaded, and all has been fine since.

If CCleaner doesn't do me I use bcwipe to clean up all fileslack, etc.

Good luck

 

[vinylweatherman]

Experiment

I wonder if they are presenting different versions to different countries? My home computer has allslots, and it was a quick and seemless download 1.5mm.
I run alljackpots on my system at work (two T1's so download was negligable)

It seems some systems handle the program and some don't? I followed you when the new lobby came out. My system hung on the initial (uninvited) download, but I uninstalled, cleaned my registry, downloaded, and all has been fine since.

If CCleaner doesn't do me I use bcwipe to clean up all fileslack, etc.

Good luck

That is my next All Slots experiment once I have demonstrated that this problems persits on further launches rather than having been detected and fixed by the upgrade.

All slots have replied to this issue (I have been feeding them the results too), and have insisted that the old games do not update every month. Technically this is correct, however presentation to the user indicates otherwise (CPU near 100% and choppy games for 2 hours+)

Their first responce to the other issues was to blame my PC as per usual. If MG upgrades are so damn good, why do MG casinos keep getting corruptly updated requiring all this fixing

I'll be b******d if I am going to install All Slots on the other PC till I am sure it isn't going to suffer the same fate (although I will at least be able to use "system restore" as a last resort).

 

[Rusty]

Excellent thread VW and this subject keeps popping up in one guise or another on this forum.

These updates take far too long
Performance is unacceptable while updating
The updates can cause system instability
There is STILL no option to download only the games you want.
Existing software is updated for no obvious or transparent reason.

MG it is time you listened!
I am sick of shouting!!
Get it sorted!!!

As has been said this must cost them a lot of new business because I am sure that if todays MG casinos were my first experience of online gaming I would be totally turned off by it.

did I say

SORT IT OUT!!!!!!!!!!

 

[vinylweatherman]

Work

I am off down the local supermarket.

All this hard work has given me an attack of the Munchkins

 

[Rusty]

But you only have one mouse and Two hands?

 

[vinylweatherman]

Bonus Mouse

But you only have one mouse and Two hands?

I only need the mouse for the bonus rounds

With barely any Americans able to deposit, and little interest this side of the pond, these tournaments are a real +EV opportunity.

Naturally, I am doing a serious investigation here!


I have found that when we get the "disconnect" problem it affects all three casinos simultaneously - and for the same length of time, not just one or two. So far, I have had the reels spinning endlessly for long periods, but with all three recovering the signal at once!
Not certain what this means, but ALL the servers for these three are in Kawanake, so it rules out the problem as being the individual casino servers.
Further experiments will determine if this is a purely Kawanake problem, or closer to home. I will do this by running an MG whose server is elsewhere alongside these three. First, I need to find an MG that fits (I have no money in 32Red, and I busted out at RiverBelle - so these candidates are out).


For my second absolutely dead serious investigation, I am playing at 0.45, 0.30, and 0.15 per spin. At 0.15 per spin, I am some 70 AHEAD, with constant decent bonus rounds relative to the tiny stake. At 0.30 and 0.45 I am down. While I have had by far the best retrigger rate at 0.30, the net payouts constantly disappoint. even at 100+ spins after retriggers I have barely managed over 150x bet - I even hit the 5 scatters! While variance comes into play, after several thousand spins I would expect short term variance to have eroded my gains at 0.15 per spin, but not so this session. This is running a consistent long term positive streak, rather than a couple of massive hits boosting the balance as might be expected in a good session at the slots.

 

[vinylweatherman]

Todays lesson

Today, it was back to the painful "update" process.

I changed the settings so I could log the times, and set about upgrading Platinum Play.

Sure enough, every single game, old and new was added to "MUP Queue" for potential update.

After the preamble, double launch, movie etc, its down to business:-

00:11:31.130: DllMain(0x78000000, DLL_THREAD_DETACH, 0x00000000) in "c:\windows\system\MSVCRT.DLL" returned 1 (0x1) by thread 0xFFE495E1.
00:11:31.135: Thread 0xFFE495E1 exited with code 0 (0x0).
00:12:03.573: Mup: Upgraded package "AcesandEights1"
00:12:03.582: MupQueue: Removed package "AcesandEights1"
00:13:23.019: Mup: Upgraded package "AcesandFaces100Play1"
00:13:23.028: MupQueue: Removed package "AcesandFaces100Play1"
00:14:19.830: Mup: Upgraded package "AcesandFaces50Play1"
00:14:19.838: MupQueue: Removed package "AcesandFaces50Play1"

........ and so on. The time stamps are in HOUR:MIN:SEC:MilliSEC

12 Minutes into launch, the casino begins the update process. At this point, it would likely be near unplayable, and most games would refuse to launch as they had not been processed.
Eventually, (and I don't use the term lightly )
the process reaches the four new games...

04:30:54.062: Mup: Upgraded package "SantaPaws1"
04:30:54.071: MupQueue: Removed package "SantaPaws1"
04:32:55.522: Mup: Upgraded package "GoldSeries_MHPontoon2"
04:32:55.536: MupQueue: Removed package "GoldSeries_MHPontoon2"
04:35:55.628: Mup: Upgraded package "MagicSpell1"
04:35:55.640: MupQueue: Removed package "MagicSpell1"
04:37:07.393: Mup: Upgraded package "BonusPoker100Play1"
04:37:07.404: MupQueue: Removed package "BonusPoker100Play1"
04:38:09.016: Mup: Upgraded package "BonusPoker50Play1"
04:38:09.030: MupQueue: Removed package "BonusPoker50Play1"
04:41:26.320: Mup: Upgraded package "PorkyPayout1"
04:41:26.333: MupQueue: Removed package "PorkyPayout1"
04:43:57.895: Mup: Upgraded package "TheHighLife1"
04:43:57.909: MupQueue: Removed package "TheHighLife1"


YES, that's right Four and a half HOURS

It is only at 4 Hours and 37 minutes that the casual player would even see any obvious sign of progress, which would be the progress bar on the new "Bonus Poker 100 play" game starting the journey.

Despite all MG casinos now undergoing an identical process, why nearly 5 Hours in this case, while others manage it in two (which is still far too long).
If, as claimed by various CS, it is not "updating", what is the big delay?

Surely, it would be better to have an "offline upgrade" option similar to the option in Cryptologic casinos, where the upgrade/verification files could be retrieved for all 150+ games at a stroke, and processed with much greater haste locally.

Perhaps there is a way to disable this painful process, and delay it till one is ready to have the PC out of action for hours at a time per casino.

 

[Mousey]

Today, it was back to the painful "update" process.

........

YES, that's right Four and a half HOURS

It is only at 4 Hours and 37 minutes that the casual player would even see any obvious sign of progress, which would be the progress bar on the new "Bonus Poker 100 play" game starting the journey.

Despite all MG casinos now undergoing an identical process, why nearly 5 Hours in this case, while others manage it in two (which is still far too long).
If, as claimed by various CS, it is not "updating", what is the big delay?
. .....

Exactly! If only the new games are actually updating, then what the devil is MG doing for four freakin' hours in our computers?? And if most or all games are receiving almost monthly updates -- why? You'd think it's got to be more than just a bit of maintenance or tidying up as all games wouldn't require such repeated attention.

I'm enjoying your posts on this VWM. Thanks for taking the time (and patience) to do this.

 

[vinylweatherman]

Pain

Exactly! If only the new games are actually updating, then what the devil is MG doing for four freakin' hours in our computers?? And if most or all games are receiving almost monthly updates -- why? You'd think it's got to be more than just a bit of maintenance or tidying up as all games wouldn't require such repeated attention.

I'm enjoying your posts on this VWM. Thanks for taking the time (and patience) to do this.

It does seem to vary. All Slots managed to log this all in a mere half an hour. It seems the delay may be at the Microgaming end in the case of the 5 hour upgrade. The whole log shows gaps of 2 to 3 minutes between each package verifying or updating, and it is likely that the casino really IS "sitting around doing sod all" while we fume at unresponsive games and buggy software.

Certainly, the All Slots log shows the difference between "checking the packages" and "updating".
Take this snippet for example:-

00:13:34.056: Mup: Upgraded package "FunHouse8" (en)
00:13:34.065: MupQueue: Removed package "FunHouse8" (en)
00:13:36.065: Mup: Upgraded package "GeniesGems2" (en)
00:13:36.074: MupQueue: Removed package "GeniesGems2" (en)
00:13:43.950: Mup: Downloaded: "http://allslots.mgsmup.com/viper/allslots/00031227.cab"
00:13:44.125: Mup: Upgraded package "GGCrazyChameleons1" (en)
00:13:44.134: MupQueue: Removed package "GGCrazyChameleons1" (en)
00:13:46.729: Mup: Upgraded package "GGGeniesGems1" (en)
00:13:46.739: MupQueue: Removed package "GGGeniesGems1" (en)

Notice how 00031227.cab slips in, this is an UPDATE for the Golden Goose variant of "Crazy Chameleons". Are we now going to see this one "tighten up" this month?? All speculation, but this log shows a number of the "old" games receiving updates, but by no means all of them - most are just checked, a process that still takes a golden age. In the above example, Golden Goose "Genies Gems" just gets the "once over" and is passed as up to date.

The $64,000 question, What changed in GG Crazy Chameleons this month?

The (en) at the end appears to be the language packs, Microgaming now support multiple languages, chosen in the lobby by the player, or detected by inspecting the PC.


This little utility is great, it lets me know when my casino is really done, so I don't try to play it while it is "underdone" and end up falling ill