Help Needed with PhatHack Wizard Issue v2.12 on KHD-710 Keg (10GB DMS)

[ste_mac]

Just to start by saying this site is absolutely amazing and only lack of technical knowledge on my behalf is causing me to post, not lack of resources. I will be making a donation come payday. I recently found out the hard way that Phatnoise MM has some issues with Vista. Attempting to sort this I formatted the DMS using windows leaving the partitions intact. I then found the PhatHack DMS Tools and attempted to Hack my Kenwood Music Keg. The programme hung after stage 5 (Applying Patch Files) with the following error box:

PhatHack DMS Patcher
Unhandled exception has occurred in your application. If  you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will close immediately.
Access is denied.
Details:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.ComponentModel.Win32Exception: Access is denied
   at UsbEject.Library.Volume.get_DiskNumbers()
   at UsbEject.Library.Volume.get_Disks()
   at UsbEject.Library.Volume.get_RemovableDevices()
   at UsbEject.Library.Device.Eject(Boolean allowUI)
   at VorTechS.DMSTools.DMS_CommonTools.EjectDevice(String DriveLetter)
   at VorTechS.DMS_Hack_Wizard.DMS_PhatHack.ApplyPatchFiles(String BackupDir)
   at VorTechS.DMS_Hack_Wizard.DMS_PhatHack.RunStageProcess()
   at VorTechS.DMS_Hack_Wizard.DMS_PhatHack.DisplayStage()
   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.1434 (REDBITS.050727-1400)
    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.1434 (REDBITS.050727-1400)
    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.1434 (REDBITS.050727-1400)
    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.1434 (REDBITS.050727-1400)
    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.1434 (REDBITS.050727-1400)
    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.1434 (REDBITS.050727-1400)
    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.1434 (REDBITS.050727-1400)
    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.1434 (REDBITS.050727-1400)
    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.1434 (REDBITS.050727-1400)
    CodeBase: file:///C:/Windows/assembly/GAC_32/CustomMarshalers/2.0.0.0__b03f5f7f11d50a3a/CustomMarshalers.dll
----------------------------------------
Accessibility
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.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.1434 (REDBITS.050727-1400)
    CodeBase: file:///C:/Windows/assembly/GAC_32/System.Web/2.0.0.0__b03f5f7f11d50a3a/System.Web.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.

When plugging the DMS into my Keg the HU (Kenwood KVT925-DVD) simply says loading. . . for a few seconds and then eject. . .
I have repeated this process with no progress and there are also no logs written to the DMS.

