Active Threads | Active Posts | Unanswered Today | Since Yesterday | This Week
MAME
12/14/18 06:18 PM
Guys, unbelievably the issue is solved 1 day after joining this awesome MAME forum, when I had no clue how to fix it for months.

I spent the whole day so far trying out ALL of your potential solutions which led me to the actual solution at the end (all credit goes to you guys, I want you to know that). You all were really so very helpful, what a community! I went to Device Drivers on Windows 10 and started testing and uninstalling each driver one by one. There was one Logitech driver that was the culprit among all my other Logitech drivers. After I uninstalled it MAME64 0.202 works perfectly now.

My exuberance is more relief after these months of it freezing on initialization of roms. It must have clashed with some MAME64 0.172 and above code when the Dev team put something into that patch, since it didn't affect the loading of ROMs for MAME64 0.171 and below. Thank God I did not have to reformat, which was suggested by someone else, elsewhere, and would have been my last resort to be honest.

I will now upgrade to the latest MAME64 0.204 for testing. I will then most likely acquire a drive with Hyperspin as the front end since I know the newest MAME64 now works on my system, I have all the roms for 0.202 and could attempt to do it myself but that seems like weeks/months of work and I really want Hyperspin working out of the box. I don't really want to learn the whole Hyperspin interface and then program each game to work right and add artwork, seems like a steep learning curve. So acquiring a drive online I believe is the way to go for me, I have seen some people selling them online.

I may start a new thread soon and ask you guys what settings you use for the newest MAME like video drivers, etc. that stuff really interest me and this has opened up the latest MAME to me now. I Hope this whole thread can help someone else out in the future in my predicament and again thank you all for your quick assistance, this community rocks!
13 355 Read More
MAME
12/14/18 01:42 PM
win32 as Vas suggested is most compatible. dinput frequently has trouble with these weird software key injectors too.
13 355 Read More
MAME
12/14/18 11:17 AM
I saw on another forum that "-keyboardprovider dinput" might do something.
13 355 Read More
MAME
12/14/18 04:50 AM
Virtual keyboards aren't necessarily a problem, provided you know where they come from and the driver that provides them is working correctly. For example, my workstation has two virtual keyboards: one is provided by the Wacom tablet driver, and one is provided by the Logitech mouse driver. They're needed so that tablet or mouse inputs mapped to keyboard combinations/macros work correctly with applications and games that read keyboard(s) using RawInput or HID APIs. These two virtual keyboards don't cause a problem with MAME on my system. If you don't know where your virtual keyboards are coming from, you probably have a problem though (maybe something not uninstalled properly).

You can try changing the keyboard input module and see if it changes the behaviour - if it's really a problem with the keyboards this will likely fix it. Add "-keyboardprovider win32" to the command line (without the quotes) and see whether the behaviour changes.

Some people have reported trouble with certain sound drivers with MAME on Windows. Can you try adding "-sound none" (without the quotes) to your command line to completely disable audio output? If that changes the behaviour it could be a sound driver issue, and you can try reinstalling your sound drivers or using a different MAME sound output module (xaudio2, dsound or portaudio).

You could try running with different video modules, too - try "-video opengl" or "-video bgfx" (without the quotes) and see if anything changes. Sometimes DirectX 9 drivers are problematic, but OpenGL drivers or the DirectX 11 drivers used by BGFX work better.
13 355 Read More
MAME
12/13/18 11:02 PM
Yep, checking out the vjoy next! I want to solve this so bad, I tried another emulator that works for the roms called FB Alpha but i like MAME and determined to fix this freezing.
13 355 Read More
MAME
12/13/18 10:37 PM
yeah, there are some situations where you end up with multiple ones, although I have plugged / unplugged a lot of things into this box over the years and it's still fairly clean. I'd still look into that vjoy thing tho, I have heard of such software causing issues (and any remote desktop software etc. if you happen to be running that) a lot of them use dodgy drivers which can end up hanging
13 355 Read More
MAME
12/13/18 10:35 PM
I went to another forum and someone said this about 5 keyboards listed in Device Manager (Like in my log in the above post). Here's what that gent said:

