Topic: Cannot Connect to YADB (Read 4090 times)

billtr · « **on:** February 04, 2004, 04:28:23 pm »

Whenever I put a CD in Media Center tries to connect to YADB. After a timeout period, I get the dialog that says failed to connect to YADB.

I may not have properly registered for YADB at install time. How can you double-check YADB connection/registration settings? Not finding that in any of the menus, or in the forum.
Thanks!

LonWar · « **Reply #1 on:** February 04, 2004, 04:43:04 pm »

Goto Help,
System Info

Past the results here.

billtr · « **Reply #2 on:** February 04, 2004, 05:41:57 pm »

Media Center Registered 9.1.308 -- C:\Program Files\J River\Media Center\

Microsoft Windows 98 SE
Intel Pentium III 745 MHz MMX / Memory: Total - 261 MB, Free - 94 MB

Internet Explorer: 6.0.2800.1106 / ComCtl32.dll: 5.81 / Shlwapi.dll: 6.00.2800.1276 / Shell32.dll: 4.72.3812.600 / wnaspi32.dll: 4.57 (1009) , ASPI for Win32 (95/NT) DLL, Copyright © 1989-1997 Adaptec, Inc. / Aspi32.sys: N/A

Ripping / Drive E: Copy mode:Normal CD Type:Auto Read speed:Max
Drive F: Copy mode:Normal CD Type:Auto Read speed:Max
Digital playback: Yes / Use YADB: Yes / Get cover art: No / Calc replay gain: Yes / Copy volume: 32767
Eject after ripping: No / Play sound after ripping: No

Burning / Drive E: PLEXTOR CD-R PX-W2410A Addr: 0:0:0 Speed:24 MaxSpeed:24 BurnProof:Yes
Test mode: No / Eject after writing: Yes / Direct decoding: Yes / Write CD-Text: No
Use playback settings: No / Normalization: None

KingSparta · « **Reply #3 on:** February 04, 2004, 05:53:13 pm »

Update to 9.1.316

billtr · « **Reply #4 on:** February 04, 2004, 06:32:25 pm »

Will do. Back to you soon.

billtr · « **Reply #5 on:** February 04, 2004, 06:57:06 pm »

YADB cannot find info for "Close to You" by the Carpenters, A&M records. It then fails with a gpf:

MEDIA JUKEBOX caused an invalid page fault in
module <unknown> at 0000:020753a2.
Registers:
EAX=00000000 CS=0167 EIP=020753a2 EFLGS=00010202
EBX=00000000 SS=016f ESP=0098b278 EBP=0098b298
ECX=7f2da241 DS=016f ESI=020753a2 FS=42ff
EDX=80007460 ES=016f EDI=000005fc GS=0000
Bytes at CS:EIP:

billtr · « **Reply #6 on:** February 04, 2004, 06:58:34 pm »

New system info:

Media Center Registered 9.1.316 -- C:\Program Files\J River\Media Center\

Microsoft Windows 98 SE
Intel Pentium III 736 MHz MMX / Memory: Total - 261 MB, Free - 122 MB

Internet Explorer: 6.0.2800.1106 / ComCtl32.dll: 5.81 / Shlwapi.dll: 6.00.2800.1276 / Shell32.dll: 4.72.3812.600 / wnaspi32.dll: 4.57 (1009) , ASPI for Win32 (95/NT) DLL, Copyright © 1989-1997 Adaptec, Inc. / Aspi32.sys: N/A

Ripping / Drive E: Copy mode:Normal CD Type:Auto Read speed:Max
Drive F: Copy mode:Normal CD Type:Auto Read speed:Max
Digital playback: Yes / Use YADB: Yes / Get cover art: No / Calc replay gain: Yes / Copy volume: 32767
Eject after ripping: No / Play sound after ripping: No

Burning / Drive E: PLEXTOR CD-R PX-W2410A Addr: 0:0:0 Speed:24 MaxSpeed:24 BurnProof:Yes
Test mode: No / Eject after writing: Yes / Direct decoding: Yes / Write CD-Text: No
Use playback settings: No / Normalization: None

billtr · « **Reply #7 on:** February 04, 2004, 07:05:22 pm »

New gpf after restart:
MEDIA JUKEBOX caused an exception 10H in module MEDIA JUKEBOX.EXE at 0167:005aea5c.
Registers:
EAX=00727f54 CS=0167 EIP=005aea5c EFLGS=00010202
EBX=0098c880 SS=016f ESP=0098c7a8 EBP=0098c7ec
ECX=00727f40 DS=016f ESI=00000001 FS=183f
EDX=000001fb ES=016f EDI=00000040 GS=0000
Bytes at CS:EIP:
d8 0d f8 1a 69 00 83 ec 08 8d 44 24 20 c6 44 24
Stack dump:
013b9030 0098e1f0 00000001 0098c7e0 013cae30 013cae90 00727f54 013cae30 013cae60 00401ffc 013b9030 00000001 013ca040 0098e198 00667978 00000001

JimH · « **Reply #8 on:** February 04, 2004, 07:09:03 pm »