Here is the log below from the PhatHack Wizard:

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


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

      Starting device evaluation:
      Determining device signature...
      done.
   Disk ID: 0
   Disk Name: WDC WD12 00BEVS-60UST SCSI Disk Device
   PnP Device: SCSI\DISK&VEN_WDC_WD12&PROD_00BEVS-60UST\4&27DAC995&0&000000
   Disk Unique ID (not serial!): 4960E4E8

      Partitions List
      ---------------

      (Debugging: About to Query WMI for Logical Disks)

      (Debugging: ..Query Complete)
      Partition: Disk #0, Partition #0
      Drive: C:
      Serial #: 665F6CA2




      Partitions List
      ---------------

      (Debugging: About to Query WMI for Logical Disks)

      (Debugging: ..Query Complete)
      Partition: Disk #0, Partition #1
      Drive: D:
      Serial #: 8874071C



      Device evaluation complete.
      Next device evaluation:
      Determining device signature...
      done.
   Disk ID: 1
   Disk Name: PhatNois e DMS 10GB USB Disk
   PnP Device: USBSTOR\DISK&VEN_PHATNOIS&PROD_E_DMS_10GB&REV_U1.1\4804A36EB7E2FFBC&0
   Disk Unique ID (not serial!): 807E3386

      Partitions List
      ---------------

      (Debugging: About to Query WMI for Logical Disks)

      (Debugging: ..Query Complete)
      Partition: Disk #1, Partition #0
      Drive: F:
      Serial #: EC815BF0




      Partitions List
      ---------------

      (Debugging: About to Query WMI for Logical Disks)

      (Debugging: ..Query Complete)
      Partition: Disk #1, Partition #1
      Drive: G:
      Serial #: 58A28E56



      Device evaluation complete.
   Succeeded....enumerating devices....
      Device
         Checking device name for USB context...
         Not a USB labelled device.
      Device
         Checking device name for USB context...
         Not a USB labelled device.
      Device
         Checking device name for USB context...
         Evaluates to true!
         Also has drive letter!
      Device
         Checking device name for USB context...
         Evaluates to true!
         Also has drive letter!
   Device enumeration complete.



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

      Starting device evaluation:
      Determining device signature...
      done.
   Disk ID: 0
   Disk Name: WDC WD12 00BEVS-60UST SCSI Disk Device
   PnP Device: SCSI\DISK&VEN_WDC_WD12&PROD_00BEVS-60UST\4&27DAC995&0&000000
   Disk Unique ID (not serial!): 4960E4E8

      Partitions List
      ---------------

      (Debugging: About to Query WMI for Logical Disks)

      (Debugging: ..Query Complete)
      Partition: Disk #0, Partition #0
      Drive: C:
      Serial #: 665F6CA2




      Partitions List
      ---------------

      (Debugging: About to Query WMI for Logical Disks)

      (Debugging: ..Query Complete)
      Partition: Disk #0, Partition #1
      Drive: D:
      Serial #: 8874071C



      Device evaluation complete.
      Next device evaluation:
      Determining device signature...
      done.
   Disk ID: 1
   Disk Name: PhatNois e DMS 10GB USB Disk
   PnP Device: USBSTOR\DISK&VEN_PHATNOIS&PROD_E_DMS_10GB&REV_U1.1\4804A36EB7E2FFBC&0
   Disk Unique ID (not serial!): 807E3386

      Partitions List
      ---------------

      (Debugging: About to Query WMI for Logical Disks)

      (Debugging: ..Query Complete)
      Partition: Disk #1, Partition #0
      Drive: F:
      Serial #: EC815BF0




      Partitions List
      ---------------

      (Debugging: About to Query WMI for Logical Disks)

      (Debugging: ..Query Complete)
      Partition: Disk #1, Partition #1
      Drive: G:
      Serial #: 58A28E56



      Device evaluation complete.


PhatHack Media Manager DMS Patcher
---------------------------------

Date: 08/01/2009
Time: 00:56:41
LogDir: C:\Users\Stevo\Documents\PhatHack Media Manager\Logs\
ToolsPath: C:\Program Files\PhatHack\PhatHack DMS Tools\DMS_Utils\


Starting up....


Loading Patch File List.

   File 1: %sys%\aadec
   File 2: %sys%\aadec.sig
   File 3: %sys%\patcher
   File 4: %sys%\patcher.sig
   File 5: %sys%\rc.sh
   File 6: %sys%\rc.sig
   File 7: %sys%\bootload.log
   File 8: %sys%\backup\phatpatch
   File 9: %sys%\backup\phatpatchver.txt
   File 10: %sys%\backup\patch.sh
   File 11: %sys%\backup\patchcomplete.mp3
   File 12: %sys%\aadec-orig
   File 13: %sys%\aadec-orig.sig
   File 14: %sys%\backup\logswitch.sh
   File 15: %sys%\PhatHack.mp3
   File 16: %sys%\PhatHack.hack
   File 17: %data%\PhatHack.mp3
   File 18: %data%\HackIntro.mp3
   File 19: %data%\PhatHack.hack


Loaded 20 file(s).


Loading Wizard Configuration...



Stages configured: 10


   Loading Stage: 1

      Stage name: Wizard Welcome

   Stage 1 loaded.

   Loading Stage: 2

      Stage name: Verify Original DMS

   Stage 2 loaded.

   Loading Stage: 3

      Stage name: Original DMS Attached

   Stage 3 loaded.

   Loading Stage: 4

      Stage name: Backup DMS

   Stage 4 loaded.

   Loading Stage: 5

      Stage name: Applying Patch files

   Stage 5 loaded.

   Loading Stage: 6

      Stage name: DMS Patch Applied

   Stage 6 loaded.

   Loading Stage: 7

      Stage name: Verify Patch State

   Stage 7 loaded.

   Loading Stage: 8

      Stage name: Patched OK!

   Stage 8 loaded.

   Loading Stage: 9

      Stage name: Failed Verify DMS

   Stage 9 loaded.

   Loading Stage: 10

      Stage name: Patch Failed!

   Stage 10 loaded.

   Loading Stage: 11

      Stage name: Unknown Error Occured

   Stage 11 loaded.


