RGP wrote:The return of Roger.....
Roger Roger
Well evribody love me here.
You cannot kick me out.
I got the question,simple abauth the usb,not moore marvel.
Anyway, marvel is a long and old story,in the end i burn the rom cart.
But i don't care,it was a foulty card. FOULTY.
Ok. GINO ROGER
That's my name.
Bye RPG and all the stuf.
dj_johnnyg wrote:Hi ROGER!
Nice to see you ignoring answers again.
I've missed you
It is unlikely that you will get a driver for the PC.
I fail to understand why you want your PC to be the supergun???
Why not put your supergun in the PC case?
Ye,right.
You think i'm stupid.
The question is simple,connect the usb off the naomi to my pc and get work whith any supergun.
I wanna connect the supergun to my pc board's because i wanna play all the game whith my supergun.
Marvel versus capcom 2? Forget abauth,this title pest me off. But i'm i still conviced abauth whath evribody knows well.
A or b version? The c version is som hack version not from capcom.
Thankyu
Roger, is sounds like you want a JPAC. This lets you hook your PC up to your Supergun via the jamma edge connector. The JPAC uses USB or PS2 (keyboard port). You will then be able to play your Dreamcast or Mame emulator on your supergun.
The JPAC is only $57 at Ultimarc.
http://ultimarc.com/jpac.html
Have fun.
The JPAC is only $57 at Ultimarc.
http://ultimarc.com/jpac.html
Have fun.
I did some research into this a while back on killercabs...
Firstly the NAOMI doesn't run UNIX... it has it's own embedded OS and is what we call an "EABI target". Applications are compiled with an SDK library similar to the dreamcast one, but I don't have a lot of access to that stuff.
The "USB" for the JVS is not USB at all, it's an entirely different serial signaling protocol which has more in common with RS422 than with USB. :)
I assume they use a USB plug because it was easier to source connectors/cables for, but it really has little in common with USB itself.
Therefore.... it's not possible to make a driver for it because it's not a device which your OHCI/UHCI USB stack is even going to pick up on!
I assume the lindberg must have a dedicated JVS port which is designed to interface with it, but I haven't worked with any lindberg hardware so I can't be sure.
There is a whitepaper in Japanese which documents the JVS standard, including the electrical and signaling characteristics, but it was pretty difficult for me to read for obvious reasons. :)
Hope this helps :P
Firstly the NAOMI doesn't run UNIX... it has it's own embedded OS and is what we call an "EABI target". Applications are compiled with an SDK library similar to the dreamcast one, but I don't have a lot of access to that stuff.
The "USB" for the JVS is not USB at all, it's an entirely different serial signaling protocol which has more in common with RS422 than with USB. :)
I assume they use a USB plug because it was easier to source connectors/cables for, but it really has little in common with USB itself.
Therefore.... it's not possible to make a driver for it because it's not a device which your OHCI/UHCI USB stack is even going to pick up on!
I assume the lindberg must have a dedicated JVS port which is designed to interface with it, but I haven't worked with any lindberg hardware so I can't be sure.
There is a whitepaper in Japanese which documents the JVS standard, including the electrical and signaling characteristics, but it was pretty difficult for me to read for obvious reasons. :)
Hope this helps :P
I see what you are saying, but if that's true, then hooking up the I/O to a computer's USB port should do nothing. In fact, you get a 'New hardware found' message, but no driver is available.
As for the JVS Standards book, I've went through the trouble of translating it, but it doesn't give any more information than we already know. It just lays it out in detailed specifics. It doesn't mention or describe the protocol in of itself.
As for the JVS Standards book, I've went through the trouble of translating it, but it doesn't give any more information than we already know. It just lays it out in detailed specifics. It doesn't mention or describe the protocol in of itself.