Rob,
Thanks for the comments. Please see the answers in-line.
First let me just say: I'm loving the PhatHack Tools. It's a great idea and an awesome utility for the PhatBox. I have two PhatBoxes: one original BMW setup and another a VW version converted to work with BMW. Both have been working flawlessly. I bought the first PhatBox for my 3er BMW in 2001 and have been enjoying it ever since. But the original DMS from the first PhatBox is going bad so I decided to upgrade.
This is a known issue, send me your e-mail address and I'll send you the newest version of the tools before I make them public which will resolve this problem.
I used the PhatHack Tools to hack the original DMS, but when I put it into the PhatBox it just played as usual. I tried again by repeating the process but with the same results.
I also tried creating a new DMS and ran into what I would consider a bug. The new HD gets partitioned and the partitions get formatted correctly, but no files are copied to the PHTSYS partition. Even though the software reports copying files and firmware onto the DMS. I wonder where do these files end up, if at all? I did notice that the "CurrentSetup.xml" file gets copied to the root of the C: drive (?!) but that's about it. Rerunning the New DMS process again on the same DMS fixes the problem and now all the correct files do appear on the DMS PHTSYS partition.
I tried this on two harddrives: first on the Western Digital 80GB WD800BEVE drive then on a Seagate 80GB ST980815A. Both are ATA-6 drives and I experienced the same exact issue with both of them.
Yep, there was a bug with un-partitioned drives causing this exact issue. It has been fixed in version 2.11 of the tools mentioned above.
Turns out the PMM 3.92 which I have installed on my system only works with the Seagate drive and not with the WD drive. As strange as it is to me, I decided to just return the WD drive and stick with the Seagate one. Oh, I also had to copy all the database, etc. files from the PHTDTA on the original drive to the PHTDTA on the new drive to make it work in PMM. This may be something that could be added to the PhatHack Tool New DMS process.
This is not likely to happen. What I have done in v2.12 is modified it to create a single playlist with the custom PhatHack startup sound so that a new DMS can be tested in a hacked PhatBox without worrying about existing playlists or any manual intervention from the user. Copying all the media from your existing DMS to then stick it in the PhatBox and find out it doesn't work would be rather frustrating given it would take a while for the file copy!