Moving to Wizard stage: 1
Stage name: Wizard Welcome
User clicked on Next

Moving to Wizard stage: 2
Stage name: Verify Original DMS
Running auto-process for stage: 1...


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

      Starting device evaluation:
      Determining device signature...
      done.
   Disk ID: 0
   Disk Name: WDC WD12 00BEVS-60UST SCSI Disk Device
   PnP Device: SCSI\DISK&VEN_WDC_WD12&PROD_00BEVS-60UST\4&27DAC995&0&000000
   Disk Unique ID (not serial!): 4960E4E8

      Partitions List
      ---------------

      (Debugging: About to Query WMI for Logical Disks)

      (Debugging: ..Query Complete)
      Partition: Disk #0, Partition #0
      Drive: C:
      Serial #: 665F6CA2




      Partitions List
      ---------------

      (Debugging: About to Query WMI for Logical Disks)

      (Debugging: ..Query Complete)
      Partition: Disk #0, Partition #1
      Drive: D:
      Serial #: 8874071C



      Device evaluation complete.
      Next device evaluation:
      Determining device signature...
      done.
   Disk ID: 1
   Disk Name: PhatNois e DMS 10GB USB Disk
   PnP Device: USBSTOR\DISK&VEN_PHATNOIS&PROD_E_DMS_10GB&REV_U1.1\4804A36EB7E2FFBC&0
   Disk Unique ID (not serial!): 807E3386

      Partitions List
      ---------------

      (Debugging: About to Query WMI for Logical Disks)

      (Debugging: ..Query Complete)
      Partition: Disk #1, Partition #0
      Drive: F:
      Serial #: EC815BF0




      Partitions List
      ---------------

      (Debugging: About to Query WMI for Logical Disks)

      (Debugging: ..Query Complete)
      Partition: Disk #1, Partition #1
      Drive: G:
      Serial #: 58A28E56



      Device evaluation complete.
Checking disks for PhatNoise original DMS disk....
PhatNoise original DMS disk found.

Moving to Wizard stage: 3
Stage name: Original DMS Attached
User clicked on Next

Moving to Wizard stage: 4
Stage name: Backup DMS
Running auto-process for stage: 3...
Created argument string of: if=\\.\PhysicalDrive1 bs=512 count=2048 of="C:\Users\Stevo\Documents\PhatHack Media Manager\DMS Backups\DMS Boot\DMS_Backup_08_Jan_2009_(12_56_39)\DMS_Backup_For_DeviceSerial_807E3386.bin"
DMS Boot bin backup name: C:\Users\Stevo\Documents\PhatHack Media Manager\DMS Backups\DMS Boot\DMS_Backup_08_Jan_2009_(12_56_39)\DMS_Backup_For_DeviceSerial_807E3386.bin
Running DD for DMS Boot Bin backup...
...process failed to launch.
Try dropping into a DOS shell and executing the following command from the PhatHack Media Manager\DMS_Utils directory:

dd if=\\.\PhysicalDrive1 bs=512 count=2048 of="C:\Users\Stevo\Documents\PhatHack Media Manager\DMS Backups\DMS Boot\DMS_Backup_08_Jan_2009_(12_56_39)\DMS_Backup_For_DeviceSerial_807E3386.bin"

Moving to Wizard stage: 5
Stage name: Applying Patch files
Running auto-process for stage: 4...
Connecting to DMS Manager......
...successfully initialised DMS manager!
DMS File Backup Dir: C:\Users\Stevo\Documents\PhatHack Media Manager\DMS Backups\DMS Boot\DMS_Backup_08_Jan_2009_(12_56_39)


Performing Patch File Update....
PhatSys Drive: F:
Exec INI location: F:\exec.ini
Exec INI exists: False
Checking backup directory exists...
...succeeded.

