NPDP-ODEM Error message

Excellent, thanks. Might even have a normal SCSI cable I could use in that case.

 

Hm. Does this mean that my GDEV is NTSC only? Tried to boot a PAL GCM image to verify that my ODEM and GDEV actually works, but only got error messages in the terminal =/
Trying to digg up a some NTSC image to try, hopefully it works better.

edit: yay, I got bootmode.elf to start so I guess it works :yatta:

 

Thanks for all the replies, I will post a picture of it tomorrow.

babu, you didn't get any error messages?

I also digged up an old server pc with windows 2000 but I forgot the admin password..OH:

 

Sorry, no errors similar to yours. =/
Though I saw some errors in the terminal while trying to get something to boot (mostly whinning about my discs being wrong).

 

Well, the windows 2000 pc gives me the same error message.... I only installed the driver and Odemsrv but that should be enough to check it I guess.

I'm afraid it's dead.

Here are 2 fast clicks for Nitro:





EDIT: I noticed the ORCA chips aren't really clear, so here's what's on them:

The top one:
OR3T80-6
BA352
1601235B
0025S

The bottom one:
OR3TP12-6
BA352
1701135B
0027S

I also saw the serial on the bottom of the board is readable, but posting serials of previous generation dev stuff can't do any harm right?

 

my BETA can switch to NTSC, PAL and JPN just as the last batch.

 

hmmm

Thanks for posting the pics

the beta sticker on there seems to raise a red flag for me, is the hardware might have a different device ID of some kind to denote its beta status, and that might be throwing off the software.

Also, your card is almost identical to mine. almost - There are 4 components missing on mine that are included on yours that I noticed at first glance. There are 7 small components in a horizontal row directly left of the bottom ORCA chip on your card, but mine one has the right-most three. The other four are simply empty sockets where they could go.

What this means is your card is in some ways different. I would like any other person willing to inspect their ODEM to note any differences they find.

The only thing that I could think is to use a hex editor to find the reference to the regular device ID and replace it with the device ID of your ODEM card and hope things don't explode. I'm not even familiar with such things, so I can't be of much more help unfortunately.

Best of luck!