Phat Hack DMS Tools unhandled exception at startup

[maniac1181]

Hi all,

I've just gotten my phatbox installed and am looking at ways to get a bigger drive in there so I installed V2.1 of the Phat Hack DMS Toold but I can't get them to work. I use windows XP pro on a Toshiba Laptop.

If I start the Phat Hack tools, I have no problem starting the program but as I see no DMS detected evn if I introduce one afterwards. If there is a cartridge in the USB2.0 dock when I start the program, I get a .NET framework error message telling me there is an Object reference not set to an instance of an object. If I go in details, I get the following.

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

************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
   at StandAloneDMSHackWizard.frmStartupWizard.GetDevices(Boolean ForNewDMS)
   at StandAloneDMSHackWizard.frmStartupWizard.frmStartupWizard_Load(Object sender, EventArgs e)
   at System.EventHandler.Invoke(Object sender, EventArgs e)
   at System.Windows.Forms.Form.OnLoad(EventArgs e)
   at System.Windows.Forms.Form.OnCreateControl()
   at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
   at System.Windows.Forms.Control.CreateControl()
   at System.Windows.Forms.Control.WmShowWindow(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.ContainerControl.WndProc(Message& m)
   at System.Windows.Forms.Form.WmShowWindow(Message& m)
   at System.Windows.Forms.Form.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.1.0.0
    Win32 Version: 0.0.2.1
    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
----------------------------------------
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
----------------------------------------
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
----------------------------------------

************** 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.

[VorTechS]

Thanks for the report.  Not sure exactly where this is occuring in the function it specifies but I'm going to do some work to see if I can sort it out.

That function should be writing a log file - can you check to see if you have:

My Documents\PhatHack Media Manager\Logs\Startup_Sequence.txt

and if so, paste the contents here please.

[VorTechS]

Un-install the tools and re-download the latest version once you've had a look to see if you have the log file.

I've made a few modifications which may resolve the issue, I've also added a refresh button so you don't need to close the tools down if you haven't got the DMS inserted when the tools startup.

[maniac1181]

Hi again,

Thanks for answering so fast and sorry for getting back so late. I uninstalled the old version, installed the new version, and I still get an error message. Here is the content of the startup_sequence.txt file you asked:

Starting Device Listing....
   Getting Device Snapshot....


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

      Starting device evaluation:
      Determining device signature...
      done.
   Disk ID: 0
   Disk Name: FUJITSU MHV2100BH PL
   PnP Device: IDE\DISKFUJITSU_MHV2100BH_PL____________________0000002A\5&D759CFD&0&0.0.0
   Disk Unique ID (not serial!): A4B9A4B9

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




      Partitions List
      ---------------
      Partition: Disk #0, Partition #1
      Drive: D:
      Serial #: CCD810BF




      Partitions List
      ---------------
      No logical disks available for device partitions.
      Device evaluation complete.
      Next device evaluation:
      Determining device signature...
      done.
   Disk ID: 1
   Disk Name: USB-HS PhatNoise DMS 20 USB Device
   PnP Device: USBSTOR\DISK&VEN_USB-HS&PROD_PHATNOISE_DMS_20&REV_0.01\6&AA0DE3E&0
   Disk Unique ID (not serial!): A3269642

      Partitions List
      ---------------
      Partition: Disk #1, Partition #0
      Drive: F:
      Serial #: 3E54AD84




      Partitions List
      ---------------
      Partition: Disk #1, Partition #1
      Drive: G:
      Serial #: 3E54AD87



      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...
         Not a USB labelled device.
      Device 3
         Checking device name for USB context...
Starting Device Listing....
   Getting Device Snapshot....


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

      Starting device evaluation:
      Determining device signature...
      done.
   Disk ID: 0
   Disk Name: FUJITSU MHV2100BH PL
   PnP Device: IDE\DISKFUJITSU_MHV2100BH_PL____________________0000002A\5&D759CFD&0&0.0.0
   Disk Unique ID (not serial!): A4B9A4B9

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




      Partitions List
      ---------------
      Partition: Disk #0, Partition #1
      Drive: D:
      Serial #: CCD810BF




      Partitions List
      ---------------
      No logical disks available for device partitions.
      Device evaluation complete.
      Next device evaluation:
      Determining device signature...
      done.
   Disk ID: 1
   Disk Name: USB-HS PhatNoise DMS 20 USB Device
   PnP Device: USBSTOR\DISK&VEN_USB-HS&PROD_PHATNOISE_DMS_20&REV_0.01\6&AA0DE3E&0
   Disk Unique ID (not serial!): A3269642

      Partitions List
      ---------------
      Partition: Disk #1, Partition #0
      Drive: F:
      Serial #: 3E54AD84




      Partitions List
      ---------------
      Partition: Disk #1, Partition #1
      Drive: G:
      Serial #: 3E54AD87



      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...
         Not a USB labelled device.
      Device 3
         Checking device name for USB context...

Hope this helps. The unhandled exception message seems to remain the same.

[VorTechS]

Okay, looking at the log and the code it appears your DMS has 3 visible partitions instead of the 2 that would be expected.  Its true that a DMS should have 3 partitions - but one of them should be an extended partition that isn't visible to WMI. 

If I'm reading the logs and the code right, when evaluating partitions it's picking up some properties from the WMI database, but the values in the database appear to be 'Nothing' as opposed to DBNULL which is also strange. 

(At this point I can hear sbingner using the phrase 'Windows Sucks')

I've modified the code where it's checking the properties picked up from the WMI database to check for nothing and deal with it accordingly.  There'll be a new build up a little bit later on when I've had a look at other things that have been reported over the last week.  Look out for the version number on the post changing to 2.3 and you'll know you can download it.

Hopefully, you'll get further with the new build.

Thanks for the patience.

[sbingner]

Technically, the requirement is for an extended partition with a logical partition in it (which will be mounted as /dos/Data) and a primary partition (1) that will be mounted as /dos -- any other partitions are a waste of space, but not something that would bother the phatbox... I've had a swap partition and an ext3 partition on my DMS at times.

That said, stock DMS should line up as only what you said...