Hack to fix the "Error retrieving DMS drive id" with PMM 3.92 problem

[zoltar]

I guess it's just bad luck picking the Samsung drive and this Chieftech enclosure.

[Death_Box]

Thank you so much for the tip. Really a good community.
It'll be better in French for me  . But  sometimes my son helps me when the post is too difficult to understand.
But never to write...
bonne chance

[hildeand]

Hi, I have a Fujitsu 80 GB original PhatNoise drive that no longer gets detected by PMM 3.92 (but does by Phatnoise Music Manager). I have been looking at this thread and seeing if it applies to my problem, but the Fujitsu drives seem to be on the inclusion part of the dll list? I also tried a few dll editors, but I could not make heads or tales out of it, let alone find the drive entries and change them...

Anyone who had this issue with a Fujitsu drive and could offer some advice?

Hilde

[Terry_Kennedy]

Hi, I have a Fujitsu 80 GB original PhatNoise drive that no longer gets detected by PMM 3.92 (but does by Phatnoise Music Manager).

That's odd - I can't see them blacklisting their own drives.

It could also be from an unrecognized cradle. Are you using a real PhatNoise cradle? What, exactly, does it say on the bottom? Under which OS? And, did you need to install any drivers to make the cradle work?

[hildeand]

I also find it strange - it does happen to two of their own, native drives as well as a hacked 160 GB drive. I run XP (in Parallels on a Mac system), using PMM 3.92, USB 2 cradle with no specific drivers installed. This has worked without problems before, but now I get the following message "Error retrieving DMS drive id" followed by something along the lines of "One or more files on the drive could be open (antivirus, explorer, etc. please make sure all files are closed".

Hilde

[Terry_Kennedy]

I run XP (in Parallels on a Mac system), using PMM 3.92, USB 2 cradle with no specific drivers installed.

Have you upgraded either MacOS or Parallels since it worked reliably? Media Manager 3.92 checks both the USB vendor/product string and the disk drive IDENTIFY data.

Can you go into Device Manager (right-click My Computer, select Properties, Hardware tab, Device Manager button), double-click on the device, select Details, select Hardware IDs from the drop-down list, and post what you see here?

Likewise for the displayed name (in Device Manager) of the hard drive?

I posted a list of the supported USB IDs as well as the supported and blacklisted drive list over here.

[hildeand]

Hi, thanks for trying to help with this!

I really cannot say when I last used PMM 3.92 and it worked, as I have used PhatMac for quite some time. It's only after I realize that PhatMac seems to mess up the DMS database and thus give poor library browsing performance that I have tried to see if using PMM would help. Thus, it is quite possible, in fact I am quite certain, that both Parallels and OS X have been updated since I can say for sure PMM worked with the DMS...

Anyway, I've checked Device Manager, and I attach two screen captures of the hardware id and device name. For sure, this is a supported drive as it is the orginal 20 GB DMS that came with my Audi PB years ago, so something is making PMM identify it as a "disk non-grata"...

If you can make something out of the screen shots, I'd appreciate any input!

Bjorn

[hildeand]

Hi,

Suddenly, Mac OS X is in a good mood and detects the DMSs using the cradle (as opposed to a USB caddy). And now the drives are identified by PMM 3.92!

I even tested running the exact same DMS through the USB caddy and then there is error retrieving the drive id. So it seems somehow being connected to Windows through the USB caddy causes this on my system.

Hilde

[lee]

Thanks for the hint. Almost one year with no access due this problem, I solved today. Open the DeviceDMS.DLL, use a Hex editor (find xvi32 on Google), open the file, search for SAMSUNG and change the S to X (will be XAMSUNG). Save and restart the PMM.