"It's quite normal to have multiple HIDs under Windows...

A human interface device or HID is a type of computer device that interacts directly with, and most often takes input from, humans and may deliver output to humans.

USB Ports will also add to that list, even if currently unused.

Plugging in and removing devices such as your iPod, iPhone, Camera, and external HDD, etc. Or moving your keyboard/mouse from one port to another, etc. Perhaps you plug the device into USB port 1, then next time USB port 2, etc. You find they get created and merely stick around afterwards. However, they don't affect the system and should be left there. Most are there for future functions to work and be accessed faster for the same driver."

The 4 displays (3 monitors, one TV) I do have so that explains that. So I guess I can eliminate those two things causing the freezes.
13 355 Read More
MAME
12/13/18 10:03 PM
Wow, you're right, that is really weird for the keyboard. As far as the displays it is correct, I have 3 monitors and one TV for a total of 4 displays. The weird part about that is it says my primary display is #1 when my primary is actually #2 display as far as Windows 10 goes, not sure how MAME arranges them. I'll check out those leads and see if anyone else see's a problem. Thanks.
13 355 Read More
MAME
12/13/18 09:57 PM
the most suspicious things in there are those 'vjoy' devices, could be some incompatibility with that software.

the entire input section of your verbose output looks kinda screwy eg. on my machine I get a nice clean

Input: Adding keyboard #0: HID Keyboard Device (device id: \\?\HID#VID_045E&PID_0750&MI_00#8&2475c9ea&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding mouse #0: Microsoft USB Wheel Mouse Optical (device id: \\?\HID#VID_045E&PID_0040#7&a152a8d&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding lightgun #0: Microsoft USB Wheel Mouse Optical (device id: \\?\HID#VID_045E&PID_0040#7&a152a8d&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd})

and nothing more

yet your machine is reporting 5 keyboards, mostly dupes, some 'WmVirtualDevice' things, 'vjoy' etc...

I strongly suspect it'll come down to something like that.

I'd advise finding a way to fully uninstall that 'vjoy' thing at least as a starting point.

it also seems to be reporting 4 displays, which is a bit odd...

13 355 Read More
MAME
12/13/18 09:34 PM
Thanks for taking a look.

Microsoft Windows [Version 10.0.17134.471]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>cd..

C:\Windows>cd..

C:\>cd mame202

