Text only | Text with Images

PhatHack

The Hacking Hoedown => PhatBox Hacking => Topic started by: Jay on December 14, 2008, 02:43:02 PM

Title: ejecting after the hack
Post by: Jay on December 14, 2008, 02:43:02 PM
first let me say thank you in advance for any help given. I am running XP-pro w/Kaspersky 2009 internet security(turned off) and PMM 2.30, my cradle is an usb 1, the DMS is 10gig and the keg is cx-910. when I use the hack software everything goes well until it is time to Eject then it tells me no DMS is detected. I have also tried using the safely remove hardware with no luck. the dms sounds like it ejected after the hack is applied only a red light on cradle. when I install it into the keg the lights come on for a few seconds and then shuts down Hdd spins down no lights and the head unit changes from Hdd ext to disk changer. I have tried all the steps in the user doc with no luck. what am I doing wrong???? any help would be greatly appreciated!!!
Title: Re: ejecting after the hack
Post by: VorTechS on December 15, 2008, 08:04:50 AM
Once the Hack Wizard applies the patch files to the DMS it will try and eject the DMS cartridge, and will only warn you it hasn't succeeded on failure.  Sounds to me like the software worked as it was intended.

When you were running the DMS tools, did you only apply the hack or did you try something else as well?
Title: Re: ejecting after the hack
Post by: Jay on December 15, 2008, 12:43:53 PM
I only applied the hack. I don't know if it makes a difference but I had wiped the dms using PPM 2.30 before starting so there is no music on it. here are the messages dms wizard give.

The wizard has finished copying the patch files onto your original DMS, or you have inserted a DMS that previously had the Patch applied and the wizard is now ready to verify the patch and clean up. 

  Close the Wizard and then remove the DMS cartridge.  Insert it into your Phatbox/Keg to run the patch. 
When the PhatBox/Keg has been updated, re-insert your DMS cartridge and the Wizard will verify the patch logs.

FLASHING across the bottom it says... Now eject the DMS in the correct manner...!

This is what it says after inserted into the KEG