Patch File 1 of 19

   Destination: F:\aadec

   Source: C:\Program Files\PhatHack\PhatHack DMS Tools\DMS_Utils\HackFiles\aadec

Skipping backup as destination file does not exist.
Applying patch file: C:\Program Files\PhatHack\PhatHack DMS Tools\DMS_Utils\HackFiles\aadec
Applying of patch file complete.

Patch File 2 of 19

   Destination: F:\aadec.sig

   Source: C:\Program Files\PhatHack\PhatHack DMS Tools\DMS_Utils\HackFiles\aadec.sig

Skipping backup as destination file does not exist.
Applying patch file: C:\Program Files\PhatHack\PhatHack DMS Tools\DMS_Utils\HackFiles\aadec.sig
Applying of patch file complete.

Patch File 3 of 19

   Destination: F:\patcher

   Source: C:\Program Files\PhatHack\PhatHack DMS Tools\DMS_Utils\HackFiles\patcher

Skipping backup as destination file does not exist.
Applying patch file: C:\Program Files\PhatHack\PhatHack DMS Tools\DMS_Utils\HackFiles\patcher
Applying of patch file complete.

Patch File 4 of 19

   Destination: F:\patcher.sig

   Source: C:\Program Files\PhatHack\PhatHack DMS Tools\DMS_Utils\HackFiles\patcher.sig

Skipping backup as destination file does not exist.
Applying patch file: C:\Program Files\PhatHack\PhatHack DMS Tools\DMS_Utils\HackFiles\patcher.sig
Applying of patch file complete.

Patch File 5 of 19

   Destination: F:\rc.sh

   Source: C:\Program Files\PhatHack\PhatHack DMS Tools\DMS_Utils\HackFiles\rc.sh

Skipping backup as destination file does not exist.
Applying patch file: C:\Program Files\PhatHack\PhatHack DMS Tools\DMS_Utils\HackFiles\rc.sh
Applying of patch file complete.

Patch File 6 of 19

   Destination: F:\rc.sig

   Source: C:\Program Files\PhatHack\PhatHack DMS Tools\DMS_Utils\HackFiles\rc.sig

Skipping backup as destination file does not exist.
Applying patch file: C:\Program Files\PhatHack\PhatHack DMS Tools\DMS_Utils\HackFiles\rc.sig
Applying of patch file complete.

Patch File 7 of 19

   Destination: F:\bootload.log

   Source: C:\Program Files\PhatHack\PhatHack DMS Tools\DMS_Utils\HackFiles\bootload.log

Skipping backup as destination file does not exist.
Applying patch file: C:\Program Files\PhatHack\PhatHack DMS Tools\DMS_Utils\HackFiles\bootload.log
Applying of patch file complete.

Patch File 8 of 19

   Destination: F:\backup\phatpatch

   Source: C:\Program Files\PhatHack\PhatHack DMS Tools\DMS_Utils\HackFiles\backup\phatpatch

Skipping backup as destination file does not exist.
Applying patch file: C:\Program Files\PhatHack\PhatHack DMS Tools\DMS_Utils\HackFiles\backup\phatpatch
Applying of patch file complete.

Patch File 9 of 19

   Destination: F:\backup\phatpatchver.txt

   Source: C:\Program Files\PhatHack\PhatHack DMS Tools\DMS_Utils\HackFiles\backup\phatpatchver.txt

Skipping backup as destination file does not exist.
Applying patch file: C:\Program Files\PhatHack\PhatHack DMS Tools\DMS_Utils\HackFiles\backup\phatpatchver.txt
Applying of patch file complete.

Patch File 10 of 19

   Destination: F:\backup\patch.sh

   Source: C:\Program Files\PhatHack\PhatHack DMS Tools\DMS_Utils\HackFiles\backup\patch.sh

Skipping backup as destination file does not exist.
Applying patch file: C:\Program Files\PhatHack\PhatHack DMS Tools\DMS_Utils\HackFiles\backup\patch.sh
Applying of patch file complete.

Patch File 11 of 19

   Destination: F:\backup\patchcomplete.mp3

   Source: C:\Program Files\PhatHack\PhatHack DMS Tools\DMS_Utils\HackFiles\backup\patchcomplete.mp3

