XBCD 0.2.7 Discussion

[Squall Leonhart]

Code: Select all

A listing of files alongside their results can be found below:
File ID 	 Filename 	Size (Byte) 	Result
27083092 	 xbcdif.dll 	 26 KB 	 FALSE POSITIVE


Please find a detailed report concerning each individual sample below:
Filename 	Result
xbcdif.dll 	 FALSE POSITIVE

The file 'xbcdif.dll' has been determined to be 'FALSE POSITIVE'. In particular this means that this file is not malicious but a false alarm. 

[MagnumIP]

Hey all, brand new to XBCD. Currently trying to get XBCD 0.2.7 to work on Win 7 Home Prem x64 with SP1 for a Hori RAP VX-SA and MAME specifically.

 

I've installed the x86/x64 VC Runtimes, I got Windows running in test mode, I signed the xbcd.sys file with the NG DSEO app and the XBCD package installs fine, but the driver INF never shows up in C:\Windows\INF. The xbcd.sys file shows up OK under C:\Windows\System32\drivers though.

 

When I go into Device Manager and manually point it to the INF file located under C:\Program Files (x86)\XBCD\Driver, it comes back with a message stating:

 

The folder doesn't contain a compatible driver for your device. If the folder does contain a driver, make sure it is designed to work with Windows for x64-based systems.

 

So is there a specific x64 based version of XBCD 0.2.7 or is there something I'm missing?

[Squall Leonhart]

Thats not a device i've ever heard of, so its unfortunately not a supported device yet.

 

check the request support board and follow the request format and i'll get to it asap.

 

Also, you might be using an old xbcd if it still mentions requiring DSEO and Test mode anywhere.

[MagnumIP]

Thats not a device i've ever heard of, so its unfortunately not a supported device yet.

 

check the request support board and follow the request format and i'll get to it asap.

 

Also, you might be using an old xbcd if it still mentions requiring DSEO and Test mode anywhere.

 

Oh sorry, I shouldn't have abbreviated it. According to the current 0.2.7 release page, it is supported as a listed device here:

 

%XBCD_360_Arcade.DeviceDesc% =Install, USB\VID_1BAD&PID_F502 ; Hori Real Arcade Pro VX SA

 

From here: http://vba-m.com/forum/Thread-xbcd-0-2-7-release-info-updates-will-be-posted-here

 

Well the xbcd 0.2.7 I'm using is from the above link. The whole DSEO and Test mode stuff is from a combination of many links I found while trying to research my issue. It sounds like that is unnecessary now with this release?

 

The root issue for me based on the message I'm getting from Win Device Manager is that it looks like the 0.2.7 package I am downloading does not seem to have an x64 driver for Win 7 x64 SP1. Can you confirm that it does have an x64 driver and it works on Win 7 SP1?

 

It's odd because Windows recognizes my Hori stick just fine with the stock microsoft driver but MameUI64 won't recognize it except for 1 button for some reason. At this point, I wanted to see if xbcd will help with the Hori stick loading in MameUI64.

[JetCell]

Hi, I just recieved a 360 MadCatz MicroCon Pro controller for my birthday and was hoping that I would be able to use it as a gamepad on my computer (Windows 7 x64). In the list of supported controllers I saw "MadCatz MicroCon" and thought that perhaps they were pretty much the same and that they would be compatible with one another. However, when I installed the program, I don't see it coming up in any sort of list at the bottom. I also don't see anything listed in the settings database and refreshing does not bring anything up. I cannot manually change the inputs, as all the drop-down menus are grayed out.

 

I'll be honest; I have no idea what I'm really doing. I've read the threads for this program over and over and can't figure out what exactly I'm supposed to do. I don't know what to do or if I'm supposed to do anything with the codes on the list of supported controllers.

 

I have no idea whether this controller isn't supported or whether I'm installing this wrong. Help with this would be fantastic if you have the patience to deal with someone not as computer literate as you are.

[Squall Leonhart]

Oh sorry, I shouldn't have abbreviated it. According to the current 0.2.7 release page, it is supported as a listed device here:

 

%XBCD_360_Arcade.DeviceDesc% =Install, USB\VID_1BAD&PID_F502 ; Hori Real Arcade Pro VX SA

 

From here: http://vba-m.com/forum/Thread-xbcd-0-2-7-release-info-updates-will-be-posted-here

 

Well the xbcd 0.2.7 I'm using is from the above link. The whole DSEO and Test mode stuff is from a combination of many links I found while trying to research my issue. It sounds like that is unnecessary now with this release?

 

The root issue for me based on the message I'm getting from Win Device Manager is that it looks like the 0.2.7 package I am downloading does not seem to have an x64 driver for Win 7 x64 SP1. Can you confirm that it does have an x64 driver and it works on Win 7 SP1?

 

It's odd because Windows recognizes my Hori stick just fine with the stock microsoft driver but MameUI64 won't recognize it except for 1 button for some reason. At this point, I wanted to see if xbcd will help with the Hori stick loading in MameUI64.

 

Did you download the version of XBCD that thread provides? the most recent versions no longer copies the driver inf to the windows folder as it handles thedevice installation via dpinst from the Program files (x86)\XBCD folder. After checking the driver, the inf does infact support that control.

 

 