C:\mame202>mame64.exe Scramble -verbose
Video: Monitor 65537 = "\\.\DISPLAY1" (primary)
Video: Monitor 65539 = "\\.\DISPLAY2"
Video: Monitor 65541 = "\\.\DISPLAY3"
Video: Monitor 65543 = "\\.\DISPLAY4"
Direct3D: Using Direct3D 9
Physical width 1063, height 1440
Direct3D: Initialize
Direct3D: Configuring adapter #0 = NVIDIA GeForce GTX 980 Ti
RawInput: APIs detected
RawInput: APIs detected
RawInput: APIs detected
DirectSound: Primary buffer: 48000 Hz, 16 bits, 2 channels
Input: Adding keyboard #0: HID Keyboard Device (device id: \\?\HID#VID_1A2C&PID_3D43&MI_01&Col05#7&118eb48c&0&0004#{884b96c3-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding keyboard #1: HID Keyboard Device (device id: \\?\HID#VID_1A2C&PID_3D43&MI_01&Col06#7&118eb48c&0&0005#{884b96c3-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding keyboard #2: HID Keyboard Device (device id: \\?\HID#VID_1A2C&PID_3D43&MI_00#7&3565f24e&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding keyboard #3: HID Keyboard Device (device id: \\?\HID#VID_1A2C&PID_3D43&MI_01&Col04#7&118eb48c&0&0003#{884b96c3-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding keyboard #4: HID Keyboard Device (device id: \\?\HID#WmVirtualDevice#2&25d493e&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding mouse #0: ELECOM USB Mouse (device id: \\?\HID#VID_093A&PID_2521#6&9c61094&1&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding mouse #1: HID-compliant mouse (device id: \\?\HID#WmVirtualDevice#2&2b3e62a0&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding lightgun #0: ELECOM USB Mouse (device id: \\?\HID#VID_093A&PID_2521#6&9c61094&1&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding lightgun #1: HID-compliant mouse (device id: \\?\HID#WmVirtualDevice#2&2b3e62a0&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding joystick #0: vJoy Device (device id: vJoy Device product_bead1234-0000-0000-0000-504944564944 instance_079b95d0-1bce-11e8-8002-444553540000)
Input: Adding joystick #1: vJoy Device (device id: vJoy Device product_bead1234-0000-0000-0000-504944564944 instance_079b95d0-1bce-11e8-8004-444553540000)
Input: Adding joystick #2: vJoy Device (device id: vJoy Device product_bead1234-0000-0000-0000-504944564944 instance_079bbce0-1bce-11e8-8006-444553540000)
Input: Adding joystick #3: vJoy Device (device id: vJoy Device product_bead1234-0000-0000-0000-504944564944 instance_079be3f0-1bce-11e8-8008-444553540000)
Direct3D: Using dynamic textures
Direct3D: YUV format = RGB
Direct3D: Max texture size = 16384x16384
Direct3D: Device created at 1045x1393
Direct3D: Initialize HLSL
Direct3D: First store options
Direct3D: HLSL initialized
Region ':maincpu' created
unzip: opened archive file roms\scramble.zip
unzip: found roms\scramble.zip ECD
unzip: roms\scramble.zip has no ZIP64 ECD locator
unzip: read roms\scramble.zip central directory
unzip: closing archive file roms\scramble.zip and sending to cache
unzip: found roms\scramble.zip in cache
unzip: opened archive file roms\scramble.zip
unzip: closing archive file roms\scramble.zip and sending to cache
unzip: found roms\scramble.zip in cache
unzip: opened archive file roms\scramble.zip
unzip: closing archive file roms\scramble.zip and sending to cache
unzip: found roms\scramble.zip in cache
unzip: opened archive file roms\scramble.zip
unzip: closing archive file roms\scramble.zip and sending to cache
unzip: found roms\scramble.zip in cache
unzip: opened archive file roms\scramble.zip
unzip: closing archive file roms\scramble.zip and sending to cache
unzip: found roms\scramble.zip in cache
unzip: opened archive file roms\scramble.zip
unzip: closing archive file roms\scramble.zip and sending to cache
unzip: found roms\scramble.zip in cache
unzip: opened archive file roms\scramble.zip
unzip: closing archive file roms\scramble.zip and sending to cache
unzip: found roms\scramble.zip in cache
unzip: opened archive file roms\scramble.zip
unzip: closing archive file roms\scramble.zip and sending to cache
Region ':audiocpu' created
unzip: found roms\scramble.zip in cache
unzip: opened archive file roms\scramble.zip
unzip: closing archive file roms\scramble.zip and sending to cache
unzip: found roms\scramble.zip in cache
unzip: opened archive file roms\scramble.zip
unzip: closing archive file roms\scramble.zip and sending to cache
unzip: found roms\scramble.zip in cache
unzip: opened archive file roms\scramble.zip
unzip: closing archive file roms\scramble.zip and sending to cache
Region ':gfx1' created
unzip: found roms\scramble.zip in cache
unzip: opened archive file roms\scramble.zip
unzip: closing archive file roms\scramble.zip and sending to cache
unzip: found roms\scramble.zip in cache
unzip: opened archive file roms\scramble.zip
unzip: closing archive file roms\scramble.zip and sending to cache
Region ':proms' created
unzip: found roms\scramble.zip in cache
unzip: opened archive file roms\scramble.zip
unzip: closing archive file roms\scramble.zip and sending to cache
Optional shared pointer ':decrypted_opcodes' not found
Optional I/O port ':IN2_GAME9' not found
Optional I/O port ':IN2_GAME8' not found
Optional I/O port ':IN2_GAME7' not found
Optional I/O port ':IN2_GAME6' not found
Optional I/O port ':IN2_GAME5' not found
Optional I/O port ':IN2_GAME4' not found
Optional I/O port ':IN2_GAME3' not found
Optional I/O port ':IN2_GAME2' not found
Optional I/O port ':IN2_GAME1' not found
Optional I/O port ':IN2_GAME0' not found
Optional I/O port ':FAKE_SELECT' not found
Optional device ':ppi8255_2' not found
Optional device ':digitalker' not found
Optional device ':cclimber_audio:aysnd' not found
Optional device ':8910.2' not found
Optional device ':dac' not found
Optional device ':audio2' not found
Optional device ':maincpu:finder_dummy_tag' not found
Optional device ':maincpu:finder_dummy_tag' not found
Optional device ':maincpu:finder_dummy_tag' not found
Optional memory region ':palette:finder_dummy_tag' not found
Optional device ':screen:finder_dummy_tag' not found
Optional device ':screen:finder_dummy_tag' not found
Optional device ':ppi8255_0:finder_dummy_tag' not found
Optional device ':ppi8255_0:finder_dummy_tag' not found
Optional device ':ppi8255_0:finder_dummy_tag' not found
Optional device ':ppi8255_0:finder_dummy_tag' not found
Optional device ':ppi8255_0:finder_dummy_tag' not found
Optional device ':ppi8255_0:finder_dummy_tag' not found
Optional device ':ppi8255_0:finder_dummy_tag' not found
Optional device ':ppi8255_0:finder_dummy_tag' not found
Optional device ':ppi8255_1:finder_dummy_tag' not found
Optional device ':ppi8255_1:finder_dummy_tag' not found
Optional device ':ppi8255_1:finder_dummy_tag' not found
Optional device ':ppi8255_1:finder_dummy_tag' not found
Optional device ':ppi8255_1:finder_dummy_tag' not found
Optional device ':ppi8255_1:finder_dummy_tag' not found
Optional device ':ppi8255_1:finder_dummy_tag' not found
Optional device ':ppi8255_1:finder_dummy_tag' not found
Optional device ':audiocpu:finder_dummy_tag' not found
Optional device ':audiocpu:finder_dummy_tag' not found
Optional device ':audiocpu:finder_dummy_tag' not found
Optional device ':soundlatch:finder_dummy_tag' not found
Optional device ':8910.0:finder_dummy_tag' not found
Optional device ':8910.0:finder_dummy_tag' not found
Optional device ':8910.0:finder_dummy_tag' not found
Optional device ':8910.0:finder_dummy_tag' not found
Optional device ':8910.1:finder_dummy_tag' not found
Optional device ':8910.1:finder_dummy_tag' not found
Optional device ':8910.1:finder_dummy_tag' not found
Optional device ':8910.1:finder_dummy_tag' not found
Starting Scramble ':'
(missing dependencies; rescheduling)
Starting Zilog Z80 ':maincpu'
Starting Watchdog Timer ':watchdog'
Starting gfxdecode ':gfxdecode'
Starting palette ':palette'
Starting Video Screen ':screen'
Starting Speaker ':speaker'
(missing dependencies; rescheduling)
Starting Intel 8255 PPI ':ppi8255_0'
Starting Intel 8255 PPI ':ppi8255_1'
Starting Zilog Z80 ':audiocpu'
Starting Generic 8-bit latch ':soundlatch'
Starting AY-3-8910A PSG ':8910.0'
Starting AY-3-8910A PSG ':8910.1'
Starting Discrete Sound ':konami'
Starting Timer ':stars'
Starting Scramble ':'
(missing dependencies; rescheduling)
Starting Speaker ':speaker'
Starting Scramble ':'
Attempting to parse: default.cfg
Attempting to parse: scramble.cfg
13 355 Read More
MAME
12/13/18 09:19 PM
Run MAME from the command line with -verbose and copy/paste what it prints out.
13 355 Read More
MAME
12/13/18 09:17 PM
Hi Haze, sorry about that, I tried to be as thorough as possible for my novice/modest MAME ability in explaining my issue. So let's see, I went to https://www.mamedev.org/release.php and downloaded a fresh mame0202b_64bit.exe at the time. I didn't overwrite another install to the same folder, it was/is fresh. I ran the .exe and it made itself it's own folder and I have tried to run it from there ever since.

