Hope I didn't speak too soon. For some reason, I cannot get the hack to take on the Phatbox. I have tried powering the head unit up, disconnecting the cable to the Phatbox (3 x) and all other methods you suggest in the instructions. It just doesn't seem to be kicking in. Instead, there is the normal 2 - 3 second delay and then music starts playing. I am attaching the log files per the instructions. I had to zip one of them up, as I exceeded the maximum size the first time I tried posting this.
Thank you for whatever assistance you can provide!
Dippdy
I finally got the hack to work on the Phatbox... I tried it one more time, and it seemed to take this time. It did reboot several times, but I kept switching it back to the Phatbox as the source and voila, success. I ran it back through the wizard and it said it was successful.
Now, I am trying to create my new DMS, and am running into issues with it. I keep receiving the same error: Creating DMS Failed. Check log for more. I am attaching the log file.
Where it errors, it says:
Drive preparation successful. Downloading firmware files...
...downloaded successfully....
...extracting contents...
...extraction failed, unable to continue. Error(s) returned:
ERROR: Could not find a part of the path 'C:\Program Files\PhatHack\PhatHack DMS Tools\Downloads\Volkswagen-Native\Temp\TTS\'.
Completion time: 00:17:24.
Any ideas?
Thanx!
dippdy
Yes, I've just taken another report with the same issue.
Are you running Windows Vista by any chance?
I'm away for a few days, and don't think I'm going to get a chance to take a look at this until next monday - but will do so as soon as I get back.
If you are running Windows Vista - then I think the issue is security based because the firmware is being extracted to the application folder which Vista probably doesn't like. Have a look and see if you can find any ways around this in the meantime and try again. If not, I'll modify the code next monday to perform the extraction to the 'Documents' folder where there should be no security issues. And if it's not security, then I've done something stupid that hasn't shown up on the alpha testers machines.
I am not on Vista at all. I am on xp. I will work on it some more to see if I can modify my xp settings to allow it to happen.
Also, I apologize. I believe I have put my comments in this thread mistakenly. Per your instructions, did you want new issues to go into a different thread? If so, is there a way I can move mine or delete them and create new?
Thanks so much!
Dippdy
I don't know, I can't get it to work at all. First of all, it says DMS not detected. The dms is plugged in and detected by windows 2000, so it is there. Second if I click on run hack wizard, i get a big long nasty exception error. it says "Index and length must refer to a location within the string. Parameter name: length." Which i assume is because since it does not detect my dms, the length string is probably empty and your program doesn't know what to do with empty strings. That is just a guess, since i really haven't looked at your code.
Why would it not detect my dms? It is an old 10Gb one from the original music keg 710 model.
Quote from: mscheaf on September 01, 2007, 08:18:16 PM
I don't know, I can't get it to work at all. First of all, it says DMS not detected. The dms is plugged in and detected by windows 2000, so it is there. Second if I click on run hack wizard, i get a big long nasty exception error. it says "Index and length must refer to a location within the string. Parameter name: length." Which i assume is because since it does not detect my dms, the length string is probably empty and your program doesn't know what to do with empty strings. That is just a guess, since i really haven't looked at your code.
Why would it not detect my dms? It is an old 10Gb one from the original music keg 710 model.
Please attach the log files found under My Documents\PhatHack Media Manager\Logs and I'll take a look at the drive snapshot to see if I can work out what's causing the problem. The reason your DMS may not being detected is because in all the test results I have had in the past, the DMS is reported by windows as being a 'Phatnoise USB' device. It's possible that this is not the case with all cradles/drives manufactured.
Secondly, there is a portion of code extracting the device letter from the combo box and I suspect that the lack of string (as you suggest) is causing problems thene. BTW, the SVN is not up-to-date with this code yet, since sourceforge changed the SVN access I need to backup the code and re-generate the Tortoise SVN folders.
Quote from: dippdydo22 on September 01, 2007, 02:18:55 PM
I am not on Vista at all. I am on xp. I will work on it some more to see if I can modify my xp settings to allow it to happen.
Also, I apologize. I believe I have put my comments in this thread mistakenly. Per your instructions, did you want new issues to go into a different thread? If so, is there a way I can move mine or delete them and create new?
Thanks so much!
Dippdy
Ah okay, then maybe this is another case of some instances of operating systems not creating folders properly, or the .NET 2.0 frameworks behaving in different ways. In some tests I found that on my machine folders were being generated using a double backslash, and getting away with it but others not, something I thought I got rid of - could be one left in. Could also be the extraction is going to a folder that hasn't yet been created. I'll check out both when I return from vacation. As I sort of hinted at before, check the destination path exists, with relevant security rights and you might actually complete the DMS creation.
Windows 2000 pro (yes i know its old, but after this long its 99.9% stable) reports the device as being 'usb-hs Phatnoise DMS 10 USB Device". it lists this under USB Mass Storage Device. It assigns it drive letter I: and J: both. My cradle is a "Phatnoise DMS USB2 rev A"
Log is attached
Thanks alot. If need be, I can do this on one of my XP machines, I just have my music on this machine so I do it here. Plus this machine is a Athlon 3700+ 2.2 GHZ that I have overclocked to 2.9 so it is obviously my favorite
I checked and all of the folders are there. It appears the path to the folder matches the path from the error message. I am not sure how I can adjust the security on the folders so that it can extract the files to that directory. I am not very good with XP. Any ideas?
Thanks!
Dippdy
Hi VorTechS,
I, too, am having problems having the DMS Hack Tools recognize my DMS. I have tried connecting two seperate DMS's, a 10 Gig and a 20 Gig, on two different computers and all combinations have not been able to see the disks on the pull down.
I'm not sure if this is the log you need, but here is is as follows:
Win32_Drive List
----------------
Starting device evaluation:
Determining device signature...
done.
Disk ID: 0
Disk Name: Maxtor 6L300R0
PnP Device: IDE\DISKMAXTOR_6L300R0__________________________BAJ41G20\364C51315348485A202020202020202020202020
Disk Unique ID (not serial!): 83D90F4
Partitions List
---------------
Partition: Disk #0, Partition #0
Drive: C:
Serial #: 40C26877
Partitions List
---------------
Partition: Disk #0, Partition #1
Drive: M:
Serial #: A0C45FAC
Device evaluation complete.
Next device evaluation:
Determining device signature...
done.
Disk ID: 1
Disk Name: ST3250623A
PnP Device: IDE\DISKST3250623A______________________________3.04____\5&C99E0DE&0&0.1.0
Disk Unique ID (not serial!): 791B350
Partitions List
---------------
Partition: Disk #1, Partition #0
Drive: D:
Serial #: 5844ACDA
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 StandAloneDMSHackWizard.frmStartupWizard.TakeDriveSnapshot(String Logdir, String Logfile, DiskSnapshot[]& AttachedDisks)
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...
Not a USB labelled device.
Device enumeration complete.
Starting Device Listing....
Getting Device Snapshot....
Any help would be greatly appreciated. Thanks a lot.
Harry
Thanks for the info on these.
dippdydo22: the logs show an error whilst querying WMI because Windows 2000 doesn't support the WMI properties being used to get the disk information. I'll do some research on this and see if there is a different way of getting the properties required.
funkdr_1999: Your problem is one that came up during the beta that someone got round by removing some USB devices that weren't needed - I think specifically it was a card reader. I put some debugging in should it occur again, and yu've helped narrow this down with your attached logs. Thanks. I'll look into this on Monday and hopefully you'll be able to get further with this.
does your application check to make sure the WMI services are in the correct state? not disabled, running whatever?
There are a lot of people who follow system 'tuning' guides that have you disable a bunch of services and WMI is usually included.
I don't think it's possible to actually fully disable WMI - as Windows itself relies on WMI, and as I'm using the .NET framework to interact with WMI via WMI messaging my assumption would be that WMI would return no records where this is the case.
If you can give me some specifics on how people are disabling WMI I'll check out the app. with the relevant things disabled to be sure.
Quote from: funkdr_1999 on September 05, 2007, 04:57:30 AM
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 StandAloneDMSHackWizard.frmStartupWizard.TakeDriveSnapshot(String Logdir, String Logfile, DiskSnapshot[]& AttachedDisks)
This has now been addressed, and was occuring when checking a device's signature (WMI Win32_Disk.signature property). If there is no signature on the device it will now be skipped.
Quote from: dippdydo22 on September 01, 2007, 06:23:55 AM
Drive preparation successful. Downloading firmware files...
...downloaded successfully....
...extracting contents...
...extraction failed, unable to continue. Error(s) returned:
ERROR: Could not find a part of the path 'C:\Program Files\PhatHack\PhatHack DMS Tools\Downloads\Volkswagen-Native\Temp\TTS\'.
Completion time: 00:17:24.
Any ideas?
Thanx!
dippdy
This is now fixed after using the firmware from the various bug reports on this issue. Seems there was an issue getting file info for directories within one of the downloaded zip files, that doesn't occur with the Kenwood firmware.
Quote from: mscheaf on September 03, 2007, 02:34:23 AM
Windows 2000 pro (yes i know its old, but after this long its 99.9% stable) reports the device as being 'usb-hs Phatnoise DMS 10 USB Device". it lists this under USB Mass Storage Device. It assigns it drive letter I: and J: both. My cradle is a "Phatnoise DMS USB2 rev A"
I've added some trapping at the point where the drive signature is being checked. I wonder if there is some form of discrepancy with the WMI database for one of your devices as all the info. I can find on Windows 2000 WMI suggests it should be no different to that of XP - which would make sense as WMI was introduced in 2000.
Download the latest version of the tools (2.3) run the program again and let's see if you can at least get somewhere without any strange errors in the log - and a DMS device listed. I've also disabled the 'Run Hack Wizard' button at design time - the error shown in your log may have been bypassing the button enabling code.
I'd appreciate a copy of the 'Startup_Sequence' log once you've downloaded, installed and run the latest version of the tools so I can see if the error you were getting was only for one device, or is a general problem with WMI under Windows 2000.
VorTechS,
Thanks for the quit reply and explanation. I found an older computer without and usb devices and everything worked perfectly! Now my mission is to get SSA working on the unit and learn how to navigate with my Kenwood DDx7015. Does anyone find navigating with this deck a pain? This question probably doesn't belong here sorry.
Anyways, thanks for the fantastic build, it worked as advertised.
So far so good... Thanks for all of the assistance. I was able to create my new 160 gig DMS and now and filling it up, which is taking a very long time! Hopefully, after this process is done it will work like a champ! Will let you know. Thanks again, this is fantastic.
Dippdy :)
For future information, I'd recommend loading up your DMS with just a few playlists in case the new DMS doesn't work.
I've had one report so far of the DMS not working, and am investigating the cause of this. Glad to see that the bug parts have been sorted out though!
VortechS,
Sorry for being such a pain, but I can't seem to get SSA working on my newly created DMS. I see on the PhatHack Wiki it states "If you have used the Hack CD to create a custom DMS and are adding SSA to that DMS, only perform steps 4 and 5". Is using the DMS Hack Tools the same as using the Hack CD? Because I did only steps 4 and 5 and cannot get it to work on my stereo. I have a Kenwood DDX7015 navigation stereo - it is possible the problem lies with the deck. Any help would be great. Thanks a lot.
VortechS -
The DMS seems to work great for MP3 files, but I have a ton of AAC files, which worked before on my old DMS cartridge. Now, when I try to play any of those files, it says that needs an "AAC Decoder." I believe I purchased this and I have the code for it, which I can apply through the Phatnoise Media Manager software, except when I go to apply the plugin, it says that I do not have any firmware installed on the DMS, although it works great with this one exception with my head unit.
Can I still install the VW 7.02 firmware through PMM and then attempt to apply the plugin for AAC? Will that undo the patch that allows me to use such a big drive?
Thanks!
Dippdy
Quote from: dippdydo22 on September 14, 2007, 02:54:29 AM
VortechS -
The DMS seems to work great for MP3 files, but I have a ton of AAC files, which worked before on my old DMS cartridge. Now, when I try to play any of those files, it says that needs an "AAC Decoder." I believe I purchased this and I have the code for it, which I can apply through the Phatnoise Media Manager software, except when I go to apply the plugin, it says that I do not have any firmware installed on the DMS, although it works great with this one exception with my head unit.
Can I still install the VW 7.02 firmware through PMM and then attempt to apply the plugin for AAC? Will that undo the patch that allows me to use such a big drive?
Thanks!
Dippdy
Okay before you do anything, let's see if we can work out why it's not working.
The original aacdecoder (aadec) is copied onto the DMS as aadec-orig, and the modified EXEC.INI put onto the DMS has aac playback pointing to the original file.
You should see an entry in exec.ini like this:
player.pna=/dos/aadec-orig
The hacked version of aadec (which I believe is for plugin authentication) is then put on to the DMS as aadec. Now, I've more than likely misunderstood something here, so I'll need to confirm that I've actually got this process right.
Can you confirm your exec.ini has the entry above?
The only thing you'll lose by reloading the firmware via PMM is the new WMA codec that the tools put onto the DMS, but it would be great if you could bear with me so we can identify the actual problem.
Quote from: funkdr_1999 on September 13, 2007, 07:29:23 PM
VortechS,
Sorry for being such a pain, but I can't seem to get SSA working on my newly created DMS. I see on the PhatHack Wiki it states "If you have used the Hack CD to create a custom DMS and are adding SSA to that DMS, only perform steps 4 and 5". Is using the DMS Hack Tools the same as using the Hack CD? Because I did only steps 4 and 5 and cannot get it to work on my stereo. I have a Kenwood DDX7015 navigation stereo - it is possible the problem lies with the deck. Any help would be great. Thanks a lot.
Steps 4 and 5 are definately the only steps you should need to do to install the replacement VIOT plugin. You might need to make a modification to Profiles.INI on PHTDATA to tell the phatbox you are using VIOT though.
There's a section called [profiles] and an entry in there which enables VIOT.
Make sure this setting is as shown below
[profiles]
enable_voice_prompts=1
See if that gets things going. Your problem might be related to the AAC problem too as the plugin authentication might be failing if I've ballsed up. Try the profiles thing first and let me know how you get on.
VorTechS -
You are fantastic for responding so quickly. This is what my exe.ini file says. Should I change something?
[Phatbox]
player.wma=/dos/phatwma
player.loop=/dos/playloopfile
auth.loop=/dos/swgrli
auth1.loop=/dos/nmp3
startprog=/dos/51d
player.flac=/dos/flacplay
player.pna=/dos/aadec-orig
auth.pna=/dos/nmp3
auth1.pna=/dos/hdparm
auth2.pna=/dos/pkeysa.e
player.ogg=/dos/oggplay-ha
auth.ogg=/dos/oggplay-la
player.m4a=/dos/needaac
auth.m4a=/dos/nmp3
player.hack=/dos/patcher
Dippdy
No, the exec.ini is correct, and so AAC playback should be working. One thing that we have noticed and that I will try to resolve for the next version of the tools, is that the CurrentSettings.xml file is missing from PhtSys and this could be causing the problem with PMM complaining about the firmware.
Also, don't update the firmware using PMM - it'll probably result in you not being able to use the new DMS!
If you have a copy of CurrentSettings.xml on an original DMS for the firmware you are using, try copying that onto the DMS and check if AAC playback starts working.
If not, see if PMM stops complaining about the firmware. It would be good to get answers to both of those.
Thanks for the patience, sorry we don't have a resolution to this yet - I don't have a working DMS myself as I don't have access to a PhatBox atm.
Just wondering if this line in the exe.ini file means anything?
player.m4a=/dos/needaac
Dippdy
Only if the AAC files you have encoded have the M4a extension (*.m4a)?
If so, then you can modify that line to use aadec-orig, but you'll need to regenerate a sig.
Ahhh, there's the rub, I think. They are m4a files. How do I regenerate a sig file?
Attach your exec.ini here and I'll generate one for you.
I put my original drive back into the cartridge and copied the PHTSYS files to my computer's hard drive. I looked at the original exec.ini and it says the same thing with the m4a files. Not sure that is the problem. Let me swap drives back and I will send you the file from the hacked dms.
Here it is. Thanks.
Okay, re-generated files - stick 'em back on and try 'em out.
I'm out now, will see how you got on later.
I tried something different, and it seems to work. In the original drive, there was a directory called Plugins and inside of that a directory for AAC in Phtsys. In the hacked drive, this directory wasn't there. Lastnight I had ran the update via PMM for the firmware, which added this directory, but the files inside that directory had a date of 5/17/07 or something close to that... I compared that directory to the original drive, and the original files were from 2005. I swapped out those files. I hadn't put in your new exec.ini files at all. I plugged it into the phatbox and away we went. AAC files are playing fine. YIPPEE.
I am leaving now for a roadtrip, with my 70 gigs of CD collection I have aquired over the years.
VorTechS, I really owe you big time. Let me know if you need any files or anything that will help you improve your process. Also, if you send me a personal message with a place I can send in a donation, or if I should make it to this site, etc., please let me know. I am happy to contribute to the greater good!
Dippdy
Quote from: VorTechS on September 14, 2007, 08:11:56 AM
Steps 4 and 5 are definately the only steps you should need to do to install the replacement VIOT plugin. You might need to make a modification to Profiles.INI on PHTDATA to tell the phatbox you are using VIOT though.
There's a section called [profiles] and an entry in there which enables VIOT.
Make sure this setting is as shown below
[profiles]
enable_voice_prompts=1
See if that gets things going. Your problem might be related to the AAC problem too as the plugin authentication might be failing if I've ballsed up. Try the profiles thing first and let me know how you get on.
Hi VorTechS,
As usual, I appreciate you help and response. I tried modiefying the [profiles] enable_voice_prompts but it actually was already done.
My log is as follows:
[Default]
num_discs=88
startup_sound=
pattern=$TITLE$ - $ARTIST$
[profiles]
active_profile=Default
enable_special_discs=1
enable_voice_prompts=1
num_discs=88
[product]
product_name=PhatNoise Media Manager
product_version=3, 9, 2, 0
Also I noticed every time I erase the PHATSYS\Plugins\plugins.dat, plug it in my hacked PhatBox, then return it to my usb dock, the plugins.dat file mysteriously appears again. I don't know why it's doing that. Could the problem lie there? Thanks a lot for you effort again.
Okay, have you (like some others) performed a firmware update using PhatNoise Media Manager?
If so, it's possible that the aadec util has been overwritten (PhtSys\aadec) in which case you'll need to put the hacked ones back in.
You can find these files in:
<Path to Hack tools>\DMS_Utils\HackFiles\aadec
<Path to Hack tools>\DMS_Utils\HackFiles\aadec.sig
If you haven't upgraded the firmware I'll have to hand over to judb and sbingner as I don't know what could be causing this problem, as I don't know much about how the plugins work.
Yes you would still need the plugin to be installed... I don't think you should mess with the "needaac" line tho
Oh, and the only reason to remove plugins.dat is to make it re-scan your plugins and install any that were missing... when it does that, it recreates plugins.dat -- as it should.
I did a search to see if someone else had given this info yet, but nothing came up, so here it is.
For Vista users...To run the backup part of the Hack Tool, you will have to run it manually, as suggested in the program documentation, BUT you will need to start the DOS prompt with Administrator priviledges.
You do this by RIGHT clicking on the "Command Prompt" icon and when the menu pops up, you will select "Run as administrator". When you are in administrator mode for DOS, the title bar for the window will say "Administrator: Command Prompt".
It looks like there may be two root causes here. One being that it doesn't seem that the Hack Tool is trying to run the dd.exe from the correct folder when it opens a DOS prompt, and the second is that once it is run from the correct location, the DOS prompt needs to be in elevated Administrator mode. I don't know if the knowledge of this will help the program's author with making his program backup properly or not, but this at least helps explain to him the root cause of the failure with Vista, and a workaround.
So...Basically...
- I tried the v2.3 of the DMS Hack Tools. It found my DMS and then tried to back it up and failed, just like the documention told me it would for Vista.
- I then went and looked at the log file and found the part where the backup failed. The author was even nice enough to put a line in the log file showing me what text to copy to run at the DOS prompt.
- I opened the DOS prompt in Admin mode.
- I changed to the directory where the Hack Tools are installed, namely, where the dd.exe program is located. In my case this was here:
C:\Program Files\PhatHack\PhatHack DMS Tools\DMS_Utils
- From that location, I then pasted the text from the log file into the DOS prompt and pressed the Enter key. It ran with no problem.
- Here is the text that I pulled from the log file and pasted into the DOS window, in my particular case:
dd if=\\.\PhysicalDrive8 bs=512 count=2048 of="C:\Users\Butch\Documents\PhatHack Media Manager\DMS Backups\DMS Boot\DMS_Backup_19_Sep_2007_(11_45_01)\DMS_Backup_For_DeviceSerial_2265140E.bin"
Hope this helps someone...
Later!
Butch
Butch,
Thanks for the additional information I'll amend the documentation. I am aware that the problem is due to the process requiring elevated rights, but have yet to find a way to do this programmatically - and suspect it will be extremely hard to do due.
Having said that, I've had reports that the formatting executable runs fine when creating a new DMS from Vista and that process is launched in exactly the same way so it's certainly a mystery why the DD executable needs something different.
I will continue to look for a solution on shelling with elevated permissions, so one day hopefully this workaround won't be needed.
I have issue with new DMS creating. When I'm pressing button "Create New DMS" (right one) I get next message:
"Unhandled exception has occurred..."
Details:
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.modCommon.GetDMSDiskID(String DriveLetter)
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.312 (rtmLHS.050727-3100)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
StandAloneDMSHackWizard
Assembly Version: 2.3.0.0
Win32 Version: 0.0.2.3
CodeBase: file:///C:/Program%20Files/PhatHack%20DMS%20Tools/StandAloneDMSHackWizard.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.312 (rtmLHS.050727-3100)
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.312 (rtmLHS.050727-3100)
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.312 (rtmLHS.050727-3100)
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.312 (rtmLHS.050727-3100)
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.312 (rtmLHS.050727-3100)
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.312 (rtmLHS.050727-3100)
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.312 (rtmLHS.050727-3100)
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%20DMS%20Tools/PhatUnzip.DLL
----------------------------------------
DMS
Assembly Version: 1.0.0.1
Win32 Version: 1.0.0.1
CodeBase: file:///C:/Program%20Files/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%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%20DMS%20Tools/Interop.WbemScripting.DLL
----------------------------------------
CustomMarshalers
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
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.
P.S.
Windows Vista
HDD Segate ST98823A ATA6 80GB
Phatbox was hacked without any issues.
Antivirus was off.
Any other USB storage devices was not connected.
Interesting!
After you start the application, and click on 'Create New DMS' (the 1st one on the left side), is your DMS listed in the 'Select destination DMS' dropdown?
If so what is listed there?
It would also be useful if you could supply me with a copy of Startup_Sequence.txt and PhatHack_NewDMS.txt which are two log files written by the software in 'Documents\PhatHack Media Manager\Logs' under your Windows Vista user profile.
Quote from: VorTechS on September 22, 2007, 08:23:43 AM
Interesting!
After you start the application, and click on 'Create New DMS' (the 1st one on the left side), is your DMS listed in the 'Select destination DMS' dropdown?
If so what is listed there?
It would also be useful if you could supply me with a copy of Startup_Sequence.txt and PhatHack_NewDMS.txt which are two log files written by the software in 'Documents\PhatHack Media Manager\Logs' under your Windows Vista user profile.
Yes, DMS is in the "Select the destination device" as "USB-HS ST98823A USB Device"
I have only Startup_Sequence.txt in the logs directory.
Thanks. I think most of the recent changes I've made to the tools were done with a formatted and partitioned DMS. I haven't tested a clean drive for a long time - so I guess something is trying to evaluate DMS drive letters when there aren't any.
I'll zap my test DMS completely and hopefully I should be able to repro this without a problem. If not, I'll get back in touch with you, otherwise download v2.4 of the tools when it becomes available.
BTW on Windows XP I've got the same issue, but I was be able to format DMS with newdms.bat from dmsutils-1.2.1.
After that I tried to create new DMS using "Windows DMS Hack Tools v2.3" with partitioned and formatted DMS and result was the same :(
Quote from: grymster on September 22, 2007, 05:08:05 AM
I have issue with new DMS creating. When I'm pressing button "Create New DMS" (right one) I get next message:
"Unhandled exception has occurred..."
Details:
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.modCommon.GetDMSDiskID(String DriveLetter)
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.312 (rtmLHS.050727-3100)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
StandAloneDMSHackWizard
Assembly Version: 2.3.0.0
Win32 Version: 0.0.2.3
CodeBase: file:///C:/Program%20Files/PhatHack%20DMS%20Tools/StandAloneDMSHackWizard.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.312 (rtmLHS.050727-3100)
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.312 (rtmLHS.050727-3100)
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.312 (rtmLHS.050727-3100)
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.312 (rtmLHS.050727-3100)
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.312 (rtmLHS.050727-3100)
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.312 (rtmLHS.050727-3100)
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.312 (rtmLHS.050727-3100)
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%20DMS%20Tools/PhatUnzip.DLL
----------------------------------------
DMS
Assembly Version: 1.0.0.1
Win32 Version: 1.0.0.1
CodeBase: file:///C:/Program%20Files/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%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%20DMS%20Tools/Interop.WbemScripting.DLL
----------------------------------------
CustomMarshalers
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
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.
P.S.
Windows Vista
HDD Segate ST98823A ATA6 80GB
Phatbox was hacked without any issues.
Antivirus was off.
Any other USB storage devices was not connected.
I'm having the same problem with a new Samsung 80GB HDD. Will be watching this thread for any tips.
Quote from: bdjones72 on September 24, 2007, 01:57:34 AM
I'm having the same problem with a new Samsung 80GB HDD. Will be watching this thread for any tips.
Can you please send me a copy of your startup_sequence.txt file so I can confirm what I think the problem is here. I've tried to repro this without success - and I think it has something to do with (hidden) partition data returned from WMI. Or it may be partition data from deleted partitions, which it is I'm not sure.
I'm sure I've identified the line of code, just need to work out what to do with it, I may well send you both a link to a test version to see how far you get with it. :)
...and by the same token, the line of code calling that code doesn't appear to be returning the right results either because of a sub-string issue which I've resolved. Please check your private messages for a test version of the tools.
2 VorTechS
Hi!
I tried test version with a clean drive it crashed right after firmware unpacking :(
Exception details:
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.modCommon.GetPhtSysDrive(String DiskID)
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.312 (rtmLHS.050727-3100)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
StandAloneDMSHackWizard
Assembly Version: 2.3.0.0
Win32 Version: 0.0.2.3
CodeBase: file:///C:/Program%20Files/PhatHack/PhatHack%20DMS%20Tools/StandAloneDMSHackWizard.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.312 (rtmLHS.050727-3100)
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.312 (rtmLHS.050727-3100)
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.312 (rtmLHS.050727-3100)
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.312 (rtmLHS.050727-3100)
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.312 (rtmLHS.050727-3100)
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.312 (rtmLHS.050727-3100)
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.312 (rtmLHS.050727-3100)
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.312 (rtmLHS.050727-3100)
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.833 (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.312
Win32 Version: 8.00.50727.312
CodeBase: file:///C:/Windows/WinSxS/x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.312_none_10b2ee7b9bffc2c7/msvcm80.dll
----------------------------------------
ICSharpCode.SharpZipLib
Assembly Version: 0.84.0.0
Win32 Version: 0.84.0.0
CodeBase: file:///C:/Program%20Files/PhatHack/PhatHack%20DMS%20Tools/ICSharpCode.SharpZipLib.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.
Quote from: VorTechS on September 24, 2007, 08:04:48 AM
Can you please send me a copy of your startup_sequence.txt file so I can confirm what I think the problem is here.
File attached.
Quote from: grymster on September 25, 2007, 12:31:02 AM
Exception details:
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.modCommon.GetPhtSysDrive(String DiskID)
Yup, it's pretty much the same issue - in a different place, but from what I can see this should be the last one.
The good news is the DMS log is looking nice and clean with the results I expected in it - so applying the same fix in the routine that's fallen over this time should be the end of the problems - and you should hopefully go all the way this time!
Check your messages for confirmation of an update to the tools.
I think mine did the same also. The tools ran thru the partitioning PHTSYS and PHTDTY parts but then got hung up on the extracting files part. However if I put the DMS into the cradle and open the Phatnoise Music Manager it recognizes the DMS however it wants to initiate it so I'm thinking that the Kenwood v13.01 firmware didn't take.
Quote
Check your messages for confirmation of an update to the tools.
;)