CRT EMUdriver installation error: wrong or missing ini settings

[Isstanar]

I've been using Windows XP  for my MAME arcade machine, but I decided to switch to Windows 7 Ultimate now, but right away I'm having a problem installing the beta CRT Emudriver.

So, on a fresh installation of Windows 7 I downloaded the CRT Emudriver (CRT Emudriver & CRT Tools 2.0 beta 9 (Catalyst 12.6) for Windows 7/8/10 64-bits) and when I run the setup program I get an error stating "error: wrong or missing ini settings". I wasn't sure why this was happening so I tried a few things like re-downloading the file, restarting the computer, and turning off user account controls, but nothing has fixed it yet. I couldn't find anything online with searches so does anyone here know what might be going on?

My Computer:
Windows 7 Ultimate
ATI Radeon 4800
CRT Emudriver & CRT Tools 2.0 beta 9 (Catalyst 12.6) for Windows 7/8/10 64-bits

[Calamity]

Please replace the "Setup.ini" file with this one.

[Isstanar]

Awesome, thank you! Works fine now.

[cornerstone]

If you don't mind me piggybacking off this topic, I had the same error.

I replaced the setup file and now CRT Emudriver will not show anything under "Compatible Devices:"

My Computer:
Windows 10 Pro
ATI Radeon HD 4600 Series
CRT Emudriver & CRT Tools 2.0 beta 9 (Catalyst 12.6) for Windows 7/8/10 64-bits


Through my search for an answer to the previous issue, I installed the newer Catalyst meant for 5000 series, and Emudriver installed successfully. VMMaker wouldn't recognize any catalyst drivers however. Any idea where to go next?


Edit: The HD 4600 does not have any of its own drivers installed. It only shows up as Basic Display Adapter in the device manager.

[Isstanar]

I was actually going to post the same thing, but I wanted to do some testing to see if I could get it to recognize the card. So far though I haven't been able to get the setup program to detect the card.

My Computer:
Windows 7 Ultimate
ATI Radeon 4890 (found out the exact model now)
CRT Emudriver & CRT Tools 2.0 beta 9 (Catalyst 12.6) for Windows 7/8/10 64-bits

I had the basic VGA adapter driver installed, ran the setup and nothing showed up on compatible devices. Like you though I tried the other calamity driver sets for the newer cards and they detected the card, but when I tried to install I get an installation error 57.

I'm not sure what else to do now either, but I'm going to keep looking.

[Calamity]

Sorry, it's a problem with utf encoding. Please try replacing this .inf file. If you have issues with the signature tomorrow I'll re-upload the whole package properly signed.

[Isstanar]

Well first off thank you so much for trying to fix all this, I've been using these drivers for a while now and its given me lots of entertainment out of my MAME machine.

I assume that file was for me since I don't remember the other driver packages using that particular INF file.

So I copied and replaced that INF file and I get a new error. I'm still in testsigning mode by the way.

"Error: The driver installation failed: 103 No More Data is available"

I don't know if it matters, but since I first installed Win7 I did all the Windows updates.

EDIT: forgot to mention that after I copied the INF file over and replaced the old one it still wasn't being detected, but I changed the setup.ini to use the "atiilhag10.inf" instead of the ""atiilhag.inf" then it detected it.

[cornerstone]

I was able to get the driver to be recognized through that last suggestion of manually changing the setup.ini to use the new atiihag10.

This may be a separate issue that I just goofed on: following the guide for HD 4xxx cards, it was supposed to see a second monitor pop up through windows. I didn't. The resolution just changed so I hooked in the arcade monitor. The games look great, but the front end (MaLa) looks pretty ugly. If were to change the resolution to 640x480, the blast city monitor interprets that as 31khz, and the jpac I'm running everything through will split the screen.

[Calamity]

Please download the package again. It should be fixed now. Thanks for reporting this.

[cornerstone]

New package causes blue screen and restart

PAGE_FAULT_IN_NONPAGED AREA (atikmdag.sys)


My Computer:
Windows 10 Pro
ATI Radeon HD 4600 Series
CRT Emudriver & CRT Tools 2.0 beta 9 (Catalyst 12.6) for Windows 7/8/10 64-bits

[Calamity]

It installed fine here this morning, twice. You probably didn't uninstall previous version first.

[cornerstone]

It installed fine here this morning, twice. You probably didn't uninstall previous version first.

I ran CRT Emudriver and clicked uninstall. The added driver installation designation was taken off the Basic Display Adapter. Is there any other steps to uninstall it? I didn't reset before reinstalling, so maybe that is it?

[Calamity]

Yes, you need to restart when Windows tells you so, otherwise it breaks the installation.

[cornerstone]

What I meant is I didn't restart between uninstalling and reinstalling. There was no prompt.

I'll try again later today or tomorrow.

I appreciate the help.

[Calamity]

What I meant is I didn't restart between uninstalling and reinstalling. There was no prompt.

It's easy to miss the prompt because it's not shown by the installer itself but by Windows, and it may get behind the installer window if it loses focus. Restarting is always compulsory when switching to or from the Basic Display Adapter state.

[Isstanar]

Meant to report back earlier, but I was messing around with Grooymame heh.

That new package worked perfectly for me, thank you so much.

Now onto the endless task of fine tuning a games list.

[cornerstone]

What I meant is I didn't restart between uninstalling and reinstalling. There was no prompt.

It's easy to miss the prompt because it's not shown by the installer itself but by Windows, and it may get behind the installer window if it loses focus. Restarting is always compulsory when switching to or from the Basic Display Adapter state.

I was able to install the Emu Driver successfully with the new package.

I'm still having an issue with detecting a second screen unfortunately. My HD 4600 has a DVI port and an unused HDMI port. My monitor is always detected as a generic PnP.

If I follow-through with the process, and just plug in the arcade monitor, I end up with a windows screen that displays in super resolutions, which is difficult to navigate. Mame looks great though, if I can get to it.

As a workaround, would I be able to add a workable resolution (384 x 224, etc.) to the list of super resolutions and have windows default to that outside of mame?

Edit: Would I be able to change the desktop resolution in the user_modes-super file to 384x224 without messing up any of the actual super resolutions?