I have tried having only one rom in the roms folder before but I just did it again, which for now is (Scramble). All the rest are on another drive waiting to see if I can ever fix the issue. i have tried other single roms as well. They all freeze on the initialization screen on versions 0.172 through 0.204, on versions 0.171 and below MAME works great and loads the roms. I just now tried your suggestion of unplugging all joystick controllers and MAME 0.202 still freezes. Thank you for your suggestions thus far. Any other suggestions from anyone would be greatly appreciated or instructions on how to spit out a log error file.
13 355 Read More
MAME
12/13/18 07:42 PM
Hi Duke,
thanks for creating the driver ... the "CEPT" string seems to point to some sort of BTX screen codes, but I could be totally wrong.
Since the MUPID was a BTX machine that accepted "apps" sent over BTX, maybe these are the screen settings for the MUPID to act as a terminal.

The disk that's in the archive was in one of the drives but doesn't seem to belong to the system as it's MFM vs. the FM only MUPID disk station.

Since my floppy writing rig doesn't seem to be capable of handling FM, I'm awaiting delivery of boot disks to test my disk station.

Christian Corti put on additional firmware and disk images of his German version MUPID (which is Grundig branded), so I'm looking forward to testing more.

Robert
4 688 Read More
MAME
12/13/18 07:40 PM
this kind of thing is usually caused by a user setting error, or some kind of corrupt resource. (both often caused by trying to upgrade MAME by simply copying an exe over an old one rather than extracting things properly, also badly packed 'extras' collections, although you don't state the use of anything like that)

you're not really explaining what you've tried at all, eg. if you've extracted a 100% fresh version of MAME, from mamedev.org into a clean folder, put a single game in the 'roms' folder and tried that.

you should also make sure all controllers etc. are unplugged in case it's an issue with something like that. if it's not a corrupt MAME install, it's likely a conflict with something else you have installed or plugged in.

MAME generally isn't very fussy, and your specs are 100% standard and suggest you should have no problems at all (it's not far off the machine I use for MAME development)



