PhatHack

The Hacking Hoedown => PhatBox Hacking => Topic started by: sbingner on September 26, 2007, 08:47:03 am

Title: Windows DMS Hack Tools v2.10 - Bug Reports
Post by: sbingner on September 26, 2007, 08:47:03 am
Duh post bug schtuff here
Title: Re: Windows DMS Hack Tools v2.4 - Bug Reports
Post by: Terry_Kennedy on September 28, 2007, 12:52:18 am
Duh post bug schtuff here

I get "Unhandled exception has occurred..." - Converstion from string "" to type 'Integer' is not valid.

This is on Windows XP (all updates) with a WD2500BEVE 250GB drive.

The whole mess is:

Code: [Select]
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.InvalidCastException: Conversion from string "" to type 'Integer' is not valid. ---> System.FormatException: Input string was not in a correct format.
   at Microsoft.VisualBasic.CompilerServices.Conversions.ParseDouble(String Value, NumberFormatInfo NumberFormat)
   at Microsoft.VisualBasic.CompilerServices.Conversions.ToInteger(String Value)
   --- End of inner exception stack trace ---
   at Microsoft.VisualBasic.CompilerServices.Conversions.ToInteger(String Value)
   at VorTechS.DMS_Hack_Wizard.DMS_PhatHack.NewDMS(String DriveLetter, StorageDevice DMSDevice, String StartupPath, Boolean& RequiresLBAInstall)
   at VorTechS.DMS_Hack_Wizard.HackWizard.NewWizard(String DriveLetter, Form OwnerForm, String StartupPath, StorageDevice DMSDevice, Boolean& LBARequired)
   at StandAloneDMSHackWizard.frmStartupWizard.Start()
   at StandAloneDMSHackWizard.frmStartupWizard.btnStart_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.832 (QFE.050727-8300)
    CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
StandAloneDMSHackWizard
    Assembly Version: 2.4.0.0
    Win32 Version: 0.0.2.4
    CodeBase: file:///C:/Program%20Files/PhatHack/PhatHack%20DMS%20Tools/StandAloneDMSHackWizard.exe
----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 8.0.0.0
    Win32 Version: 8.0.50727.42 (RTM.050727-4200)
    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.832 (QFE.050727-8300)
    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.832 (QFE.050727-8300)
    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.832 (QFE.050727-8300)
    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.832 (QFE.050727-8300)
    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.832 (QFE.050727-8300)
    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.832 (QFE.050727-8300)
    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
----------------------------------------
DMS
    Assembly Version: 1.0.0.1
    Win32 Version: 1.0.0.1
    CodeBase: file:///C:/Program%20Files/PhatHack/PhatHack%20DMS%20Tools/DMS.DLL
----------------------------------------
DMS Hack Wizard
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Program%20Files/PhatHack/PhatHack%20DMS%20Tools/DMS%20Hack%20Wizard.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.42 (RTM.050727-4200)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_32/CustomMarshalers/2.0.0.0__b03f5f7f11d50a3a/CustomMarshalers.dll
----------------------------------------
System.Web
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.832 (QFE.050727-8300)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.Web/2.0.0.0__b03f5f7f11d50a3a/System.Web.dll
----------------------------------------
PhatPartition
    Assembly Version: 1.0.2748.25673
    Win32 Version:
    CodeBase: file:///C:/Program%20Files/PhatHack/PhatHack%20DMS%20Tools/PhatPartition.DLL
----------------------------------------
msvcm80
    Assembly Version: 8.0.50727.163
    Win32 Version: 8.00.50727.163
    CodeBase: file:///C:/WINDOWS/WinSxS/x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.163_x-ww_681e29fb/msvcm80.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
