NPDP-ODEM Error message

Hey there,

I've had a GDEV with an ODEM for a while now, and I recently acquired the SDK discs. After I had some problems with finding the drivers on the discs, a couple very friendly people here helped me out and provided me with the Uberinstaller. When I ran the disc it looked like it installed everything just as it should, except that it didn't install the drivers automatically. I had to grab the .inf file from the folder the uberinstaller temporary copies the files to. When I try to run OdemSrv now, it immediately gives me the following error message:

Incorrect FPGA1 version of "ODEM PCI I/F"

F1VER=2000a190 (>=20014060 ? )
F2VER=2000b070 (>=20014050 ? )

Doe anyone know what this could be and how I can solve this?

Someone told me that it could be that my ODEM is too old which I think is plausible (first revision ODEM with beta sticker on the bottom).

Thanks in advance!

 

I would also like to know even the nature of this error message. I haven't seen it before and anyone with knowledge that might be helpful, please share

 

Anyone..?

 

No idea, can see if I find anything when I get home after work.
Maybe you got the wrong drivers or something? If you got a older SDK try using it instead.

 

Hmm, yeah, I guess that could be the problem. I also got the older SDK, but for some strange reason it won't install the drivers on my pc nor can I find the actual .inf file on the disc.

 

seems to be an ODEM related issue (compatibility) - I ve never encountered it before however. Does the ODEM appear in as Hudson blah blah blah in system manager?

 

The Uberinstaller was quite a late release, wasn't it? My guess would be that you either have a pre-release first-version ODEM, or the first ODEM wasn't supported in that driver set. I'd try finding an older SDK first - the drivers off that might let you use the newer tools.

Good luck!

 

If I recall, you had to manually grab the .inf file from the uberinstaller's temp directory and get it to recognize that way, correct? To me, this flags as a problem... but you said that the earlier SDK you tried (one from 2001 I think?) offered you very little success... I'm not sure at this point... do you have another computer you can toss the ODEM in to eliminate any possibility that the computer itself is causing the issue?

 

Yep, it does. Windows says it´s working properly.

I think the Uberinstaller was released in 2004, so it is indeed a quite late release. My ODEM is a beta release so it surely is plausible my ODEM is too old for the uberinstaller driver.

I do have the 2001 SDK, but for some reason I couldn´t find the drivers on those discs. I´ll post some screenshots of the folders the discs contain later today. babu told me he found his .inf file in NPDP-GDEV_v121_3-08-02.zip, but I could find that zip file either..

Yep true. I´ll pop out an ancient pc today and hope that will work.

 

Well, here are some screenshots:

The error message:


GameCube SDK Contents:


Inside the "GameCube SDK" folder:


Inside the "Host I/O" folder:


Inside the "Drivers" folder:


Can anyone say if his disc is the same?

 

Anyone willing to check their disc?

 

Well I tried the older driver that I got from someone here, but no luck either. I think there could be 2 things wrong. Either the PC (does an ODEM even run under a shitty spec XP home PC?) is wrong or I have a faulty ODEM...

I'll try to get something with Windows 2000, since the SDK is developed for that OS.

If anyone else has suggestions, please let me know! I'm getting a bit lost.

 

home XP you say?

To my knowledge, it's for win2K and Professional XP.

 

Matthijscoman, can you post a photo of your ODEM? I'd like to visually compare it to mine to see if there are any differences. Possibly include (if not legible in the photo) any writing on the main ORCA chips.

 

I received a GDEV today marked beta - β. And my ODEM card have no marking so I assume it's the final.. going to try it tonight and see if I get any similar problems.
One thing though, I don't have a cable for mine but iirc. OE said that the DDH cable work just as good. So I was thinking of using it instead, but as can't find the post where he might have said it I thought I checked a second time, anyone that can confirm this?

 

Beta marked GDEVs aren't really beta. They have updated boards and components that match the ordinary GDEVs (that lack the beta sign).

True Beta gdevs are quite rare actually and you can tell them from the lack of certain stuff such as the RTC battery (If i recall correctly) and obviously the RJ ports instead of the retail GC ports for controllers (not a criterion, just shows a really old GDEV)

 

I thought that was alpha - α

 

no, the BETAs were sent back for upgrades as well.

 

Yep, 'tis fine, its just a standard 64pin SCSI.

 

Incorrect.

Beta marked GDEV's were always NTSC, they NEVER made a Beta marked PAL machine, so as a Development Kit it truly was stuck at the Beta stage for quite some time until PAL enabled units received certification and approval.

Also the Beta marked Ver 1 ODEM's were strictly at the Beta stage of their life cycle and were immediately replaced with the Ver 2 (as well as new software code), as per the following link, oh and of course not forgetting the USB2EXI, that was also Beta staged as well, though it never needed the H/W or S/W upgrades like the ODEM or GDEV required throughout their lifespan:

http://oldengineer.com/gallery/v/nintendo/ngcd/6ngcd.html