Controller not recognised when VMU is inserted
Justin Bell
I just got a DC, and the controller only works when no VMU is installed.
any clues?
--
Justin
Oracle
I had something like that happen with a VMU that had a corrupted save file.
What would happen is that the DC would lock up whenever that particular
VMU was insterted. It didn't matter which port, which game, or which
controller. What I did was to delete all of the saves from that VMU.
Of course, I couldn't use the DC to do it so I had to use the VMU itself.
After the corrupt file was gone, everything worked okay.
--
This message sent with the spirit of the Nine Muses,
Calliope, Clio, Polyhymnia, Euterpe, Terpsichore,
Erato, Melpomene, Thalia and Urania.
Justin Bell
> Justin Bell wrote:
>>
>> Anyone see this?
>>
>> I just got a DC, and the controller only works when no VMU is installed.
>>
>> any clues?
>
> I had something like that happen with a VMU that had a corrupted save file.
> What would happen is that the DC would lock up whenever that particular
> VMU was insterted. It didn't matter which port, which game, or which
> controller. What I did was to delete all of the saves from that VMU.
> Of course, I couldn't use the DC to do it so I had to use the VMU itself.
> After the corrupt file was gone, everything worked okay.
Odd. What's happening is that when no VMU is inserted the controller
works fine, when I insert the VMU the DC no longer sees the controller,
when I take it back out it sees it just fine again
this is with 2 VMUs
--
Justin
Oracle
Well, if you have another controller, you can try that, or it's possible
that both VMU's are corrupt as well. If you just got the DC and you're
using totally first-party licensed goods, then you're possibly in your new
90-day warranty period. It's not at all impossible that you have a bad
controller. The Dreamcast seems to be fairly forgiving of controllers
(I have Saturn->DC adapters and PSX->DC adapters and those work fine with
a VMU and have for over a year. So, the DC seems pretty flexible even
with totally unlicensed setups.
At this point, I'd say you seem to have eliminated the VMU (unless, of
course, they have identical files) and the evidence is pointing at your
controller or your Dreamcast. A bad DC is doubtful, imho, but half of
the field of electronics is magic. The minute you say it can't happen,
it does. Oh yeah, bad batteries. Check that too. Weak batteries in a
VMU can scramble the marbles up as well. Take 'em out if they're dead
and you don't want to pay $3 a pop to replace the carcasses.
You can try to eliminate the controller (if you have more than one or
access to a proven working one) to see if that's the problem. The
ideal situation would be to have another DC or controller to try. That
would make troubleshooting and isolation of the faulty component much
easier.
Justin Bell
> Justin Bell wrote:
>>
>> In article <3C1BD666...@mindspring.com>, Oracle wrote:
>> > Justin Bell wrote:
>> >>
>> >> Anyone see this?
>> >>
>> >> I just got a DC, and the controller only works when no VMU is installed.
>> >>
>> >> any clues?
>> >
>> > I had something like that happen with a VMU that had a corrupted save file.
>> > What would happen is that the DC would lock up whenever that particular
>> > VMU was insterted. It didn't matter which port, which game, or which
>> > controller. What I did was to delete all of the saves from that VMU.
>> > Of course, I couldn't use the DC to do it so I had to use the VMU itself.
>> > After the corrupt file was gone, everything worked okay.
>>
>> Odd. What's happening is that when no VMU is inserted the controller
>> works fine, when I insert the VMU the DC no longer sees the controller,
>> when I take it back out it sees it just fine again
>>
>> this is with 2 VMUs
>
> access to a proven working one) to see if that's the problem. The
> ideal situation would be to have another DC or controller to try. That
> would make troubleshooting and isolation of the faulty component much
> easier.
I bought a brand new controller today... same problems
it works just fine until I insert the VMU
on the "file" menu, it shows the controller in the right port, I insert
the VMU and the image of the controller goes away, remove the VMU and
it's back
--
Justin
Joe Ottoson
nos...@nations.ucs.indiana.edu wrote on 12/18/01 9:46 PM:
> I
>> You can try to eliminate the controller (if you have more than one or
>> access to a proven working one) to see if that's the problem. The
>> ideal situation would be to have another DC or controller to try. That
>> would make troubleshooting and isolation of the faulty component much
>> easier.
>
> I bought a brand new controller today... same problems
>
> it works just fine until I insert the VMU
>
> on the "file" menu, it shows the controller in the right port, I insert
> the VMU and the image of the controller goes away, remove the VMU and
> it's back
If the VMU's batteries are low, or the connections are screwy, you can get
that to happen. Try taking the batteries out. If the thing works after that,
then it's the low batteries that are causing the problem.