Windows DMS Hack Tools v2.10 - Bug Reports

[moedope]

ok, thanks for the quick reply but i was searching the forums and saw another post with a similar problem and i changed the hdd like the other qerman guy did and presto it work, gest the 40 gigs is kinda incompatible or damaged oh well a 30 gig is enouhg 4 now

[urchrzan]

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.

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.

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.  When the PMM recognized the new DMS I ran a complete refresh on all the music files and database to synch everything up.

So I have the new DMS ready to use but I have to hack the box first.  I will try the hack process with the second PhatNoise DMS I have (the one I got with the second PhatBox) and see if that will make a difference.

Any suggestions or advice will be much appreciated?

Here's my system configuration:
Win XP Home, PMM 3.92, PhatHack Tools 2.10, original PhatBox DMS is 20GB, DMS Cradle is "DMS-USB2 rev-"

Rob

[VorTechS]

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!

[urchrzan]

Thanks! I just sent you my e-mail address.

Regarding seeding the PHTDTA partition with a sample playlist, what you said is exactly what I meant. Sorry for being unclear.

Rob

[Hankle]

I ran PhatHack in DMS Tools mode to try and repair my DMS, which I accidentally deleted the partitions on.  I selected Install Non-hacked Firmware and Reflash Box with Firmware.  But when I clicked Repair DMS (FULL), I get an Unhandled Exception:

************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
   at StandAloneDMSHackWizard.frmStartupWizard.RepairFormat(String LogDir, String NewDMSLogFile, Boolean PHTSYSOnly)
   at StandAloneDMSHackWizard.frmStartupWizard.RepairDMS(Boolean PhtSYSOnly, String LogFile, String FunctionTitle)
   at StandAloneDMSHackWizard.frmStartupWizard.btnRepairFULL_Click(Object sender, EventArgs e)
   at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
   at System.Windows.Forms.ToolStripButton.OnClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
   at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
   at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
   at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.ToolStrip.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
StandAloneDMSHackWizard
    Assembly Version: 2.12.0.0
    Win32 Version: 0.0.2.12
    CodeBase: file:///C:/Program%20Files/PhatHack/PhatHack%20DMS%20Tools/StandAloneDMSHackWizard.exe
----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 8.0.0.0
    Win32 Version: 8.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
System.Configuration
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
PhatUnzip
    Assembly Version: 1.3.3.0
    Win32 Version: 1.3.3
    CodeBase: file:///C:/Program%20Files/PhatHack/PhatHack%20DMS%20Tools/PhatUnzip.DLL
----------------------------------------
VorTechS.DMSTools
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.0.0
    CodeBase: file:///C:/Program%20Files/PhatHack/PhatHack%20DMS%20Tools/VorTechS.DMSTools.DLL
----------------------------------------
DMS
    Assembly Version: 1.0.0.1
    Win32 Version: 1.0.0.1
    CodeBase: file:///C:/Program%20Files/PhatHack/PhatHack%20DMS%20Tools/DMS.DLL
----------------------------------------
UsbEject
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Program%20Files/PhatHack/PhatHack%20DMS%20Tools/UsbEject.DLL
----------------------------------------
PhatDriveSnapshot
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Program%20Files/PhatHack/PhatHack%20DMS%20Tools/PhatDriveSnapshot.DLL
----------------------------------------
Bass.Net
    Assembly Version: 2.3.1.8
    Win32 Version: 2.3.1.8
    CodeBase: file:///C:/Program%20Files/PhatHack/PhatHack%20DMS%20Tools/Bass.Net.DLL
----------------------------------------
Interop.WbemScripting
    Assembly Version: 1.2.0.0
    Win32 Version: 1.2.0.0
    CodeBase: file:///C:/Program%20Files/PhatHack/PhatHack%20DMS%20Tools/Interop.WbemScripting.DLL
----------------------------------------
CustomMarshalers
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_32/CustomMarshalers/2.0.0.0__b03f5f7f11d50a3a/CustomMarshalers.dll
----------------------------------------
PhatPartition
    Assembly Version: 2.0.3049.16715
    Win32 Version:
    CodeBase: file:///C:/Program%20Files/PhatHack/PhatHack%20DMS%20Tools/PhatPartition.DLL
----------------------------------------
msvcm80d
    Assembly Version: 8.0.50727.762
    Win32 Version: 8.00.50727.762
    CodeBase: file:///C:/Windows/WinSxS/x86_microsoft.vc80.debugcrt_1fc8b3b9a1e18e3b_8.0.50727.762_none_24c8a196583ff03b/msvcm80d.dll
----------------------------------------

Any ideas?
-Hank

[VorTechS]

Interesting, haven't seen one of these for a while!  Would you be willing to try out the new tools?