I'm getting the error "Error retrieving DMS drive id" after installing 3.92. Anyone have 3.92 working with a hacked drive?
I installed 3.76 over 3.92. PMM would start, show a message that I had to upgrade to the latest version, and quit. I then uninstalled 3.76, and reinstalled it. Now it works the way it was before. 3.92 looked nice, though. Seems as though they incorporated Phatvoice into it as well as adding better unicode support in ogg files.
Hi,
Well, 3.92 works for me. I also installed over 3.76 (didn't want to lose any settings) and I use it with a hacked 80 GB drive with no problems.
On the other hand I know that my drive does have a signature on it in the first 1 meg (copied from my original 20 gig drive), so although it is not valid for the 80 gig unit, it may be keeping the software happy. Has anyone tried on a drive without any signature?
I'll check and see if mine has that signature. Is it added by the hack cd? If not can you point me to a link to add it?
Thanks.
Normally the hack CD will copy the drive signature area from the old DMS disk drive to the new disk drive, although the signature is not needed by a fully hacked box. Or you can do it by hand using a block copying function under Windows or Linux. There is a program called DD which can be used to do this.
See this link, but also use the search tool to find more info on the forum
http://forum.phathack.com/cgi-bin/yabb2/YaBB.pl?num=1123119033/9#9
Of course, it might not be working for some other reason...
be warned that if you use DD to copy the first 1 meg of the drive over you'll have to repartition and reformat the drive using the hack cd because the partition table is also included in that 1 meg section and will not match your new drive size. so anything you have on the drive will have to be re copied.
Thanks judb - I had forgotten that very important point - it's been too long since I played with it.
or if you do it like this it should leave your partition table intact:
dd if=originaldrive of=keys.dat bs=512 skip=1 count=2047
then to the new drive
dd if=keys.dat of=newdrive bs=512 seek=1 count=2047
If course, it could still blow up your new drive so dont blame me if you try it and it doesn't work. In linux originaldrive and newdrive will be something like '/dev/sda' on windows something like '\\\\.\\PhysicalDrive9' where 9 is the number assigned to it in disk management as drive ID
Thanks Sam. I tried that on my hacked DMS with a keys.dat from my original DMS. No change. I still get the error retrieving DMS id message from PMM 3.92. I'm wondering if it's because I installed Ubuntu on my DMS and those signature files are gone? I don't think that's it.
Next, I found a drive-sig-1mb.bin from my original hack and dd'ed that over to my new DMS with dd if=c:\drive-sig-1mb.bin of=\\.\physicaldrive5 bs=512 count=2048 3.92 still barfs. Oh well. Any other ideas?
I am getting the same message using an unhacked drive in a drive enclosure. Anyone ever get to the bottom of this?
Quote from: Irish Eyes on March 20, 2008, 10:06:12 AM
I am getting the same message using an unhacked drive in a drive enclosure. Anyone ever get to the bottom of this?
I take it that you mean a drive from an original DMS but used in a third-party disk box with its own USB to IDE chip? In that case you may see this message. I have found that the USB to IDE chips vary in what they allow Phatnoise Media Manager to access. I don't think we have a list of chips which work and those that don't. Even if we had a list, it would be hard to choose enclosures on the basis of the chip within. I can only suggest trying a different enclosure from a different manufacturer, or using a supported DMS cradle.
Thanks S80.
I have an original cradle on the way via ebay, I'll try it out in that.
Pete
UPDATE
S80 was spot on. Tried the drive in the cradle and all was well. Incidentally Music Manager is also now able to eject the drive - I previously got the "unable to eject drive... virus software etc" message.
Now if I could get Phatmac to work properly I would be very happy!
Cool 8) Thanks for the feedback.
Glad you got it sorted.
Les.
Just for my clarification, if you get the sig file from the original dms and copy it to the new drive (based on instructions here) with a supported cradle, then you should not get the PMM 3.92 drive id error? I haven't been able to get any version of Media Manager to recognize my 120 gb drive, but I haven't tried my original USB 1.1 cradle, only USB 2.0. Is this correct or am I confused ??? Thanks!
Kegger, the answer to your question is probably not, and I don't think we've definitively identified the issue that causes the error. I have a WD 80 GB drive that works with 3.92, no problem. I also have Samsung 120 and 160 GB drives created using exactly the same methods that refuse to work with 3.92 (not to mention a WD 250 GB drive that has a whole other set of issues). You may find the same drive more cooperative in a 1.1 cradle, but not necessarily. Whatever the issue is, it doesn't seem to be the sig file, or at least not just the sig file. It may also have to do with the chipsets of the drive or the USB cradle, or both.
mark: you were going to do some tests with PhatHack MM, did you ever get round to doing this?
Yes, I tried it just now. No issues transferring tracks to the 250GB using Phathack MM, just a bit slow. It doesn't seem to generate voice prompts, is that supposed to be working yet?
There are two issues there, both easily fixed both in the options screen.
Select the DMS device, and set the DO NOT TRANSCODE TO THIS DEVICE flag to stop tthe program transcoding your files to the default format/bitrate and also make sure the Voice options are set.
I think there's an issue if you haven't been into the options screen before causing the voice prompt thing, but once you save I understand that's resolved.
I checked both options, it still isn't generating the prompts. The program also crashes very frequently, particularly whenever I try to import music. Anyway, we're probably wandering off-topic here, so I can send you an e-mail of the issues I experienced if you like.
Yes please, send the issues over.
Also make sure you are on the latest version 0.8f....