13 355 Read More
MAME
12/13/18 07:06 PM
Hello all, great to be a part of this community now. I know you all are incredibly busy but hope someone can help me with my MAME problem that has been plaguing me for months.

Basically I can load ROMs into all versions of MAME 0.171 and below - on my computer (it will load the ROM) after the black initialization screen. If it is 0.172 all the way to the newest version 0.204 my computer will freeze on the black initialization screen and won't load the Rom when I click to load ROM, I also can't close MAME at that point and have to CTRL - ALT- DELETE and then I have to end the MAME process to close it.

I know this is a strange problem but I have not been able to figure it out with ten's of hours of research, Google searches, downloads like all the DirectX files, etc...I've tried all the video modes available to me like (Dierect3D, GDI, OpenGL, BGFX), I want to be clear that versions of MAME 0.172 through 0.204 do and work do open. I can go to configure and use the tools. The freezing problem happens only when I try to load a ROM into versions 0.172 through 0.204. It freezes the initialization screen. 0.171 and below MAME versions work fine.

It sucks so bad I haven't been able to figure this out. I have no idea what MAME added between versions 0.171 and 0.172 but whatever it was it makes playing the newest MAME version impossible for me.

I'm turning into a MAME junkie and can't get enough but this is really putting a huge damper on it. Anyways I hope to hear back from someone that can help fix this situation for me and my family. I am not sure how to do a log if there is an option to do that to show you guys. Maybe someone can show me how to do that to get started?

Thanks for any help given!

I have MAME version 0.202 for testing (All matching sets)
full set of 0.202 ROMS merged,
full set 0.202_Software_List_ROMs_merged,
full set of 0.202 Samples,
full set of 0.202 CHDs

Here are my computer specs:
Windows 10 Professional additions
Motherboard: MSI GD-65 Gaming
Processor: 17-4790k (Overclocked to 4.6) - have taken overclock off to test and issue still persists.
Graphics Card: Nvidia 980TI
RAM: 32 gigs of DDR3 g.skill
13 355 Read More
MAME
12/13/18 06:31 PM
I'll add a partially working driver for the disk station soon. Here's a screenshot of it with no disk inserted:

