Right, so I recently clean installed my computer and I have the original PMM 2.0 disc. Is there anywhere I can get the 2.30, or should I use the other manager that I have read about?
Thanks-
Go to my alternative PhatNoise website: www.phatnoise.org
You can get the non-activation version of PMM 2.30
Quote from: VorTechS on December 01, 2007, 08:59:54 AM
Go to my alternative PhatNoise website: www.phatnoise.org
You can get the non-activation version of PMM 2.30
Many thanks ... and great work on the Hack tool.
Quote from: VorTechS on December 01, 2007, 08:59:54 AM
Go to my alternative PhatNoise website: www.phatnoise.org
You can get the non-activation version of PMM 2.30
I wasn't able to find that file, so I downloaded the media manager 3.92, but I can't seem to get my DMS to show up on that. Does it function in the same was as the music manger? If so, do you know what may be preventing the DMS from showing up? I was able to connect to the DMS via Music Manger 2.0 just fine.
Thanks
In terms of locating the DMS, yes it works the same - but it will perform an upgrade on your eixsting database structure.
Assuming the DMS is unchanged since the last time you had the software and it was working, check under Windows to ensure that the two partitions (drives) show up.
These are PHTSYS and PHTDTA.
While researching other information I found that you made need to download the driver for your cradle after upgrading to different versions of Media manager:
http://www.phatnoise.com/downloads/download_pmmsw.aspx
Not sure if this is your problem or not. Good luck. This is my first post so I hope it is helpful.
Quote from: VorTechS on December 03, 2007, 08:53:37 AM
In terms of locating the DMS, yes it works the same - but it will perform an upgrade on your eixsting database structure.
Assuming the DMS is unchanged since the last time you had the software and it was working, check under Windows to ensure that the two partitions (drives) show up.
These are PHTSYS and PHTDTA.
For some reason I can't get the PHTDTA drive to show up anymore. Very annoying. It mounts on my Mac just fine.
Did you follow the instructions in the documentation from the PhatMac site?
I recall reading that you have to avoid certain prompts the Mac will give you - otherwise it might cause problems with the partitions?
Other than that I can only suggest using the hack tool to wipe the disk and re-create the partitions.
I have never used PhatMac, but I use PMM through VMWare Fusion on my mac.
The drive still works fine in the car which makes me doubt if anything is wrong with the partitions. It has always taken a long time to mount the PHTDTA drive, but now it simply never does, but it does freeze windows up which makes me think it is trying to mount it.
Even more odd, nothing has changed since the last time I successfully synced and ejected.
If the PHTSYS drive mounts okay (even through VMWare) it's not likely to be a driver issue, but could be a pointer to a problem with the filesystem. Try a defrag/checkdisk and see if things improve.
Quote from: VorTechS on December 08, 2007, 08:49:36 AM
If the PHTSYS drive mounts okay (even through VMWare) it's not likely to be a driver issue, but could be a pointer to a problem with the filesystem. Try a defrag/checkdisk and see if things improve.
On the virtual drive or on the phatbox drive?
I would try to eliminate VMWare from the equation, although it shouldn't matter - and I would do the check on both 'drives' PHTSYS and PHTDTA.
I only have a Mac so VMWare is a must. I tried chkdsk on all relevant drives and still I was having the same issue. I got a message: "unknown error occurred while accessing E:\CurrentSetup.xml"
Also, even when the PHTDTA finally mounts, I can't actually open any of the files on it. I think something may be messed up with the partition. When I plug in my other DMS drive (I have 2), it pops right up and Media Manager works fine.
Notably, it still works fine in the car.
I think this DMS may be doomed for windows use so I am gonna try PhatMac real quick and if doesn't work, I will reformat and start at the top.
Crap, now things have really gone to hell. Tried PhatMac, but for whatever reason even though the disk was empty it was showing like 25 GB of space not available. I reformatted the drive and tried to run the PhatHack 2.10 tool again, but it "failed creating DMS." Couldn't find the log file, but now I have no idea what to do.
Quote from: Nixlimited on December 09, 2007, 02:03:18 AM
Crap, now things have really gone to hell. Tried PhatMac, but for whatever reason even though the disk was empty it was showing like 25 GB of space not available. I reformatted the drive and tried to run the PhatHack 2.10 tool again, but it "failed creating DMS." Couldn't find the log file, but now I have no idea what to do.
Were are you located? Perhaps there's another forum member near you who could help (or at least re-initialize the DMS on their Windows system).
The log file is located in My Documents\PhatHack Media Manager\Logs
Just attach whatever files you have there except startup_sequence.txt
Here is the relevant stuff from the DMS log:
PhatHack Media Manager DMS Creator
---------------------------------
Date: 12/8/2007
Time: 19:16:04
LogDir: C:\Documents and Settings\Administrator\My Documents\PhatHack Media Manager\Logs\
ToolsPath: C:\Program Files\PhatHack\PhatHack DMS Tools\DMS_Utils\
Retrieving WMI device snapshot...
Win32_Drive List
----------------
Starting device evaluation:
Determining device signature...
done.
Disk ID: 0
Disk Name: VMware, VMware Virtual S SCSI Disk Device
PnP Device: SCSI\DISK&VEN_VMWARE_&PROD_VMWARE_VIRTUAL_S&REV_1.0\4&5FCAAFC&0&000
Disk Unique ID (not serial!): C754C754
Partitions List
---------------
Partition: Disk #0, Partition #0
Drive: C:
Serial #: 880A6E70
Device evaluation complete.
Next device evaluation:
Determining device signature...
done.
Disk ID: 1
Disk Name: USB-HS WDC WD800BEVE-00 USB Device
PnP Device: USBSTOR\DISK&VEN_USB-HS&PROD_WDC_WD800BEVE-00&REV_0.01\7&7B490D4&0
Disk Unique ID (not serial!): 365A882E
Partitions List
---------------
Partition: Disk #1, Partition #0
Drive: E:
Serial #: 39EF1AE4
Device evaluation complete.
Getting DMS Disk ID from snapshot...
Disk ID is ...1
Opening device through kernel....
....device opened successfully.
Checking for existing partitions...
...partitions found, wiping the disk layout...
Creating new DMS partitions...
....created successfully.
Starting WMI Cycle [waiting for WMI to mount partitions and assign drive letters]...
Checking mounted drives for disk...
[Cycle 1] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 2] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 3] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 4] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 5] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 6] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 7] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 8] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 9] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 10] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 11] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 12] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 13] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 14] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 15] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 16] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 17] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 18] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 19] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 20] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 21] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 22] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 23] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 24] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 25] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 26] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 27] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 28] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 29] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 30] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 31] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 32] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 33] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 34] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 35] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 36] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 37] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 38] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 39] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 40] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 41] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 42] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 43] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 44] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 45] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 46] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 47] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 48] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 49] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 50] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 51] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 52] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 53] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 54] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 55] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 56] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 57] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 58] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 59] Re-checking mounted drives for disk...
Re-checking WMI device list....
[Cycle 60] Re-checking mounted drives for disk...
Re-checking WMI device list....
Completion time: 19:23:03
It seems that although the disk accepted the partition request, WMI failed to recognise that two partitions were present within 60 iterations of checking + the starting 30 seconds delay ... which should have been more than enough time to locate the partitions successfully.
I'm assuming the machine that you are running this on performs adequately, and then when you used to mount the disks it didn't take too long to locate the partitions?
Gut feeling says the disk is about to go, and you might be better looking for a new disk.
It seems to be the same issue I was having with mounting it to sync music i.e. that it took forever to mount the second partition ( PHTDTA. What's odd is that it mounts immediately on my Mac (outside of VMWare).
The disc is brand new, though, so it would be surprising for it to go this quickly., but you may be rightt
I've tried the tools in VMWare with my 60GB DMS (one day I'll actually get to use it!) using a Kenwood cradle (USB 1.1) and although I get the same 'really long time to mount PHTDTA' issue, I have no problems running the partition/formatting.
At the point where the tools stop, you should have a disk with two partitions - neither of them formatted.
You could use 'Computer Management' within windows to do the formatting and see if your situation improves.
You could also try a low level format to just double check there are no other underlying issues with the disk.
Quote from: VorTechS on December 10, 2007, 08:04:32 AM
I've tried the tools in VMWare with my 60GB DMS (one day I'll actually get to use it!) using a Kenwood cradle (USB 1.1) and although I get the same 'really long time to mount PHTDTA' issue, I have no problems running the partition/formatting.
At the point where the tools stop, you should have a disk with two partitions - neither of them formatted.
You could use 'Computer Management' within windows to do the formatting and see if your situation improves.
You could also try a low level format to just double check there are no other underlying issues with the disk.
I may plug the cradle (usb 2.0) into my tuning laptop (win xp) and see if I can reformat and at least get the DMS functional again. Here's the problem: there seems to be no option in the PhatHack tools to prepare a disk that is already formatted.
There is, it's the 'Update Firmware' option.
Select 'Create New DMS' then choose your firmware, and other relevant options. And instead of clicking on 'Create New DMS' to do the partitioning, click on 'Update Firmware'.
If you don't see the button 'Update firmware' look for the dropdown on the far right of the toolbar (known issue being resolved in next build)
So I tried everything on a PC last night (formatted, ran PhatHack tools, then tried to use media manager). I seemed to get through the PhatHack tools fine, but then I got the familiar "unable to access e:/CurrentSetup.xml", and I also got a Windows Delayed Write error on both drives. I have to believe that the drive has gone bad. Maybe this drive wasn't tough enough to be in the car ... who knows. Hope I can return it.
Have any suggestions on anything I should try before returning it?
Have any suggestions on what type of drive to get? This is an 80GB Maxtor.
Thanks-
Quote from: Nixlimited on December 11, 2007, 07:50:49 PMHave any suggestions on what type of drive to get? This is an 80GB Maxtor.
As a general rule, do not get another Maxtor. No manufacturer is 100% reliable, but Maxtors are not only particularly unreliable, they have even been known to cause hardware conflicts. I believe the original Phatnoise drives were all Toshibas, so that is one way to go.