Hi, I just recieved a 360 MadCatz MicroCon Pro controller for my birthday and was hoping that I would be able to use it as a gamepad on my computer (Windows 7 x64). In the list of supported controllers I saw "MadCatz MicroCon" and thought that perhaps they were pretty much the same and that they would be compatible with one another. However, when I installed the program, I don't see it coming up in any sort of list at the bottom. I also don't see anything listed in the settings database and refreshing does not bring anything up. I cannot manually change the inputs, as all the drop-down menus are grayed out.

 

I'll be honest; I have no idea what I'm really doing. I've read the threads for this program over and over and can't figure out what exactly I'm supposed to do. I don't know what to do or if I'm supposed to do anything with the codes on the list of supported controllers.

 

I have no idea whether this controller isn't supported or whether I'm installing this wrong. Help with this would be fantastic if you have the patience to deal with someone not as computer literate as you are.

 

Theres actually a few controllers with the same name which have an entirely different product id (and sometimes even vendor id's)

 

Requests for missing controls is provided at http://vba-m.com/forum/Forum-controller-not-supported-request-it-here , just follow the sticked template

[MagnumIP]

Hi, I just recieved a 360 MadCatz MicroCon Pro controller for my birthday and was hoping that I would be able to use it as a gamepad on my computer (Windows 7 x64). In the list of supported controllers I saw "MadCatz MicroCon" and thought that perhaps they were pretty much the same and that they would be compatible with one another. However, when I installed the program, I don't see it coming up in any sort of list at the bottom. I also don't see anything listed in the settings database and refreshing does not bring anything up. I cannot manually change the inputs, as all the drop-down menus are grayed out.

 

I'll be honest; I have no idea what I'm really doing. I've read the threads for this program over and over and can't figure out what exactly I'm supposed to do. I don't know what to do or if I'm supposed to do anything with the codes on the list of supported controllers.

 

I have no idea whether this controller isn't supported or whether I'm installing this wrong. Help with this would be fantastic if you have the patience to deal with someone not as computer literate as you are.

 

If the stock Windows driver doesn't give you the control settings you need, then you can use the XBCD driver. ONce you run the installation, you may need to go to the Device Manager to update the driver. Device Manager can be found under Control Panel - System - Device Manager. You'll need to find your controller in the list, right click it and choose Update Driver. Then choose the manual options and browse to the path that has the XBCD driver which is xbcd.inf. THe path will be C:\Program files (x86)\XBCD. THen it should let you choose the XBCD driver.

 

However, whenI got that far, Windows would tell me it wasn't a compatible x64 driver so not sure if you will run into the same thing since you're on WIn 7 x64 as well.

 

Once you get the driver loaded, you should be able to run the XBCD setup tool to map your inputs.

---

Did you download the version of XBCD that thread provides? the most recent versions no longer copies the driver inf to the windows folder as it handles thedevice installation via dpinst from the Program files (x86)\XBCD folder. After checking the driver, the inf does infact support that control.

 

 

 

I did download that version. Even if the INF is not placed there automatically, when I try to manually select the INF from the Program files (x86)\XBCD path via DEvice Manager, it won't let me install it. It gives me the same message above about not being a compatible x64 driver.

 

I gave up on XBCD and finally figured out what my original issue was. I wasn't hitting ENTER on the Tab-in game control settings in MAME. I thought you just select the input and move the joystick. Because it wasn't responding, I thought it wasn't seeing the joystick. D'oh! Once I hit Enter on the input inside the Tab-in game controls, the joystick controls were communicating just fine. Talk about missing the obvious.

 

 

Admin edit - striked out redundant advice. Device manager is no longer the suggested method of installation

[Squall Leonhart]

the driver (.sys) is probably corrupted from attempting to sign an already signed driver

 

You aren't supposed to select the driver through device manager anymore, you do it through the Reinstall Driver shortcut in the xbcd program group

 

What is the file name of the xbcd setup you downloaded.

[MagnumIP]

the driver (.sys) is probably corrupted from attempting to sign an already signed driver

 

You aren't supposed to select the driver through device manager anymore, you do it through the Reinstall Driver shortcut in the xbcd program group

 

What is the file name of the xbcd setup you downloaded.

 

That's possible since I messed around with the various bcdedit, DSEO, etc. options for a while before giving up.

 

I don't have the names of the setup files at the moment but I tried each link in that post, the mediafire and SkyDrive link for the 0.2.7 files. This was on Win 7 Home Premium x64 with SP1. I uninstalled the previous before trying the next.

 

So when you run the installer once, is the XBCD driver supposed to be loaded/applied to the controller at that point? Or do you have to run the Reinstall Driver shortcut after the initial install to make sure that your controller has the XBCD driver?

 

Don't sweat it though, I got mine working with the MS driver so I'm happy for now.

[Squall Leonhart]

during the setup process, the xbcd installer should vanish for a moment and a DPInst wizard should appear

 

 

It will detect available compatible devices and then will install on xbox devices

on 360 pads it will report that a newer driver is already installed and ask for your input on installing xbcd.

 

I'm using xbcd on windows 7 sp1 (ultimate/home premium) here with the driver, so its not a matter of binary support.