Same disk?

Did you reboot?

How about other disks?

billtr · « **Reply #9 on:** February 04, 2004, 07:13:18 pm »

I rebooted. Tried disk #1 from "The Very Best Of Chicago". This gpf resulted:
MEDIA JUKEBOX caused an exception 10H in module MEDIA JUKEBOX.EXE at 0167:005aea5c.
Registers:
EAX=00727f54 CS=0167 EIP=005aea5c EFLGS=00010202
EBX=0098c880 SS=016f ESP=0098c7a8 EBP=0098c7ec
ECX=00727f40 DS=016f ESI=00000001 FS=2997
EDX=00000202 ES=016f EDI=00000040 GS=0000
Bytes at CS:EIP:
d8 0d f8 1a 69 00 83 ec 08 8d 44 24 20 c6 44 24
Stack dump:
013aa590 0098e1f0 00000001 0098c7e0 013c6180 013c3d20 00727f54 013c6180 013c3cf0 00401ffc 013aa590 00000001 013c5130 0098e198 00667978 00000001

JimH · « **Reply #10 on:** February 04, 2004, 07:21:12 pm »

You may have something else going on.

Try reinstalling.

billtr · « **Reply #11 on:** February 04, 2004, 07:24:14 pm »

You mean uninstall, reboot, install, reboot then re-register, correct?

JimH · « **Reply #12 on:** February 04, 2004, 07:34:44 pm »

Just reinstall.

billtr · « **Reply #13 on:** February 04, 2004, 08:45:37 pm »

I had to reinstall when upgrading, because the updater could not connect to J River. So, this time I'll do the whole wad.

billtr · « **Reply #14 on:** February 04, 2004, 10:11:16 pm »

Complete. Read Chicago OK except for track 19. When attempting a re-read I got this gpf:
MEDIA JUKEBOX caused an invalid page fault in
module <unknown> at 0000:020753a2.
Registers:
EAX=00000000 CS=0167 EIP=020753a2 EFLGS=00010202
EBX=00000000 SS=016f ESP=0098b278 EBP=0098b298
ECX=7f2da241 DS=016f ESI=020753a2 FS=214f
EDX=800074c8 ES=016f EDI=00000574 GS=0000
Bytes at CS:EIP:

Stack dump:
7f2d7cd2 00000574 00000046 00000000 0098b910 00000574 006d2630 00000001 0098b320 7f2d7fc9 00000800 00000574 00000046 00000000 0098b910 7ffffffd

billtr · « **Reply #15 on:** February 04, 2004, 10:12:55 pm »

Trying the Carpenters disk was OK, read it all.

John Gateley · « **Reply #16 on:** February 04, 2004, 10:17:16 pm »

If I understand right, now you have no problem with YADB, but are having a problem ripping, correct?

I'd start looking at hardware failure, with memory being a good thing to check, also make sure all fans are still running and nothing's to hot.

j

billtr · « **Reply #17 on:** February 05, 2004, 01:20:32 am »

No problems ripping, have not tried it yet. Problem was when attempting to read info on the same disk from YADB it hung. Unfortunately the Chicago disk track 19 is missing from the one I picked.

This is a minor problem. The big problem is solved. For the future, I guess YADB has to get a bit more robust and flexible.

I will try ripping soon.

Thanks for your help!

JimH · « **Reply #18 on:** February 05, 2004, 07:18:35 am »

Quote from: billtr on February 05, 2004, 01:20:32 am

This is a minor problem. The big problem is solved. For the future, I guess YADB has to get a bit more robust and flexible.

I don't think you were seeing a YADB problem. That's just when it happened.

billtr · « **Reply #19 on:** February 05, 2004, 09:15:41 am »

I would disagree. I have been running Media Center since December, sometimes for 12 hours a day, playing various CD's and mp3s. It has GPF'd a few times, mostly when I did something strange like try to remove a CD quickly before it had a chance to read it. Media Player 8 was a dog, GPF'd more frequently than a stable application should have.

The YADB issue was a dead ringer. Put the CD in, play it with no problem. Allow YADB to do its thing and the gpf occurred. From a software testing perspective I would say there was a 100% correlation between going for YADB and the gpf.

Now as to the root cause, it may lie in the old media library. Someone suggested I reinstall. That is what I did the first time I upgraded. The gpf still occurred. It was only when I uninstalled completely (clearing registry and all library files), restarted, reinstalled that I got it to work at all.

JimH · « **Reply #20 on:** February 05, 2004, 09:25:12 am »

That could have been something like a bad disk sector or memory error. Lots of other possibilities. YADB has been working perfectly in the version you're using and you hadn't switched versions.

Other changes on the machine?

billtr · « **Reply #21 on:** February 05, 2004, 09:34:05 am »

No. I have a 30Gb drive, 7Gb free, the info dump showed 96Mb free, I had rebooted so no memory leaks could have interfered. I am not having any problems with the machine on startup or during operation all day.

I do a lot of software development and database work, this machine has been a rock from the day it was turned on. Applications do not gpf on it. I'm a music nut, so almost always have something playing.

