Topic: VXPocket & MiniMe Driver Conflict

[Steve J]

I just received a Mini-Me and tried configuring the USB this weekend. I'm running into apparent driver conflicts though.

I have a Dell Insprion 8200, XP Pro OS, NTFS file system, VXPocket V2 already installed. I've minimized the number of services running; and except for communications (LAN & modem connections), IE, SF 6.0 and assortment of audio utilities like EAC, I don't have anything else running.

Problem I'm getting is that I can get the USB driver for the MME installed & functioning correctly; but then I can't use the VXPocket. I uninstall & reinstall the VXPocket and the USB driver for the MME no longer works correctly. Seems as though the two really don't like each other. I even tried running the MME without the USB driver; but severe latency problems appeared. As I still need the VXPocket for digital transfers, doing without it is not an option.

Anyone know if there is a way to make the two get along? I thought about doing a dual-boot setup; but I'm not sure it's worth the hassle...especially since I've pretty much set the lappy up for recording only anyway. And as I think about it, the only advantage I see to having the USB is more options for patching out of the MME (which is helpful for those times when I'm at the front of a chain).

Thoughts? Ideas? Raw eggs thrown with Clemens-like velocity? Thanking you very much...

[caymanreview]

it might be just an issue with that laptop, i successfully used my mme with usb and vx pocket v2 at the same time with no issues

[adventuregeorge]

I had to downloaded  the drivers from Apogee.

After that I updated my drivers and it worked fine.

What are using for software to record onto the hard drive?

I use Soundforge 7.0 and have no problems.

[Steve J]

I'm using SF 6.0; and I too, tried all the drivers at Apogee without any positive results.  I've been poking around a bit and did find a note about a hardware problem with the VX & the Inspiron 8200 (noisy audio output). It suggests changing the I/O resources by changing the device address. Haven't tried that yet to see if it resolves my current dilemma; and since the first time into the fire for this configuration is this Friday, I may just go with what'll work for sure and experiment when I get back.