Title: Re: Windows DMS Hack Tools v2.4 - Bug Reports
Post by: Terry_Kennedy on September 28, 2007, 12:58:24 am
[Annoying post length limit - reminds me again why SMF sucks and I've been avoiding this board since it switched.]

The NewDMS_Log says:

Code: [Select]

PhatHack Media Manager DMS Creator
---------------------------------

Date: 9/27/2007
Time: 20:54:20
LogDir: C:\Documents and Settings\Terry Kennedy\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: WDC WD2500JD-00GBB0
PnP Device: IDE\DISKWDC_WD2500JD-00GBB0_____________________02.05D02\4&244BA08&0&0.0.0
Disk Unique ID (not serial!): E97DE97D

Partitions List
---------------
Partition: Disk #0, Partition #0
Drive: C:
Serial #: 901A8099



Device evaluation complete.
Next device evaluation:
Determining device signature...
Error occured during drive snapshot:
System.InvalidCastException: Conversion from type 'DBNull' to type 'Integer' is not valid.
   at Microsoft.VisualBasic.CompilerServices.Conversions.ToInteger(Object Value)
   at VorTechS.DMS_Hack_Wizard.modCommon.TakeDriveSnapshot(String Logdir, String Logfile)

Getting DMS Disk ID from snapshot...
Disk ID is ...

Opening device through kernel....

The Startup_sequence says:

Code: [Select]
Starting Device Listing....
Getting Device Snapshot....


Win32_Drive List
----------------

Starting device evaluation:
Determining device signature...
done.
Disk ID: 0
Disk Name: WDC WD2500JD-00GBB0
PnP Device: IDE\DISKWDC_WD2500JD-00GBB0_____________________02.05D02\4&244BA08&0&0.0.0
Disk Unique ID (not serial!): E97DE97D

Partitions List
---------------
Partition: Disk #0, Partition #0
Drive: C:
Serial #: 901A8099



Device evaluation complete.
Skipping device with no signature.
Skipping device with no signature.
Skipping device with no signature.
Skipping device with no signature.
Next device evaluation:
Determining device signature...
done.
Disk ID: 5
Disk Name: USB-HS WDC WD2500BEVE-0 USB Device
PnP Device: USBSTOR\DISK&VEN_USB-HS&PROD_WDC_WD2500BEVE-0&REV_0.01\8&15750E10&0
Disk Unique ID (not serial!): 86031EBD

Partitions List
---------------
Partition: Disk #5, Partition #0
Drive: K:
Serial #: 946F17DF




Partitions List
---------------
No logical disks available for device partitions.
Device evaluation complete.
Succeeded....enumerating devices....
Device 1
Checking device name for USB context...
Not a USB labelled device.
Device 2
Checking device name for USB context...
Evaluates to true!
Also has drive letter!
Device enumeration complete.
Starting Device Listing....
Getting Device Snapshot....


Win32_Drive List
----------------

Starting device evaluation:
Determining device signature...
done.
Disk ID: 0
Disk Name: WDC WD2500JD-00GBB0
PnP Device: IDE\DISKWDC_WD2500JD-00GBB0_____________________02.05D02\4&244BA08&0&0.0.0
Disk Unique ID (not serial!): E97DE97D

Partitions List
---------------
Partition: Disk #0, Partition #0
Drive: C:
Serial #: 901A8099



Device evaluation complete.
Skipping device with no signature.
Skipping device with no signature.
Skipping device with no signature.
Skipping device with no signature.
Next device evaluation:
Determining device signature...
done.
Disk ID: 5
Disk Name: USB-HS WDC WD2500BEVE-0 USB Device
PnP Device: USBSTOR\DISK&VEN_USB-HS&PROD_WDC_WD2500BEVE-0&REV_0.01\8&15750E10&0
Disk Unique ID (not serial!): 86031EBD

Partitions List
---------------
Partition: Disk #5, Partition #0
Drive: K:
Serial #: 946F17DF




Partitions List
---------------
No logical disks available for device partitions.
Device evaluation complete.
Succeeded....enumerating devices....
Device 1
Checking device name for USB context...
Not a USB labelled device.
Device 2
Checking device name for USB context...
Evaluates to true!
Also has drive letter!
Device enumeration complete.
Title: Re: Windows DMS Hack Tools v2.4 - Bug Reports
Post by: sbingner on September 28, 2007, 01:24:21 am
post size limit removed... I hadn't ran into it being a problem in the past.
Title: Re: Windows DMS Hack Tools v2.4 - Bug Reports
Post by: VorTechS on September 28, 2007, 05:27:01 am
Thanks Terry, I'll take a look at this in about an hour.

Looks like another case of WMI records not containing data - although this looks real familiar.
Title: Re: Windows DMS Hack Tools v2.4 - Bug Reports
Post by: Terry_Kennedy on September 28, 2007, 05:30:50 am
Thanks Terry, I'll take a look at this in about an hour.

Thanks for the quick response. The old-style newdms.bat was able to initialize the DMS to something PMM seems comfortable with. I haven't started putting music on it yet, so I can try out any changes you make.
Title: Re: Windows DMS Hack Tools v2.4 - Bug Reports
Post by: VorTechS on September 28, 2007, 06:18:04 am
Just building a new version now, if you can drop into IRC I can give you a quicker turnaround when you are ready to test.

I've not heard of any issues other than my own, where the new DMS is not working with PMM.  The exception to the rule is the 'firmware not valid' issue which the current versions of the new tools should solve - although that's subject to sbingner's interpretation of what PMM might be looking for ;)
Title: Re: Windows DMS Hack Tools v2.4 - Bug Reports
Post by: VorTechS on September 28, 2007, 06:34:46 am
Mailed you [address on your profile] a link to the next test version ....
Title: Re: Windows DMS Hack Tools v2.4 - Bug Reports
Post by: Terry_Kennedy on September 28, 2007, 06:36:52 am
Mailed you [address on your profile] a link to the next test version ....

[Update] The most recent test version fixed it.

Thanks!
Title: Re: Windows DMS Hack Tools v2.4 - Bug Reports
Post by: VorTechS on October 01, 2007, 06:35:56 am
Awesome, released as v2.5 for anyone watching this....
Title: Re: Windows DMS Hack Tools v2.10 - Bug Reports
Post by: Mikromidas on November 12, 2007, 11:17:44 pm
I got as far as formatting the new 250GB DMS. When trying to download new firmware I get this message:

Code: [Select]
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.MissingMethodException: Method not found: 'Void VorTechS.DMSManager.FileCopy.DownloadFile(System.String, System.String)'.
   at StandAloneDMSHackWizard.frmStartupWizard.DownLoadFile(String SourceFile, String DestFile, String LogDir, String Logfile)
   at StandAloneDMSHackWizard.frmStartupWizard.GetFirmwareFiles(String LogDir, String LogFile)
   at StandAloneDMSHackWizard.frmStartupWizard.UpgradeFirmware(String LogDir, String NewDMSLogFile, Int32 DiskID, Boolean LBARequired)
   at StandAloneDMSHackWizard.frmStartupWizard.btnFirmwareOnly_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.832 (QFE.050727-8300)
    CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
StandAloneDMSHackWizard
    Assembly Version: 2.10.0.0
    Win32 Version: 0.0.2.10
    CodeBase: file:///C:/Program%20Files/PhatHack/PhatHack%20DMS%20Tools/StandAloneDMSHackWizard.exe
----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 8.0.0.0
    Win32 Version: 8.0.50727.42 (RTM.050727-4200)
    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.832 (QFE.050727-8300)
    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.832 (QFE.050727-8300)
    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.832 (QFE.050727-8300)
    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.832 (QFE.050727-8300)
    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.832 (QFE.050727-8300)
    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.832 (QFE.050727-8300)
    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
----------------------------------------
DMS
    Assembly Version: 1.0.0.1
    Win32 Version: 1.0.0.1
    CodeBase: file:///C:/Program%20Files/PhatHack/PhatHack%20DMS%20Tools/DMS.DLL
----------------------------------------
DMS Hack Wizard
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Program%20Files/PhatHack/PhatHack%20DMS%20Tools/DMS%20Hack%20Wizard.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.42 (RTM.050727-4200)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_32/CustomMarshalers/2.0.0.0__b03f5f7f11d50a3a/CustomMarshalers.dll
----------------------------------------
PhatPartition
    Assembly Version: 1.0.2872.15992
    Win32 Version:
    CodeBase: file:///C:/Program%20Files/PhatHack/PhatHack%20DMS%20Tools/PhatPartition.DLL
----------------------------------------
msvcm80d
    Assembly Version: 8.0.50608.0
    Win32 Version: 8.00.50727.42
    CodeBase: file:///C:/WINDOWS/WinSxS/x86_Microsoft.VC80.DebugCRT_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_f75eb16c/msvcm80d.dll
----------------------------------------
UsbEject
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Program%20Files/PhatHack/PhatHack%20DMS%20Tools/UsbEject.EXE
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.



Title: Re: Windows DMS Hack Tools v2.10 - Bug Reports
Post by: VorTechS on November 13, 2007, 06:15:22 am
Sorry, I've had another report of this and will patch it up this morning.  It's an installer issue again, I'll let you know when it's patched up again.
Title: Re: Windows DMS Hack Tools v2.10 - Bug Reports
Post by: VorTechS on November 13, 2007, 08:31:38 am
Okay, please re-download the tools - I've patched it up and tested it on VMWare and everything is back to normal.

Apologies, IF there is a need for another build I'll make sure the installer is working correctly in future!
Title: Re: Windows DMS Hack Tools v2.10 - Bug Reports
Post by: bpr on December 01, 2007, 08:00:16 pm
It says my original DMS is patched, but it doesn't patch my keg, it just acts as it always does.  When I try to start the hack wizard over, it jumps to step 7 and gives me this:

StartIndex cannot be less than zero.
Parameter name: startIndex.

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.ArgumentOutOfRangeException: StartIndex cannot be less than zero.
Parameter name: startIndex
   at System.String.InternalSubStringWithChecks(Int32 startIndex, Int32 length, Boolean fAlwaysCopy)
   at System.String.Substring(Int32 startIndex)
   at VorTechS.DMS_Hack_Wizard.DMS_PhatHack.CheckPatchResultsLog(String PatchLogFileName)
   at VorTechS.DMS_Hack_Wizard.DMS_PhatHack.VerifyPatchWorked(String PhtSys, String LogDir, String LogFile)
   at VorTechS.DMS_Hack_Wizard.DMS_PhatHack.CheckPatchAndCleanUp()
   at VorTechS.DMS_Hack_Wizard.DMS_PhatHack.RunStageProcess()
   at VorTechS.DMS_Hack_Wizard.DMS_PhatHack.DisplayStage()
   at VorTechS.DMS_Hack_Wizard.DMS_PhatHack.btnNext_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.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.832 (QFE.050727-8300)
    CodeBase: file:///G:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
StandAloneDMSHackWizard
    Assembly Version: 2.10.0.0
    Win32 Version: 0.0.2.10
    CodeBase: file:///G:/Program%20Files/PhatHack/PhatHack%20DMS%20Tools/StandAloneDMSHackWizard.exe
----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 8.0.0.0
    Win32 Version: 8.0.50727.42 (RTM.050727-4200)
    CodeBase: file:///G:/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.832 (QFE.050727-8300)
    CodeBase: file:///G:/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.832 (QFE.050727-8300)
    CodeBase: file:///G:/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.832 (QFE.050727-8300)
    CodeBase: file:///G:/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.832 (QFE.050727-8300)
    CodeBase: file:///G:/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.832 (QFE.050727-8300)
    CodeBase: file:///G:/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.832 (QFE.050727-8300)
    CodeBase: file:///G:/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:///G:/Program%20Files/PhatHack/PhatHack%20DMS%20Tools/PhatUnzip.DLL
----------------------------------------
DMS
    Assembly Version: 1.0.0.1
    Win32 Version: 1.0.0.1
    CodeBase: file:///G:/Program%20Files/PhatHack/PhatHack%20DMS%20Tools/DMS.DLL
----------------------------------------
DMS Hack Wizard
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///G:/Program%20Files/PhatHack/PhatHack%20DMS%20Tools/DMS%20Hack%20Wizard.DLL
----------------------------------------
Interop.WbemScripting
    Assembly Version: 1.2.0.0
    Win32 Version: 1.2.0.0
    CodeBase: file:///G:/Program%20Files/PhatHack/PhatHack%20DMS%20Tools/Interop.WbemScripting.DLL
----------------------------------------
CustomMarshalers
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.42 (RTM.050727-4200)
    CodeBase: file:///G:/WINDOWS/assembly/GAC_32/CustomMarshalers/2.0.0.0__b03f5f7f11d50a3a/CustomMarshalers.dll
----------------------------------------
System.Web
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.832 (QFE.050727-8300)
    CodeBase: file:///G:/WINDOWS/assembly/GAC_32/System.Web/2.0.0.0__b03f5f7f11d50a3a/System.Web.dll
----------------------------------------
UsbEject
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///G:/Program%20Files/PhatHack/PhatHack%20DMS%20Tools/UsbEject.EXE
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
Title: Re: Windows DMS Hack Tools v2.10 - Bug Reports
Post by: VorTechS on December 03, 2007, 07:36:12 am
Thanks for reporting this issue, it's a known one.
Some boxes do not play the startup sound for some reason, and we use the startup sound to activate the hack.

I'm currently in the process of modifying the hack to insert a new playlist as the first playlist item ensuring that the hack will run.
Look out for v2.11 of the tools coming as soon as I can get them done....
Title: Re: Windows DMS Hack Tools v2.10 - Bug Reports
Post by: DrHandball on December 16, 2007, 01:26:18 pm
I installed version 2.10 of the Hack Tools and when I try to start it I get an error message that the program had a problem and needs to shut down.  That's as far as it gets.  So I'm not able to use them to hack my DMS.  BTW I disconnected all other USB storage devices.

Suggestions please.

TIA
Title: Re: Windows DMS Hack Tools v2.10 - Bug Reports
Post by: VorTechS on December 18, 2007, 06:23:06 am
Check you have the Microsoft.NET Framework 2.0 installed, if not then you need to install it.

If you do, please click on 'Details' and paste the details here (first few lines will be fine)
Title: Re: Windows DMS Hack Tools v2.10 - Bug Reports
Post by: DrHandball on January 01, 2008, 04:19:50 am
I thought I would update this thread.  Turns out I had a number of system problems.  I had to reinstall windows over itself and am now in the process of reinstalling all my applications.  I'll update this thread once that is completed and I try using PhatHack again.
Title: Re: Windows DMS Hack Tools v2.10 - Bug Reports
Post by: moedope on January 08, 2008, 03:06:19 am
ok this is a great prog, thanks to the coders
my problem is that the hole proces finished and was able to do a 40 gig dms but some times it wont load the 40 gig dms, i notice thad when i insert the original dms the red ligth in my kenwood keg goes on and when i insert the 40 gig one the red ligth wont go on and the radio sais eject, when it finaly work its great but most of the times it wont work, and i even reset the radio a few times and even unpluged it a couple of times, any help would be great
Title: Re: Windows DMS Hack Tools v2.10 - Bug Reports
Post by: VorTechS on January 08, 2008, 07:35:10 am
Sounds to me like you just need to push the cartridge in a little harder....
Title: Re: Windows DMS Hack Tools v2.10 - Bug Reports
Post by: moedope on January 08, 2008, 03:36:09 pm
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
Title: Re: Windows DMS Hack Tools v2.10 - Bug Reports
Post by: urchrzan on March 17, 2008, 01:30:40 am
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



Title: Re: Windows DMS Hack Tools v2.10 - Bug Reports
Post by: VorTechS on March 17, 2008, 08:12:28 am
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!
Title: Re: Windows DMS Hack Tools v2.10 - Bug Reports
Post by: urchrzan on March 17, 2008, 06:54:48 pm
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
Title: Re: Windows DMS Hack Tools v2.10 - Bug Reports
Post by: Hankle on February 02, 2010, 04:30:41 am
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
Title: Re: Windows DMS Hack Tools v2.10 - Bug Reports
Post by: VorTechS on February 03, 2010, 10:33:22 am
Interesting, haven't seen one of these for a while!  Would you be willing to try out the new tools?