Skipping backup as destination file does not exist.
Applying patch file: C:\Program Files\PhatHack\PhatHack DMS Tools\DMS_Utils\HackFiles\backup\patchcomplete.mp3
Applying of patch file complete.

Patch File 12 of 19

   Destination: F:\aadec-orig

   Source: C:\Program Files\PhatHack\PhatHack DMS Tools\DMS_Utils\HackFiles\aadec-orig

Skipping backup as destination file does not exist.
Applying patch file: C:\Program Files\PhatHack\PhatHack DMS Tools\DMS_Utils\HackFiles\aadec-orig
Applying of patch file complete.
Backing up original Exec.INI file...
Backup of file exec.ini failed due to error: Could not find file 'F:\exec.ini'.
Applying AAC hack...
INI update succeeded.
Creating hack entry in EXEC.INI...
INI update succeeded.



Patch Failure [Serious].  No profiles.INI available to modify!

Any help provided with this problem would be greatly appreciated I have tried to provide as much detail as I can but this is all very new to me.

Thanks in advance

Steve

[VorTechS]

Don't panic with this error.  Carry on with the process as per the instructions.
The application failed to Eject the DMS cartridge from Windows for you... but the patch has applied successfully.

I'll add this to the list for the next version of the tools.

[ste_mac]

Hi VorTechS

Many thanks for you more than prompt reply. I have continued to attempt to hack my box today but with no success. Each time I plug my DMS into my Keg and search for the src on my HU the Keg will only show up as DISC-CH in AUX MODE. I have tried unplugging and reconnecting the Keg many times. I have attempted to only apply the Firmware (Kenwood v 13.01 without the hack) using PhatHack Tools. I have tried this option with the Reflash Box with Firmware checked and unchecked that made no difference. I have also attempted this with the hack but to no avail.

After reading more of the forum I decided to try corrupting the RAMdisc.sig (renamed it as RAMdiscsig.bak) and also replacing the bootload.log with properties.xml.

This is what the bootload.log file showed after loading the DMS into the Keg again:

BOOT0-1: OK
BOOT0: Successful
BOOT9: Successful
BOOTB: Successful
BOOTF: Successful
BOOT*-X: Failed

The lights on the keg: red stays solid and green flashes continually at regular intervals. This doesn't stop even after the ignition is turned off.
There are also no logs saved in the log file on the DMS only a folder named previous and this is empty.
I'm not sure if this is a problem with the firmware or lack there of on the Keg itself, could it be a problem flashing the box?
I don't have any music loaded onto the DMS as Phatnoise MM will not save and eject in Vista not sure if this may cause some issues.
Would it make a difference that I also cleaned the DMS with Phatnoise MM?
I have not done anything to the partitions

Kind Regards

Steve

P.S Not sure if I should have posted this in another thread/forum. If that is the case I apologise in advance.

[sbingner]

corrupting it only is good if you ALREADY are getting errors like you pasted... change it back to a good signature...

Oh, you did still HAVE a ramdisk.sig file right?  It needs to exist as an invalid file to make it work if it froze up at the ramdisk.sig patch

[ste_mac]

The situation has now changed but I'm not sure how. I have reformatted a couple of times and tried loading up different firmware onto the DMS (currently non-hacked 13.01 Kenwood).

My HU is now recognising my Keg as HDD EXT as it was before but when I power up the HU says Loading . . . for about 30 seconds then Eject. There doesn't appear to be any activity at all in terms of the lights on the Keg.

I copied in the "RC Pairs" (Level 10) hoping to create a logtxt.txt as I have read before but this did not produce anything.

Do you have any suggestions on where to go from here?

Steve

[ste_mac]

Yes I did still have a ramdisc.sig file. Corrupting those files didn't seem to have any effect, so, I stupidly decided to explore new avenues.