[Linked Image]

Disks boot too, but the keyboard seems erratic:

[Linked Image]

[Linked Image]

It doesn't boot the disk you provided though, this is this one: ftp://ftp.informatik.uni-stuttgart.de/pub/cm/mupid/disks/mcpm.imd

There is also an alternate firmware for it at ftp://ftp.informatik.uni-stuttgart.de/pub/cm/mupid/roms/

This seems to be the Grundig FL100? Screenshot:

[Linked Image]

Maybe it expects some kind of special terminal?
4 688 Read More
MAME
12/13/18 12:29 PM
You can see the pictures here.

The system 220 is an EGA system (as in integrated EGA chip on the board), but the one I have was upgraded with an ISA VGA card with a Paradise chip.

The System 40 is a VGA system (integrated Ati VGA), a newer Big Jim chip and integrated disk controller.

Both systems have a backplane (TOWER EGA I/O in case of the 220 and TOWER VGA I/O in case of System 40) and then a CPU card (286 for the 220 and 386SX for the system 40), and can have additional expansion cards.
2,557 4,241,640 Read More
MAME
12/12/18 09:33 PM
Ok, I managed to dump all eproms, but the plcc 27c64 on the WDC Disk Controller and the MBL8042 chips used as keyboard controllers.

@rfka01, I'm sending you a PM.

Cheers,
Rob
2,557 4,241,640 Read More
MAME
12/12/18 02:45 PM
My PR includes the international versions in the comment section of the driver, other than that I've just added the missing ROM versions. I'm fine with your view of things, it was just an idea to give the existing stuff more coverage.
133 73,432 Read More
MAME
12/12/18 10:25 AM
But it isn't a newly supported system, so gaming the script that generates the list is misleading.
133 73,432 Read More
MAME
12/12/18 09:48 AM
I'm quite content with having the M24 - that was the version offered here in Europe. I think it's a matter of visibility, e.g. in your compilation of new features for every monthly version. They will be trawled by the search machines and might give people an incentive to check out MAME if they include their local verson. Maybe one of the US and/or French contributors (for Logabax) could give us their opinion on that matter.
133 73,432 Read More
MAME
12/12/18 05:57 AM
Is it really worthwhile when the machines are actually identical? I mean, there's something to be said for aliased ROM definitions when the machine config or inputs are different, but for a pure badge-engineered version, I don't think it's worth it.
133 73,432 Read More
MAME
12/12/18 05:04 AM
Originally Posted by rfka01
Is there a way to add an alias to access the M24 driver under another name without duplicating the ROM section?


#define rom_pc6300 rom_m24

You still need a COMP macro for the pc6300 though.
133 73,432 Read More
MAME
12/11/18 10:23 PM
I've sent a PR that adds the rest of the ROM revisions to the Olivetti M24 driver.

The emulated M24 somehow gained a second, faulty RT clock ... why does the BIOS even detect two RT clocks? smile

[Linked Image]

A real M24 is content with having one RT clock ...

[Linked Image]

The ROMs of the badge engineered incarnations of the M24, the AT&T PC 6300, the Xerox 6060 and the Logabax Persona 1600 are identical to the M24, retaining the Olivetti string in the ROM.

Is there a way to add an alias to access the M24 driver under another name without duplicating the ROM section? If so, I'd suggest to add at least a pc6300 alias to make the driver more familiar to US users.
133 73,432 Read More
Non-Windows MAME Support
12/11/18 09:46 PM
2 67 Read More
Page 1 of 6 1 2 3 4 5 6
Who's Online Now
4 registered members (AJR, R. Belmont, Olivier Galibert, Reznor007), 104 guests, and 1 spider.
Key: Admin, Global Mod, Mod
Shout Box
Forum Statistics
Forums9
Topics8,606
Posts112,515
Members4,827
Most Online296
Dec 5th, 2018
Powered by UBB.threads™ PHP Forum Software 7.6.1.1
(Release build 20180111)
Page Time: 0.030s Queries: 6 (0.011s) Memory: 5.2618 MB (Peak: 5.3851 MB) Zlib enabled. Server Time: 2018-12-15 13:40:52 UTC