billtr · « **Reply #22 on:** February 05, 2004, 10:13:47 am »

Another gpf. This time on submitting information on an album to YADB. It did not find it, gave me the dialog, I filled out all the fields, submitted it, dialog saying that data was being sent to YADB popped up then gpf.

Lost all my typing.

Here is the gpf:
MEDIA JUKEBOX caused an invalid page fault in
module PLAYBACKENG.DLL at 0167:01f31c65.
Registers:
EAX=020f372c CS=0167 EIP=01f31c65 EFLGS=00010202
EBX=00000000 SS=016f ESP=0098aa1c EBP=0098aa24
ECX=033e1b98 DS=016f ESI=020f36f0 FS=111f
EDX=00000008 ES=016f EDI=00000000 GS=0000
Bytes at CS:EIP:
8b 01 8d 55 f8 52 68 f8 79 f8 01 51 ff 10 85 c0
Stack dump:
020f36f0 020f36f0 0098aa58 01f36b19 020f372c 00000001 020f2800 020f36f0 020f381c 020f36f0 020f3550 01f36ac3 0098aa88 01f69b42 00000002 0098aa94

JimH · « **Reply #23 on:** February 05, 2004, 10:17:40 am »

Bill,
Can you look more closely at your PC? Network problem? Internet problem?

Windows up to date? IE/Tools/Windows Update.

Jim

billtr · « **Reply #24 on:** February 05, 2004, 10:47:14 am »

Jim,
I am a professional programmer. I do extensive networking, database stuff, programming, word and excel for requirements documents and financial work. I have DSL going through a nat router.

My machine does not gpf. The last 3 weeks I have used it 15 hours per day, typically in the evenings it is on and I am working for 2-4 hours. Weekends are often all weekend. I've had it for over a year. If it gpf'ed I would junk it, or go bankrupt.

This is the first application I have run in a very long time that gpf's. Its predecessor was worse.

The software is having a problem when it goes after YADB. The YADB database itself is probably fine. Without looking at the code, what it looks like to me is a lack of exception handling in the data manipulation software, or a timing issue where something aborts instead of gracefully exiting if it does not get what it wants.

KingSparta · « **Reply #25 on:** February 05, 2004, 11:02:44 am »

there was a bug in the YADB code at one time that when some cd's would access YADB it would crash MC9

This was fixed that i know of since they got it to work on the 20 or so CD's YADB\MC would crash on.

I would dump the windows 98 if you can.

i think some users with windows 98 have more problems than other maybe due to the skins that now can not be turned off. with a already unstable platform and maybe old video drivers it may not take much to push windows 98 over the side.

billtr · « **Reply #26 on:** February 05, 2004, 11:07:13 am »

All critical updates installed. I do not have the .net framework. I noticed the Internet Explorer Navigation Sound Update which was optional, I installed it.

billtr · « **Reply #27 on:** February 05, 2004, 11:10:25 am »

Yes, I am thinking of going Lindows OS. Pretty tired of Microsoft. I had to completely reinstall XP on my son's new computer.

So far in my experience the Win 95/98 platform is the best MS has offered. Win2k, XP are bloatware that are fat targets for hackers, offering little in the way of real improvement.

billtr · « **Reply #28 on:** February 05, 2004, 11:14:29 am »

I do have a strange video card. It's the old 16Mb voodoo card. Do you think that would be doing it? I have no problem with skins and visualizations, only yadb.

KingSparta · « **Reply #29 on:** February 05, 2004, 11:24:35 am »

Dang 16 Megs, that voodoo card is rather old, if you had another card you could try it out.

Some users sometimes get a GPF's using windows 98 with older video cards and or video drivers.

This was also a problem back with Media Jukebox 6 when it used another skinning engine, and that was about the same date as when the voodoo 16meg cards were out.

I am not sure if this would be the problem but it could be who knows.

Windows XP is more stable than windows 98 without a doubt, even if it may be bloat ware. You can turn off the bloat ware options and get more speed out of windows XP.

With all Microsoft Os's they are a bigger target so more viruses and Trojans are made for it. It is not like the others do not have there own problems.

billtr · « **Reply #30 on:** February 05, 2004, 11:31:35 am »

King Sparta, you have been very helpful. I won't let this degenerate into an OS wars column ;-).

I have a Nividia 64Mb card around that is 2 years old, taken out of my wife's box when I supercharged it. It is not compatible with the latest in hotshot games, but it is a solid card. It lacks the video capture and audio input of the 3dFx, but I have not used those features much and I am concerned that it is an ancient, unsupported beast.

I will give it a shot this weekend and report back.

KingSparta · « **Reply #31 on:** February 05, 2004, 11:58:33 am »

Quote

I won't let this degenerate into an OS wars column ;-)

I was hoping for the best, I might have had to whip out my IBM punch cards on you.

I hope it works out for you

ATI 9700, 128 Megs Here, really nice graphics, i think there has been one or two new cards out since I bough this card last year. Really nice card to handle all the Death matches etc....

INTERACT FORUM

Author Topic: Cannot Connect to YADB (Read 4090 times)