Further to my post before and a couple more hours of tinkering, (probably wasn't a good idea) as my stereo is now constantly turning itself on and off. The screen will partly fold out then try to go back and then out again and so on. It was originally only doing this while the keg was attached (Red light on, green light blinking on steadily, this happens for approx 1 min then all off).

Upon detaching the keg and turning off the ignition normal operation was resumed. It seems to be caught in some kind of loop. There are still no log files being written from the "RC Pairs" (Level 10).

Cheers

Steve

[ste_mac]

Today I tried taking the Keg apart just to check for loose connections and any fried components, everything seems fine IDE cable still glued in place and no charred bits.

The Keg and whatever is going on with that seems to have had quite an adverse effect on my HU, even with the Keg disconnected the screen seems to keep about twice a second. With this going on the screen doesn't even get to the fully open position. I am goin to try disconnecting the battery to see if that sorts the problem.

Is it possible that all this is down to a faulty DMS? Everything worked fine untill I tried to put some new songs on the DMS with my Vista laptop for the first time. I encountered problems with the save and eject function as is well documented in these forums. I then wiped the DMS using Phatnoise MM and I have never been able to get this to function again.

I have also tried Repair DMS (PHTSYS) and Repair DMS (Full) neither of which work giving the error message Failed to Format DMS partitions. Here are the logs below:

Repair DMS (Full) Log:

Preparing format parameters....
PHTSYS Arguments: -v -n PHTSYS -F 32 F: 0
PHTDTA Arguments: -v -n PHTDTA -F 32 G: 0
Formatting PHTSYS....
completed: Failed!.
Formatting PHTDTA....
completed: Failed!.

The new DMS preparation has failed.

Repair DMS (PHTSYS) Log:

Preparing format parameters....
PHTSYS Arguments: -v -n PHTSYS -F 32 F: 0
PHTDTA Arguments: -v -n PHTDTA -F 32 G: 0
Formatting PHTSYS....
completed: Failed!.

The new DMS preparation has failed.

Preparing format parameters....
PHTSYS Arguments: -v -n PHTSYS -F 32 F: 0
PHTDTA Arguments: -v -n PHTDTA -F 32 G: 0
Formatting PHTSYS....
completed: Failed!.

The new DMS preparation has failed.

Thanks in advance to anyone that may be able to help or shed any light on the situation.

Steve

[sbingner]

That's the same error somebody else was getting, it's telling mkfs to creae a 0-byte partition with it obviously can't do...  you could run mkfs manually, or I'm sure vortechs will be able to find the problem with the tools...  can you post your partition table off the drive?

[VorTechS]

It's odd it's doing it with both partitions though!  There's possibly a flaw with the re-reading of the disk partitions, perhaps it's taking longer than expected.  I've also realised the first attempt actually wouldn't work, as the Profiles.INI is needed.

Best bet here, is to wipe the existing partitions through Computer Management and have the tools create a new, non-hacked DMS.  Don't attempt to create the partitions yourself manually, unless you know how to do so at an offset of 1024 bytes.  If the problem persists, it would be useful to have the disk so I can reproduce the problem and debug through it.  No biggie if not, I'll see if I can work through the logic in the v3 tools and identify any possible holes.

[sbingner]

maybe it's a vista problem

did you run it as administrator?

[VorTechS]

Oh yea, that would do it... Vista would need to be run elevated otherwise the O/S might protect some things (but obviously not very well!)

[ste_mac]

Hi VorTechS,

I agree that this is probably a Vista issue. There doesn't appear to be any option for me to run the PhatHack tools as administrator when opening. I think I have got everything working again now though in a fashion. I do get the corrupt track message everytime I change discs, but I'm guessing that could be easily fixed by simply removing that .wav? file from PHTSYS. My keg appears to be hacked.

I think all my problems stemed from my car battery being slightly flat. Although there was enough power for my stereo to operate I think the Keg being slightly more sensitive was starved of power and because of this started acting strangely. Everyhting worked fine again after a jump start and some battery charging.

I am going to try and get my old computer (XP) back up and running to see if the same issues are encountered with regards creating new DMS etc. I have also sourced a new hard drive to run in my hacked box. Once I have done this and got everyhting up and running and if you still want/need the disc I would gladly donate it in the name of science.

All your help and support has been greatly appreciated in solving all the problems and mess created by the idiots at Phatnoise. This is an awesome resource saving many kegs/phatboxes from the bin. Keep up the good work.

Cheers

Steve

[VorTechS]

If it's proven to be a Vista issue I shouldn't need the disk.  Right-click on the icon that launches the tools and there should be an option run as either administrator or elevated.  Can't remember which it is now