It would appear the patch failed on your PhatBox, please join the PhatHack Community forums [http://forum.phathack.com] and post the contents of the file PHTSYS/logfile.txt 

Patch was not applied or failed to start, there is no patchverify.log

Here is the wizard log maybe it will help.

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

      Starting device evaluation:
      Determining device signature...
      done.
   Disk ID: 0
   Disk Name: ST9120822A
   PnP Device: IDE\DISKST9120822A______________________________3.ALC___\5&5FD921D&0&0.0.0
   Disk Unique ID (not serial!): F60CF60C

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

      (Debugging: About to Query WMI for Logical Disks)

      (Debugging: ..Query Complete)
      Partition: Disk #0, Partition #0
      Drive: C:
      Serial #: 782B4D1C



      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_A4.0\8870326A8E22FFB6&0
   Disk Unique ID (not serial!): D5A2FE3C

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

      (Debugging: About to Query WMI for Logical Disks)

      (Debugging: ..Query Complete)
      Partition: Disk #1, Partition #0
      Drive: H:
      Serial #: 3C343A4F




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

      (Debugging: About to Query WMI for Logical Disks)

      (Debugging: ..Query Complete)
      Partition: Disk #1, Partition #1
      Drive: I:
      Serial #: 3C343A51



      Device evaluation complete.


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

Date: 12/13/2008
Time: 12:38:45
LogDir: C:\Documents and Settings\bob\My 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: ST9120822A
   PnP Device: IDE\DISKST9120822A______________________________3.ALC___\5&5FD921D&0&0.0.0
   Disk Unique ID (not serial!): F60CF60C

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

      (Debugging: About to Query WMI for Logical Disks)

      (Debugging: ..Query Complete)
      Partition: Disk #0, Partition #0
      Drive: C:
      Serial #: 782B4D1C



      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_A4.0\8870326A8E22FFB6&0
   Disk Unique ID (not serial!): D5A2FE3C

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

      (Debugging: About to Query WMI for Logical Disks)

      (Debugging: ..Query Complete)
      Partition: Disk #1, Partition #0
      Drive: H:
      Serial #: 3C343A4F




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

      (Debugging: About to Query WMI for Logical Disks)

      (Debugging: ..Query Complete)
      Partition: Disk #1, Partition #1
      Drive: I:
      Serial #: 3C343A51



      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:\Documents and Settings\bob\My Documents\PhatHack Media Manager\DMS Backups\DMS Boot\DMS_Backup_13_Dec_2008_(12_38_44)\DMS_Backup_For_DeviceSerial_D5A2FE3C.bin"
DMS Boot bin backup name: C:\Documents and Settings\bob\My Documents\PhatHack Media Manager\DMS Backups\DMS Boot\DMS_Backup_13_Dec_2008_(12_38_44)\DMS_Backup_For_DeviceSerial_D5A2FE3C.bin
Running DD for DMS Boot Bin backup...
...process executed cleanly.

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:\Documents and Settings\bob\My Documents\PhatHack Media Manager\DMS Backups\DMS Boot\DMS_Backup_13_Dec_2008_(12_38_44)


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

Patch File 1 of 19

   Destination: H:\aadec

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

Backing up original file: H:\aadec
Backup of original file complete.
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: H:\aadec.sig

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

Backing up original file: H:\aadec.sig
Backup of original file complete.
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: H:\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: H:\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: H:\rc.sh

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

Backing up original file: H:\rc.sh
Backup of original file complete.
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: H:\rc.sig

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

Backing up original file: H:\rc.sig
Backup of original file complete.
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: H:\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: H:\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: H:\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: H:\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: H:\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: H:\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 original file complete.
Applying AAC hack...
INI update succeeded.
Creating hack entry in EXEC.INI...
INI update succeeded.

Patch File 13 of 19

   Destination: H:\aadec-orig.sig

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

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

Patch File 14 of 19

   Destination: H:\backup\logswitch.sh

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

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

Patch File 15 of 19

   Destination: H:\PhatHack.mp3

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

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

Patch File 16 of 19

   Destination: H:\PhatHack.hack

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

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

Patch File 17 of 19

   Destination: I:\PhatHack.mp3

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

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

Patch File 18 of 19

   Destination: I:\HackIntro.mp3

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

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

Patch File 19 of 19

   Destination: I:\PhatHack.hack

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

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



Checking for hack log directory...
Log directory did not exist, created successfully.
Log directory exists, checking for log files...
... No patch.log exists.
... No patchverify.log exists.
... No patchwrite.log exists.
...log directory checking complete.


Creating Hack Playlist....


Hack Playlist created


Refreshing DMS contents....


Done.  Checking for hack playlist....


Inserting Hack Playlist as 1st playlist....


.....Done!


Re-generating PBX and SIG files....


.....Done!


Updating profile databases....


.....Done!
Backing up PROFILES.INI
Backup Complete.


Updating profile disc count....


.....Done!


Updating Phatman.ini Modification Count....


.....Done!
Patch File Update completed without errors.

Moving to Wizard stage: 6
Stage name: DMS Patch Applied
User cancelled the wizard.






Title: Re: ejecting after the hack
Post by: VorTechS on December 15, 2008, 01:49:53 PM
When you say you wiped it, how did you wipe it?
Title: Re: ejecting after the hack
Post by: Jay on December 15, 2008, 08:46:23 PM
I had wiped the dms using Phatnoise music manager 2.30 utilites- hardware options-Phatnoise DMS Maintenance  Wipe DMS.
Title: Re: ejecting after the hack
Post by: Jay on December 16, 2008, 01:16:45 AM
I found this while searching. V2.10 The hack may not run on some boxes, because those boxes do not run the startup sound. was this fixed for V2.12 My box does not have a start-up sound
could this be the problem?? Is there a workaround?
Title: Re: ejecting after the hack
Post by: Jay on December 18, 2008, 01:03:51 AM
AH. sorry turn out to be user error. for anyone who is interested I was using a bench set-up and powering down the system between uses so the keg was resetting it self. what I ended up doing was restoring everything to non-hacked firmware added a couple of  disks
updated the keg made sure it played then without powering down the bench(just the head unit off) loaded the hack onto dms, inserted into keg and BINGO. everything went according to the manual. THANK YOU!!!!! for writing a great program.once I got out of my own way all went well. :)
Text only | Text with Images